Salvation

Salvation is a decentralized platform that tokenizes African infrastructure projects as yield-bearing bonds, combining RWA tokenization standards with prediction markets to create financial accountability for development funding. Built on Mantle Network, the protocol enables investors to earn 8-15% APY from operational infrastructure like water wells, solar microgrids, and schools, while prediction markets provide price discovery for project risk and enable hedging strategies.

The Problem with Traditional Aid:

Africa faces a $100B+ annual infrastructure gap. Traditional development funding suffers from zero accountability—donors give money, NGOs self-report progress, and projects fail with no consequences. There's no financial return for funders, no risk pricing for projects, and verification is theater. Salvation transforms this model: donations become investments, hope becomes yield, and trust becomes prediction markets.

Bond Tokenization (ERC-3643-Lite):

Each infrastructure project is tokenized using a pragmatic implementation of the ERC-3643 RWA standard. The BondFactory contract mints project-specific bond tokens representing pro-rata yield rights from operational revenue. Key compliance features include:

- IdentityRegistry.sol: KYC allowlist tracking verified investors

- ComplianceModule.sol: Transfer restrictions with canTransfer() hooks on every transfer

- Freeze capabilities: Per-address and global freeze for regulatory compliance

- Forced transfer: Admin function for legal asset recovery

Bond tokens are fully transferable on secondary markets among KYC-verified addresses, creating liquidity for investors who need to exit positions before project maturity.

Yield Distribution (ERC-4626):

Revenue flows from operational projects (water usage fees, solar energy sales, tuition payments) are converted to stablecoins and deposited into ERC-4626 compliant YieldVault contracts. This standard ensures DeFi composability—Salvation yield vaults can integrate with aggregators, lending protocols, and other DeFi infrastructure. Bond holders claim yield pro-rata to their token holdings, with options for manual claiming or auto-compounding.

Prediction Markets for Accountability:

Every project has associated binary prediction markets created by the MarketFactory contract:

- Completion Markets: "Will this project be operational by [date]?"

- Performance Markets: "Will revenue exceed $X in Y months?"

- Milestone Markets: "Will milestone N complete by [date]?"

Markets use Logarithmic Market Scoring Rule (LMSR) pricing in the BinaryMarket contract. This creates several accountability mechanisms:

1. Risk pricing: Market prices reveal collective assessment of project success probability

2. Hedging: Bond holders can buy NO tokens to insure against project failure

3. Information revelation: Speculators with local knowledge profit by trading on information

4. Early warnings: Falling YES prices signal problems before official reports

Oracle & Verification Layer:

The OracleAggregator contract aggregates verification from multiple sources before resolving prediction markets:

- Satellite imagery: Sentinel Hub API verifies construction progress and infrastructure existence

- IoT sensors: Water flow meters, solar generation monitors provide operational data

- AI agents: LangChain-powered agents analyze evidence packages and recommend milestone completion

- Local verifiers: Staked human agents provide on-ground verification

The MilestoneTracker contract maintains a state machine for each project, advancing through milestones only after oracle consensus confirms completion.

AI Verification Agents:

The agents/ package implements autonomous verification using LangChain and LangGraph:

- Proposal Analyzer: Evaluates new project submissions for feasibility

- Milestone Verifier: Analyzes evidence (photos, sensor data, satellite images) against milestone criteria

- Re-Analyzer: Re-evaluates projects when new information emerges

Agents communicate via A2A SDK protocol, enabling agent-to-agent coordination for complex verification tasks.

Insurance Pool:

5% of all bond purchases flow to the InsurancePool contract. If a project fails (verified by oracle resolution), bond holders can claim partial refunds from the pool. This creates systemic risk buffering and aligns protocol incentives with project success.

Smart Contract Architecture:

```

contracts/

├── core/

│ ├── ProjectRegistry.sol # Project metadata & state machine

│ ├── BondFactory.sol # Mints bond tokens per project

│ ├── BondToken.sol # ERC-3643-Lite yield-bearing token

│ └── YieldVault.sol # ERC-4626 revenue distribution

├── compliance/

│ ├── IdentityRegistry.sol # KYC allowlist

│ └── ComplianceModule.sol # Transfer restrictions

├── prediction/

│ ├── MarketFactory.sol # Creates markets per project

│ ├── BinaryMarket.sol # LMSR YES/NO trading

│ └── MarketResolver.sol # Oracle-triggered resolution

├── oracle/

│ └── OracleAggregator.sol # Multi-source verification

└── insurance/

└── InsurancePool.sol # Failed project compensation

```

Frontend & User Experience:

The Next.js 15 frontend provides three primary user flows:

1. Investor Flow: Browse projects, view prediction market odds, purchase bonds, track yield, claim returns

2. Speculator Flow: Trade prediction markets based on research, profit from information edge

3. Sponsor Flow: Submit projects with milestones, receive funding at verification checkpoints

Privy embedded wallets enable email-based onboarding without MetaMask, critical for reaching mainstream impact investors unfamiliar with Web3.

Subgraph Indexing:

The Graph subgraph indexes all on-chain events for efficient querying—projects, bonds, trades, milestones, yields. Deployed via Goldsky for Mantle Sepolia compatibility.