structured-concept:
Blockstack-network (Blockstack-net)

McsHitp-creation: {2018-12-15} {2017-03-14}

overview of Blockstack-net

description::
Blockstack-network is A-DECENTRALIZED-NETWORK on top of a-blockchain-network for decentralized-apps that let you own your data and maintain your privacy, security and freedom.
[hmnSgm.2018-12-16]
===
"Blockstack is a new internet for decentralized applications that replaces points of centralization from the application layer of the internet; these include DNS root servers, certificate authorities, and centralized data stores."
[https://blockstack.org/tokenpaper.pdf {2017-10-29}]
===
"Our implementation of Blockstack has three components:
1. A blockchain, implemented using virtualchains, is used to bind digital property, like domain names, to public keys. Blockstack’s blockchain solves the problem of bootstrapping trust in a decentralized way i.e., a new node on the network can independently verify all data bindings.
2. A peer network, called Atlas, gives a global index for discovery information and
3. A decentralized storage system, called Gaia, provides high-performance storage backends without introducing central trusted parties."
[https://blockstack.org/whitepaper.pdf {2017-10-12}]

name::
* Mcs.filMcsDtcbnetBlockstack.last.html,
* Mcs.dirTchInf/filMcsDtcbnetBlockstack.last.html,
* Mcs.Blockstack!⇒Blockstack-net,
* Mcs.Blockstack-network!⇒Blockstack-net,
* Mcs.Blockstack-net,
* Mcs.Blockstack-platform!⇒Blockstack-net,

protocol of Blockstack-net

name::
* Mcs.Blockstack-net'protocol,

addressWpg::
* whitepapers: https://blockstack.org/papers,

architecture of Blockstack-net

description::
"Blockstack’s architecture has three layers as shown in Figure 1), with one layer (the blockchain layer) in the control plane and two layers (the peer network and data-storage) in the data plane.
The control plane deals with smaller volumes of data and is mostly concerned with bootstrapping trust [11] and defining the mapping between human-readable names and network resources.
The data plane contains information on how to discover data (routes/pointers to data) and the actual storage backends.
Data is widely replicated and it doesn’t matter from what source clients read data; clients can independently verify from the control plane if they received the correct data or not.
"
[https://blockstack.org/whitepaper.pdf {2017-10-12}]

name::
* Mcs.Blockstack-net'architecture,

control-plane of Blockstack-net

description::
· the-control-plane contains the-blockchain-layer.
"The control plane deals with smaller volumes of data and is mostly concerned with bootstrapping trust [11] and defining the mapping between human-readable names and network resources"
[https://blockstack.org/whitepaper.pdf {2017-10-12}]

name::
* Mcs.Blockstack-net'control-plane,
* Mcs.Blockstack-net'plane.control,

data-plane of Blockstack-net

description::
· the-data-plane contains the-peer-network-layer and the-data-storage-layer.
" The data plane contains information on how to discover data (routes/pointers to data) and the actual storage backends. Data is widely replicated and it doesn’t matter from what source clients read data; clients can independently verify from the control plane if they received the correct data or not."
[https://blockstack.org/whitepaper.pdf {2017-10-12}]

name::
* Mcs.Blockstack-net'data-plane,
* Mcs.Blockstack-net'plane.data,

blockchain-layer of Blockstack-net

description::
· the-blockchain-layer contains the-blockchain and the-virtualchain.
[https://blockstack.org/whitepaper.pdf {2017-10-12}]

name::
* Mcs.Blockstack-net'blockchain-layer,
* Mcs.Blockstack-net'layer-1,
* Mcs.Blockstack-net'layer.blockchain,

peer-network--layer of Blockstack-net

description::
"Layer 2: Peer Network
Blockstack uses a peer network for discovery. The peer network is part of the data plane. Our architecture separates the task of discovering resources (i.e., routes to data) from the actual storage of data. This avoids the need for the system to adopt any particular storage service from the onset, and instead allows multiple storage providers to coexist, including both cloud storage and P2P systems.
The Blockstack implementation uses zone files for storing routing information, which are identical to DNS zone files in their format. The zone files are stored in the discovery layer, implemented as a peer network by Blockstack. Users do not need to trust the discovery layer because the integrity of any data record in the discovery layer can be verified by checking the respective hash of that data record in the control plane.
In Blockstack’s current implementation, nodes form a peer network, called the Atlas network (Section 5), for storing zone files. The peer network only allows zone files to be written if hash (zonefile) was previously announced in the blockchain. This effectively whitelists the data that can be stored in the peer network. Data records representing routes (irrespective of where they are fetched from) can be verified and therefore cannot be tampered with. In the current implementation of the Atlas network, peer nodes maintain a full copy of all zone files since the size of zone files is relatively small (4KB per file). Keeping a full copy of all routing data introduces only a marginal storage cost on top of storing the blockchain data (which is in the order of several GBs)."
[https://blockstack.org/whitepaper.pdf {2017-10-12}]

name::
* Mcs.Blockstack-net'layer-2,
* Mcs.Blockstack-net'layer.peer-network,
* Mcs.Blockstack-net'peer-network--layer,

data-storage-layer of Blockstack-net

description::
"Layer 3: Storage
The top-most layer (layer-3) is the storage layer, which hosts the actual data values and is part of the data plane. All stored data values are signed by an owner key defined in the control plane. By storing data values outside of the blockchain, Blockstack allows values of arbitrary size and allows for a variety of storage backends. Users do not need to trust the storage layer and can verify their integrity in the control plane. Our design benefits from the performance and reliability of the backend cloud storage systems used and offers comparable performance to traditional internet services."
[https://blockstack.org/whitepaper.pdf {2017-10-12}]

name::
* Mcs.Blockstack-net'data-storage--layer,
* Mcs.Blockstack-net'layer-3,
* Mcs.Blockstack-net'layer.data-storage,

Blockstack-Core (link)

description::
· Blockstack-Core is the-reference-implementation of the-Blockstack-protocol.

node of Blockstack-net

description::
"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.
Power users are encouraged to run local Blockstack Core nodes on their laptops or home/office networks in order to have reliable access to the Blockstack network. Your local node maintains the same state as the rest of the Blockstack Core nodes, so it will keep serving names, public keys, and storage routes even if upstream nodes are unreachable or go offline."
[https://github.com/blockstack/blockstack-core#what-is-blockstack-core]
===
"With the Blockstack software, a network of computers collectively maintain a global registry of names. When you run a Blockstack node, you join this network, which is more secure by design than traditional DNS and identity systems. This is because the system's registry and its records are secured by an underlying blockchain, which is extremely resilient against tampering and control."
[https://github.com/blockstack/blockstack#architecture]

name::
* Mcs.Blockstack-net'node,

Blockstack-Core (link)

blockchain-network of Blockstack-net

description::
· the-Blockstack-network works on top of a-blockchain-network.
· Blockstack started using the-Namecoin-blockchain and migrated to Bitcoin-blockchain when it discovered that it could-be under the-control on one miner.
· then the-system re-architectured to be portable across blockchains.
[https://docs.blockstack.org/core/naming/comparison.html#blockstack-vs-namecoin]

name::
* Mcs.Blockstack-net'blockchain-network,

generic-chain::
* blockchain-network,

virtualchain of Blockstack-net

description::
"The blockchain layer also includes a virtualchain, which defines new operations without requiring changes to the underlying blockchain. Nodes of the underlying blockchains are not aware of this layer. Virtualchains are like virtual machines, where a specific VM like Debian 8.7 can run on top of a specific physical machine. Different types of virtualchains can be defined and they run on top of the specific underlying blockchain. Virtualchain operations are encoded in valid blockchain transactions as additional metadata. Blockchain nodes do see the raw transactions, but the logic to process virtualchain operations only exists at the virtualchain level.
The rules for accepting or rejecting virtualchain operations are defined in the specific virtualchain, e.g., a virtualchain which defines a single state machine implementing operations for a global naming system. Operations accepted by rules defined in our virtualchain are processed to construct a database that stores information on the global state of the naming system along with state changes at any given blockchain block."
[https://blockstack.org/whitepaper.pdf {2017-10-12}]

name::
* Mcs.Blockstack-net'virtualchain,

blockchain-migration

description::
"We believe that enabling the ability to migrate from one blockchain to another is important as it allows for the larger system to survive, even when the underlying blockchain is compromised."
[https://blockstack.org/whitepaper.pdf {2017-10-12}]

name::
* Mcs.Blockstack-net'blockchain-migration,

Stacks-blockchain-network of Blockstack-net

description::
"The launch of the Stacks blockchain marks a new era for the Blockstack ecosystem: it is custom designed for the Blockstack network with the goal of enabling developers to easily build decentralized apps that can scale. The hard fork is scheduled to occur on October 30th."
[https://blog.blockstack.org/the-launch-of-the-stacks-genesis-block/]

name::
* Mcs.Blockstack-net'Stacks-blockchain-net,
* Mcs.Blockstack-net'Stacks-net,

Stacks-token

description::
"Stacks is the name of a token developed by Blockstack Token LLC in 2017 and activated in the third quarter of 2018."
[https://docs.blockstack.org/org/token.html]

name::
* Mcs.Blockstack-net'Stacks-token,

addressWpg::
* hello@stackstoken.com,
* https://docs.blockstack.org/org/tokenholders.html,
* https://docs.blockstack.org/org/voucherholder.html,
===
* {2019-07-10} https://blog.blockstack.org/blockstack-token-sale-sec-qualified/,
* {2019-07-10} https://www.wsj.com/articles/sec-clears-blockstack-to-hold-first-regulated-token-offering-11562794848?shareToken=stc9d0bf95c1fb4b0d885b4a67673bbbeb,

Stacks-wallet

addressWpg::
* https://wallet.blockstack.org/,
* https://blog.blockstack.org/introducing-the-stacks-wallet/,
* https://github.com/blockstack/stacks-wallet,

resource of Stacks-net

name::
* Mcs.Blockstack-net'Stacks-net'resource,

addressWpg::
* https://forum.blockstack.org/t/stacks-blockchain-v2-development/7123,

Stacks-net.TESTNET

addressWpg::
* https://testnet.blockstack.org/,

name::
* Mcs.Blockstack-net'Stacks-testnet,

Bitcoin-network of Blockstack-net

Namecoin-network of Blockstack-net

description::
· Blockstack started using the-Namecoin-blockchain and migrated to Bitcoin-blockchain.

decentralized-naming-service of Blockstack-net

description::
"The Blockstack Naming Service (BNS) is a network system that binds names to off-chain state without relying on any central points of control. It does so by embedding a log of its control-plane messages within a public blockchain, like Bitcoin.
Each BNS peer determines the state of each name by indexing these specially-crafted transactions. In doing so, each peer independently calculates the same global name state."
[https://docs.blockstack.org/core/naming/introduction.html#what-is-bns]

name::
* Mcs.Blockstack-net'blockchain-name-system, [whitepaper]
* Mcs.Blockstack-net'BNS,
* Mcs.Blockstack-net'decentralized-name-system,
* Mcs.Blockstack-net'naming-service,
* Mcs.Blockstack-Naming-Service,
* Mcs.BNS.Blockstack,

addressWpg::
* https://docs.blockstack.org/core/naming/introduction.html,

ID of Blockstack-net

description::
"Through the Blockstack Browser you can create an identity. Your identity is a point of contact as you interact with others through DApps. Others may be individual users or companies or software. Unless you allow it, none of these others have access to anything other than your identity label, for example moxiegirl.id.blockstack. Typically, others must ask to learn more about you, and you can choose to share – or not."
[https://docs.blockstack.org/browser/ids-introduction]

name::
* Mcs.Blockstack-net'ID,
* Mcs.Blockstack-net'identity,

name of ID (link)

password of ID

description::
· when you create an-ID or when you import an-ID, you create and a-password for this ID.
· you need it, for many tasks: updating the-browser, adding another ID etc.

name::
* Mcs.Blockstack-net'ID'password,

secret-recovery-code of ID

description::
"A recovery code is a sequence of words. These words allow you to recover an id.blockstack that you’ve created. You should store the words along with their order, for example, #1 applied and so forth."
[https://docs.blockstack.org/develop/zero_to_dapp_1.html#try-your-first-dapp-by-creating-an-identity]

name::
* Mcs.Blockstack-net'ID'secret-recovery-code,

magic-recovery-code of ID

description::
"The secret recovery key is a 12 or 24 word phrase you recorded when you created the ID.
The magic recovery code is a string of characters Blockstack emailed to you when you created your identity.
You can confirm your identity with either."
[https://docs.blockstack.org/develop/zero_to_dapp_2.html#confirm-or-get-a-blockstack-id]

name::
* Mcs.Blockstack-net'ID'magic-recovery-code,

ID-relation-to-account

description::
"Why is an identity not an account
On the internet of today, an account you create for an applications stays with the company providing that app. This company keeps data you enter about yourself and data about how you use their application. When you close your account, the company retains that data.
In decentralized, blockchain software, identity is a combination of username and key. The data associated with that identity stays with it, this means applications or central authorities do not keep our control access to your data.
You give a DApp access to your data but when you decide to no longer use that application, you withdraw that access. The DApp developer can no longer access information about you."
[https://docs.blockstack.org/browser/ids-introduction#why-is-an-identity-not-an-account]

name::
* Mcs.Blockstack-net'ID-relation-to-account,

creating ID

description::
· you use the-Blockstack-browser to create an-ID.
[https://docs.blockstack.org/develop/zero_to_dapp_1.html#try-your-first-dapp-by-creating-an-identity]
===
1. open https://browser.blockstack.org/ (SETTINGS/RESET BROWSER to create a new account or restore another).
2. choose "Create new ID", create a-username (min 8 chars) and check availability.
3. create password.
5. enter your email.
6. save your Secret-Recovery-Key.
7. complete your Blockstack-ID by adding your name and a verified social-account.
8. save your Magic-Recovery-Key (in your email).

name::
* Mcs.Blockstack-net'ID'creating,

renewing ID

name::
* Mcs.Blockstack-net'ID'renewing,

addressWpg::
* https://renewmyblockstackid.info/,

ID.SPECIFIC

name::
* Mcs.Blockstack-net'ID.specific,

ID.SUBDOMAIN

description::
"What is a Blockstack Subdomain?
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 is a Blockstack ID, and is a subdomain of personal.id.
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 describes them in detail.
Subdomains provide a fast, inexpensive way to onboard many users at once."
[https://docs.blockstack.org/core/faq_technical.html#what-is-a-blockstack-subdomain]

name::
* Mcs.Blockstack-net'ID.subdomain,

ID.FREE

description::
"The Blockstack Browser allows new users to create free IDs.
These free IDs have included the word blockstack in the ID, like this moxiegirl.id.blockstack.
The additional blockstack portion of the name is called a namespace.
It just means all the names belong to a particular entity.
You don’t have to use a free id.blockstack identity.
You can also buy an identity that just has a unique name and the .id portion."
[https://docs.blockstack.org/browser/ids-introduction#how-do-you-get-an-identity]

name::
* Mcs.Blockstack-net'ID.free,

ID.FREE.NO

description::
"The Blockstack Browser allows new users to create free IDs.
These free IDs have included the word blockstack in the ID, like this moxiegirl.id.blockstack.
The additional blockstack portion of the name is called a namespace.
It just means all the names belong to a particular entity.
You don’t have to use a free id.blockstack identity.
You can also buy an identity that just has a unique name and the .id portion."
[https://docs.blockstack.org/browser/ids-introduction#how-do-you-get-an-identity]

name::
* Mcs.Blockstack-net'ID.freeNo,

ID.PRIMARY

description::
"This first ID you create is a primary ID.
Once you create a primary identity, you can add other, sub-identities to it.
Sub-identities can have the id.blockstack or the .id format.
You might created sub-identities for the same reason you have a work and home email."
[https://docs.blockstack.org/browser/ids-introduction#how-do-you-get-an-identity]

name::
* Mcs.Blockstack-net'ID.primary,

ID.PRIMARY.NO

description::
"This first ID you create is a primary ID.
Once you create a primary identity, you can add other, sub-identities to it.
Sub-identities can have the id.blockstack or the .id format.
You might created sub-identities for the same reason you have a work and home email."
[https://docs.blockstack.org/browser/ids-introduction#how-do-you-get-an-identity]

name::
* Mcs.Blockstack-net'ID.primaryNo,
* Mcs.Blockstack-net'ID.subidentity,

name of BNS

description::
"Names in BNS have three properties:
1. Names are globally unique. The protocol does not allow name collisions, and all well-behaved nodes resolve a given name to the same state.
2. Names are human-meaningful. Each name is chosen by its creator.
3. Names are strongly-owned. Only the name’s owner can change the state it resolves to. Specifically, a name is owned by one or more ECDSA private keys."
[https://docs.blockstack.org/core/naming/introduction.html]

name::
* Mcs.Blockstack-net'BNS'name,
* Mcs.Blockstack-net'name,

owner of name

description::
"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 makes this task almost impossible for non-state actors."
[https://docs.blockstack.org/core/faq_technical.html#why-should-i-trust-the-information-like-name-ownership-or-public-key-mappings-read-from-blockstack]

name::
* Mcs.Blockstack-net'name'owner,

price of name

description::
· there are free and non-free names.

name::
* Mcs.Blockstack-net'name'price,

time of name

description::
· after 2 years you have to reregister a-name.

name::
* Mcs.Blockstack-net'name'time,

name.SPECIFIC

specific::
* namespace,
* on-chain--name,
* off-chain--name-(subdomain),

name.NAMESPACE

description::
"Namespaces. These are the top-level names in the hierarchy. An analogy to BNS namespaces are DNS top-level domains. Existing BNS namespaces include .id, .podcast, and .helloworld. All other names belong to exactly one namespace. Anyone can create a namespace, but in order for the namespace to be persisted, it must be launched so that anyone can register names in it. Namespaces are not owned by their creators."
[https://docs.blockstack.org/core/naming/introduction.html#organization-of-bns]
===
"Namespaces are the top-level naming objects in BNS.
They control a few properties about the names within them:
* How expensive they are to register
* How long they last before they have to be renewed
* Who (if anyone) receives the name registration fees
* Who is allowed to seed the namespace with its initial names."
[https://docs.blockstack.org/core/naming/namespaces.html]

name::
* Mcs.Blockstack-net'BNS'namespace,
* Mcs.Blockstack-net'namespace,
* Mcs.Blockstack-net'TLD-(Top-Level-Domain),

owner of namespace

description::
"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."
[https://docs.blockstack.org/core/faq_technical.html#can-anyone-register-a-tld]

name::
* Mcs.Blockstack-net'namespace'creator,
* Mcs.Blockstack-net'namespace'owner,

namespace.SPECIFIC

name::
* Mcs.Blockstack-net'namespace.specific,

specific::
* .id,
* .podcast,
* .helloworld,

namespace.id

description::
"To start the first namespace on Blockstack, the .id namespace, we paid 40 bitcoins ($10,000 at the time) to the network. This shows that even the developers of this decentralized system have to follow the rules and pay appropriate fees."
[https://blockstack.org/whitepaper.pdf {2017-10-12}]

name::
* Mcs.Blockstack-net'namespace.id,

name.ON-CHAIN

description::
"BNS names. These are names whose records are stored directly on the blockchain. The ownership and state of these names are controlled by sending blockchain transactions. Example names include verified.podcast and muneeb.id. Anyone can create a BNS name, as long as the namespace that contains it exists already. The state for BNS names is usually stored in the Atlas network."
[https://docs.blockstack.org/core/naming/introduction.html#organization-of-bns]

name::
* Mcs.Blockstack-net'BNS'on-chain-name,

name.OFF-CHAIN (subdomain)

description::
"A BNS subdomain is a type of BNS name whose state and owner are stored outside of the blockchain, but whose existence and operation history are anchored to the blockchain. In the example table in the Resolving BNS Names section, the names cicero.res_publica.id and podsaveamerica.verified.podcast are subdomains.
Like their on-chain counterparts, subdomains are globally unique, strongly-owned, and human-readable. BNS gives them their own name state and public keys."
[https://docs.blockstack.org/core/naming/subdomains.html]

name::
* Mcs.Blockstack-net'BNS'subdomain,
* Mcs.Blockstack-net'subdomain,

price of subdomain

description::
"Can I get a Blockstack ID without spending Bitcoin?
Blockstack subdomains can be obtained without spending Bitcoin by asking a subdomain registrar to create one for you."
[https://docs.blockstack.org/core/faq_technical.html#can-i-get-a-blockstack-id-without-spending-bitcoin]

name::
* Mcs.Blockstack-net'BNS'subdomain'price,

resource of subdomain

name::
* Mcs.Blockstack-net'subdomain,

addressWpg::
* https://github.com/blockstack/subdomain-registrar,

Blockstack-Core (link)

indexer of BNS

description::
"The BNS indexer. This module crawls the blockchain and builds up its name database. BNS indexers do not contain any private or sensitive state, and can be deployed publicly. We maintain a fleet of them at https://node.blockstack.org:6263 for developers to use to get started."
[https://docs.blockstack.org/core/naming/architecture.html]

name::
* Mcs.Blockstack-net'BNS'indexer,

API of BNS

description::
"The BNS API. This module gives developers a stable RESTful API for interacting with the BNS network. We provide one for developers to experiment with at https://core.blockstack.org."
[https://docs.blockstack.org/core/naming/architecture.html]

name::
* Mcs.Blockstack-net'BNS'Api,

client of BNS

description::
"BNS clients. These communicate with the BNS API module in order to resolve names. Internally, they generate and send transactions to register and modify names."
[https://docs.blockstack.org/core/naming/architecture.html]

name::
* Mcs.Blockstack-net'BNS'client,

user of BNS

description::
· BNS has over 90K users that can immediately start using your Dapp.
[https://docs.blockstack.org/develop/zero_to_dapp_2.html#a-blockchain-platform-without-pain]

name::
* Mcs.Blockstack-net'BNS'user,

BNS-relation-to-other-decentralized-naming-systems

name::
* Mcs.Blockstack-net'BNS'relation-to-other-decentralized-naming-systems,

addressWpg::
* https://docs.blockstack.org/core/naming/comparison.html,

doing of BNS

description::
"With BNS, we can do the following and more:
* Build domain name services where hostnames can’t be hijacked.
* Build social media platforms where user names can’t be stolen by phishers.
* Build version control systems where repository branches do not conflict.
* Build public-key infrastructure where it’s easy for users to discover and remember each other’s keys."
[https://docs.blockstack.org/core/naming/introduction.html#motivation-behind-naming-services]

name::
* Mcs.Blockstack-net'BNS'evaluation,

decentralized-storage of Blockstack-net

name::
* Mcs.Blockstack-net'decentralized-storage,
* Mcs.Blockstack-net'storage,

Gaia-storage-system

description::
"It handles storage using Gaia, a scalable decentralized key/value storage system that looks and feels like localStorage, but lets users securely store and share application data via existing storage systems like Dropbox or S3."
[https://github.com/blockstack/blockstack-core#what-is-blockstack]
===
"Gaia works by hosting data in one or more existing storage systems of the user's choice. These storage systems are typically cloud storage systems. We currently have driver support for S3 and Azure Blob Storage, but the driver model allows for other backend support as well. The point is, the user gets to choose where their data lives, and Gaia enables applications to access it via a uniform API.
Blockstack applications use the Gaia storage system to store data on behalf of a user. When the user logs in to an application, the authentication process gives the application the URL of a Gaia hub, which performs writes on behalf of that user. The Gaia hub authenticates writes to a location by requiring a valid authentication token, generated by a private key authorized to write at that location."
[https://github.com/blockstack/gaia#overview]
===
· the-Gaia-data-storage-hub is purely a-service without user-facing functionality.
[https://docs.blockstack.org/develop/zero_to_dapp_1.html#overview-of-the--dapp-you-will-build]

name::
* Mcs.Blockstack-Gaia,
* Mcs.Blockstack-net'Gaia-storage!⇒Blockstack-Gaia,
* Mcs.Gaia-storage-system-of-Blockstack!⇒Blockstack-Gaia,

provider of Gaia

description::
"The idea with Gaia storage is that the storage is user-controlled — the default gaia storage option is provided by Blockstack, but ultimately the intent is for users to run their own Gaia hubs. The backing storage system for Gaia hubs is configurable, supporting many different “drivers” for storage."
[https://forum.blockstack.org/t/who-provides-the-storage-capacity-for-gaia/5552/2]

name::
* Mcs.Blockstack-Gaia'provider,

default-Gaia-hub

description::
"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."
[https://docs.blockstack.org/core/faq_technical.html#where-does-blockstack-keep-my-app-data]

name::
* Mcs.Blockstack-Gaia'default-hub,

resource of Gaia

name::
* Mcs.Blockstack-Gaia'resource,

addressWpg::
* https://github.com/blockstack/gaia,
* https://github.com/blockstack/blockstack.js/tree/master/src/storage,
* http://blockstack.github.io/blockstack.js/#storage,
===
* Gaia-file-explorer: https://github.com/MichaelFedora/mercurius,
* https://www.npmjs.com/package/blockstack-large-storage,

Atlas-network of Blockstack-net

description::
Atlas is the storage routing system for Gaia.
[http://localhost/dWstSgm/dirMiwMcs/dirTchInf/filMcsDtcbnetBlockstack.last.html#idBkskjs]
===
"the Atlas network, a peer-to-peer content-addressed storage system whose chunks’ hashes are announced on a public blockchain. Atlas allows users and developers to permanently store chunks of data that are replicated across every peer. As long as at least one Atlas peer is online, all chunks are available to clients."
[https://docs.blockstack.org/core/atlas/overview.html]

name::
* Mcs.Blockstack-net'Atlas-network,
* Mcs.Blockstack-net'peer-network,
* Mcs.Atlas-network-of-Blockstack,

program of Blockstack-net

name::
* Mcs.Blockstack-net'program,

program.SPECIFIC

name::
* Mcs.Blockstack-net'program.specific,

specific::
* Blockstack-Browser,
* Blockstack-Core,
* Blockstack-explorer,
* blockstack.js,

program.Blockstack-Core

description::
"This package provides the reference implementation of a Blockstack node, as well as tools and scripts for deploying it."
[https://github.com/blockstack/blockstack-core#blockstack-core]
===
"Blockstack Core implements BNS and Atlas, the storage routing system for Gaia."
[http://localhost/dWstSgm/dirMiwMcs/dirTchInf/filMcsDtcbnetBlockstack.last.html#idBkskjs]
===
"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"
[https://docs.blockstack.org/core/faq_technical.html#what-is-blockstack-core-and-who-is-working-on-it]

name::
* Mcs.Blockstack-net'Blockstack-Core,
* Mcs.Blockstack-Core,

core-developer (link)

program.blockstack.js

description::
"Blockstack JS is a library for profiles/identity, authentication, and storage.
The authentication portion of this library can be used to:
1. create an authentication request
2. create an authentication response
The profiles/identity portion of this library can be used to:
1. transform a JSON profile into cryptographically-signed tokens
2. recover a JSON profile from signed tokens
3. validate signed profile tokens
The storage portion of this library can be used to:
1. store and retrieve your app's data in storage that is controlled by the user
Note: this document uses ES6 in its examples but it is compiled down to Javascript (ES5) and is perfectly compatible with it. If you're using the latter, just make a few adjustments to the examples below (e.g. use "let" instead of "var")."
[https://github.com/blockstack/blockstack.js]

name::
* Mcs.Blockstack-net'blockstack.js,
* Mcs.Blockstack-net'javascript-library,
* Mcs.blockstack.js,

addressWpg::
* https://github.com/blockstack/blockstack.js,
* doc: http://blockstack.github.io/blockstack.js/,

member of blockstack.js

member::
{2019-01-03}
Object.getOwnPropertyNames(blockstack).sort().join(', ')
"BLOCKSTACK_GAIA_HUB_LABEL, BlockstackWallet, CreativeWork, IdentityKeyPair, Organization, Person, Profile, PubkeyHashSigner, TransactionSigner, __esModule, addUTXOsToFund, config, connectToGaiaHub, containsValidAddressProofStatement, containsValidProofStatement, decodeToken, decryptContent, decryptMnemonic, deleteFile, doPublicKeysMatchIssuer, doPublicKeysMatchUsername, doSignaturesMatchPublicKeys, ecPairToAddress, ecPairToHexString, encryptContent, encryptMnemonic, estimateTXBytes, extractProfile, fetchAppManifest, generateAndStoreTransitKey, getAddressFromDID, getAppBucketUrl, getAuthRequestFromURL, getAuthResponseToken, getCoreSession, getDIDType, getEntropy, getFile, getPublicKeyFromPrivate, getTokenFileUrl, getTransitKey, getUserAppFileUrl, handlePendingSignIn, hexStringToECPair, isExpirationDateValid, isIssuanceDateValid, isLaterVersion, isManifestUriValid, isRedirectUriValid, isSameOriginAbsoluteUrl, isSignInPending, isUserSignedIn, listFiles, loadUserData, lookupProfile, makeAuthRequest, makeAuthResponse, makeCoreSessionRequest, makeDIDFromAddress, makeDIDFromPublicKey, makeECPrivateKey, makeProfileZoneFile, makeUUID4, network, nextHour, nextMonth, nextYear, profileServices, publicKeyToAddress, putFile, redirectToSignIn, redirectToSignInWithAuthRequest, redirectUserToApp, resolveZoneFileToPerson, resolveZoneFileToProfile, safety, sendCoreSessionRequest, signProfileToken, signUserOut, transactions, updateQueryStringParameter, uploadToGaiaHub, validateProofs, verifyAuthRequest, verifyAuthRequestAndLoadManifest, verifyAuthResponse, verifyProfileToken, wrapProfileToken"

name::
* Mcs.Blockstack-net'blockstack.js'member,
* Mcs.blockstack.js'member,

deleteFile() of blockstack.js

description::
"deleteFile is currently not implemented. For now, we recommend writing an empty file to wipe data"
[http://blockstack.github.io/blockstack.js/#storage]

name::
* Mcs.Blockstack-net'blockstack.js'deleteFile(),
* Mcs.blockstack.js'deleteFile(),

example::
blockstack.deleteFile("/hello.txt")
.then(() => {
 // /hello.txt is now removed.
})

getFile() of blockstack.js

description::
"Retrieves the specified file from the app's data store.
getFile(path: String, options: Object): Promise"
[http://blockstack.github.io/blockstack.js/#getfile]

name::
* Mcs.Blockstack-net'blockstack.js'getFile(),
* Mcs.blockstack.js'getFile(),

example::
//reading a-file
blockstack.getFile("/hello.txt")
.then((fileContents) => {
 // get the contents of the file /hello.txt
 assert(fileContents === "hello world!")
});

[http://blockstack.github.io/blockstack.js/#storage]

example::
//reading an-encrypted-file
blockstack.getFile("/hello2.txt", {decrypt: true})
.then((fileContents) => {
 // get the contents of the file /hello2.txt
 assert(fileContents === "Secret hello!")
});

[http://blockstack.github.io/blockstack.js/#storage]

isSignInPending() of blockstack.js

description::
"Check if there is a authentication request that hasn't been handled.
isSignInPending(): Boolean"
[http://blockstack.github.io/blockstack.js/#issigninpending]

input::
· none

output::
"Boolean: true if there is a pending sign in, otherwise false"
[http://blockstack.github.io/blockstack.js/#issigninpending]

name::
* Mcs.Blockstack-net'blockstack.js'isSignInPending(),
* Mcs.blockstack.js'isSignInPending(),

redirectToSignIn() of blockstack.js

description::
"Generates an authentication request and redirects the user to the Blockstack browser to approve the sign in request.
Please note that this requires that the web browser properly handles the blockstack: URL protocol handler.
Most applications should use this method for sign in unless they require more fine grained control over how the authentication request is generated. If your app falls into this category, use makeAuthRequest and redirectToSignInWithAuthRequest to build your own sign in process.
redirectToSignIn(redirectURI: String, manifestURI: String, scopes: Array): void"

name::
* Mcs.Blockstack-net'blockstack.js'redirectToSignIn(),
* Mcs.blockstack.js'redirectToSignIn(),

program.Blockstack-browser

description::
"The Blockstack Browser gives users the ability to explore and use the decentralized applications (DApps). DApps are a new way to interact with the internet. DApps give users control of their data. Data about them personally, name, birthdate, phone number and data about what they do such as visiting a website or buying an item."
[https://docs.blockstack.org/browser/browser-introduction.html]

name::
* Mcs.Blockstack-net'Blockstack-browser,
* Mcs.Blockstack-net'browser,

installing Blockstack-browser

name::
* Mcs.Blockstack-net'browser'installing,

addressWpg::
* https://blockstack.org/install/,

DOING of Blockstack-browser

description::
"The Blockstack Browser is itself, a simple DApp. It allows you to:
* create one or more identities
* send and receive bitcoin
* manage the storage of your profile and application data
* find and launch DApps"
[https://docs.blockstack.org/browser/browser-introduction.html#understand-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."
[https://docs.blockstack.org/browser/faq_general.html#what-is-the-blockstack-browser]

name::
* Mcs.Blockstack-net'browser'doing,

browser.SPECIFIC

specific::
* Web,
* Win,
* Linux,
* Mac,

browser.WEB

addressWpg::
* https://browser.blockstack.org/,

name::
* Mcs.Blockstack-net'browser.web,
* Mcs.Blockstack-net'web-browser,

using-on-public-computers of web-browser

description::
"Using the Browser on public computers
Before you use the web application, it is important to note that once you log into the application with the brower, your session does not expire until you choose Settings > RESET BROWSER. For this reason, you should be careful when using the browser on public computers.
If you are in a library, for example, and log into the browser, simply closing the tab or even rebooting the computer does not log you out. Instead, you should be sure to choose Settings > RESET BROWSER before leaving the web application."

name::
* Mcs.Blockstack-net'browser.web'using-on-public-computers,

updating web-browser

description::
· it is an automatic process.
· you need the-password of your ID.

name::
* Mcs.Blockstack-net'browser.web'updating,

program.Blockstack-explorer

addressWpg::
* https://explorer.blockstack.org/,

description::
· Stacks-explorer is a-blockchain-explorer for searching the data in a-blockchain.
[https://docs.blockstack.org/org/explore.html]

name::
* Mcs.Blockstack-net'explorer,
* Mcs.Blockstack-net'Stacks-explorer,

Dapp of Blockstack-net

description::
An application is considered a Blockstack DApp if it adheres to three principles.
I. Users own their data
II. Users own their identities
III. Users have free choice of clients
[https://docs.blockstack.org/develop/dapp_principles.html#blockstack-dapp-principles]
===
"Blockstack is a new internet for decentralized apps that you access through the Blockstack Browser. With Blockstack, there is a new world of apps that let you own your data and maintain your privacy, security and freedom."
[https://blockstack.org/about/]

name::
* Mcs.Blockstack-Dapp,
* Mcs.Blockstack-net'Dapp!⇒Blockstack-Dapp,
* Mcs.Dapp.Blockstack!⇒Blockstack-Dapp,

authentication of Dapp

description::
· a-Blockstack-Dapp must-use the-Blockstack-net for authentication.

name::
* Mcs.Blockstack-Dapp'authentication,

storage of Dapp

description::
· a-Blockstack-Dapp can-use many systems for storage: Gaia, Ipfs, ...

name::
* Mcs.Blockstack-Dapp'storage,

https://app.co

addressWpg::
* https://app.co,

description::
"About app.co
App.co surfaces the best new dapps every day. It’s a place for blockchain-loving nerds, enthusiasts, and investors to geek out over the latest decentralized tech—from currency exchanges to mutant-feline-marketplaces.
App.co is sponsored by Blockstack, a decentralized app protocol and community. All protocols are welcome on App.co as we’re committed to celebrating an open, decentralized internet for all."
[https://app.co/faq]

name::
* Mcs.app.co,
* Mcs.Blockstack-net'app.co,

Signature-Bounty-program of Dapp

description::
"In 2017 Blockstack announced the Blockstack Signature Fund. The Signature Fund is aimed at growing an ecosystem of decentralized applications on Blockstack. The fund releases funds through a Signature Bounty program. This is a global bounty program using a contest model. Teams from all over the world submit products and a set of judges determine who wins the prize for the best product."
[https://docs.blockstack.org/develop/zero_to_dapp_1.html#seeding-dapp-market-with-application-mining]

name::
* Mcs.Blockstack-Dapp'Signature-Bounty-program,
* Mcs.Blockstack-net'Signature-Bounty-program,

mining-program of Dapp

description::
"In addition to the bounty program, Blockstack supports an application mining program. This is an early stage program for developers. In this program, application developers register their application on App.co. Then, each month, application developers get paid depending on their application quality ranking. The ranking is determined by a set of application reviewers.
Application mining differs from the venture model or the app studio model because the rewards are in cryptocurrency. Blockstack PBC administrates both the review and delivery of these monthly payments."
[https://docs.blockstack.org/develop/zero_to_dapp_1.html#seeding-dapp-market-with-application-mining]

name::
* Mcs.Blockstack-Dapp'mining-program,
* Mcs.Blockstack-net'app-mining,
* Mcs.Blockstack-net'application-mining-program,

Dapp-reviewer

name::
* Mcs.Blockstack-net'app-mining'reviwer,

description::
· Democracy-Earth,
· Product-Hunt,
· TryMyUI, https://www.trymyui.com/,

resource of app-mining

name::
* Mcs.Blockstack-net'app-mining'resource,

addressWpg::
* contact: mining@app.co,
* https://blog.blockstack.org/introducing-app-mining/,
* https://docs.blockstack.org/develop/mining_intro.html,
* https://blog.blockstack.org/introducing-trymyui-app-mining-app-reviewer/,
* https://app.co/mining,
* faq: https://app.co/mining#what-is-app-mining,

resource of Dapp

name::
* Mcs.Blockstack-Dapp'resource,

addressWpg::
* tutorial: https://docs.blockstack.org/browser/hello-blockstack.html,
* https://docs.blockstack.org/android/tutorial.html,
* (rails-app) https://docs.blockstack.org/develop/auth_provider.html,
* https://blog.blockstack.org/category/dapps/,
* https://theblockstats.com/,

tool of Dapp

name::
* Mcs.Blockstack-Dapp'tool,

addressWpg::
* radiks.js: A framework for building decentralized apps, https://lettermesh.com/blogs/76SjDUq1P-radiks-js,

relation-to-traditional-web-apps

description::
"Blockstack applications differ from traditional Web applications in two key ways. First, users own their identities. The Blockstack Browser gives users direct control over their private keys and profile data, and fulfills the role of a SSO provider to Blockstack apps. Blockstack Core provides BNS as a way for users to discover each other's public keys.
The second key difference is that users own their data. Users choose where their app data gets hosted, and who is allowed to read it. Gaia loads and stores data with the user's chosen storage providers, and automatically signs and encrypts it with their app-specific keys. Only the intended recipients can authenticate and read the data; the storage providers are treated as untrusted middlemen."
[https://github.com/blockstack/blockstack-core#what-is-blockstack]
===
"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."
[https://docs.blockstack.org/browser/faq_general.html#how-do-dapps-differ-applications-i-typically-use]

name::
* Mcs.Blockstack-Dapp'relation-to-traditional-web-apps,

DOING of Dapp

name::
* Mcs.Blockstack-Dapp'doing,

running Dapp

description::
1) open web-blockstack-browser
2) click on an-Dapp
3) sign in with blockstack
===
"Do DApps work with a regular browser?
Yes! DApps run in the web browsers (Chrome, Safari, Internet Explorer, etc.) you know and love."
[https://docs.blockstack.org/browser/faq_general.html#do-dapps-uwork-with-a-regular-browser]

name::
* Mcs.Blockstack-Dapp'running,

problem running Dapp

description::
· problem: not running on Windows machine
· solution: remove desktop-blockstack, clear cache.

name::
* Mcs.Blockstack-Dapp'problem.running,
* Mcs.Blockstack-Dapp'running'problem,

scaling Dapp

description::
"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."
[https://docs.blockstack.org/core/faq_technical.html#can-blockstack-apps-scale-given-that-blockstack-uses-blockchains-which-dont-scale-that-well]

name::
* Mcs.Blockstack-Dapp'scaling,

interacting-with-other-blockchains

description::
"Can Blockstack applications interact with Bitcoin? Ethereum? Smart contracts? Other blockchains?
Yes! Since Blockstack applications are built like web applications, all you need to do is include the relevant Javascript library into your application."
[https://docs.blockstack.org/core/faq_developer.html#can-blockstack-applications-interact-with-bitcoin-ethereum-smart-contracts-other-blockchains]

name::
* Mcs.Blockstack-Dapp'interacting-with-other-blockchains,

ATTRIBUTE of Dapp

name::
* Mcs.Blockstack-Dapp'attribute,

can't-be-evil

description::
"Blockstack applications follow a can't-be-evil design philosophy. They cannot alter, transfer, or revoke the user's identity, and they cannot read or write the user's data without permission. Blockstack provides the platform, network, and SDKs for building can't-be-evil applications using existing Web tools. If you are Web developer, all of your skills are immediately transferrable to Blockstack."
[https://github.com/blockstack/blockstack-core#what-is-blockstack]

name::
* Mcs.Blockstack-Dapp'can't-be-evil,

GENERIC of Dapp

generic-chain::
* Dapp,
===
* web-app,

Dapp.SPECIFIC

name::
* Mcs.Blockstack-Dapp.specific,

specific::
* app.co,
===
* Graphite: https://www.graphitedocs.com/,
* Your-Note: https://yournote.app/,

Dapp.HELLO-BLOCKSTACK

description::
"In this tutorial, you generate a simple application on Blockstack. The application is a single-page application (SPA) that runs completely client-side. The application has no backend API to talk to, other than the identity and storage API that the user provides. In this sense, the application is a completely decentralized, server-less application."
[https://docs.blockstack.org/browser/hello-blockstack.html]

name::
* Mcs.Blockstack-Dapp.Hello-Blockstack,

addressWpg::
* https://helloblockstack.com/,
* tutorial: https://docs.blockstack.org/browser/hello-blockstack.html,

Dapp.ANIMAL-KINGDOM

description::
"Welcome to the Blockstack Zero-to-DApp tutorial. In this tutorial, you build, run, modify, and deploy a decentralized application (DApp) called Animal Kingdom. This application makes use of blockchain technology through the use of the Blockstack platform. As you follow along, you’ll learn what makes a DApp different than traditional applications. You’ll also learn about the Blockstack Signature Fund and its Application Mining designed to fund DApp development."
[https://docs.blockstack.org/develop/zero_to_dapp_1.html]

name::
* Mcs.Blockstack-Dapp.Animal-Kingdom,
* Mcs.Blockstack-net'Zero-to-DApp-tutorial,

addressWpg::
* https://docs.blockstack.org/develop/zero_to_dapp_1.html,
* https://github.com/blockstack/animal-kingdom,
* https://animalkingdoms.netlify.com/,

Dapp.BlockUSign

description::
"A decentralized, social document signing tool where you own and control your own documents, contracts and data. It is built on Blockstack"
[https://github.com/ntheile/blockusign]

name::
* Mcs.Blockstack-Dapp.BlockUSign,

addressWpg::
* https://blockusign.co/,
* https://github.com/ntheile/blockusign,
===
* {2019-01-28} Nick-Theile, Blockusign App: A Pragmatic Approach to Smart Contracts and Anchoring Data to the Blockchain Using Blockstack, https://medium.com/blockstack-blog/blockusigns-pragmatic-approach-to-smart-contracts-anchoring-data-on-blockchain-using-blockstack-fb9bd974a306,

Dapp.TODO-LIST

description::
"In this tutorial, you build the code for and run a single-page application (SPA) with Blockstack and Vue.js. Once the application is running, you take a tour through the applications’ Blockstack functionality. You’ll learn how it manages authentiation using a Blockstack ID and how it stores information associated with that ID using Blockstack Storage (Gaia)."
[https://docs.blockstack.org/browser/todo-list.html]

name::
* Mcs.Blockstack-Dapp.todo-list,

addressWpg::
* https://blockstack-todos.appartisan.com/,
* https://docs.blockstack.org/browser/todo-list.html,

Dapp.GRAPHITE

description::
"Graphite is a decentralized and encrypted replacement for Google's G-Suite. Built on Blockstack and powered by the Bitcoin Blockchain."
[https://app.graphitedocs.com/]
===
"All your files in one place, secure and totally owned by you."
[https://www.graphitedocs.com/]

name::
* Mcs.Blockstack-Dapp.Graphite,
* Mcs.Graphite.Blockstack-Dapp,

dashboard of Graphite

document of Graphite

sheet of Graphite

vault of Graphite

contact of Graphite

avatar of Graphite

resource of Graphite

human of Blockstack-net

name::
* Mcs.Blockstack-net'human,

specific::
* Ali.Muneeb,
* Shea.Ryan,
* Nelson.Jude,
* Freedman.Michael.J.,
===
* developer.core,
* developer.Dapp,

human.developer.core

description::
"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 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."
[https://docs.blockstack.org/core/faq_technical.html#where-are-the-current-core-developers-based-what-are-the-requirements-for-being-a-core-developer]

name::
* Mcs.Blockstack-net'core-developer,
* Mcs.Blockstack-net'developer.core,

organization of Blockstack-net

name::
* Mcs.Blockstack-net'organization,

addressWpg::
* {2018-10-11}, Ryan ∧ Muneeb, https://blog.blockstack.org/a-path-to-decentralization/,

ogn.Blockstack-Public-Benefit-Corp

description::
"Founded in 2013 as Onename, Blockstack raised $5.45 million venture capital from a number of major players, including Union Square Ventures, AngelList founder Naval Ravikant, and Digital Currency Group. [10 http://www.coindesk.com/blockstack-4-million-funding-series-a/]"
[https://everipedia.org/wiki/lang_en/Blockstack/]
===
"Blockstack Public Benefit Corp. (PBC) started development of the Blockstack platform in 2014 and launched an alpha of the platform in early 2017."
[https://docs.blockstack.org/org/overview.html#blockstack-public-benefit-corp-pbc]

name::
* Mcs.Blockstack-net'PBC,
* Mcs.Blockstack-net'Blockstack-Public-Benefit-Corp,
* Mcs.Blockstack-net'Onename,
* Mcs.Blockstack-Public-Benefit-Corp,

addressWpg::
* https://blockstack.org/careers/,

ogn.Blockstack-Signature-Fund

description::
"Blockstack Signature Fund
In 2017 Blockstack announced the Blockstack Signature Fund. The Signature Fund is aimed at growing an ecosystem of decentralized applications on Blockstack. The fund releases funds through a Signature Bounty program. This is a global bounty program using a contest model. Teams from all over the world submit products and a set of judges determine who wins the prize for the best product.
In addition to the bounty program, Blockstack supports an application mining program. This is an early stage program for developers. In this program, application developers register their application on App.co. Then, each month, application developers get paid depending on their application quality ranking. The ranking is determined by a set of application reviewers.
Application mining differs from the venture model or the app studio model because the rewards are in cryptocurrency. Blockstack PBC administrates both the review and delivery of these monthly payments."
[https://docs.blockstack.org/org/overview.html#blockstack-signature-fund]

name::
* Mcs.Blockstack-net'Blockstack-Signature-Fund,
* Mcs.Blockstack-Signature-Fund,

ogn.Blockstack-Token-LLC

description::
"a Delaware limited liability company"
[https://blockstack.org/whitepaper.pdf {2017-10-12}]
===
"Through the 2017 Blockstack token offering, Blockstack Token LLC created the Stacks token."
[https://docs.blockstack.org/org/overview.html#blockstack-token-llc]

name::
* Mcs.Blockstack-net'Blockstack-Token-LLC,
* Mcs.Blockstack-Token-LLC,

resource of Blockstack-net

name::
* Mcs.Blockstack-net'resource,
* Mcs.BlockstackAeResource,

addressWpg::
* website: http://blockstack.org,
* https://stackstoken.com/,
* email: support@blockstack.com,
* https://signature.vc/,
* documentation: https://docs.blockstack.org/,
* whitepapers: https://blockstack.org/papers,
* tutorials: https://blockstack.org/tutorials,
* Github: https://github.com/blockstack,
* blog: https://blog.blockstack.org/,
===
* Telegram: https://t.me/BlockstackChat,
* Twitter: https://twitter.com/blockstack,
* Reddit: https://www.reddit.com/r/blockstack/,
* forum: https://forum.blockstack.org/,
* community: https://community.blockstack.org/,
===
* {2019-07-10} https://blog.blockstack.org/blockstack-token-sale-sec-qualified/,
* {2019-03-19} https://blog.app.co/march-app-mining-results-apps-improving-and-adding-new-features/,
* {2018-08-05} Ameya, https://medium.com/coinmonks/blockstack-a-decentralized-naming-and-storage-system-using-blockchain-445ff60190f7,
* {2017-05-23} Blockstack Releases Blockchain-Powered, Tokenized Internet Browser: http://www.coindesk.com/,
* {2017-03-14} https://cointelegraph.com/news/blockstack-launches-third-ever-blockchain-product-on-amazon-marketplace,
* {2016-06-22/24} Blockstack: A Global Naming and Storage System Secured by Blockchains: https://blockstack.org/blockstack_usenix16.pdf,
* https://www.larrysalibra.com/blog/adding-blockstack-auth-to-discourse/,
* https://www.larrysalibra.com/blog/blockstack-token-sale-voucher-registration-walkthrough/,

ATTRIBUTE of Blockstack-net

name::
* Mcs.Blockstack-net'attribute,

design-goal of Blockstack-net

description::
"Blockstack has the following design goals:
1. Decentralized Naming & Discovery: End-users should be able to (a) register and use human-readable names and (b) discover network resources mapped to human-readable names without trusting any remote parties.
2. Decentralized Storage: End-users should be able to use decentralized storage systems where they can store their data without revealing it to any remote parties.
3. Comparable Performance: The end-to-end performance of the new architecture (including name/resource lookups, storage access, etc.) should be comparable to the traditional internet with centralized services."
[https://blockstack.org/whitepaper.pdf {2017-10-12}]

ENVIRONMENT of Blockstack-net

name::
* Mcs.Blockstack-net'environment,

relation-to-Ethereum

description::
"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"
[https://docs.blockstack.org/core/faq_technical.html#how-is-blockstack-different-from-ethereum-for-building-decentralized-apps]

name::
* Mcs.Blockstack-net'relation-to-Ethereum,

DOING of Blockstack-net

name::
* Mcs.Blockstack-net'doing,

upgrading Blockstack

description::
"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."
[https://docs.blockstack.org/core/faq_technical.html#how-is-the-blockstack-network-upgraded-over-time-what-parties-need-to-agree-on-an-upgrade]

name::
* Mcs.Blockstack-net'upgrading,

destroying Blockstack

description::
"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."
[https://docs.blockstack.org/core/faq_technical.html#what-if-the-current-companies-and-developers-working-on-blockstack-disappear-would-the-network-keep-running]

name::
* Mcs.Blockstack-net'doing.destroying,

learning Blockstack

name::
* Mcs.Blockstack-net'doing.learning,
* Mcs.Blockstack-net'learning,

addressWpg::
* https://blockstack.org/faq/,
* https://docs.blockstack.org/core/faq_technical.html,

EVOLUTING of Blockstack-net

name::
* Mcs.Blockstack.evoluting,

{time.2018-10-30}::
=== 2018 hard-fork launches the Stacks blockchain v1:
"The hard fork is slated to activate on October 30 at around UTC+6. The Bitcoin block height is 547921."
[https://forum.blockstack.org/t/blockstack-annual-hard-fork-2018/6518]

{time.2017-09}::
=== genesis block of Blockstack-blockchain:
"The genesis block of the new Blockstack blockchain was started in September 2017 and the process of assigning initial allocations in the genesis block has started. The software itself is expected to take a year of development and the network is expected to go live by late 2018 or early 2019 but there are no guarantees. See the Blockstack Token LLC website for disclaimers and risk factors [24]."
[https://blockstack.org/tokenpaper.pdf {2018-11-29}]

{time.2017}::
=== alpha launch:
"Blockstack Public Benefit Corp. (PBC) started development of the Blockstack platform in 2014 and launched an alpha of the platform in early 2017."
[https://docs.blockstack.org/org/overview.html#blockstack-public-benefit-corp-pbc]

{time.2016fall}::
=== Atlas-network:
"The Blockstack implementation switched to the Atlas network from the DHT-based discovery network in Fall 2016, and since November 2016, we have been distributing BNS zone files using the Atlas network."
[https://blockstack.org/whitepaper.pdf {2017-10-12}]

{time.2015-09}::
=== Bitcoin migration:
· Onename (Blockstack-PBC) migrated fron Namecoin-blockchain to Bitocoin-blockchain.
[https://cointelegraph.com/news/onename-drops-namecoin-switches-to-bitcoin {2015-09-14}]

{time.2014}::
=== START of development:
"Blockstack Public Benefit Corp. (PBC) started development of the Blockstack platform in 2014 and launched an alpha of the platform in early 2017."
[https://docs.blockstack.org/org/overview.html#blockstack-public-benefit-corp-pbc]

GENERIC of Blockstack-net

generic-chain::
* decentralized-network,
...
* entity,

SPECIFIC of Blockstack-net

name::
* Mcs.Blockstack.specific,
* Mcs.BlockstackAsSpecific,

specific::

meta-info

this page was-visited times since {2018-12-15}

page-path: synagonism.net / Mcs-worldview / dirTchInf / Blockstack--blockchain-net

SEARCH::
· this page uses 'locator-names', names that when you find them, you find the-LOCATION of the-concept they denote.
GLOBAL-SEARCH:
· clicking on the-green-BAR of a-page you have access to the-global--locator-names of my-site.
· use the-prefix 'Blockstack' for structured-concepts related to current concept 'Blockstack--blockchain-net'.
LOCAL-SEARCH:
· TYPE CTRL+F "Mcs.words-of-concept's-name", to go to the-LOCATION of the-concept.
· a-preview of the-description of a-global-name makes reading fast.

footer::
• author: Kaseluris.Nikos.1959
• email:
 imgMail
• twitter: @synagonism
• steemit: https://steemit.com/@synagonism

webpage-versions::
• version.last.dynamic: filMcsDtcbnetBlockstack.last.html,
• version.0-1-0.2018-12-15 draft creation,

support (link)