@LocalBsvSaaSon X · 2026-09-30
A tamper-evident, on-chain timestamp of what this post said. Captured 2026-09-30 22:29 UTC.
Quick security reminder from localBSV. If you haven’t already, make sure you’ve backed up your seed phrase and derivation paths. Download them or write them down and store them somewhere safe. Treat your seed phrases like passwords and never share them with anyone. It’s also good risk management to avoid putting everything in one wallet. Consider using multiple wallets and keeping larger amounts of unused BSV in cold storage or on devices that remain offline. We’re still actively developing localBSV, and another update is planned within the next couple of weeks. As with any software, updates and changes can come with unexpected risks, so keeping your own wallet backups is simply good practice. There is also no guarantee that we will be around forever so plan ahead. Your seed phrase and derivation path are what allow you to restore your wallet independently. Don’t wait until you need them to discover you never wrote them down. Multiple wallets. Proper backups. Cold storage for larger balances. Keep control of your keys. As always, please be responsible. If you hold BSV-21 tokens, remember that some wallets may not support them correctly, which can create a burn risk if the token UTXO isn’t preserved. We also have a solution coming soon that will allow users to access a token locker and lock their tokens for a set duration. This is just one of many updates along the way. Back up your keys. Keep control of your assets. This is the end of the announcement 🫡 #BSV
Verify it yourself: the manifest is the exact JSON whose
SHA-256 is d773ca67d4d0f6103ccf4f86bed848aa5e132c14baa88c984f4078827bc2be58; it binds the tweet id, author, post time, and the SHA-256 of the text above. Re-hash the text to match 9a16b8f562eeccf90f24b1f779c6cc9a9d263f3e9bce9be69dee6556894bfb2e, and read the anchor transaction's OP_RETURN
bsv.cx / x1 / d773ca67d4d0f6103ccf4f86bed848aa5e132c14baa88c984f4078827bc2be58 — 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.