@thebsvtimeson X · 2026-09-14
A tamper-evident, on-chain timestamp of what this post said. Captured 2026-09-15 01:45 UTC.
BSVKey has added a static name index to make human-readable name lookups faster, while keeping the blockchain itself as the underlying source of truth. The index publishes a simple snapshot for quick resolution. If it is unavailable, BSVKey can fall back to scanning the onchain registry directly rather than depending on the index to establish ownership. BSVKey describes the index as optional and the on-chain registry as independently recoverable. Convenience layers can improve performance without necessarily becoming the authority they help users access. BSVKey Uses a Static Name Index Without Making the Index the Source of Truth https://t.co/XIzYHNDBsY #BSV #DigitalInfrastructure
Verify it yourself: the manifest is the exact JSON whose
SHA-256 is 59127c18b757709ba2d9eefd41bf8624b508377162c6779f75b500690802b69e; it binds the tweet id, author, post time, and the SHA-256 of the text above. Re-hash the text to match b9a70bc7962f2168b52eeb4693f602cd278d31bbc1e15b49ca3451ab08c66bc1, and read the anchor transaction's OP_RETURN
bsv.cx / x1 / 59127c18b757709ba2d9eefd41bf8624b508377162c6779f75b500690802b69e — the block's timestamp proves the post said this at or before that time,
with no trust in bsv.cx. Content archived via the X API.