pull down to refresh

built on bitcoin, very little footprint on the blockchain
cypherpunk (no premine, no separate token, no foundation)
built in a scalable way

reply

where is the data stored then?

reply

subspaces and data related to names can be stored off chain

we have a proof of concept for subspace management here: https://github.com/spacesprotocol/subspacer

you can see how we store data off chain for example with fabric:
https://github.com/spacesprotocol/fabric

reply

how does one find that registry? For DNS we have NS records to know what server to fetch delegated data from. What do we do in spaces to find the relevant server starting from data on the blockchain?

reply

the space owner publishes the zk receipt on chain so all subspace key holders have proof of ownership

reply

Just how small is the blockchain's footprint, really? Can you break down the technical stuff for me?

reply

Most transactions are the size of a regular bitcoin transaction, and limited only to top-level spaces. Subspaces are handled off chain with zero knowledge proofs. So we can scale to billions of subspaces/names with little on chain footprint. The only data stored on chain is the top level space name in the transaction to open the auction. Top level spaces are limited to roughly 10 per day.

reply

but a subspace owner can go on chain whenever they want, or do subspace delegations always stay off chain?

reply

yes they can take their ownership on chain if they want, and it is treated as a top level space

reply

once they go on chain, can they go back off chain?

reply

i think so, yes - if they let the onchain subspace utxo expire and are included in the space owner receipt committed onchain afterwards

reply

can they delegate it back to the space owner without waiting for expiration?