So here it is:
Your node will be tested to see if they indeed do have the whole Bitcoin blockchain stored locally.
Your node will be asked to sign a message of a hash of the whole (or part of the recent) blockchain with the private key to their collateral or whatever it was called.
This stops someone from creating a service that will supply the... Oh... The hash... Damnit this isn't going to work. My original idea was that they need to sign the whole (or part of the recent) blockchain with their private key to their collateral. I guess that would work. But would the signature be really long? I don't really know much about signing messages. I was thinking of using a hash of the blockchain to shorten the message but then someone could supply the hashes to your node. Anyway, yeah, did I solve the problem?
Oh god, while I was writing this I heard a mousetrap go off in the room next to mine. I keep hearing Noises in the room now.
