Working on the contracts

The contracts live in contracts/: clearing/ (TobinClearingV1) and token/ (TobinTestToken, a capped-supply test token). They are experimental validation code, not production code, and not the broader protocol's v0.2.

Build and testCopy Anchor Link

cd contracts
cargo test --locked --workspace                                  # native contract tests
cargo build --locked -p tobin-clearing-v1 --example bridge       # the development bridge
stellar contract build                                           # Wasm (needs the Stellar CLI)

Rust is pinned at 1.96.0 with the wasm32v1-none target; Soroban SDK is 29.0.0.

RulesCopy Anchor Link

• Do not change the contracts, the deployment manifest or accepted evidence as part of unrelated work.
• Use checked arithmetic. Never floating point.
• Preserve the validation rules in Netting and contract validation.
• Ceilings (4 participants, 16 obligations, 16 instructions) are compile-time constants and provisional engineering targets, not verified limits.
• Wasm hashes are recorded under ci/; changing a contract changes them and is a release-controlled event.
• Any Testnet action (deployment, key creation, minting, RPC calls beyond read-only) needs the owner's explicit authorisation. Mainnet is out of scope.

ReferenceCopy Anchor Link

See the contracts reference for the function list, and the canonical ABI and authorization reference for the authorization matrix.