5 ms·

You are making an assumption about how blockchains work. Do you think the linked-list like structure of how blocks are added to the chain is how data is stored

You are making an assumption about how blockchains work. Do you think the linked-list like structure of how blocks are added to the chain is how data is stored and retrieved? For reference: https://en.bitcoin.it/wiki/Bitcoin_Core_0.11_(ch_2):_Data_Storage https://en.bitcoin.it/wiki/Bitcoin_Core_0.11_(ch_2):_Data_St... https://hackernoon.com/getting-deep-into-ethereum-how-data-is-stored-in-ethereum-e3f669d96033 https://hackernoon.com/getting-deep-into-ethereum-how-data-i...

zelly 7y ago
I'm aware it is implemented more efficiently. The problem it is trying to solve is orthogonal to what DNS does: search vs. verification. DNS needs to resolve an name on the order of nanoseconds across a distributed system. It is designed with this in mind. A blockchain is designed with integrity in mind. Wallets can verify transactions on the order of nanoseconds with SPV--also distributed because a client can get the intermediate block headers from any server. Querying data, like for DNS, has constraints different from verifying integrity, like for a ledger. Sure, you can use a blockchain for storage, but who do you trust to do the lookups? It can't be on chain because it will be far too slow. You'd end up having to trust some entity like Cloudflare to run a DNS-on-blockchain node that stores the ground truth, going full circle back to regular DNS. What's the equivalent of SPV for DNS-on-blockchain where I can do and verify name resolution with limited resources?
- decentralised 7y ago
  In terms of access time, the standard would be O(1) for hashtables which would be my best guess at how to best represent an ip to domain mapping. Reading from on chain data is done locally (if you have your own node) and is near instant, but for wider reach I think DNS over HTTP would be needed or wasm clients that can be run in a browser. Here is a possible implementation in Ethereum: https://medium.com/the-ethereum-name-service/ethdns-9d56298fa38a https://medium.com/the-ethereum-name-service/ethdns-9d56298f...

zelly 7y ago

I'm aware it is implemented more efficiently. The problem it is trying to solve is orthogonal to what DNS does: search vs. verification. DNS needs to resolve an name on the order of nanoseconds across a distributed system. It is designed with this in mind. A blockchain is designed with integrity in mind. Wallets can verify transactions on the order of nanoseconds with SPV--also distributed because a client can get the intermediate block headers from any server. Querying data, like for DNS, has constraints different from verifying integrity, like for a ledger. Sure, you can use a blockchain for storage, but who do you trust to do the lookups? It can't be on chain because it will be far too slow. You'd end up having to trust some entity like Cloudflare to run a DNS-on-blockchain node that stores the ground truth, going full circle back to regular DNS. What's the equivalent of SPV for DNS-on-blockchain where I can do and verify name resolution with limited resources?

decentralised 7y ago
In terms of access time, the standard would be O(1) for hashtables which would be my best guess at how to best represent an ip to domain mapping. Reading from on chain data is done locally (if you have your own node) and is near instant, but for wider reach I think DNS over HTTP would be needed or wasm clients that can be run in a browser. Here is a possible implementation in Ethereum: https://medium.com/the-ethereum-name-service/ethdns-9d56298fa38a https://medium.com/the-ethereum-name-service/ethdns-9d56298f...