PROP99

1. Problem

• Real-world assets (real estate, invoices, cash-flow assets) lack a trustless and programmable on-chain representation, making them difficult to integrate into DeFi.

• Asset verification and valuation depend heavily on centralized institutions, manual audits, and opaque pricing mechanisms.

• Existing RWA tokenization solutions fail to provide verifiable evidence trails for asset authenticity and valuation logic.

• Layer-2 based RWA systems often do not clearly inherit Ethereum security guarantees, reducing cross-ecosystem trust.

• Compliance-aware asset lifecycle management (verification → tokenization → updates) is fragmented and not protocol-native.

2. Solution (In Short)

• A rollup-native RWA protocol deployed on Mantle L2 for low-cost, high-throughput execution.

• Off-chain AI oracle networks independently verify asset documents, imagery, and market data.

• Oracle consensus results are finalized on-chain and anchored to Ethereum via Mantle’s rollup messaging layer.

• Assets are tokenized through a factory-based smart contract architecture, ensuring scalability and modularity.

• The protocol exposes an on-chain valuation oracle enabling RealFi and DeFi composability.

FLOW CHART

3. How It Works (Detailed Flow)

• A user initiates the process by submitting asset metadata, ownership details, and cryptographic hashes of supporting documents to the OracleRouter contract on Mantle L2. This transaction creates a unique verification request on-chain, recording the requester, asset type, location identifiers, and evidence references in an immutable manner.

• Once the request is emitted, off-chain AI oracle nodes continuously monitoring Mantle L2 detect the verification event. Each oracle independently retrieves the referenced documents and evidence, performs document integrity checks, analyzes satellite imagery and market data, and generates a signed valuation, confidence score, and risk assessment without trusting any single data source.

• The oracle nodes submit their signed responses back to Mantle L2, where the ConsensusEngine contract validates oracle authenticity, enforces quorum rules, checks confidence thresholds, and computes a weighted aggregate valuation. This ensures that no single oracle can influence the final result and that valuations are statistically consistent.

• After consensus is reached, a cryptographic commitment representing the verified asset state is anchored to Ethereum using Mantle’s L2-to-L1 rollup messaging system. This step binds the verification outcome to Ethereum’s security model, making the existence and timing of the verification globally provable beyond Mantle itself.

• Finally, the RWATokenFactory deploys an asset-specific token contract, registers the asset and its valuation in the AssetRegistry, and publishes the price through an on-chain valuation oracle. The resulting tokenized asset can now participate in RealFi and DeFi applications while remaining auditable, verifiable, and protocol-controlled throughout its lifecycle.

4. Key Features

• Rollup-native architecture leveraging Mantle L2 for execution and Ethereum for security anchoring.

• Multi-oracle AI verification to reduce single-source trust and valuation manipulation.

• Factory-deployed RWA tokens, enabling one-asset-one-token isolation and clear ownership semantics.

• On-chain asset registry and valuation oracle supporting continuous price updates and auditability.

• Protocol-level compliance controls, ensuring secure and regulated asset transfers without relying on centralized custody.

5. CONTRACTS DEPLOYED/USED

ORACLE_ROUTER_ADDRESS=0xf4d1656069B739d652CdFC8Cc6ddE2Cd0b2d9A9C

CONSENSUS_ENGINE_ADDRESS=0xd964828145Eb879fD0204A85774391b3dD192e1A

VERIFICATION_ANCHOR_ADDRESS=0xeBE3F5A0411a78B61626c90258a3d46380a11a20

ASSET_REGISTRY_ADDRESS=0x94768a15Cd37e07eEcc02eDe47D134A26C1ecB3f

RWA_TOKEN_FACTORY_ADDRESS=0x68283AAa8899A4aA299141ca6f04dF8e5802509f

COMPLIANCE_MODULE_ADDRESS=0x0bfB6f131A99D5aaA3071618FFBD5bb3ea87C619

L2CrossDomainMessenger = 0x4200000000000000000000000000000000000007

L2_TO_L1_MESSAGE_PASSER= 0x4200000000000000000000000000000000000016

L1Block = 0x4200000000000000000000000000000000000015

5. REFERENCES

GitHub : https://github.com/austinjeremiah/Prop99
Documentation : https://github.com/austinjeremiah/Prop99/blob/main/Readme.md
Pitch Deck : https://www.canva.com/design/DAG-agOBeas/AYV_tDpaOLuXPVbcfOHQ1Q/edit?utm_content=DAG-agOBeas&utm_campaign=designshare&utm_medium=link2&utm_source=sharebutton