Practical overview
When it fits
Consider Scribe when an EVM smart-contract project needs an oracle component based on aggregated Schnorr signatures and its developers can assess the integration and licensing requirements.
Who it is for
- EVM developers evaluating an oracle component for smart-contract data feeds.
- Contributors working with Solidity and the Foundry toolchain.
Documented uses
- Supply oracle data to EVM smart contracts.
- Install the Scribe module in a Foundry project.
- Set up the repository's documented development and test environment.
Requirements & limits
- Scribe is a protocol component and repository, not a documented external API service.
- The supplied repository information does not identify deployment networks.
- The primary license is BUSL-1.1; specified files may also be licensed under MIT.
- The complete differential fuzz test suite requires an additional
schnorrbinary inbin/.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Set up the Scribe development environment
Prepare a local checkout for the documented Foundry and vector-based test workflow.
Before you start
- Foundry, with installation instructions linked from the README.
- Yarn for dependencies used by vector-based tests.
Steps
Clone the Scribe repository and change into its directory.
Run
forge install.Run
yarn installto install dependencies for vector-based tests.
Expected outcome
The README's initial development setup steps are complete.
Guide limitations
- The complete test suite, including differential fuzz tests, also requires the oracle-suite's musig
schnorrbinary in thebin/directory. - These setup steps do not describe deployment.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 17 October 2026
- Original website title
- chronicleprotocol/scribe · Official homepage title · retained in its source language

