Consolidate all the FAQS
mitchell [1:16 PM]
lets go ahead and push, freddie is good with the foundation piece there will be updates in the coming days, but this is way way better than current and really close
This is a general FAQ intended for users of decentralized applications. If you are a developer, refer to the [technical FAQ].
This is a FAQ intended for users of decentralized applications. A comprehensive list of FAQs that touch on general, technical, and App Mining questions is [also available]({{site.baseurl}}/faqs/allFAQS.html).
* TOC
{:toc}
## What is the decentralized internet?
The Blockstack ecosystem enables the new decentralized internet. Decentralization means authority moving from central authority to local authority. Simply put, in a decentralized internet, you own your data, not the applications or services you use.
Blockstack envisions a world where users control their own data, and power flows back to the users. For example, when you buy something from an online company, that company collects and stores data about you:
* your name
* the information about the product you bought
* the number on your credit card
In the decentralied internet, that information stays with you and it isn't
collected or stored by anyone. Applications that operate in the decentralized
internet are called _decentralized applications_ or DApps for short.
## What is Blockstack?
Blockstack is an ecosystem to support both DApp users and DApp developers. For
users, Blockstack makes software to create Blockstack identities and find DApps.
For developers, Blockstack develops an ecosystem of software and services that developrs can use to build DApps.
## How do DApps differ applications I typically use?
DApps differ from Web applications in two ways:
* **Users have identities not accounts**. The user brings their identity to the
applications; applications do not require the user to create accounts and
passwords.
* **Users own their data**. Users control access to their data. Users decide where to store their data and which applications can read or write to your. Companies and their decentralized applications don't keep or save your data.
## Where is my identity kept?
Your identity is a unique string you and other people can read such as `moxiegirl.id`. A private key is a string of letters only you know. When you create an identity, a **hash** is made of your id and your private key registered with Blockstack.
Your personal data storage is built around this ID. Apps that want to access your data use your permission and identity to find it.
You have to remember and keep your private key in a safe place like a password manager. If you lose a private key, _no one else, no person, no software, can help you get your identity back_.
## Can Blockstack control my data or ID when I use it?
No. When you're using a Blockstack client you control your data and ID with a
private key. As long as no one gets access to your private key, no one can
control your data or ID. When you use Blockstack, by design, your private keys
are never sent to any remote servers.
## Do DApps work with a regular browser?
Yes! DApps run in the web browsers (Chrome, Safari, Internet Explorer, etc.) you know and love.
## What is the Blockstack Browser?
The Blockstack Browser is the DApp users use to create and manage their identities and configure their data storage. The browser is also where users can go to discover and use apps using Blockstack.
The Blockstack Browser also handles login requests from DApps that allow their users to log in with Blockstack. When a user clicks a **Log In with Blockstack** button, they are redirected to the Blockstack Browser to approve the request before being logged into the app.
## Are Blockstack applications usable today?
Yes! Blockstack applications are as easy to use as normal Web applications, if
not easier. Moreover, they are just as performant if not more so.
If you install the [Blockstack
Browser](https://github.com/blockstack/blockstack-browser), or use our
[Web-hosted Blockstack Browser](https://browser.blockstack.org), you can get
These FAQs are intended for developers of Blockstack.
This document lists frequently-asked questions developers about Blockstack application development. If you are new to Blockstack, you should read the [general questions]({{site.baseurl}}/faqs/allFAQs.html) first.
* TOC
{:toc}
## I'm a web developer. Can I build on Blockstack?
Yes! Blockstack is geared primarily towards web developers. All of your
existing knowledge is immediately applicable to Blockstack. Anything you can do
in a web browser, you can do in a Blockstack app.
## I'm a non-web developer. Can I build on Blockstack?
Yes! Blockstack implements a [RESTful API](https://core.blockstack.org) which
lets you interact with Blockstack from any language and any runtime. In fact,
the reference client
([blockstack.js](https://github.com/blockstack/blockstack.js)) is mainly a
wrapper around these RESTful API calls, so you won't be missing much by using a
language other than Javascript.
## What's the difference between a web app and a Blockstack app?
Blockstack apps are built like [single-page web
apps](https://en.wikipedia.org/wiki/Single-page_application)--- they are, in
fact, a type of web application.
Blockstack apps are a subset of web applications that use Blockstack's
technology to preserve the user's control over their identities and data. As
such, they tend to be simple in design and operation, since in many cases they
don't have to host anything besides the application's assets.
## Do I need to learn any new languages or frameworks?
No. Blockstack applications are built using existing web frameworks and programming
The only new thing you need to learn is either [blockstack.js](https://github.com/blockstack/blockstack.js) or
the [Blockstack RESTful API](https://core.blockstack.org).
## How does my web app interact with Blockstack?
The [blockstack.js](https://github.com/blockstack/blockstack.js) library gives
any web application the ability to interact with Blockstack's authentication and
storage services. In addition, we supply a [public RESTful API](https://core.blockstack.org).
## What does `blockstack.js` do?
This is the reference client implementation for Blockstack. You use it in your
web app to do the following:
* Authenticate users
* Load and store user data
* Read other users' public data
## How do I use `blockstack.js`?
We have [several examples](/browser/hello-blockstack.html) you can use to get started. Please see the API documentation [here](https://github.com/blockstack/blockstack.js).
## How can I look up names and profiles?
You can use `blockstack.js`, or you can use the [public Blockstack Core
endpoint](https://core.blockstack.org).
For more technical FAQs about Blockstack Core nodes, the Stacks blockchain, and other architectural elements, see the [entire set of technical FAQs]({{site.baseurl}}/core/faq_technical.html).
## How can I read my public app data without `blockstack.js`?
If you have a technical question that gets frequently asked on the
[forum](https://forum.blockstack.org) or [Slack](https://blockstack.slack.com),
feel free to send a pull-request with the question and answer.
The URLs to a user's public app data are in a canonical location in their
profile. For example, here's how you would get public data from the
[Publik](https://publik.ykliao.com) app, stored under the Blockstack ID `ryan.id`.
This document lists frequently-asked questions by developers interested in working with Blockstack application and core components. If you are new to Blockstack, you should read the [general questions]({{site.baseurl}}/faqs/allFAQs.html) first.
If you have a technical question that gets frequently asked on the
[forum](https://forum.blockstack.org) or [Slack](https://blockstack.slack.com),
feel free to send a pull-request with the question and answer.
## Who should build on Blockstack?
Everyone! But more seriously, if you are building an application in JavaScript
that requires sign-in and storage you should look at using Blockstack. The APIs
we provide are not only decentralized (No dependency on Google, Facebook, or
other OAuth provider) but easier to use than traditional OAuth. Also you no
longer have to maintain and secure databases with all your user information.
That data is stored securely with the people who created it.
## What is a "serverless" app?
The application itself should not run application-specific functionality on a server. All of its functionality should run on end-points. However, the application may use non-app-specific servers with the caveat that they must not be part of the trusted computing base. This is the case with storage systems like Amazon S3 and Dropbox, for example, because Blockstack's data is signed and verified end-to-end (so the storage systems are not trusted to serve data). Serverless can also mean applications where some amount of server-side logic is still written by the application developer but unlike traditional architectures is run in stateless compute containers that are event-triggered, ephemeral (may only last for one invocation)
## How are Blockstack domains different from normal DNS domains?
Blockstack domains are not registered on the traditional DNS run by an organized called ICANN. Instead they're registered on a blockchain in a fully decentralized way. This means that Blockstack domains are truly owned by their owners and cannot be taken away. All Blockstack domains have public keys by default (public keys are required to own the domains), unlike the traditional DNS where a small fraction of domains get the (optional) public key certificates.
## What is a virtual chain?
Blockstack is designed around a "virtual chain" concept, where nodes only need to reach consensus on the shared "virtual chain" they're interested in. Virtual chains do not interact with one another, and a single blockchain can host many virtual chains. These virtual chains can live in any blockchain for which there exists a driver, and virtual chain clients only need to execute their virtual chain transactions (i.e. Blockstack only processes Blockstack virtual chain transactions).
## What is Blockstack Core and who is working on it?
Blockstack Core is the reference implementation of the Blockstack protocol described in our white paper. It consists of a couple of parts:
- Virtualchain implementation: This is a python library that parses the underlying blockchain (Bitcoin) and builds the state of the Blockstack DNS.
- Blockstack Core: Uses the Virtualchain to build the DNS state and comes to a consensus on that state in a peer network (Atlas).
- Blockstack API: Indexes the data stored by Blockstack Core and makes it available in a performant way to applications.
The project is open-source and anyone can contribute! The major contributors are mostly employees of Blockstack PBC. You can see the full list of contributors here: https://github.com/blockstack/blockstack-core/graphs/contributors
## How is Blockstack different from Ethereum for building decentralized apps?
You can think of Ethereum as a "heavy" blockchain that does everything for you. All the complexity is handled on-chain, computations are run there, and all scalability and security concerns need to be handled at the blockchain level. It amounts to a "mainframe" that runs all the applications in the ecosystem.
Blockstack puts minimal logic into a blockchain and handles scalability outside of the blockchain by re-using existing internet infrastructure. Our architectural design mirrors how computing has developed; moving from mainframes to smaller networked entities.
Read more about the differences between Blockstack and Ethereum dapps in the following forum post: https://forum.blockstack.org/t/what-is-the-difference-between-blockstack-and-ethereum/781/2
## Can Blockstack only run on Bitcoin?
The model we're currently exploring is where Blockstack can process multiple blockchains to construct the global state where each namespace is tied to a single blockchain. Meaning that say the .id namespace is defined to run on Bitcoin and a .eth namespace is defined to run on Ethereum. Blockstack can process transactions from both blockchains and update the state of namespaces, but the consistency of any given namespace depends only on the underlying blockchain it was defined on.
## Does Blockstack use a DHT (Distributed Hash Table)?
It does not, as of November 2016. It uses a much more reliable system called the Atlas Network. Details here: https://blog.blockstack.org/blockstack-core-v0-14-0-release-aad748f46d#.30gzlthdw
## Can the Blockstack network fork?
Yes, the Blockstack network can fork if the underlying blockchain encounters a deep fork. In this case, blockstack nodes on either side of the fork will diverge from one another.
We have yet to encounter a deep fork. If this does happen, then Blockstack will use the virtualchain state on the majority fork once the fork resolves.
We also hard fork the network once a year to make protocol breaking changes and upgrade the network. The last one of these happened on block `488500` on the bitcoin blockchain. There are more details about the fork in this forum post: https://forum.blockstack.org/t/blockstack-annual-hard-fork-2017/1618
## How is the Blockstack network upgraded over time? What parties need to agree on an upgrade?
We're working on an on-chain voting strategy similar to how mining works, where anyone can cast a vote proportional to the amount of Bitcoin burned. Similar to how Bitcoin upgrades, a new feature will activate if a certain threshold (e.g. 80%) of votes consistently request its adoption over a given time interval (e.g. a couple weeks).
Until then, we will publicly announce the availability of new software, with the promise that each release will bring highly-desired features to make upgrading worth the users' whiles.
## Who gets the registration fees for name registrations?
With the current design, names are purchased by paying tribute with Bitcoin mining fees.
## Where are the current core developers based? What are the requirements for being a core developer?
Most of the core developers work in NYC and Hong Kong. Developers who've contributed to the [core open-source software](https://github.com/blockstack/blockstack-core) over a long enough time period, by default, get included in the list of core developers. There is no formal process for being part of this informal list. Core developers, generally, have the ability to write high-quality code, understand distributed systems and applied crypto, and share a vision of building a truly decentralized internet and are dedicated to that cause.
## I heard some companies working on Blockstack have raised venture capital, how does that impact the project?
Blockstack, like Linux, is an open-source project with a GPLv3 license for the core technology. Just like different companies build apps and services on top of Linux and have different individual business models, there are companies who're building apps & services for Blockstack on top of the core open-source technology and these companies have various business models and funding sources respectively. Having more venture-backed companies join the ecosystem for a decentralized internet is a good thing for everyone participating in the ecosystem including users and developers.
## Where is my data stored and how do I control who access it?
You control where your data is stored (you could run your own server, or use your own cloud storage - Dropbox, Amazon S3, and keep backups across all). You then use those places as locations pointed to by the URLs in your Blockstack ID's zone file.
## Why should I trust the information, like name ownership or public key mappings, read from Blockstack?
Blockstack records are extremely hard to tamper with. This is because the bindings for name ownership (names on Blockstack are owned by public keys) are announced in a proof-of-work blockchain (Bitcoin) and to change these binding an attacker will need to come up with a blockchain with more proof-of-work than the current Bitcoin blockchain but with a different history. Bitcoin's [current hash rate](https://blockchain.info/charts/hash-rate) makes this task almost impossible for non-state actors.
## Can anyone register a TLD?
Yes, anyone can register a TLD. If a TLD has not been registered already and you're willing to pay the registration fee for it, you can go ahead and register that TLD. There is no centralized party that can stop you from registering a TLD.
## What programming language can I use to build these apps?
To make apps that run in the web browser using Blockstack, you can use JavaScript and any of the same web frameworks or libraries you use today such as React, AngularJs, Vue.js or jQuery. The Blockstack Core is implementated in Python, but you can use any language you like for native apps as long as you are able to consume a JSON REST API.
## Do I need to run a full Blockstack node to use Blockstack?
tl;dr: You don't, but its very easy to.
To reduce the overhead involved in getting started we maintain a fleet of Blockstack Core nodes that your Blockstack applications connect to by default. If you want to run your own we provide detailed instructions on our [install page](https://blockstack.org/install). It only takes about 5-10 minutes to spin up your full node!
## What is the capacity per block for registrations using Blockstack?
Initial registrations can be done at an order of hundreds per block and once an identity is registered you can do “unlimited” updates to the data because that is off-chain. We’re also working on a more scalable solution where a very large number of identities can be registered but that’s not live yet and is in the pipeline as a rough benchmark. in summer 2015, Blockstack did 30,000+ identity registrations in a matter of few days live on the blockchain and Blockstack was actually throttling its servers and not taking up more than 100-200 transactions per block. It could’ve easily taken up more transactions without impacting the network.
## What language is the Blockstack software written in?
Python 2 and Node.js
## What incentives are there to run a Blockstack node?
Running a Blockstack node keeps you secure by ensuring that your app gets the right names and public keys. It's not expensive; it takes as much resources as a Chrome tab.
## Can Blockstack apps scale, given that Blockstack uses blockchains which don't scale that well?
Yes. Blockstack only uses the blockchain for name registration. Everything else happens off-chain, so apps work just as fast as they do on the Web.
## What if the current companies and developers working on Blockstack disappear, would the network keep running?
Yes, the Blockstack network will keep running. All of Blockstack's code is open-source and anyone can deploy Blockstack nodes or maintain the code. Further, Blockstack nodes don't need to coordinate with each other to function. Any node that a user deploys can function correctly independently.
## Where does Blockstack keep my app data?
As a Blockstack user, you can choose exactly where your data gets stored.
Blockstack uses a decentralized storage system called
[Gaia](https://github.com/blockstack/gaia) to host your data. Gaia is different
from other storage systems because it lets you securely host your data wherever you want — in cloud
software providers, on your personal server, or in another decentralized storage
system like BitTorrent or IPFS.
When you register, you are given a default Gaia hub that replicates your
data to a bucket in Microsoft Azure. However, you can configure and
deploy your own Gaia hub and have Blockstack store your data there instead.
The [Blockstack Naming Service]({{ site.baseurl }}/core/naming/introduction.html) and the [Atlas network]({{ site.baseurl }}/core/atlas/overview.html) work together to help other users discover your
app-specific public data, given your Blockstack ID.
* TOC
{:toc}
## What is a Blockstack Subdomain?
## DApp developers
This is also a Blockstack ID, and can be used for all the things a Blockstack ID
can be used for. The only difference is that they have the format `foo.bar.baz`
instead of `bar.baz`. For example,
[jude.personal.id](https://core.blockstack.org/v1/users/jude.personal.id) is a
Blockstack ID, and is a subdomain of `personal.id`.
{% for faq in site.data.theFAQs.faqs %}
{% if faq.category == 'dappdevs' %}
### {{ faq.question }}
{{ faq.answer }}
{% endif %}
{% endfor %}
Subdomains are first-class Blockstack IDs---they can be used for all the same
things that an on-chain Blockstack ID can be used for, and they have all of
the same safety properties. They are globally unique, they are strongly owned
by a private key, and they are human-readable.
Subdomains are considerably cheaper than Blockstack IDs, since hundreds of them
can be registered with a single transaction. The [BNS
documentation]({{ site.baseurl }}/core/naming/introduction.html) describes them in detail.
## Core developers
Subdomains provide a fast, inexpensive way to onboard many users at once.
{% for faq in site.data.theFAQs.faqs %}
{% if faq.category == 'coredevs' %}
### {{ faq.question }}
{{ faq.answer }}
{% endif %}
{% endfor %}
## Can I get a Blockstack ID without spending Bitcoin?
## Open source developers
Blockstack subdomains can be obtained without spending Bitcoin
by asking a subdomain registrar to create one for you.
The Blockstack Ecosystem has a mission to bring a new internet where users
control the access to, and use of, their own identity and data. With this
mission in mind, three independent entities were formed:
Blockstack is a full-stack decentralized computing network that enables a new generation of applications where developers and users can interact fairly and securely. Blockstack uses blockchain technology to build protocols and developer tools designed to enable a fair and open Internet that returns digital rights to developers and consumers.
* TOC
{:toc}
These three affiliated entities drive the advancement of the Blockstack mission.
In this section, you learn about the mechanisms each entity uses to advance the
overall mission.
## What is the Blockstack Ecosystem?
The Blockstack Ecosystem is the legal entities and community structures that support the Blockstack technology, the apps that rely on it, and the people that work with it. The ecosystem’s mission is to foster an open and decentralized Internet that establishes and protects privacy, security and freedom for all users.
## Blockstack Public Benefit Corp (PBC)
The documentation on this site focuses on the technologies produced by three entities in the ecosystem.
### Blockstack Public Benefit Corp (PBC)
Blockstack Public Benefit Corp. (PBC) started development of the Blockstack
platform in 2014 and launched an alpha of the platform in early 2017. The
@ -38,11 +36,11 @@ Using Blockstack’s technology developers can start building immediately on the
blockchain with the knowledge you have today. You won’t need to spend time or
effort developing expertise in specialized languages or technologies.
## Blockstack Signature Fund
### Blockstack Signature Fund
{% include signature_fund.md %}
## Blockstack Token LLC
### Blockstack Token LLC
Through the 2017 Blockstack token offering, Blockstack Token LLC created the
Stacks token. This year's hard fork is an especially exciting milestone for the ecosystem because it distributes the first Stacks tokens to existing purchasers and recipients. This hard fork launches the Stacks blockchain v1, and enables the following two features for the Blockstack network:
Moxiegirl
6 years ago
GitHub