4 ms·

Thanks for the question! Graphite Publishing only uses blockchain for user identity. And even then, a user creating an account doesn't really see that in the ex

Thanks for the question! Graphite Publishing only uses blockchain for user identity. And even then, a user creating an account doesn't really see that in the experience. All data is stored in the storage hub of the user's choosing rather than being stored in a database centralized to Graphite Publishing. In fact, Graphite Publishing doesn't have access to anyone's data. But you're right, a blockchain is not necessary for decentralized blogging and is not used for data storage at all in this app.

amelius 8y ago
Can't it use standardized technology for auth / user identity? I suspect most users don't like dealing with multiple services for the same thing.
- jhunter1016 8y ago
  It absolutely could, but then you're giving ownership to whoever manages that authentication service. Since the creation of your username is what creates your key pair, you own your encryption keys. And since your username is anchored to the bitcoin blockchain, there is no central authority that can say "you no longer have access to this account." Logging in with Google or Facebook or any other third party service is probably the biggest problem with traditional apps. Perhaps more so than them storing your data. Sure, they can (and have sold user data), but if these providers are the owners of your digital identity, they also control whether or not you have access. Slack, Twitter, Google, et al have been known to lock people out of their accounts without warning.
- bcdoubter 8y ago
  And when somebody takes your existing chain then generates a bunch of new users in a 51% attack, how do you recover the usernames on the alternate chain? edit: sorry for reply to wrong post. Should have responded to jhunter1016 below.
  - stdcli 8y ago
    The nice thing about Blockstack is it is not dependent on any one Blockchain. It can be ported to other blockchains and has been previously. Right now it sits on top of bitcoin as it is very hard to perform a 51% attack. if Bitcoin was under 51% attack, then we would simply accept the name state on the best fork. To learn more about how we would handle this case, you can look here: https://forum.blockstack.org/t/bitcoin-network-disruption/1344 https://forum.blockstack.org/t/bitcoin-network-disruption/13... Blockstack Core implements BNS and Atlas, the storage routing system for Gaia. Blockstack Core nodes form the backbone of the Blockstack network. Each node indexes the Bitcoin blockchain and maintains a full replica of all names, public keys, and storage routing information. This makes the Blockstack network particularly resilient to node failure---applications only need to talk to a single Blockstack Core node to work, and a new or recovering node can quickly reconstruct all of its missing state from its peers. All Atlas nodes lie on top maintain a 100% state replica, and they organize into an unstructured overlay network. The unstructured approach is easier to implement, has no overhead for maintaining routing structure and is resilient against targeted node attacks. When a new Atlas node boots up, it first gets the index of all data keys and hashes of values stored in the blockchain. After getting the index, Atlas nodes talk to their peers to fetch key/value pairs they dont have. The Atlas network implements a K-regular random graph. Let us know if you have any more questions.

amelius 8y ago

Can't it use standardized technology for auth / user identity? I suspect most users don't like dealing with multiple services for the same thing.

jhunter1016 8y ago
It absolutely could, but then you're giving ownership to whoever manages that authentication service. Since the creation of your username is what creates your key pair, you own your encryption keys. And since your username is anchored to the bitcoin blockchain, there is no central authority that can say "you no longer have access to this account." Logging in with Google or Facebook or any other third party service is probably the biggest problem with traditional apps. Perhaps more so than them storing your data. Sure, they can (and have sold user data), but if these providers are the owners of your digital identity, they also control whether or not you have access. Slack, Twitter, Google, et al have been known to lock people out of their accounts without warning.
bcdoubter 8y ago
And when somebody takes your existing chain then generates a bunch of new users in a 51% attack, how do you recover the usernames on the alternate chain? edit: sorry for reply to wrong post. Should have responded to jhunter1016 below.
- stdcli 8y ago
  The nice thing about Blockstack is it is not dependent on any one Blockchain. It can be ported to other blockchains and has been previously. Right now it sits on top of bitcoin as it is very hard to perform a 51% attack. if Bitcoin was under 51% attack, then we would simply accept the name state on the best fork. To learn more about how we would handle this case, you can look here: https://forum.blockstack.org/t/bitcoin-network-disruption/1344 https://forum.blockstack.org/t/bitcoin-network-disruption/13... Blockstack Core implements BNS and Atlas, the storage routing system for Gaia. Blockstack Core nodes form the backbone of the Blockstack network. Each node indexes the Bitcoin blockchain and maintains a full replica of all names, public keys, and storage routing information. This makes the Blockstack network particularly resilient to node failure---applications only need to talk to a single Blockstack Core node to work, and a new or recovering node can quickly reconstruct all of its missing state from its peers. All Atlas nodes lie on top maintain a 100% state replica, and they organize into an unstructured overlay network. The unstructured approach is easier to implement, has no overhead for maintaining routing structure and is resilient against targeted node attacks. When a new Atlas node boots up, it first gets the index of all data keys and hashes of values stored in the blockchain. After getting the index, Atlas nodes talk to their peers to fetch key/value pairs they dont have. The Atlas network implements a K-regular random graph. Let us know if you have any more questions.