🤯 

 By assembling by the bits randomly you end up with a 256-bit number, a #bitcoin #privatekey (you would check it is within the domain of possible keys)

Each side is numbered

Use the key to generate receive addresses, #bitcoin public keys (l#npub ‘s, too), even sign transactions at some point

Since your key is made completely offline you don’t have to worry about hacking 

 How about the check sum? 

 Works fine👍🏻—this #bitcoin key is the 256-bit integer, so no checksum needed 

 So it works every time?

You would have to enter each 1 or 0 into a wallet manually to get any use out of it right? Aren't you afraid of making a mistake?  

 Next is to build a signer or address generator to do it automatically ala seedsigner or crux/maix, but in the meantime I made a spreadsheet to help translate the private key into public keys/npub/addresses—you can use any tool to do this and of course #offline is best

Converting 256 bits into digital form is easier than you expect—took about two or three minutes.  You quadruple check, to be sure, as you would for anything of value, and of course you have backups 

 Its interesting as it looks like you start with the backup, then move into the digital space. 

Pretty cool!

How about a passphrase? I guess that would have to be on a separate piece. 

 Not sure I understand the questions—there are 256 bits to the integer, and 256 bits on this key

Depending on the orientation when randomly placed into the key the bit is set as a 1 or a 0

I include a few extra bits in case some get lost under a cushion 

 Choosing between 128x ones and 128x zeros would be less random than choosing between 200x ones and 200x zeros. 

 There are 256 bits for this #bitcoin #privatekey

Each individual bit can be either a 1 or a 0, depending on how it is placed into the key

This eliminates the problem I think you are highlighting 

 Ahh, OK. Yes, its hard to see exactly what's going on here. 

 Yes, I move pretty fast😉