What contributing will look like

Contribution transaction planning

A planning map only. It shows where things stand and what a future contribution flow would require. No transaction is built, signed, or submitted; no ADA is requested; no funds move.

Transaction design proposal prepared. An architecture-only design for a future contribution flow exists (lifecycle, strategy options, risk register, and gate sequence). Design only — no transaction build, no signTx, no payment address, and no funds. Nothing here is enabled.

Funding address strategy proposal prepared — no payment address is active. An architecture-only proposal covers address options, custody policy, chain observation, and emergency-stop requirements. No payment address, no QR code, and no funds. Nothing here is enabled.

Pre-funding implementation architecture prepared. Funding address implementation, chain observer design, contribution candidate lifecycle, and emergency-stop designs exist as proposals. Still no payment address, still no QR, still no funding activation. Design only — nothing here is enabled.

Testnet/preprod funding rehearsal architecture prepared. A testnet/preprod funding implementation proposal, a fail-closed activation design, and a rehearsal runbook exist. Still no payment address, still no QR, still no funding activation. Design only — any future rehearsal would be testnet/preprod-only and clearly labelled.

Disabled testnet funding config exists — funding still not active. A disabled testnet/preprod config (masked address only) is prepared. Still no payment address shown, still no QR, still no funding activation.

Compliance/KYC architecture planned — no identity documents are collected. A privacy-first KYC/KYB readiness design exists for possible future funding. No personal data, no documents, no provider integration, and no funding are enabled.

Observer dry-run readiness — no chain payments are observed or recorded. The ContributionObservation table exists for candidate data (public chain candidate data only — never a Contribution, testnet and redacted). The observer is not live: no external API call, no chain query, no address/UTxO scan. Any candidate row is recorded only through one guarded testnet helper. No payment address, no QR, no funding activation. This campaign is still not accepting support.

Observer candidate dry-run prepared — simulated only, no chain query, no DB writes. An admin readiness view shows deterministic in-memory sample candidates (redacted). Nothing is observed or stored; no payment address, no QR, no funding activation.

Observer provider readiness prepared — no provider API calls are made. Provider environment presence may be checked (values never shown); no Koios/Blockfrost/Ogmios call, no live observer, no DB writes, no funding activation.