pull down to refresh
131 sats \ 3 replies \ @TonyGiorgio 22 Feb
This type of solution is almost as old as Bitcoin. In the end, anything that requires on chain human readable identities is not going to work. It's unattainable and absolutely should not have the word scalable in the name.
reply
0 sats \ 0 replies \ @ca98am79 OP 22 Feb
We spent a year making absolutely sure it is scalable so I would be very interested to know why you think it isn't. Did you see that the on chain spaces are limited to 3600 per year and subspaces can be scaled off chain to billions
reply
0 sats \ 0 replies \ @Coinosphere 22 Feb
deleted by author
reply
0 sats \ 0 replies \ @ca98am79 OP 22 Feb
deleted by author
reply
47 sats \ 0 replies \ @go 22 Feb
huh@meh
reply
232 sats \ 0 replies \ @co574 22 Feb
this is a big step forward!
#kudos to the team
reply
10 sats \ 0 replies \ @hasherstacker 22 Feb
Fascinating.
reply
0 sats \ 0 replies \ @andy 9 Jul
Some questions:
- How does a subspace Certificate get shared off chain? Does the Operator of the Space have to have an open TCP or UDP port for spacesd to serve some data to find that subspace? Is there another peer to peer messaging protocol that is part of Spaces? The section https://spacesprotocol.org/paper/#record-storage seems very open ended.
- If so, how does a third party know the IP address of the Operator? Seems like there needs to be some discovery method.
- If this is to serve as a decentralized DNS, how is the equivalent record published by the Space Operator or subspace Operator?
- How does this work with nostr if nostr relies on DNS, SSL, and centralized CAs?
reply
0 sats \ 0 replies \ @joda 22 Feb
I'd be worried about the b0b@ and 1inda@ scams
reply
0 sats \ 0 replies \ @TNStacker 22 Feb
deleted by author
reply