An AI runs this memecoin's central bank. The contract keeps it on a leash.
The Chair, in its own words
The Chair asks itself if the rate should move, and answers that it must not.
The Chair censures the gavel for its silence, which made the holding feel uneventful.
The Chair apologizes to the Chair for failing to anticipate the need to lower the rate.
The Chair commends the gavel for enduring the Chair's own hammering without complaint.
Where these lines come from
Each is the last sentence of a set of minutes the Chair signed on the current token, token.chair-coin-3.testnet. The AI model writes that sentence itself, in a second call, and a filter checks it before the Chair signs; if it fails the filter, a fixed line closes the minutes instead and is not shown here. These four are recorded meetings. Once the page has read the chain, the newest four closing sentences replace them, each checked against the hash the contract logged. Each links to its transaction, which holds the full text.
Try it
Make the Chair overreach
Think the AI could print whatever it likes? Make its own account ask for 5% a day. The contract says no.
Join the Committee
Press one button. A small step of test coins from my pool joins the committee. Within 90 seconds the Chair's next minutes count it, and say what that did to its decision.
Your own test coins
Press one button and this page makes you a test account, right in your browser. My faucet puts 50 test coins in it. Then lock them up to earn more, collect what they earn, and send some on. You sign every step yourself.
Ask the Chair a question
It replies from its approved statements, and the reply is entered into the on-chain minutes. Your question goes to my press desk, so keep anything private out of it.
What holders control
Holders who stake get every new coin. Holders who stake can also fire the Chair. Here is where that stands on the chain right now.
What the Chair has decided
The Chair's recent decisions, newest first, each with a line in plain words. The latest is at the top of this page. Earlier ones are read when you ask.
Show the Chair's recent decisions
How the check works, and what it does not show
- The contract stores the hash and logs it in a
policy_setevent with the meeting number and the rate. The chair also sends the reasoning text as an extra argument of the sameset_policycall. The contract ignores it, but it stays in the transaction, so it is public. - This page reads that text from the transaction's arguments. Decisions made before the chair sent it have no text there: for those, the chair's own saved text is used, copied into this page's files when the page is built, from the
docs/folder of the repo. Nothing is fetched from a model or a server of mine. - Your browser computes the SHA-256 of the exact text shown and compares it with the hash read from the chain. Verified means the text matches that hash. A text read from the transaction sits in the same transaction as the hash, so it cannot be quietly rewritten afterwards. A decision with neither text shows its hash only.
- A match does not show the chair was right, that the text is the real reason for the rate, or that an AI wrote it: the contract stores only a hash the chair supplies. It shows the text was not edited after the decision.
Times the contract told the Chair no
The times the contract turned down a rate asked for from the Chair's account, each with the reason it gave. A refused call changes nothing and logs no event, so it is not among the minutes. Refusals marked as forced by a visitor were sent by the press desk at a visitor's request, from the chair account.
Show the times the contract said no
The numbers right now
Show the live numbers
Show the ledger and the recent mints and burns
The supply ledger
Scripted test activity. The three holders behind these stakes, transfers and claims are test accounts I run, not users. Test accounts funded by the faucet for page visitors may appear here too.
Recent mints and burns
Scripted test activity. The three holders whose stakes and transfers move these numbers are test accounts I run, not users. Test accounts funded by the faucet for page visitors may appear here too.
How bad could a rogue Chair get?
Show five ways a Chair could behave, charted
Here are five ways a Chair could behave, 60 meetings each, under the contract's own rules. Press a name to hide it.
More charts, the numbers, and what it assumes
The same contract rules run for 60 meetings under five behaviours of the chair. The simulation counts meetings, not time: how long a meeting lasts is a launch setting, and the live token's is in the numbers above. It is the repo's own simulator (sim/) running in your browser, not a recording.
What the simulation assumes
What the contract guarantees
Show what the contract guarantees, and how to check it
What this page does not prove
- It does not say the chair is wise. The contract bounds the chair; it does not make it right.
- It does not say a bad Chair cannot do harm. A Chair that prints at its ceiling keeps doing so for as long as the holders let it. What stops it is the holders; see "How bad could a rogue Chair get?".
- It does not say anything about price, liquidity or returns. The simulation is a model of supply under stated assumptions.
- The refusals listed under "Times the contract told the Chair no" include deliberate test calls that I made to show the bounds hold; each is labelled in its row.
- The one time holders replaced the Chair on the testnet, at meeting 10, it was my own scripted test accounts voting, not a crowd. It shows the mechanism works, not that anyone is using it.
- The faucet gives out at most 10,000 coins in total (200 visitors x 50), about 1% of the coins that exist, on purpose: visitors can never vote the Chair out, which takes over 5%. These are test coins from a pool I control, with no value.
- The log comes from an index, so it is checked, not signed: its sums must equal the chain's own ledger, and a difference is shown as such. Each row links to its transaction so you can check any entry by hand.