A modular, audit-ready security infrastructure for the Stellar network. Vero replaces single-maintainer PR review with a decentralized Guardian consensus model, backed by on-chain votes — no single reviewer decides what merges.
- A developer opens a PR tagged
wave-contributionon a Vero repo. - vero-relayer-service catches the merge event and registers it as a task on Stellar.
- vero-core-contracts records Guardian votes on-chain and tallies consensus.
- Guardians review and cast their votes through vero-guardian-dashboard, signed with a Freighter wallet.
- vero-audit-guard continuously monitors the whole pipeline for anomalies, static-analysis findings, and policy violations.
- vero-core-engine ties state logic, treasury governance, and relayer communication together as the protocol's control plane.
- 🧠 Brain —
vero-core-contracts&vero-core-engine: the decentralized logic layer and core state control plane, built on Soroban. - 🛡️ Shield —
vero-audit-guard: automated security monitoring, continuous static analysis, and anomaly detection. - 👁️ Eyes —
vero-guardian-dashboard: the command center for human validators, enabling on-chain audits and task management. - 🌉 Bridge —
vero-relayer-service: the automated event-to-task pipeline connecting GitHub activity to Stellar transactions.
Who this is for, what problem it solves, and how we measure whether it is working:
- Initial Wedge and ICP — the first user and the problem they have
- North-Star Metric — what success means and how it is measured
| Repo | What it does | Stack |
|---|---|---|
| vero-core-contracts | On-chain Guardian consensus — tracks PR IDs and requires a vote threshold before marking work verified | Rust / Soroban |
| vero-core-engine | Integration layer and control plane — state logic, multi-sig treasury governance, relayer comms | TypeScript |
| vero-audit-guard | Security monitoring — static analysis, anomaly detection, immutable audit trail | TypeScript |
| vero-guardian-dashboard | Guardian portal — wallet-connected review and voting UI | TypeScript / Next.js |
| vero-relayer-service | GitHub ↔ Stellar bridge — listens for merged PRs, registers on-chain tasks | JavaScript / Node.js |
| vero-sdk | Shared Stellar client library — typed contract client, nonce management, RPC failover | TypeScript |
Contributions are welcome across every repository in this organisation.
- Browse the open issues in any repo above and find one you can do well.
- Comment on it to say you're picking it up, and wait for a maintainer to assign it to you — this keeps two people from doing the same work.
- Branch from
mainusing a descriptive name, e.g.fix/issue-42-short-description. - Open a pull request whose description includes
Closes #<issue-number>, so the issue closes automatically when the PR merges. - Make sure CI is green. Every repo runs tests, linting, and a security audit on each pull request.
A few things that make review faster:
- Keep each pull request to a single issue. Unrelated changes are harder to review and slower to merge.
- Include tests for behaviour you add or change.
- If CI fails, push a fix to the same branch — no need to open a new pull request.
- If your branch falls behind
mainand conflicts, rebase onto the latestmain.
Each repository has its own CONTRIBUTING.md, issue templates, and pull request
template — start there for setup instructions specific to that codebase.
New to the project? Issues labelled good first issue are a reasonable place to
begin.
MIT, per repository. See each repo's LICENSE file.