ekumamatthew/the_synod

★ 0Forks 0JavaScriptGitHub ↗Compare

README

The Synod

The Synod is a decentralized oracle network for Soroban focused on resolving high-ambiguity real-world questions and publishing normalized, auditable verdicts on-chain.

The project is licensed under the Apache License 2.0.

Vision

Soroban applications need a trustworthy way to consume off-chain reality when the answer cannot be reduced to a simple price feed or single API response. The Synod addresses that gap by combining:

  • evidence retrieval from authoritative sources
  • multi-agent evaluation and semantic consensus
  • compact on-chain settlement for Soroban consumers

Product Direction

The project is being shaped around a few core principles:

  • keep heavy reasoning and retrieval off-chain
  • keep Soroban writes compact and deterministic
  • treat evidence and auditability as first-class outputs
  • phase in stronger trust minimization over time

The initial product direction is aimed at use cases such as:

  • prediction market resolution
  • public-notice and event-based triggers
  • regulatory or compliance event verification

Planned System Areas

The repository will evolve around these major areas:

  • Soroban contracts for request intake, publication, and consumer callbacks
  • an off-chain listener and relayer for event ingestion and transaction submission
  • worker and evaluator agents for retrieval, scoring, and consensus
  • evidence storage, explorer APIs, and operator tooling

Repository Layout

The repository is organized around a few top-level work areas:

  • contracts/ for Soroban smart contract crates
  • services/ for off-chain services such as bridge and API packages
  • sdk/ for client-facing SDK packages
  • examples/ for end-to-end usage examples
  • docs/ for tracked project documentation and maintainer guidance

Each area contains a short README so contributors can orient themselves quickly.

Current Status

This repository is currently in the planning stage. The next major step is to convert the product requirements into a technical design specification and then scaffold the first implementation slices.

Community

Project collaboration standards and contributor guidance live in:

Maintainer-facing workflow guidance lives under:

Development

The repository exposes a small root command surface through npm scripts:

  • npm run format
  • npm run format:check
  • npm run lint
  • npm run typecheck
  • npm test

If you want optional local Git hooks, run:

npm run hooks:install

Configuration guidance and sample environment variables live in:

Contributors

ekumamatthew

Issues