Questions, answered plainly

It is free. No license fee, no usage fee, and no share of what you bill your clients. Development is paid for by BonaBuild; selling BONA adds capacity on top of that. Either way it is not paid for by members. The catch, if there is one, is that what gets built is decided collectively — you may have to make a case for the software you want.

No. Membership and software access are free and require no token at all. A firm can deploy every application in the library without ever holding a single unit. BonaBuild funds and writes the software regardless; BONA adds capacity and governs the roadmap. It does not gate the software.

Members do. Anyone can open a request for free — no token needed. Members then back the requests they need by locking BONA against them, and the ranking is quadratic: score is (Σ√c)². A hundred firms locking 100 BONA each scores 1,000,000; one firm locking 10,000 scores 10,000. Same money, 100× the score. The top request is what the next round funds.

No. Backing locks your BONA against a request — it is not spent, transferred or burned. You can withdraw it at any time, in any state, without anyone's approval: the contract has no freeze, no sweep, and no function by which we could move a single locked token. Nothing is paid, so there is nothing to refund. Locked BONA still counts for governance voting.

So what stops you backing everything at once? Your balance. A token can sit behind one request or another, not both — and that choice is what makes the signal mean something.

No, and this is deliberate. The software ships to every member on the same day, free, whether they backed it or not. Backing signals what is needed; it buys no access, no discount, no early release and no control over the specification.

Partly, and we are precise about which parts. Self-hosted web and server applications are open source under AGPL-3.0 — source published, modifications shared back. Desktop and mobile applications (.exe, .apk) are free but closed, and we never describe those as open source. The token contracts are MIT and verified on Basescan, which is non-negotiable: anyone must be able to confirm for themselves that there is no mint function.

No. You may use it commercially for your clients and keep 100% of what you bill for your own work — installation, customisation, support, hosting. You may not redistribute or resell the applications themselves, or rebrand them as your product. For desktop and mobile apps the licence prohibits it outright; for AGPL components, enclosure is prevented because you cannot close the source.

BonaBuild funds development itself — the software is written and given away whether or not anyone buys BONA. Selling BONA adds capacity on top of that. The sale is open continuously at one published price, identical for every buyer, with no rounds, tiers, early-bird discounts or referral rewards. Proceeds go to a 2-of-4 multisig and are split 20% liquidity, 70% development, 10% infrastructure. Every disbursement is published with its transaction hash.

No. Your money goes into the liquidity pool and is claimed by whoever is selling — it is a trade between two holders and the treasury is not a party to it. This is true of every token on every exchange. Only buying from the sale contract itself puts money into the project.

Because a pool returns a fraction of the same tokens' worth. Selling 3,333,333 BONA through a pool that ends at 0.018 USDC yields about 20,000 USDC — an average of 0.006. Selling them directly at a fixed 0.01 yields 33,333 USDC and moves no market price at all. At scale it fails outright: 30,000,000 BONA pushed into a pool holding 30,000 USDC returns roughly 28,000 USDC and collapses the price by over 99%. You cannot take more out of a pool than buyers put in. We never sell treasury tokens into the pool.

Voting weight on what gets built next, a vote on how the money is spent, and a permanent public record of the purchase. That is the list. You do not get product access, a discount, an early release or a premium tier — the module a round funds ships free to every member on release day, including members who bought nothing.

No, and there never will be. A buy-back could only be paid from later buyers' money, which is a Ponzi structure regardless of anyone's intent. There is no refund either: the sale settles in a single transaction, so there is no window in which we hold money that has not yet bought anything. What you keep is what you were told you would get — the BONA, the vote, and the public record of the purchase.

No. BONA is delivered to your wallet in the transaction you pay in — no lock, no vesting schedule, no claim step. You can transfer it or lock it behind a request from that moment. The first 1,800 BONA sold went through an earlier sale contract that wrote each purchase into a vesting contract; those remain claimable by their owners on their original six-month schedule and are not affected by the change. Voting weight is your wallet balance, plus anything still in that early vesting contract, plus anything you have locked behind a request.

In your wallet. The sale contract transfers the BONA to your address in the same transaction that takes your USDC, and you can confirm it on Basescan by opening your own address there — the balance is listed under its token holdings. Wallet apps only display tokens they already know about, and BONA is not yet on the aggregator lists most of them read, so it has to be added once. Either press Show BONA in my wallet on the token page, or add a custom token by hand: contract 0xC0833296346D7a699949B5DF547279b1641Ea2cd, symbol BONA, 18 decimals, on the Base network. Some wallet apps — Coinbase Smart Wallet, and some mobile wallets — cannot take the automatic prompt and need the manual step. Adding the token changes nothing about the balance; it only tells the app to show what is already yours.

A listing is one of our goals and we are working toward it. It is not a commitment, we give no date, and we will not describe it as settled. We cannot control the outcome, so any sentence you could plan around would be dishonest.

We do not give price targets, forecasts or projections, and we will not. BONA carries no promise of profit, return or appreciation. The price may fall and you may lose the entire amount you pay.

BONA is a standard ERC-20 and is transferable from the moment you receive it. We hold no power to stop that — we deliberately built the contract without a pause, a blacklist or an owner. We neither prevent resale nor promote it, and we make no statement about what it might be worth.

No. The contract has no minting function at all — not a restricted one, an absent one. Supply is permanently 100,000,000. You can read the source on Basescan and confirm it yourself. It also means the 60% sale pool is a hard ceiling: when it runs out, the sale stops and the project has to stand on the software it has built.

A 2-of-4 multisig with published signers — no single key can move funds; every movement requires two signatures. Spending requires a passed proposal, and every disbursement is published with its transaction hash. The tokens themselves are fed to the sale contract in small batches rather than all at once, so the amount reachable by any single failure stays bounded.

15% of supply pays for work that is delivered and verified: a bug report the team reproduces, a translation, documentation, an integration. The amounts sit in a published schedule, so what a finding is worth is decided before it is found rather than after. Every payment is published with what was delivered and its transaction hash. It pays for work only — never for signing up, holding BONA, following an account, or referring anyone. Those pay people to be present rather than to build, and they would wreck the member-account counting the request ranking depends on.

From the 70% development line of the sale proceeds, and every payment is published with its transaction hash. The team’s 10% token allocation has no cliff: it releases linearly across 36 months, more slowly than any other allocation and never in a lump on a single day. That makes it long-term alignment rather than income.

10% of supply, divided into five equal seats of 2,000,000 BONA, addresses published. There is no cliff: it releases linearly over thirty-six months, about 55,556 BONA per seat per month, so it never unlocks a lump on any single day and releases more slowly than any other allocation. The multisig funds each seat in three annual tranches.

Team members change, so the contract holds seats rather than a fixed list of addresses. When someone leaves, their seat is vacated — and that moves nothing: they keep every tranche already funded to them, vesting to their own address on its original schedule. Their replacement inherits what remains of that seat's 2,000,000, never a fresh one. There is no revoke, clawback, sweep or rescue function in the contract, and the tests assert their absence.

To the open-source components, yes — the self-hosted applications and the token contracts. Desktop and mobile applications are closed, so their source is not open to external merges. Testing, reproducible bug reports, translation, documentation and proposal review apply across the whole library and earn BONA either way.

Free off-chain voting through Snapshot, public source-code verification on Basescan, transaction costs low enough that members never think about them, and Ethereum-level settlement. Governance tooling mattered more to this project than a fraction of a cent per transaction.