BitRegalo is infrastructure that a marketplace, an enterprise, a bank or a startup connects to the platform it already runs. Its records are written once to public contracts that nobody can edit afterwards, the platform's own developers included. Its payment commitments, such as a held payment or a refund, execute exactly as agreed when they are triggered.
Today BitRegalo runs on BNB Smart Chain Testnet, a public test network where tokens have no value, and has been deployed unchanged to a private Hyperledger Besu test network. It has not been independently audited and it is not on a main network. You can try every step in the reference app with practice tokens.
Escrow #1042 · Roof framing, stage 2
Held12,500.00USDT
Locked in the contract
Neither side can spend it. Three things can happen next, and only three. Try them.
A platform connects BitRegalo for the part of its system that should not depend on trusting whoever runs it: its records and its promises about payments.
Your platform keeps its product, its customers and its interface. It reads BitRegalo's records and has its users sign BitRegalo actions from inside its own site, app or back office.
A request, an award, a payment, a sale or a redemption is written to your organisation's own contracts with its parties, its amount and the time. No function exists to edit or delete it.
A payment is held by a contract with its outcomes fixed in advance. When one is triggered, the payment goes where the contract says. Nobody can send it anywhere else or stop it from leaving.
Connect the platform you already run. Launch a workspace of your own. Or try it on the BitRegalo network, which is open to anyone.
For a product that already takes payments: a marketplace, an enterprise system, a bank, a startup. It keeps its own site, app or back office and connects BitRegalo for the records and commitments that should not depend on trusting it. This is the use the protocol is built for.
For an organisation that wants its own contracts, not an account on someone else's ledger. Everything done inside a workspace is recorded under it, and BitRegalo cannot change it after it is launched.
BitRegalo's own public workspace, open to anyone with no organisation behind them. Its web app is the reference implementation, and the place to try every part of the protocol with practice tokens that have no value.
Requests and listings meet in a marketplace you can browse by country.
A platform's own database asks its users to trust whoever runs it. Here the rules are public contracts. A record is written once, and a held payment has only three outcomes.
BitRegalo never holds anyone's tokens, and neither does a workspace admin. A workspace or BitRegalo can pause new activity. Nobody can pause a release, a hand-back or a return.
Each does one job, and they fit together. A request or a listing settles who does the work and for how much. An escrow holds the payment until it is done. Every step is a record nobody can edit, and a workspace holds all of it for one organisation.
An organisation's own contracts. Everything done inside it is recorded under it. Used by organisations that run a platform, a programme or a supply chain.
“I need this.” Suppliers answer with a price and a time, and the buyer chooses one offer.
Used by buyers who want to compare prices, from a household job to a building package.
“I offer this.” A fixed price and delivery time, open to anyone or to one named buyer.
Used by suppliers who sell a set job or product.
Holds the payment until the work is done. Then only three things can happen to it:
A request or a listing can also be paid directly, or recorded only, with no payment at all.
Used by anyone paying for work before it is delivered, including one person holding a payment for another.
Every step above is written once: who asked, who answered, who was chosen, what was paid, sold or redeemed, and when. Anyone can read it. Nobody can edit or delete it, including the organisation that wrote it and BitRegalo.
Used by anyone who has to show later what happened: a supplier who lost a tender, a customer owed a refund, an auditor.
The BitRegalo network is BitRegalo's own public workspace, open to everyone. An organisation can run its own.
These are illustrations, not customers. The industries change; the records and the commitments underneath stay the same.
Example: a marketplace. Each order's payment is held in a commitment. The supplier is paid when the buyer releases it, and if the order never arrives the payment can only go back to the buyer.
Example: a head contractor. Each progress payment is held until the stage is certified. The subcontractor can check it is there, and nobody can move it except to them or back to the buyer.
Planned, not built
Example: a gift ordered from another country. A delivery code lets the recipient confirm a delivery without a wallet, and gives the supplier proof of the handover. Today only the buyer's own wallet can release a held payment.
The buyer orders flowers from a florist in Spain for a friend there. The payment is held by the contract, and the buyer's app creates a long random delivery code. The contract keeps only its fingerprint.
The buyer sends the code to the friend as a QR code or a link. It can be printed. The florist never sees it before delivery.
At the door the florist scans the code with their own phone. The friend needs no wallet, no app and no account.
Presenting the code releases the payment to the florist on the spot and records the handover with its time. That record is the florist's proof of delivery.
If nobody presents the code before the deadline, the payment can only go back to the buyer.
Presenting the code can only ever send the payment to the supplier. The code has to be long and random, which is why it travels as a QR code and not as a short number to type.
Every rule on this page is carried out by published contracts you can read and check. The rules belong to the protocol, not to a network, so any implementation has to keep them.
// once an escrow holds the payment
vault.release(id) // buyer only: pays the supplier
vault.cancel(id) // supplier only: hands it back
vault.expire(id) // anyone, after the deadline: back to the buyerA platform you want to connect, a workspace you want to launch, or a question about the protocol: write or call. No forms.
Want the detail first? Read the whitepaper, see how a platform connects, or try the reference app.
BitRegalo® Limited — New Zealand
BitRegalo® Limited is a New Zealand company and intends to operate in line with the New Zealand law that applies to it. Users and organisations are responsible for compliance with the laws that apply to them in their own jurisdictions.