+ I give some money to a registrar, and ask them to register/renew/transfer 'gavinandresen.dianna'
+ The registrar makes sure the register/renew/transfer operation is valid
+ The registrar bundles up a bunch of register/renew/transfer operations and then asks/pays a Bitcoin miner to merge-mine that hash to securely timestamp those changes
+ After they're timestamped, the registrar asks that all of those record changes be inserted into a shared distributed hash table, providing the DIANNA proof-of-work and the bitcoin block hash.
+ The nodes maintaining the shared DHT make sure the records have the right DIANNA proof-of-work, that the bitcoin block is valid, and that the changes aren't over-ridden by a later bitcoin block, and then update the records.
This is totally something new. My interpretation:
We will separate all participants by group:
1. Clients - they want domains
2. Mining pools - they do timestamping
3. Storage pools - they save the timestamped blocks
4. Need possible coordinators - registars. They take money from clients, pay part to miners for timestamping and pay part to storages for saving. And some part leave for themselfs.
The money will be any external financial structure: bitcoin or fiat - this is up to registars what to accept and how to pay to storage and miners pools. And not be an internal of system.
The DIANNA's block chain (to be stored at storage pools) is similar to bitcoin, but:
- Need to store only last TTL full blocks, all others are kept on each storage as headers. Since block with domains expires - system not need to know the full block, so block goes to history as its header.
- Instead of coin transactions there will be a domain transactions
The possible problem here is how to make consistent block chain of last TTL block distributed by storage pools.