Mappers Protocol is currently maintained by a single maintainer (@iamPhatom_). This document describes how decisions are made today and how that will change as the project grows.
All merge decisions, roadmap direction, and release timing are currently made by the project maintainer. This is a deliberate, temporary state for an early-stage protocol, not a long-term governance structure.
- Smart contract changes (
programs/) require the highest scrutiny. Any change affecting fund custody, PDA derivation, or authority checks must include a written rationale and, where possible, updated test coverage before merge. - Non-critical changes (docs, dashboard UI, tooling) may be merged with lighter review.
- Disagreements are resolved by the maintainer with public rationale given in the relevant issue or PR — not silently.
As the protocol approaches Mainnet-Beta, governance will transition in this order:
- Add trusted co-maintainers with merge rights, scoped by directory (see
CODEOWNERS). - Move oracle authority from a single keypair to a multisig/threshold scheme (tracked in the whitepaper's Security Model section).
- Establish a public RFC process for protocol-level changes (fee model, consensus thresholds, PDA schema changes).
If you believe a decision was made improperly or not transparently, open a GitHub Discussion or contact the maintainer directly. This is separate from the Code of Conduct enforcement process, which covers interpersonal conduct, not project decisions.