Skip to main content

Start here

Status: Built, runs on simulatorStatus: Pending counsel

Merces is software for raising capital against a capped share of future income; this section explains the idea before you choose a role.

The person raising capital is the issuer. A backer supplies capital under agreed terms. Mercery is the mechanism that connects raising, reporting, paying and buying back.

Begin with the idea​

  • What is Merces? explains who it is for and what the instrument represents.
  • Merces and Mercery separates the product, the mechanism and the records it creates.
  • The glossary defines the words used throughout the docs.

Read the status before acting​

The protocol has local implementations on Solana and Monad. The checked source baseline has no devnet or testnet deployment. A simulator result is evidence about local software; it is not a place to send money.

Status: Built, runs on simulator

The signing flow uses placeholder contract texts and a mock signing provider. Counsel must supply the final texts. These docs do not turn a software example into an available offer.

Status: Pending counsel

Looking for the public programme?​

Humanathon is Merces's planned public season. It has its own rules and entry process. Begin with What Humanathon is; taking part does not oblige anyone to raise.

Not advice

Nothing in these docs is legal, tax or investment advice. Merces is software and a protocol, not a lender or broker. Before you decide anything, talk to a qualified adviser who knows your situation.

What can go wrong​

Code being built does not mean a deployment, a legal agreement or an income-source provider is ready. Check the status of each part before treating a description as something you can use. Raising and backing both depend on terms that still need legal review.