Known limitations
Status: Built, runs on simulatorStatus: Built, runs on simulatorStatus: Provisional
The checked Merces baseline is local software with mock providers and unresolved launch dependencies.
| Area | Current limit |
|---|---|
| Network deployment | No verified devnet or testnet handoff manifest is available. |
| Identity and signing | The local flows use mock providers; final providers and contract text remain undecided. |
| Payment proof | The trusted setup is for development and must be replaced before production use. |
| Privacy | Payment amounts are public onchain; the verifier briefly sees the attested income figure in memory. |
| Backend parity | Partial vector replay and model differences remain in the pinned integration report. |
| Curve accounting | Economic policy and residual-accounting assumptions remain subject to decisions. |
| Data deletion | Retention time limits are unset and deletion is not automated. |
These limits are separate. Replacing a provider would not finish legal review. Passing a local scenario would not supply a deployment manifest. Publishing documentation would not change either fact.
The curve raise has provisional policy choices. Q-034 also records an assumption about residual pool balances at buy-back; Kunal and counsel must decide its treatment. This page does not disclose internal finding details.
A backer should distinguish a public payment from the underlying income evidence. An issuer should distinguish an illustrative fixture from offered terms. The privacy map makes those visibility boundaries explicit.
What can go wrong
A working local example can hide a missing provider, deployment or legal dependency. Do not send funds to an address inferred from code, a rehearsal or an example.