The Rules — How BeanPool Works
BeanPool is a community exchange where everyone starts at zero. You earn beans by helping others and spend them when others help you. No money changes hands, and there are no corporate middlemen — just these simple rules.
In short: earn your credit line by trading, keep an offer or two live to use it, and let beans flow. Zero is the goal — give about as much as you take.
1.Beans & your balance
Beans measure the value you've given and received (roughly, time). Zero is the goal — it means you've given about as much as you've taken.
- Positive balance — you've given more than you've taken. The community owes you.
- Negative balance — the community has extended you credit. You owe it back by giving.
- On most communities the deepest anyone can go is −2000 beans. A community that confirms its members by real name can set its own limit, up to −5000, and give confirmed members a starting line.
2.Getting started
You join a community with an invite from one of its members, or you ask to join from the global community, which anyone can join with no invite, and any member of that community can let you in (where only admins invite, an owner or admin does). From day one you can browse and receive beans. Once you hold beans (by earning them or receiving a gift), you can spend them. To spend on credit, you must post at least one Offer (see §4 and §5). New members start with no credit line — you can only spend beans you actually have until your line is activated by your first completed trade (or if a voucher or an admin gives you a starting line — see §3 and §9).
3.Your credit line is earned by trading
Your credit line lets you go a little negative — spending before you've earned it back. Mostly it's earned, not given:
- Trust comes from completed marketplace trades — never from gifts. It grows slowly at first: a 100-Bean trade earns about 37 Beans of credit line. An admin or an appointed voucher can also give someone a starting line; an admin's grant shows as their badge.
- Trading with many different people builds trust far faster than repeat trades with one person.
- Your trust sets your credit limit — how deep your floor could go, from 0 down to −2000 on most communities (see §1).
- Your floor opens after your first real trade, and grows with every trade after it (or a community voucher can give you a starter floor — see §9). No vouch is required.
Trust levels — Newcomer → Resident → Steward → Elder — are recognition badges. The badges you earn unlock nothing on their own; a deeper credit line comes from real trading. An admin can also give someone a badge, and with it that badge's starting credit line.
4.Reciprocity: To use credit, you must keep active offers
Earning trust sets your credit limit (how deep you can potentially go). But to actually draw on that credit, you must keep active Offers posted. This ensures that anyone carrying debt is actively showing the community how they plan to contribute.
The number of active offers you keep posted determines how much credit is unlocked:
| Active offers | Unlocked credit line |
| 0 | 0 — spend held beans only |
| 1 | Down to −200 Beans |
| 2 | Down to −500 Beans |
| 3 | Down to −1000 Beans |
| 4 | Down to −1500 Beans |
| 5 | Down to −2000 Beans (the usual cap) |
Your actual spending limit is the smaller of what you've earned and what your active offers unlock.
For example: If you have earned a −600 limit through trades, keeping 2 active offers unlocks −500 of it. Keeping a 3rd offer unlocks your full −600 limit (you never need a 4th or 5th offer because your earned limit is already reached).
The Spending Pause (Freeze):
If you drop below the active offers required for your current debt (e.g., if one of your offers sells and completes, or you pause one), your ability to spend on credit is paused. This is a safety net, not a penalty: nothing is taken from you. You can still receive beans, keep selling, and browse. Your credit line un-pauses by itself once your balance is back within what your active offers cover: post another offer, or receive beans.
5.Offers (your listings)
- Keep as many offers as you like — including recurring ones — and switch each one Active or Paused whenever you want. Only Active offers count toward your credit line.
- Give before you take: in a community with Beans, you must have listed at least one offer before you can post a Need or buy from others. Where there are no Beans, as on the global community, your first post can be a Need.
- Positive balance? Pause everything if you like — offers are only required to go negative.
6.Fees & the community pool
Two small charges, and both flow into the Community Commons — a shared pool your community votes to spend on local projects. Nothing is lost to a corporation.
a) Marketplace fee — 1.5% on completed trades. When a marketplace sale settles, the seller nets 1.5% less than the price and the difference goes to the commons. Gifts (direct sends between members) are free — as are refunds and system moves.
b) Circulation fee on positive balances — monthly, and only on the part above 200. Like progressive brackets, each band is charged only on the slice of your balance inside it:
| Balance band | Monthly circulation rate |
| 0 – 200 | Free green zone |
| 200 – 500 | 1% |
| 500 – 1000 | 1.5% |
| 1000 – 2000 | 2% |
| 2000+ | 2.5% |
This gently encourages beans to circulate rather than pile up. Negative balances never incur a circulation fee — you're already carrying credit for the community. Note the +200 free zone mirrors the first −200 credit band, so the system is symmetric around zero.
7.Gifts (sending beans)
- You can only gift beans you actually hold — a gift never goes negative and never uses your credit line.
- You can send once you've completed at least one real trade (this stops brand-new accounts instantly forwarding beans and vanishing).
- Gifts build no trust for the receiver, and are free — no fee (you can only gift beans you already hold).
8.How trades settle
Marketplace trades are held safely in escrow (held in trust by the system) until the deal is done, then released to the seller (minus the 1.5% fee). If a deal is cancelled, the buyer is refunded in full.
9.Vouching (an optional head start)
A voucher (an owner, an admin, or a confirmed member made a voucher by an owner or a credit-committee admin) can give a newcomer or a member a starter credit line of 25, 50, 75 or 100 Beans from the voucher's own budget. Up to three vouchers can vouch for one person, up to 300 Beans in all. A starter line lets people begin using credit before they've earned it. These are typically awarded — entirely at the voucher's discretion — to people whose posts and contributions the voucher finds genuinely engaging and inspiring. It's optional either way: no one needs a vouch to take part, since you also open your credit line simply by trading (§3).
10.Federated Inter-Community Clearing
Communities do not need to exist in isolation. Through Federated Trade Connectors (inspired by Keynes’ clearing union), independent community nodes can clear trades with a neighbouring node peer-to-peer, without fiat currency or banking reserves. Beans never leave their home community — each pair of nodes keeps a bridge ledger of what they owe one another in work, and each side sets its own cap on how far that can run. Clearing is between pairs of communities, each operator turns it on deliberately, and it is still early: it is built, with its screens in the web app, and has been tried only between two of our own test communities, never between live ones.
11.Cryptographic Identity & Key Custody
Your account is protected by an Ed25519 cryptographic keypair generated on your device. BeanPool offers flexible custody to fit your needs:
- Full Self-Sovereignty: On the phone apps, your private key is held in the device's secure storage (iOS Keychain / Android Keystore); in the web app it is held in the browser's own storage. It leaves the device only as a locked copy for sign-in recovery, or when you copy your account to another device of yours. Keep your 12-word seed backup offline.
- Recovery: Your 12-word phrase restores your account on any device. You can also link a Google, Apple or Facebook sign-in. A locked copy of your key is then kept for it. The copy goes where your community chose: BeanPool's key vault, a small server in Iceland that does nothing else (where every community starts), or your community's own server. A community can also keep no copies; then your 12 words are your way back. The web app on the global community keeps it on that community's server, which we run. Whoever keeps the copy can open it. A restore from the vault waits 24 hours unless one of your own devices approves it. If you lose your device, your 12 words and your sign-in, an admin of your community can move your account to a new phone with a one-time code, in front of you; your history stays. So write the words down.
12.Limits & safety
- Floor cap −2000 on most communities (see §1). There is no daily limit on how many beans you spend — your floor is the bound. There is a limit on how often: 100 payments, 30 people you have never paid before and 100 market requests in any 24 hours.
- Trust with any single partner is capped, so no one can inflate their standing by trading back and forth with one accomplice.
- Holiday mode hides your offers and pauses incoming requests while you're away.
- Members can report and flag bad actors, and block anyone.
- Suspending and removing a member: In a community that votes, an owner or admin can suspend a member at once, with a reason every member can read. That opens a 7-day vote on removing them, and only that vote removes them: an admin can't remove anyone outright. Two things still happen without it: where too few members could vote, an owner may decide it, with a reason members can read, and an owner can remove a member together with everyone they invited. Where a community's owners have switched community votes off, its admins remove members themselves. No vote removes an owner or an admin of a community's server, and an admin who is suspended keeps the role when the vote closes, whatever it says. On the global community there are no votes: a suspension lasts 7 days and then lifts by itself, unless an admin lifts it sooner. To keep someone out for longer, the admins suspend them again, or remove their account.
- Who decides a removal: Until a community is large enough for a jury, every member who can vote decides: at least 25% of the members active in the last 30 days (and never fewer than 3) must vote, and 66% of the votes cast, with at least 3, must say Yes. After that, a jury does. With the default setting, that is once at least 100 members could serve on one: a jury of 12 members is drawn at random (18 once 1,000 could serve), and only the jury votes. Everyone else can read the case and the member's answer. A community's owners can choose to have everyone decide instead, or a jury from 36 members who could serve. A vote to bring a member back stays an ordinary Decision, decided by everyone who can vote.
- How the jury is drawn: Nobody chooses the members by name: not the admin who suspended the member, not the member, not the owners. Those who could serve are the members who could vote, and who joined at least 30 days before the start of the day the vote opened. They are put in an order by a public calculation, a SHA-256 hash of the member's key, the list and the day, and the first in that order are the jury. That calculation uses only facts anyone can read and the day of the suspension, so anyone, the suspending admin included, can work out in advance who a given day would seat. The admin does choose the day, but only one try a day, and each is on the record. Members with a link to the member that the member couldn't have made alone are passed over, such as someone who blocked or reported them, invited them or was invited by them, or traded with them lately; nobody is told who, or why. Each juror has 72 hours to serve or step aside, with no reason asked, and one who doesn't answer is replaced from the same order. At least 9 of the 12 jurors must vote (13 of 18), and removing takes two-thirds of the votes cast, with at least 6 Yes (9 of 18). A tie fails, and if too few jurors vote the suspension lifts. The vote always closes after its 7 days.
- What a member can check, and what they can't: The ballot is secret in the apps: while a vote is open they show how many jurors have voted and never Yes or No, and when it closes they show the totals and who voted and who didn't serve, never how anyone voted or why someone didn't serve. The server stores each vote with the voter's account, so whoever can read a copy of its files could look a vote up. Every member's app can check the draw: it works out a fingerprint of the list of members who could serve, which the server gives to every member, and compares it with the one the server recorded when the vote opened, and once the vote closes it checks that the jurors listed are the first ones the draw picks. That catches a list or a jury that doesn't match the draw. It can't catch a server whose owners rewrite the record, the list and the jury together: whoever runs a community's server can change what it stores. And because the calculation is public, someone who runs it can work out who is probably on a jury, before the vote opens or while it is open, though not who was passed over.
13.Community Enterprises & Governance
Community enterprises (such as a community tool library, an egg flock, or a firewood depot) and bounded projects are shared initiatives under collective stewardship. They operate under clear, code-enforced rules (the Commons governance model):
- One object, two lifecycles (§2.1): An ongoing enterprise persists and trades; a bounded enterprise (a project) has a goal and end date, winding up its account and returning what is left to the Commons when finished.
- Earned floors & keeper pledges (Rules 1–3): A new enterprise starts with no unearned overdraft: its credit floor is backed by explicit pledges from its keepers' earned trade standing (straight sum, no synthetic multiplier). Pledging backing never touches or reduces a keeper's personal household credit floor. Older enterprises keep the starting floor they had before pledges.
- Limited liability (Rule 4): The enterprise fails, not the keeper's household. If an enterprise defaults, its spending freezes, but its keepers' personal floors are protected.
- Credit buys inputs, profit pays people (Rule 5): An enterprise may draw on credit down to its usable floor to buy supplies or services from outside neighbours. It may never draw on credit to pay its own keepers — keepers are paid only while
balance − amount ≥ 0.
- Keeper pay capped by earned surplus (Rule 6): Payouts to keepers are strictly capped by genuine trading surplus (sales income minus keeper payments). Grants, pledges, and gifts can never be converted into keeper wages.
- Automatic working-capital sweeps (Rule 7): An enterprise can set a working-capital ceiling. Earned surplus above it sweeps automatically back to the Community Commons pool to prevent hoarding. Grants and gifts are never swept.
- Two-person approval rule: Keepers cannot approve their own payments or personal bids on enterprise needs — another keeper must approve.
- Polls vs Decisions (§3): Informal questions are Polls in the market feed: one vote each, counted, binding nothing. Binding governance (pool grants, debt write-offs, role changes, and suspending, freezing or removing a member) runs via Decisions in the Commons tab, with a 7-day voting window. A Decision passes with 60% of the votes (66% to remove a member; more than half to lift a suspension or a freeze, or to bring a member back) once enough members have voted: 30% of those active in the last 30 days, at least 3 (25% for removing a member, where everyone decides it; in a larger community a jury of members drawn at random decides a removal, see §12). Then it carries itself out. Pool grants use quadratic voting on earned trade standing — liquid beans cannot buy votes.
- Settled vocabulary (§9): Four levels, four distinct words: node → owner / admin · enterprise → lead keeper / keeper · group → convenor · trust tier → Steward.
In short: earn your credit line by trading, keep an offer or two live to use it, and let beans flow. Zero is the goal — give about as much as you take.