Verified by others

Don't take our word for it

NETTEN says it never holds your money and never signs for you. Here is who checked that, what they found, what they didn't look at, and how you can check it again yourself.

HoldsKVT-REC-2026-NETTEN-01

Claim checked

“NETTEN never signs for a merchant.”

Checked by Kairo Vault Technologies G.K. (Tokyo). Independent of NETTEN. No fee was paid. NETTEN agreed to be named.

What they found

None of the six outside accounts that had paid NETTEN's fee account could be signed for by any NETTEN account. Each could only be signed with its own key: no regular key, no signer list, no delegated permissions. NETTEN's own five accounts also use only their own keys.

Ledger
107,713,543
Closed
17 Oct 2026, 08:29:51 UTC
Ledger hash
0D47D33833D9642C3EB7049CB89B6D5AABC1934C78C3AAE64B1FC1ABCA88BE78

Kairo Vault re-ran the check at ledger 107814299 on 21 Oct 2026 and told us it still holds, with the same six outside payers. The signed record stays dated to ledger 107713543.

What it does not cover

  • Only on-ledger signing authority (master key, regular key, signer list, delegated permissions) at one ledger. A later change needs a new reading.
  • Only the accounts in the record. NETTEN users who never paid the fee account on the ledger are not covered.
  • Nothing off the ledger: how keys are made or stored, NETTEN's servers, or its app code.
  • It is not an audit, a certification or a security review, and gives no opinion on NETTEN as a business.

Check it yourself

  1. Download the files below and keep them together. Check none of them changed:

    shasum -a 256 -c SHA256SUMS.txt
  2. Check Kairo Vault's signature (OpenSSL 3). Expect "Signature Verified Successfully":

    printf 'KVT-REC-2026-NETTEN-01/v1\n' | cat - NETTEN_Record_KVT-REC-2026-NETTEN-01.md > message.bin
    openssl pkeyutl -verify -pubin -inkey kvt-record-key-R1.pub.pem -rawin -in message.bin -sigfile NETTEN_Record_KVT-REC-2026-NETTEN-01.sig
  3. Read the ledger yourself (Python 3.8+, no account, no keys). Expect "servers_agree": true and "HOLDS":

    python3 recheck.py --ledger 107713543

Keep them together and unchanged, or the signature won't check. The zip is exactly what Kairo Vault sent us (sha256 b8ef332305e76996…).

  • NETTEN_Record_KVT-REC-2026-NETTEN-01.mdThe signed record · 4.7 KBsha256 27ebb06bc7f7b190630c7caad7dae8f049b87dad4c31970853977e15dac47c57
  • NETTEN_Record_KVT-REC-2026-NETTEN-01.sigKairo Vault's signature · 64 Bsha256 72f0d5721f408e18e681f53da8468c81f1b994749031ddc81b65e704fa3eb0c5
  • kvt-record-key-R1.pub.pemKairo Vault's public key (Ed25519 bd56ae14…c2ed22) · 113 Bsha256 3be91c5af7800ea72ad23c7ea4c9b5edc615cdac3f0c56099f73fe4a4a7048dd
  • recheck.pyThe re-check script (reads two public ledger servers) · 6.4 KBsha256 0b9ae9d98158b6058d83e511c5655b616019471648fef3097d3875228aef5e7a
  • result_107713543.jsonKairo Vault's own result · 4.8 KBsha256 56ca6a84e521985cf57e98cbf4a4b4c8a2ddd985dc796affb2b6614306cdbbc6
  • SHA256SUMS.txtHashes of the five files above · 470 B
  • VERIFY.txtThe three steps, from Kairo Vault · 741 B

NETTEN's own accounts

These are public. Look them up on any XRP Ledger explorer.

Want to check another claim?

We'll open the ledger, the accounts and the reasoning to any independent reviewer, and publish what they find, good or bad. Write to [email protected].