https://t.co/b7rlZ7Vass
1/21 Don't fear it, secure it.
A thread on creating a secure #Bitcoin backup with the Hodlr Disks from @hodlrswiss.
If you value permissionless money & the ability to transact without being censored then self-custody & get your bitcoin out of third party control.

https://t.co/b7rlZ7Vass
https://t.co/oj5iNfMVsF
More from Crypto
1/ Bitcoin: a bold new world.
Satoshi published the white paper on 10/31/2008. Right at the moment of peak despair during the 2008 financial crisis. Trust had been lost in a world that ran on trust.
2/ But why October 31st? It certainly wasn’t because Satoshi was a fan of halloween, it must have had a deeper meaning. With all of his actions, he demonstrated a careful precision.
He had been working on Bitcoin for at least a year and a half before publishing the white paper.
3/ “I believe I've worked through all those little details over the last year and a half while coding it, and there were a lot of them. The functional details are not covered in the paper, but the sourcecode is coming soon” - Satoshi Nakamoto
4/ On August 18, 2008 Satoshi registers registers https://t.co/rMWwiEwtxT through https://t.co/Uj8lMr10kB.
Satoshi was ready and waiting to hit the send button throughout 2008. What was so special about October 31st?
5/ I believe that Satoshi published the Bitcoin white paper on 10/31 as a hat tip to the ancient Gaelic festival of “Samhain” which was also the date in which Martin Luther nailed his 95 Theses to a church door. Both represent an end of the old and the beginning of the new.
Satoshi published the white paper on 10/31/2008. Right at the moment of peak despair during the 2008 financial crisis. Trust had been lost in a world that ran on trust.
2/ But why October 31st? It certainly wasn’t because Satoshi was a fan of halloween, it must have had a deeper meaning. With all of his actions, he demonstrated a careful precision.
He had been working on Bitcoin for at least a year and a half before publishing the white paper.
3/ “I believe I've worked through all those little details over the last year and a half while coding it, and there were a lot of them. The functional details are not covered in the paper, but the sourcecode is coming soon” - Satoshi Nakamoto
4/ On August 18, 2008 Satoshi registers registers https://t.co/rMWwiEwtxT through https://t.co/Uj8lMr10kB.
Satoshi was ready and waiting to hit the send button throughout 2008. What was so special about October 31st?
5/ I believe that Satoshi published the Bitcoin white paper on 10/31 as a hat tip to the ancient Gaelic festival of “Samhain” which was also the date in which Martin Luther nailed his 95 Theses to a church door. Both represent an end of the old and the beginning of the new.
Out of curiosity I dug into how NFT's actually reference the media you're "buying" and my eyebrows are now orbiting the moon
Short version:
The NFT token you bought either points to a URL on the internet, or an IPFS hash. In most circumstances it references an IPFS gateway on the internet run by the startup you bought the NFT from.
Oh, and that URL is not the media. That URL is a JSON metadata file
Here's an example. This artwork is by Beeple and sold via Nifty:
https://t.co/TlJKH8kAew
The NFT token is for this JSON file hosted directly on Nifty's servers:
https://t.co/GQUaCnObvX
THAT file refers to the actual media you just "bought". Which in this case is hosted via a @cloudinary CDN, served by Nifty's servers again.
So if Nifty goes bust, your token is now worthless. It refers to nothing. This can't be changed.
"But you said some use IPFS!"
Let's look at the $65m Beeple, sold by Christies. Fancy.
https://t.co/1G9nCAdetk
That NFT token refers directly to an IPFS hash (https://t.co/QUdtdgtssH). We can take that IPFS hash and fetch the JSON metadata using a public gateway:
https://t.co/CoML7psBhF
Short version:
The NFT token you bought either points to a URL on the internet, or an IPFS hash. In most circumstances it references an IPFS gateway on the internet run by the startup you bought the NFT from.
Oh, and that URL is not the media. That URL is a JSON metadata file
Here's an example. This artwork is by Beeple and sold via Nifty:
https://t.co/TlJKH8kAew
The NFT token is for this JSON file hosted directly on Nifty's servers:
https://t.co/GQUaCnObvX

THAT file refers to the actual media you just "bought". Which in this case is hosted via a @cloudinary CDN, served by Nifty's servers again.
So if Nifty goes bust, your token is now worthless. It refers to nothing. This can't be changed.
"But you said some use IPFS!"
Let's look at the $65m Beeple, sold by Christies. Fancy.
https://t.co/1G9nCAdetk
That NFT token refers directly to an IPFS hash (https://t.co/QUdtdgtssH). We can take that IPFS hash and fetch the JSON metadata using a public gateway:
https://t.co/CoML7psBhF
