Real-world operations
Status: Not decided
Using Merces depends on people and policies outside the chain as well as the mechanism's arithmetic.
The signed agreement, participant eligibility, evidence review, support and retention policy need their own decisions. A transaction does not supply a missing contract or an approved country list. The local mock flows demonstrate software paths; they do not resolve those questions.
Available explanations
- Accountants and attestor pay separates registration from professional eligibility and payment arrangements.
- Support and incident reporting states the current contact gap and how to preserve useful, non-sensitive information.
- Data retention and deletion distinguishes intended retention from implemented deletion.
Contract enforcement, what follows stopped payments, country eligibility, taxes and formal dispute handling remain unpublished review drafts. The public open questions identifies their owners.
An issuer's personal circumstances are not a public status explanation. A backer sees the mechanism's visible records within the stated access rules. Anyone handling an incident must keep that distinction in mind.
What can go wrong
An unresolved off-chain process can prevent someone completing a task even when a contract function exists. These docs do not make an unchosen provider or legal procedure available.