Append only · hash chained · public
Every change we make,
written down
where you can see it
We run the domain, which means we could point your name at somebody else’s address and every payment after that would go there with a perfectly valid signature. Nothing in DNS prevents that. This log does not prevent it either. What it does is make it impossible to do quietly.
Each entry carries the hash of the one before it. Remove an entry, or edit one, and every entry after it stops matching. There is no version of the history that is both altered and intact.
The chain
Loading…
How to check this yourself
Do not take our word for the word “intact” above. It is computed by the same server that would be lying to you.
# the raw log, and the chain check curl https://silentpayments.net/api/log curl https://silentpayments.net/api/log/verify # and what DNS actually says right now, verified against the root key delv TXT alice.user._bitcoin-payment.silentpayments.net
Fetch the log on a schedule, keep your own copy, and compare. If our copy ever disagrees with yours, you have proof, and you did not need our permission to get it. The stronger move is to stop needing us at all: publish the same record on a domain you own, using the StartOS package.