How records are secured
Every record Tribalblock issues can be checked by anyone, without trusting us. Here is what that actually means.
What tamper-proof means
When a record is issued, its details (who it is for, what it is for, the date, and who issued it) are turned into a unique fingerprint, and that fingerprint is signed. Change a single character and it no longer matches. A record is not tamper-proof because it is hidden. It is tamper-proof because any change to it becomes obvious.
Who vouches, and who can check
Tribalblock vouches
We issue and sign every record, so each one traces back to us. We are the party making the claim.
Anyone can check
The evidence is public. None of it requires our permission to inspect, and none of it sits only on our servers.
How you know the business agreed
Anyone can claim to issue records on a business’s behalf. What makes it more than a claim is that the business publishes a small record in their own domain settings, carrying Tribalblock’s public key. Only whoever controls the domain can publish it, so it is evidence that the business authorized us to issue records in their name. Every record shows whether that authorization is currently in place, so you can check it per record rather than taking a blanket promise.
What gets checked
Open any record and five checks run against it, live.
The record exists and its details can be read.
The record is committed to a confirmed Bitcoin transaction in a specific block. Checked against public block explorers, not against anything of ours.
The record’s details still match what was signed when it was issued.
Whether the issuing business’s authorization record is published and matches the signing key.
The record is still where it was issued and has not been transferred away.
Every check is shown, whether it passes or not. A record missing its domain authorization is labelled as such rather than quietly passing.
What happens if Tribalblock disappears
A fair question to ask of anyone holding your records. The anchor does not live on our servers. It lives on Bitcoin. The proof is published to a public repository operated by Lightning Labs, outside our infrastructure. If Tribalblock shut down tomorrow, both would still be there, and the record would still be checkable. What you would lose is this website, which is the convenient way to check. Not the record, and not the ability to check it.
What the record actually is
Each record is a digital token issued using Taproot Assets, an open protocol built on Bitcoin by the team behind the Lightning Network. It has three parts.
The anchor cannot be edited by anyone, including us. The proof itself is kept off the chain, and verifying a record means checking that proof against the anchor. Proofs are published to a Universe, a public repository anyone can query, and Tribalblock’s records go to the public universe run by Lightning Labs, so the proof is not held only by us.
Technical details
For anyone who wants the field-level view.
The record’s unique identifier, and the last part of its verification link.
The Bitcoin block the anchor was confirmed in, and how many blocks have been added since.
A TXT record published on the issuing business’s domain, carrying Tribalblock’s public key. The exact record is provided during onboarding.
The issuer’s own verified record, which this one links back to. Records chain upward to Tribalblock’s root record.
Tribalblock signs each record with its own key. Recipients do not hold keys or manage wallets. This is why the domain authorization and the public anchor matter: they are what make the arrangement checkable rather than something you take on trust.