JUjude-·Jul 12, 2019
Core platform developer here (for 4+ years). Would absolutely work on this project in my spare time if I wasn't already employed at Blockstack PBC. You can also check our various projects' contributor graphs on Github (all under https://github.com/blockstack) if you want to gauge developer interest.
EDIT: providing more context below:
The reason Blockstack appeals to me is because I think it is one of the few projects with a reasonable, sustainable architecture for ensuring that users own all their data. In particular, Blockstack apps with the same performance characteristics as traditional Web applications _while also_ ensuring that users (1) don't have to run their own servers if they don't want to, and (2) don't have to keep their personal devices online 24/7. The storage layer, Gaia, achieves this by leveraging any/all existing stor
Read the rest
age media for hosting and serving the data, including commodity cloud storage and CDNs.
Because users provide the primary replicas of their data, they retain control and ownership of it even if the application goes away, or if they switch applications. Indexes and aggregations of user data -- such as the notions of a Twitter feed or a comment thread -- are treated as downstream, soft-state replicas derived from user data, and can be independently reconstructed by anyone. Blockstack apps nevertheless can easily create such indexes and aggregations with Radiks -- https://github.com/blockstack-radiks.
The blockchain component is buried deep in the stack, and is used today for user discovery: user A can discover user B's public key and URLs to their data. By running a Blockstack node, you learn every user's public keys and URLs. This enables Blockstack apps to encrypt data end-to-end so only its intended recipients can see it (Gaia and its underlying storage media only see ciphertext). Users don't directly interact with the blockchain; this is all handled through the user's Blockstack authenticator (https://github.com/blockstack/blockstack-browser) and through blockstack.js.
The system can handle a large number of users today. Most user registration is handled through a batching mechanism, whereby ~160 name/pubkey/URL triples are announced and replicated to the Blockstack peer network per blockchain transaction. At 8 transactions/block, this yields over 180,000 registrations/day.
The reason to introduce a token is to implement smart contracts, which in turn are meant to allow applications to implement small programs to manage a small amount of global state without needing a dedicated, trusted server. Not all applications will need smart contracts -- in fact, all Blockstack apps today that I know of (see https://app.co/blockstack) get along just fine without them. However, there are a few cases where having a small amount of global state is useful -- for example, if you were to build Reddit on Blockstack, you might have a smart contract that lists a directory of all subreddits and the list of admins who curate them.
A lot of thought, time, and energy has gone into the design and implementation of Blockstack's software stack prior to this sale, and the system has been running successfully in production for 3+ years.