From the readme
4. Publish a kind:60600 event, referencing the above and including a Bitcoin self-transfer as proof.
Login to reply
Replies (4)
Yes, but what I meant to ask is if you can elaborate on how that limits the solution at scale
Well let's say it catches on and is on track to replace the 350 million or so entries in ICANN. At bitcoin's speed of roughly 7 transactions per second that would take like 1.5 years of this to the exclusion of all other transactions
Ah, ok.
DNN doesn't have to replace ICANN, but it can with time assuming people like it. What you said in my eyes is good news actually. In realistic terms, people won't hop on to DNN at the same time, it'll be gradual, slowly but surely people would get a DNN name/ID (if I had to guess when it would have above 50% of the market, it'll probably be 25 to 50 years later).
Though let's assume this scenario where every renter of those 350 million domains suddenly wanted to have their name on DNN, then 2 years or less of waiting (heck, 3 years why not), to move the whole of this massive legacy system to a new one, in one go, in that time frame, and then everything is done? That's fantastic and fast actually.
Would be nicer if it could be done with opentimestamp or something