Skip to content

docs(governance): monetary policy anchor — fixed cap/dynamic supply vs the 2026 interim measures - #109

Merged
glandua merged 1 commit into
mainfrom
docs/monetary-policy-anchor
Sep 11, 2026
Merged

glandua merged 1 commit into
mainfrom
docs/monetary-policy-anchor

Conversation

@glandua

@glandua glandua commented Sep 10, 2026

Copy link
Copy Markdown
Contributor

What

Adds docs/governance/monetary-policy-anchor.md: a one-page statement of the long-term monetary design this repository specifies (M012 fixed cap + dynamic supply, with M013 fee routing, M014 fee-paid validators, M015 contribution rewards), what is actually on chain as of 2026-09-10, how each 2026 measure maps to the design, twelve consistency rules for public text, and the open questions the anchor leaves to the RFC process.

Also refreshes the README's on-chain figures (emissions zero, ~239.8M supply, ~5.0M pool, 11 validators) with a verification date, and links the anchor from the token-economics synthesis.

Why

Between July and September the chain moved with stock modules and no upgrade: #64 and #74 took emissions to zero, #66 started a 15% burn stream from community-pool inflow, #73 cut the set to eleven, and #76–#78 fund liquidity, stewardship hours and a validator floor from the community pool. None of these is the specified design, and several are easy to describe in ways that contradict it — "the fixed cap is in place", "#66 burns supply", a 221M cap quoted as decided while supply sits at ~239.8M. Contributors and agents drafting forum posts, proposal text, RFC reviews and digests need one frame to stay consistent with while the interim runs. This page is that frame.

What it does not do

Verification

  • Chain figures read from the public LCD at 14:37–14:43 UTC on 2026-09-10 (paths listed in §2 of the document).
  • Forum and proposal texts read the same day.
  • Secret scan clean; links resolve for a public reader.

Follow-ups (separate PRs, after working-group input)

  1. Re-base the M012 cap placeholder via RFC (supply is above 221M).
  2. Refresh the 221M/224M scenario inputs in docs/GLOSSARY.md, docs/governance/economic-reboot-proposals.md §Proposal 3, docs/integrators/m012.md, simulations/cadcad/README.md once the RFC settles the cap.

Drafted with an agent; reviewed and opened by a person.

🤖 Generated with Claude Code

…s the 2026 interim measures

Adds docs/governance/monetary-policy-anchor.md: the long-term design (M012–M015)
in one page, what is on chain as of 2026-09-10, how proposals #64/#66/#72/#73/#74/#75
and the live community-pool spends map to it, twelve consistency rules for public
text, and the open questions left to the RFC process. Refreshes README on-chain
figures (emissions, supply, pool, validators) and links the anchor from the
token-economics synthesis. Specification text is untouched; cap re-basing stays an
RFC question (OQ-M012-1).

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@glandua
glandua merged commit eb07b30 into main Sep 11, 2026
4 of 5 checks passed
@glandua
glandua deleted the docs/monetary-policy-anchor branch September 11, 2026 02:30
@glandua

glandua commented Sep 11, 2026

Copy link
Copy Markdown
Contributor Author

Note on the red Contracts (Rust) check this PR was merged with. The PR changed three markdown files and no Rust. The failure is a linker error on CosmWasm host imports (rust-lld: undefined symbol: db_read, addr_validate, secp256k1_verify, …) for every contract in the workspace. The same signature failed on #108 in June under rustc 1.96.0, this run used rustc 1.98.1, and main itself now runs red after the #107 and #109 merges; main last passed on 2026-04-25 under the stable of that day. The workflow installs dtolnay/rust-toolchain@stable with no rust-toolchain.toml, and the workspace has no committed Cargo.lock, so the environment drifts under the code. Tracked with a proposed fix in #110. Nothing in this PR depends on the contracts job.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant