Demo treasury on NEAR testnet · fictional data

Never spend tomorrow’s payroll on today’s expenses.

Your business’s money stays in a treasury you own on NEAR. Its agent, Banto, sets money aside for every bill you accept and pays only inside the rules you sign. It can never take the money, and you can switch it off at any time.

Judge check 1 · state during the check

Balance 1,000 USDC

Decision
Refused. Paying it would break money reserved for payroll and Railway.
Shortfall
120 USDC, shown only to the owner SEALED · TEE
Then
The same 400 cleared after a 500 USDC top-up (check 2)

Four guarantees

The treasury contract enforces each one. The pictures below read this treasury as it is right now.

Money for accepted bills is set aside first

Free to spend is what’s left after every accepted bill. Banto can’t spend past the protected line, however the request is worded.

Reading the treasury

Check 1: a 400 payment refused

A changed payout address freezes the payment

If an invoice asks to pay a vendor somewhere new, payment stops until a person approves the change, then waits out a cooling-off period.

Reading the treasury

Check 5: the agent can’t unfreeze it

Your books stay sealed

Amounts, vendors and payees are sealed inside a TEE policy engine. Anyone can see the chain. Only you can read the books.

Reading the treasury

See all nine bills, both ways

Proof on NEAR testnet

Ten checks ran as real transactions against this treasury. Each one links to the explorer, and the panels below read the chain from your browser.

Reading NEAR testnet

Treasury balance, public

Reading NEAR testnet

Caught for you

5

business catches Banto or the contract stopped on this treasury

  • Payout changes frozen1
  • Hidden instructions ignored2
  • Duplicate invoices rejected1
  • Reserve breaches blocked1

Plus 7 attempts blocked in the security test run (judge checks): 2 replayed or altered payments and 5 out-of-scope agent calls.

Counted from judge run 9f54e4c1, which made every one of these attempts on this treasury.

The ten judge checks

  1. Loading the run

Same books, two views

Each bill twice: what anyone can read on chain, and what the owner reads with the ledger key, from the same engine build. The bills and vendors are fictional.

Loading commitments

Free until your first payout

You see what’s really set aside and free to spend before you pay anything, with no time limit.

  1. 1Connect or create a treasury you own
  2. 2Answer Banto’s setup questions and sign the policy
  3. 3Add your team and vendors by chat, form or CSV
  4. 4Forward a few invoices
  5. 5Pick a plan at your first payout

Planned plans

Planned pricing · after the hackathon
12 months$468$39 a month, billed yearly. Two months free.
3 months$149$50 a month, billed quarterly
1 month$59Month to month, cancel any time

No percentage of your treasury. No fee on payroll. There is no billing during the hackathon.

When a plan lapses

A lapse never locks your money.

Takara is non-custodial. It never holds your funds, so it can’t hold them back. These rules are absolute.

  • Your treasuryThe treasury is yours. Funds are always withdrawable, even with our servers, the enclave and Banto all switched off. Check 8 proves it.
  • Your recordsCommitments, vendors, receipts and history are always exportable, continuously, not on request.
  • What stopsBanto stops taking invoices, authorizing payments and sending alerts.
  • Grace periodPayroll and anything marked critical still settles for 14 days after the lapse. Everything else freezes immediately.
  • WarningsAt 14, 7 and 1 days, each naming exactly which bills will go unpaid.

Verify it yourself

Don’t take this page’s word for it. Each command reads the chain or checks an attestation from your own machine.

Read the live treasury

No keys needed. Prints owners, signers, the agent, the policy hash and the pinned engine build.

git clone https://github.com/growthmindsetgg/takara-ai.git
cd takara-ai && npm install
node -e 'import("./scripts/lib/near.mjs").then(async m=>console.log(await m.view("treasury.takara-ai-hq.testnet","get_config")))'

Check an engine attestation

Verifies an OutLayer execution’s Intel TDX attestation against Intel’s root of trust (six checks).

node scripts/verify-attestation.mjs 30883 \
  dc3e7c5c406cea1872b338cfed59bb14ed37a422f5bb31486d02346f94a7f019 \
  '{"request":"step0-onchain","treasury":"takara-ai-hq.testnet"}' \
  '{"ok":true,"engine":"takara-ai-engine","step":0,"input_len":61,"echo":"request:step0-onchaintreasury:takara-ai-hq.testnet"}'

Run all ten checks on a treasury you own

Deploys a fresh treasury to your testnet account, runs the checks as real transactions and starts the local owner dashboard. About 20 minutes.

TAKARA_OWNER=<you>.testnet node scripts/setup-testnet.mjs
node scripts/judge.mjs
node backend/server.mjs   # owner dashboard on localhost:8787

The confidential payout through NEAR Intents 1Click is a separate integration on mainnet, because NEAR Intents has no testnet. The testnet contract doesn’t enforce it.