You might also be able to just write out instructions. E.g. it seems clear that each glyph encodes 11 bits of information because there are 11 potential strokes in each glyph. The table says what stroke to apply when the bit is 00000000001, 00000000010, 00000000100, etc., so you can probably just write down 11 indicators of what the strokes mean and a copy of the actual bip39 list and a sentence or two saying "go through the word list and increment an 11 bit number every time you encounter a word. The glyphs are the words you need." Then you'll have everything you need to reconstruct your seed.
Funny how none of the bitcoiners thought to back this up on the BTC blockchain ... and instead think about saving it to PDF/Email...as if those won't be lost with time potentially.
I'd probably do as supertestnet says and backup the algorithm which explains how to get the binary bits out of glyphs and how that relates to bip39 list, which I assume I'd be able to pull up from the internet at any point in the future.
Then I'd probably link to the block/tx where I stored the data to "decrypt" the cypher.
If your data no longer exists on Bitcoin Ledger, most likely your bitcoin you're attempting to recover won't be worth anything anyways at that point... so I'd consider this a reasonable way to back up this information long term.
And where do you store the reference link of the transaction? Somewhere you can lose it? Saving it to the blockchain is not appealing in terms of cost/benefit. I would rather save it on Github and Gitlab if redundancy is needed for example, and why not locally. It is free if you already have an external backup drive.
Yes is really interesting method to hide the seed. The question is: where do you hide also the decoding sheet? Because without that one, your seed is worthless.
Doing so does not increase security, but increases the risk of loss.
Unless we make a backup of the website.
You might also be able to just write out instructions. E.g. it seems clear that each glyph encodes 11 bits of information because there are 11 potential strokes in each glyph. The table says what stroke to apply when the bit is 00000000001, 00000000010, 00000000100, etc., so you can probably just write down 11 indicators of what the strokes mean and a copy of the actual bip39 list and a sentence or two saying "go through the word list and increment an 11 bit number every time you encounter a word. The glyphs are the words you need." Then you'll have everything you need to reconstruct your seed.
Funny how none of the bitcoiners thought to back this up on the BTC blockchain ... and instead think about saving it to PDF/Email...as if those won't be lost with time potentially.
I'd probably do as supertestnet says and backup the algorithm which explains how to get the binary bits out of glyphs and how that relates to bip39 list, which I assume I'd be able to pull up from the internet at any point in the future.
Then I'd probably link to the block/tx where I stored the data to "decrypt" the cypher.
If your data no longer exists on Bitcoin Ledger, most likely your bitcoin you're attempting to recover won't be worth anything anyways at that point... so I'd consider this a reasonable way to back up this information long term.
Reference Talk: "Jason Lowery - Softwar (MIT 2023)"
And where do you store the reference link of the transaction? Somewhere you can lose it?
Saving it to the blockchain is not appealing in terms of cost/benefit. I would rather save it on Github and Gitlab if redundancy is needed for example, and why not locally. It is free if you already have an external backup drive.
After inscription, the plates resemble to some of the ancient findings of Archeology.
Yes is really interesting method to hide the seed.
The question is: where do you hide also the decoding sheet?
Because without that one, your seed is worthless.
😅🧐 this
I suppose as long as this website is up you'll be able to decode it right?
hahaha good point :)
You could also make a local copy of the website („Save as PDF“) and store it in the cloud/send it to yourself via email.
Some options to make a back up of a simple website such as this one
🫡
Smart. This and the seedqr, I like both ways.