trusset-kyc is the command line tool for sealed KYC records. It runs on your own machine and has two sides:
- The verifier seals the KYC file of an investor so that only the bank can read it, signs it, and posts it to the bank’s inbox on Trusset.
- The bank downloads the sealed envelope, verifies and decrypts it locally, files the record, and proves to Trusset that it opened it. Trusset then deletes the ciphertext.
Who uses it
Approving a record and listing its wallet on a whitelist are not part of the tool. The bank does that in the Issuer Portal or through the API, and its own wallet signs.
What Trusset sees
- The envelope header: envelope ID, source ID, wallet address, profile key, recipient key ID, two digests and three timestamps.
- The size of the ciphertext and the time of delivery.
- Whether and when the bank opened, approved or rejected a record, and whether the verifier revoked it.
What Trusset cannot do
- Read a record. Records are encrypted to the bank’s X25519 key with HPKE (RFC 9180). The private key never leaves the bank’s keystore.
- Forge or alter a record. Each record is signed twice with the verifier’s Ed25519 key: once inside the ciphertext, once over the header and the ciphertext. The bank’s tool checks both against a key the bank pinned itself.
- Move a record to another wallet, source or profile. Those fields are in the signed header, the header is bound into the encryption, and the same fields are repeated inside the signed record.
- Claim that a record was opened. Opening is proven with a random value that exists only inside the ciphertext.
The two pinning rules
These two rules are what make the list above hold even if Trusset were compromised:- The verifier pins the bank’s key from the invite. The tool never encrypts to a key that Trusset reports. If Trusset reports a different key than the invite holds,
sendrefuses. - The bank pins each verifier’s signing key in its own keystore. The signing key Trusset reports is shown as a hint and is never used to verify a record.
source add --replace --former-key retire, or --former-key revoke when the old key was exposed. A former key never opens a new record, whatever date the envelope claims. A retired key keeps the records filed under it verifying; a revoked key does not, and it can never be pinned again, not even after source remove.
verify checks a filed record against a key the person running it trusts: the pin in the local keystore, one of its retired keys, or the key or fingerprint given on the command line. Without one of these the record does not verify, because the key that comes with the folder proves nothing on its own.
What the tool does not decide
The tool moves a file and proves where it came from. It does not judge whether the verification behind it is sufficient. Whether a bank may rely on a verifier’s KYC, and how personal data may pass between the two, is governed by the agreements between the bank and the verifier. The tool does not check what a verifier seals. A record with wrong content is still validly signed, so the review of the file stays with the bank.Getting the tool
The tool is not published to a package registry. Trusset provides it during onboarding. It needs Node.js 18 or newer and has no runtime dependencies. All cryptography uses thecrypto module built into Node.js. From the folder you received:
node bin/trusset-kyc.js --help.
File modes are not enforced on Windows. Use a directory there that only your account can read.
Version 1.2.0. Apache-2.0 license.
Bank walkthrough
From the record key to an opened and filed record
Verifier walkthrough
From the invite to a delivered record, its status and a revocation
CLI reference
Every command, option, environment variable and exit code
Keys and files
What is written to disk, how keys are protected, what to back up
