Guides for issuers

Status: Built, runs on simulatorStatus: Coming soon

These guides help an issuer understand a series before committing its terms and prepare for the reports that follow a raise.

Merces describes a capped share of future covered income. A backer funds units under that agreement. The product brief excludes giving backers a say in your life choices. That boundary is a product requirement; it does not make every implementation or legal question settled.

Start with the decision

Read Is Merces right for me? to separate a possible fit from a readiness decision. Then read What backers can see, especially the distinction between an income figure and a public payment. Sharing fewer fields with the application does not erase the public chain record.

The task guides cover applying, choosing terms, signing, reporting, drawing scheduled funds and ending new issuance. They remain unpublished while the backend handoff and executable workflows are incomplete. Their existence does not establish that an application is open or that a transaction can be submitted on a deployed network.

Keep three records distinct

The agreement states the intended obligations. The onchain series records the inputs and state that handlers enforce. Your reporting records supply evidence for each period. Check that all three refer to the same series and terms before relying on an amount.

The glossary explains covered income, the threshold and the cap. The generated contract reference exposes handler names, while status definitions describe recorded states. Neither is an application walkthrough.

What can go wrong

A familiar display label can hide an unresolved term or an incomplete workflow. A report being accepted does not itself mean that a positive payment has settled. These guides distinguish the decisions, records and transactions so that a later runnable walkthrough can check each result.