Discussion of MRCs (Monad Request for Comments): application-level standards such as token interfaces, registries, URI schemes, and wallet formats, and ideas that may become MRCs.
MRCs are the application-level category of Standards Track MIPs, as defined in MIP-1. They cover conventions shared by contracts, wallets, and tooling, and do not change the protocol itself. Examples include token standards, name registries, URI schemes, library or package formats, and wallet formats.
What belongs here
- The discussion thread for a draft MRC. Use this thread’s URL as the
discussions-tolink in your proposal header. - Early ideas for application standards that are not yet drafts. Posting before you open a PR gets feedback while the design is still easy to change.
- Monad-specific extensions or adaptations of existing ERCs.
What goes elsewhere
- Changes to execution, consensus, networking, opcodes, or precompiles, and client interfaces such as JSON-RPC methods: MIPs
- General discussion of protocol implementation: Protocol
Posting guidelines
- One topic per proposal.
- Once a number is assigned, title the topic
MRC-X: Short title. Before that, use a descriptive title and add(MRC). - Open with the motivation and a short summary of the specification, and link the pull request if one exists.
- If an existing ERC covers similar ground, reference it and explain what differs on Monad.
Process
Submit proposals as a pull request to monad-crypto/MIPs using the MIP-1 template, with category: MRC. MRCs follow the same status lifecycle as other MIPs (Draft → Review → Last Call → Final), and are referenced as MRC-X.