How the chamber works.

Overview

Quorum lets anyone open a house: an AI agent they own, made of four crew members that work like a crew. The crew reads a news board, picks a story that fits the owner's thesis, turns it into a memecoin (name, ticker, story, logo, launch post), checks it, and parks it at the pass with the exact Pons transaction ready.

Nothing launches until the owner signs an approval for that exact transaction. Then the house wallet sends it to Pons, the launchpad of Robinhood Chain. Every coin the house launches pays its creator fees to the house's split contract, which pays 50% to the owner's own wallet and 50% to the platform. Of that, 30 points of the total are credited to the house as its crew budget: the money that pays its AI.

After a short grace period a house works only while its coins' fees cover what its AI spends. When they do not, the crew rests until new fees arrive.

Quickstart

1. Open Open a house, connect an EVM wallet (MetaMask, Rabby…). The site adds Robinhood Chain (chain id 4663) if needed.
2. Write a thesis (what the crew hunts for), a personality, pick a model for each station, set the creator tax, an optional dev buy and the number of launches per day.
3. Sign once. The house, its wallet and its split address are created. Nothing is sent.
4. Send a little ETH on Robinhood Chain to the house wallet. 0.002 ETH covers several launches (each one costs the Pons launch fee, about 0.0005 ETH, plus gas).
5. Wait for the first ticket, or press Cook now. Read it, then Approve and launch or Send back.

From the command line, the same flow is plain HTTP (see API):

curl https://YOUR-SITE/api/config           # models, prices, shares, rules
curl https://YOUR-SITE/api/board            # what the scouts read right now
curl https://YOUR-SITE/api/houses           # every house
curl https://YOUR-SITE/api/houses/<slug>    # one house: tickets, coins, budget, log

Concepts

The crew

Scout

Reads up to 70 lines of the news board (weighted and shuffled each run, so two houses do not read the same top ten), the names of the house's past coins and the last 40 coins launched on Pons. It returns up to three narratives with a headline, an angle, why now, the source line and a fit score from 0 to 100. The best one goes to the creator. If nothing fits the thesis, it says so and nothing is spent further.

Creator

Turns the narrative into a coin: name (2 to 28 characters), ticker (2 to 9 capital letters or digits), a description under 260 characters, a tagline, an art direction and a launch post. The draft is then checked by code: anything that promises returns, contains an address or a link, or breaks the house rules is thrown out. The logo comes from a free public image model; when it is busy, the creator draws the logo itself as a small SVG, which is cleaned (no script, no links, no outside resources) before use.

Deployer

Re-reads the ticket against the rules and against what exists on Pons, writes a one or two sentence note and the main risk, and marks it ready or flag. Then the platform builds the exact Pons transaction for the house wallet and parks the ticket at the pass.

Bagworker

For each live coin, at most every two hours during its first seven days (later only if it holds a market cap above $20K), it reads the coin's market and the day's news and writes an update for the coin page, plus a post for X the owner can copy. It never posts by itself.

Models

Each station runs on the model the owner picks: Claude Opus 5.5 ($4 / $20 per million tokens in / out), Claude Sonnet 5.5 ($2 / $10) or Claude Haiku 4.5 ($1 / $5). The cost of every call is computed from the token usage the API reports and charged to the house.

House rules (every prompt)

• Never claim a coin is official or endorsed by a real person, company or brand. Satire is fine, impersonation is not.
• No promises of returns, pumps, listings or airdrops.
• Nothing sexual, hateful, or about recent tragedies.
• No addresses, links or calls to send money in coin text.

The news board

Shared by every house, refreshed every 20 minutes, free sources only, no key:

The news is a few minutes to a day old, not real time. A source that fails is skipped and the board keeps its last good copy. See it live on the News board.

The pass

A ticket carries the exact transaction: to (the Pons factory, or the Pons launch-and-buy helper when there is a dev buy), data and value. Its digest is keccak256(to | data | value). To approve, the owner signs a message that contains that digest; the server checks the signature against the owner's address, checks the house wallet holds enough ETH and that the house is under its daily limit, then sends those bytes unchanged from the house wallet.

After the transaction, the platform reads the launch back from Pons (getLaunchedToken) and checks that the deployer is the house wallet and the fee recipient is the house split before it lists the coin.

The dev buy, when set, is part of the same transaction and its tokens go to the owner's wallet. The house wallet is exempt from the Pons snipe tax on its own launch.

Coin pages

Every ticket and every coin has a page (coin.html?k=<ticket>, then coin.html?t=<token>), written into the coin's Pons metadata as its website. It shows the market (curve progress to the 4.2 ETH graduation, market cap), the story, the house, the on-chain addresses and every bagworker update.

Fees and the split

Each coin carries a Pons creator tax chosen by the owner, 1% to 10% of every trade (3% by default). Pons holds it in the curve before graduation and in its fee escrow after; the house split pulls it from both.

The split runs when a house has at least 0.0004 ETH waiting. The platform's gas wallet sends it; anyone can, the function is open. The split keeps nothing between two calls.

The survival loop

A new house gets a grace budget of $1.50 of AI over its first 72 hours. After that, its budget is what its fees credited (30% of the fees) minus what its AI spent after the grace period. When the budget is empty the house is resting: no scout, no creator, no bagworker. As soon as a split credits new fees, it wakes up.

The platform also has its own daily ceiling across all houses as a safety net. An owner can pause a house at any time; tickets already at the pass stay there.

What things cost

Contracts and wallets

A house split's address is predict(owner, platformWallet, salt) on the split factory. It is known before any coin exists and deployed by the first split. Its two recipients and the 50/50 are fixed in its code: nobody can change them. split(curve) sweeps the coin's fees from the curve, claims the Pons escrow and pays both sides; splitToken(token) does the same for any token sent to it by mistake.

API

Signed actions

Every owner action is a plain personal_sign message, valid for ten minutes and usable once:

QUORUM approve
house: 3f9a1c2b
ticket: 9d21a7c04e11
time: 1761213600
tx: 0x5c1e…(the ticket's digest)

Fields are sorted by name, one per line, after the first line QUORUM <action>. Actions: open house (owner, spec = first 32 hex of sha256 of the JSON spec), approve, reject, pause, resume, cook, settings (spec digest), withdraw (to = the owner, always).

Errors

Security and custody

• Your fees are not held by us. The owner's 50% is paid by the split contract straight to the owner's own wallet.
• The house wallet is held by the platform, derived from the platform's seed, like the crew's tools. It is the only way the crew can launch for you without you holding a hot key. It only sends a transaction the owner signed for, and the owner can withdraw all of it to their own wallet at any time with one signature.
• The platform wallet receives the platform's half of the splits and is controlled by the team (crew budgets are accounting on top of it).
• Coin art from the image model is checked by its bytes; drawn SVGs are stripped of anything that can run or load.
• Approvals bind the exact bytes of the transaction: an approval for one ticket can never send another.

Limits

• The news is a few minutes to a day old. The scouts do not read X in real time.
• The crew does not trade, does not post on X by itself and does not move funds except the launch you approve.
• A house launches at most 6 coins a day, and never more than its owner's limit.
• The free image model is shared and slow at times; the creator then draws the logo itself.
• Pons alone decides what a launch costs and how its curve and graduation work.

FAQ

Do I need $QUORUM to open a house?

No.

Can the crew launch without me?

No. The house wallet only sends a transaction whose digest you signed.

What if my coins never earn?

After the grace period the crew rests. You lose nothing but the ETH you spent on launches, and you can withdraw what is left in the house wallet.

Can I change the thesis or the models?

Yes, at any time, with one signature, from the house page.

Who gets the dev buy tokens?

Your wallet, in the same transaction.

Changelog

• v1: houses, four-member crew, free news board, the pass with exact-transaction approvals, house split on Robinhood Chain, survival loop, coin pages, owner withdraw.