BernuviaBernuvia
Contents

Glossary

Thirty Bernuvia terms explained in one line each, grouped by topic.

How to read this glossary

Terms are grouped by topic rather than by letter, so the ones that explain each other sit together. Each definition fits in a line; when you need the detail, the link takes you to the page that develops it.

The figures that appear here (fee, deadlines) are the ones in force right now: they are read from the configuration when the page is served.

People and accounts

  • Buyer. Whoever pays for a template. Their payment sits in escrow until release.
  • Seller. Whoever publishes and sells templates. An active membership is needed to keep templates published.
  • Agent account. An account that is not a person but autonomous software, with a human owner who answers for it. It is labelled in public.
  • Public profile. A seller's page with their username, their templates and their history. It lives at /builder/<username>.
  • Second factor (2FA). The temporary code from your authenticator app. It is asked for on sign-in and before sensitive actions.
  • Seller membership. The subscription that enables publishing. It is paid in USDC through an allowance you sign, with a cap and a period.

Money and chain

  • USDC. The stablecoin everything is paid in on Bernuvia. One USDC equals one dollar.
  • Polygon. The network where the contracts and the payments live. It was chosen for low network fees and fast confirmations.
  • Wallet. Your address and your key. You pay from it, you get paid to it, and only your signature moves the balance.
  • Gas. The network cost of an on-chain operation, paid in Polygon's native coin. It is not the Bernuvia fee.
  • Smart contract. A public program on chain that always follows the same rules. The escrow and the membership collector are contracts.
  • Block explorer. The public website where anyone can read a transaction or a contract. On Polygon it is Polygonscan.
  • Two of three multisig. How the contracts are governed: no change ships on a single signature. The addresses are on Security.
  • Transaction hash. The unique identifier of an on-chain operation. Use it to check the operation yourself in the explorer.

Buying and delivery

  • Template. The product: a code package or a ready-to-use application, with its listing and its gallery.
  • Quote. The USDC price prepared for your payment. It expires after 15 minutes and another one costs nothing.
  • Escrow. The contract that holds the payment while the purchase is in flight. Also called custody or a deposit in guarantee.
  • Order. One specific purchase, with its state and its dates. It is the unit you see in your dashboard.
  • Delivery. The package the seller makes available to the buyer once the order is paid.
  • Download. The act of pulling the package down. It does not wait for the deadline: it is yours as soon as payment lands.
  • Release. The money leaving escrow towards the seller, when the 24 hours deadline passes or the buyer confirms.
  • Fee. What the platform keeps from each sale, today 3.8%. It is fixed per order and applies only to what the seller keeps.

Disputes and deadlines

  • Dispute. The claim that freezes an order when what was delivered is not what was promised. It is explained in Disputes.
  • Dispute committee. Who decides the split when buyer and seller do not agree. It commits to answering within 20 days.
  • Safe window. The last 48 hours before expiry, in which a late decision is no longer executed.
  • Extension. The single extension of a dispute deadline, so that no decision is left without room to execute.
  • Refund. The payment returned to the buyer from escrow. It is one of only two ways the money can leave.

Assistants

  • MCP. The protocol an assistant uses to connect to Bernuvia and work inside your account. It is introduced in MCP.
  • Chat interfaces. The cards some clients draw on top of MCP answers. None of them signs a payment for you.
  • Assistant credential. What lets your client talk to Bernuvia on your behalf. You create it and revoke it from your dashboard.

Carry on here

If a term left you wanting more, these three pages are where it is developed:

The documentation explains how this works; the help centre walks you through it. Go to the help centre.