thanks for the email, i was pretty pumped when i got it but ... damn, i thought you only sent this a week or so ago... lol. sorry for the lag.
would love to chat with you about it.
i want to sell Hyperdex UUID's (HUUID) like they sell ipv4 addresses. each Hyperdex UUID would reference essentially a row of data somewhere in the confederated Hyperdex. I am thinking of selling the UUID and then offering a dns/bind-style lookup that would allow someone to translate HUUID -> ip address + port where the service lives to retrieve that row of data.
for the lookup data i was thinking about the following:
element | description |
HUUID | this is the id i want to sell |
data definition | HUUID of the data definition for this record {{define term}} |
hash | hash of the initial data in the create of the record |
timestamp | unix timestamp nanosecond of initial create |
pubkey | Public key of the record (or owner of the record?) |
service address | ip addres of the service |
service protocol | protocol of the service that returns the data |
the actual “data-data” lives at the end of the service address.
uhhh, this got into pretty deep water already.. into questions on the Hyperdex UUID design. this might require more than an email (oh, its now a Notion page). if i want every record to have its own crypto wallet functionality. do i add an element w/ a bitcoin address? .... or do i craft my own crypto wallet? or do i make HUUID's crypto wallet compatible? its still blows my mind that there are not bitcoin address collisions. I was thinking of making HUUID's pretty straight numerical, but maybe i do crypto address compatible w/ some error correcting in there too.
and a question on the pubkey? i did some research and its pretty clever how bitcoin does it, basically each pubkey only “flashes” on the blockchain at the time of the transaction, and then its confirmed, and the world moves on- they keep it hidden so the adversary doesn't have all the time in the world to crack it. my question is this necessary?
my follow-up research:
https://en.bitcoin.it/wiki/BIP_0032
https://en.bitcoin.it/wiki/Bech32
i kinda want to implement the lookup service as an oracle sitting on top a blockchain to allow the owners to do all the updating on their own (changing the ip addresses)