Reference / Roadmap
Expand coverage without weakening evidence.
The roadmap has two parallel goals: add more Stellar protocols and expand the monitoring surface around each dependency. The local archive and shared indexer core come first because every later decoder, signal source, and alert needs a reproducible history and a safe live handoff.
01 / Delivery sequence
Technical milestones.
01 Implemented
Archive-backed evidence core
The current POC proves that a local Stellar archive can produce exact, queryable dependency and version history with bounded resources.
- Local Galexie mirror and resumable compact Rust indexer
- Exact wallet-to-contract reverse index and source-backed protocol roots
- Contract executable history, Wasm observations, and lifecycle events
- Wallet activity projection, read-only API, and real-data demo
- Bounded YieldBlox historical finding and controller watcher
02 In progress
Shared archive and live indexing core
Extract the optimized historical logic behind a versioned input and module boundary, then add a restart-safe recent-ledger tail.
- RPC getLedgers acquisition with explicit oldest and newest source range
- One normalized ledger input for archive, RPC, and later Captive Core
- Atomic fact, finding, and checkpoint commit
- Automatic local-archive gap fill before live resumes
- Archive/live parity tests over overlapping ledgers
03 Planned
Backfillable module framework
Make new protocol parsers and derived indexes deployable without losing earlier history or blocking the active read generation.
- Versioned module and output-schema contract
- Offline replay into isolated staging generations
- Determinism, idempotency, coverage, and resource promotion gates
- Live catch-up buffer and atomic generation switch
- Historical findings retained with notification delivery disabled
04 Planned
Broader protocol attribution
Move from verified roots toward complete, time-aware protocol surfaces while preserving every unknown contract as an address-backed record.
- Soroswap pair and DeFindex vault factory-child discovery
- Aquarius and Phoenix pool expansion
- Blend deployment and Reflector runtime-root coverage
- Time-valid roles, controller history, and attribution conflicts
- Source-backed Templar, Sushi, and additional Stellar ecosystem roots
05 Planned
Protocol-specific security intelligence
Add semantic decoders where generic contract facts cannot explain risk or intent.
- Blend, Reflector, and Classic SDEX decoders for generalized YieldBlox-style detection
- Aquarius upgrade-delay and emergency-control monitoring
- DeFindex vault roles, Phoenix controls, FxDAO roles, and Soroswap adapters
- Unknown-Wasm coverage findings instead of stale decoding
- Deterministic evidence separated from AI-assisted impact explanation
06 Planned
Wider monitoring surface
Correlate on-chain changes with the technical places developers otherwise monitor manually.
- Soroban Governor proposals and execution payloads
- Admin, guardian, treasury, oracle, signer, and threshold histories
- GitHub commits, releases, deployment manifests, and security advisories
- Stellar SDK, package registry, protocol, Core, and RPC releases
- Project-specific pending multisig feeds where a verifiable source exists
07 Planned
Reliable delivery and team workflows
Turn committed findings into an operational alert product only after detection and recovery guarantees are observable.
- Durable idempotent alert outbox and Telegram delivery
- Webhooks, email, per-user history, and delivery receipts
- Application dependency subscriptions and impact routing
- Team-reviewed enterprise alerts with evidence and audit trail
- Paid entitlements and Stellar USDC settlement after delivery is proven
02 / Protocol expansion
Prioritize by dependency risk and verifiable surface.
| Wave | Coverage | Reason |
|---|---|---|
| First | Blend + Reflector + Classic SDEX | Cross-protocol lending and oracle dependency with a confirmed incident fixture. |
| Next | Soroswap + DeFindex | Factory events make child discovery testable and unlock broader wallet attribution. |
| Then | Aquarius + Phoenix + FxDAO | Known administration and runtime surfaces support high-signal control monitoring. |
| Close gaps | Templar, Sushi, and new ecosystem projects | Attribute production roots before claiming ecosystem-wide DeFi coverage. |
03 / Signal expansion
Monitor the dependency, not only its contract address.
What executes
Deployments, executable changes, calls, events, state, restorations, failures, and code hashes.
Who can change it
Admins, guardians, treasuries, governors, signers, thresholds, controllers, and executed payloads.
What applications consume
Repositories, releases, SDKs, packages, deployment manifests, interfaces, and breaking changes.
What changes the risk
Governance proposals, security advisories, Stellar protocol releases, Core/RPC changes, and incidents.
04 / Acceptance standard
Coverage claims need proof.
- every monitored protocol publishes its known contracts, roles, source URLs, and observed-at boundary;
- factory-backed protocols report discovered children and unexplained conflicts;
- every versioned decoder lists recognized Wasm hashes and emits unknown-code coverage findings;
- every live module has passed deterministic archive replay and source-parity tests;
- every alert retains coordinates, primary evidence, module version, confidence, and coverage limits;
- every delivery channel exposes retry and receipt state independently of detection;
- status pages distinguish delayed, unavailable, partial, and healthy sources.