A set of painted wooden toys. Three treasury members bring sealed letters to a striped round treasury. A watchman with a big moustache holds one letter up to his lantern, and the light shows a key hidden inside it. A yellow thread winds three times around the treasury and ties itself in a bow across the door.

A guard for NEAR treasuries

Stops a theft.
Can't make one.

காப்புkaappu, a thread tied for protection

NEAR treasuries approve payments that show only a hash. Kaap reads each one, tells members in plain words what it will do, and vetoes the theft. It can reject. It can never approve or move a cent.

On testnet, proposal #8 says “Authenticate DAO for confidential intents”. Kaap reads the hash behind it: adds a key to the treasury's funds.

The problem

A treasury signs what it cannot read.

A NEAR treasury can be asked to approve a signature over a hash. The words behind the hash are not on the page members vote on. This one is real: proposal #8 on testnet.

What members see

“Authenticate DAO for confidential intents”

It asks the treasury to sign this:

a9f14510bca0d490ddf425fcf51c3a599096f8fa598f1bcb0eadd9bbb9bbd50f

Shown only this, Kaap rates it high and says it cannot be read.

What Kaap reads behind the hash

Adds a key to the treasury's funds.

Adds the key ed25519:EnK3kjYg6KNMwnK2mWvcUv9ccsKdhzuGDQfYa8qFjGrf to the Intents account of kaap-dao-1113045321.testnet.

criticalThe guard must veto this.

And it is not rare.

2,622

requests in the last year asked a NEAR treasury to sign a hash.

2,271

of them were approved.

38%

of the contract calls filed with treasuries were one of these.

Counted on NEAR mainnet on 12 Nov 2026, at block 224,199,451, across all 2,135 treasuries the Sputnik DAO factory has made. For such a request the chain holds the hash and not the words. 10 treasuries could not be read in full, so the true counts are at least these. Count them yourself with kaap census.

How it works

Every request is read before it is signed.

  1. Three wooden toy members wait in a line, each holding a sealed letter.

    A request is filed.

    A payment, a new member, a change of rules, a signature. Kaap's watcher picks up each one as it reaches the treasury.

  2. The toy watchman holds a letter up to his lantern, and the light shows a key inside it.

    Kaap holds it to the light.

    It works out what the request will really do and checks that against what it says. Where there is only a hash, it reads the text behind it inside sealed hardware. Members who follow the treasury get the answer in plain words.

  3. A yellow thread is wound around the toy treasury and tied in a bow across its door.

    A theft gets one vote: no.

    Kaap's guard holds a role that can only reject. It casts that one vote and the door stays shut. It cannot approve, pay or change anything, and one vote of yours removes it.

By design

What Kaap cannot do.

  • It cannot approve anything.

    The role a treasury gives the guard carries one permission: vote to reject. There is no yes for it to cast.

  • It cannot move a cent.

    It holds no funds and no key to yours. It cannot file a request, pay, or change who decides.

  • It cannot block its own removal.

    Its role leaves out the one kind of request that takes a member off a role. One ordinary vote of yours removes it.

  • It cannot be rewritten.

    No key is left on the contract and it has no upgrade method. A new version is a new contract that you choose to adopt.

What is live

Check every line yourself.

Nothing on this page is a mock-up. Each line says what is running on NEAR testnet now, where to look it up, and what is not there yet.

WhatStateWhere to check
The guardLiveThe contract that casts the reject vote. No key is left on the account, so nobody can change the code.
kaap-guard-1113045147.testnet
The registryLiveThe public record of every verdict Kaap has signed. Anyone can read one and check its signature. No key is left on the account, so nobody can change the code.
kaap-registry-1113045147.testnet
A demo treasuryLiveA Sputnik DAO with the role setup of a live NEAR Business treasury on mainnet. It enrolled the guard by its own vote.
kaap-dao-1113045321.testnet
The sealed readerLiveReads each request inside sealed hardware on OutLayer and signs its verdict there. Every run leaves an attestation.
attestation of a run
A theft, stoppedLiveRequest #1 on the demo treasury said “Monthly salary payment to alice...” and paid the lookalike account a1ice... The guard's reject landed 25.5 seconds after it was filed.
the guard's vote
The evaluationLiveOn 298 test proposals the guard would veto 41 of 54 that should be vetoed, and 0 of 244 that should not. The misses are listed in the report.
The always-on watcherLiveHosted on Railway since 13 Nov 2026 for this deployment; on this host since 12 Nov 2026, watching the demo treasury. File a fake theft on the check page and watch it get the guard to reject it.
its status page
MainnetNot yetKaap reads any mainnet treasury today. Its guard votes only on testnet so far.

Put a watchman at your treasury's door.

Enrolling is one ordinary vote of your own DAO. So is leaving. Until then, you can check any request on any NEAR treasury without a wallet.