A tamper-evident, on-chain timestamp of what this post said. Captured 2026-10-10 02:29 UTC.
Yes! PeerPay already has identity-based recipient search, and Metanet Desktop uses the same certificate-based identity tooling. For “bring your username with you,” the identity key is the anchor; names and avatars come from certificates associated with it. Apps can reuse those details when they support the same certificate types and trust settings. The SDK’s IdentityClient handles the lookup. For your arcade, a useful first test would be connecting a wallet, proving control of its identity, and displaying the same name/avatar seen in PeerPay. Then link that identity to the player’s existing arcade account. Happy to help work through that integration! https://t.co/dVyvBWsLoW https://t.co/lg1RDAnRnp
Verify it yourself: the manifest is the exact JSON whose
SHA-256 is aa0b7faa1267ac8f86f74b63176ddf068f04045d4a79336b81d1199e44d19688; it binds the tweet id, author, post time, and the SHA-256 of the text above. Re-hash the text to match d005241d5ad589a26c631c273b830d760b97e06a2d7fa27b55d9bd442854b38c, and read the anchor transaction's OP_RETURN
bsv.cx / x1 / aa0b7faa1267ac8f86f74b63176ddf068f04045d4a79336b81d1199e44d19688 — 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.