🐦 Archived X post

A tamper-evident, on-chain timestamp of what this post said. Captured 2026-09-11 04:13 UTC.

@NickG222222on X · 2026-09-10

archived media

So, for the record, this morning I completely deleted @rockwallet since they told me I had to. Also tried to buy $500 worth of BSV. In order to do that I had to sell some BSV in order to acquire SOL so I can swap USDC (which I could buy for a $25 fee) to SOL so that I could swap SOL to BSV Lol ... As @EquityDiamonds has noted we are in 2009 levels of retardation with regards to purchasing BSV Here's the process for purchasing BSV through Exodus 1. Login to Exodus 2. In order to purchase anything, have to buy USDC (or something comparable) in order to buy a swappable crypto for BSV eg ETH or SOL (in Exodus' case) 2. In order to buy USDC or something comparable, particular CCs or debit cards (or other payment mechanisms like Google Pay, Venmo, etc) must be acceptable 3. Once you figure out how to pay, you will pay a relatively large fee: FOR EXAMPLE I JUST PAID $28 TO BUY $500 OF USDC (😆) 3. Once USDC is purchased, you have to swap the USDC for ETH or SOL which will then allow you to swap for the original Bitcoin. I chose SOL in this case (which I had done in the past) 4. Now, in order to swap USDC for SOL, you must HAVE SOL 5. So, I had to swap some of my BSV FOR SOL where I am now waiting 3 hours for the transaction to settle (😆) 6. Once SOL transaction is settled, only THEN are you allowed to swap SOL for BSV (Presumably... As I am not quite there yet) 7. So, in total, it appears I will pay up to +$50 in fees to buy $500 of BSV but also apparently have to wait 4 hours in order to swap SOL for BSV at whatever price BSV is at, at the time TOTALLY retarded
posthttps://x.com/NickG222222/status/2098120704751493595
author id1970819363604488192
posted2026-09-10T18:45:31.000Z
manifest sha256e5df77959f745a88aca060a9c97c2222eaa88af749cee742ca99d1276a84aeaa
text sha25602eea8674315e17146c5d19028eb15561e5e1845d3e06d16fad4ea79a6d85e4e
media sha256ac16b715dd5fd2d8612785241ee2db06fab169ce2b868d3e23158b71c5ecabcf (photo, 42401 bytes)
on-chain⛓ anchored — 89fabeecdbca56dd1c64a982fd2f1431e663010fd62d78d01b63f75108b2f75d

Verify it yourself: the manifest is the exact JSON whose SHA-256 is e5df77959f745a88aca060a9c97c2222eaa88af749cee742ca99d1276a84aeaa; it binds the tweet id, author, post time, and the SHA-256 of the text above. Re-hash the text to match 02eea8674315e17146c5d19028eb15561e5e1845d3e06d16fad4ea79a6d85e4e, and read the anchor transaction's OP_RETURN bsv.cx / x1 / e5df77959f745a88aca060a9c97c2222eaa88af749cee742ca99d1276a84aeaa — 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.

← bsv.cx · JSON · ⚠ Report