diff --git a/Stacks FAQ.md b/Stacks FAQ.md deleted file mode 100644 index 66eba9e..0000000 --- a/Stacks FAQ.md +++ /dev/null @@ -1,139 +0,0 @@ -# Stacks FAQ - -Note this is an *ongoing Stacks FAQ* and can continue to be updated by various community and entity leaders. Please feel free to add question and answer suggestions via GitHub issues in the Stacks repository here - thanks! - -## **Blockchain state post mainnet launch** - -While Stacks 2.0 code has undergone significant testing (public testnets running for ~8 months; multiple security audits; bug bounties), like any complex software (~200K lines of code!) and protocol, there can be latent or emergent bugs (remember the early days of [Bitcoin](https://en.wikipedia.org/wiki/History_of_bitcoin) and [Ethereum](https://medium.com/mycrypto/the-history-of-ethereum-hard-forks-6a6dae76d56f)). See [this post](https://forum.stacks.org/t/500-blocks-into-the-stacks-2-0-mainnet/11606) for a summary of salient updates following the first 500 blocks, and this general [status update](https://blog.stacks.co/stacks-2-status-update). You can also view this [Stacks status page](https://stacks-status.com/ ). - -Additional details: We’ve crafted a proposal for dealing with any CRITICAL issues post-launch: critical meaning there’s active or imminent threat to the network security or assets. For everything else, we will follow the SIP process (outlined in [SIP-000](https://github.com/stacks-network/stacks-blockchain/blob/master/sip/sip-000-stacks-improvement-proposal-process.md)). - -Regarding critical but non-consensus-breaking updates (e.g. a crash on the networking path): - -- The Stacks Foundation, working with Stacks core developers, will publish a new release on Github. -- Anyone running a Stacks 2.0 node SHOULD upgrade. This would be just a routine software update, no impact to chainstate. - -Regarding critical, consensus-breaking updates (e.g. an exploit is discovered in PoX or Clarity): - -- The Stacks Foundation, working with Stacks core developers, will publish a new release on Github. -- Anyone running a Stacks 2.0 node MUST upgrade. This will be a hard-fork of the chain. -- In the first month or two immediately post launch, miners should anticipate and be prepared to (frequently) upgrade their nodes to: - - Incorporate fixes for critical issues in the first category. - - Incorporate regular updates that are not-critical, but still useful: for instance, improvements in logging, configuration management, monitoring etc. - - ## Stacks Token - - **What is the connection between Stacks and Bitcoin?** - -The Stacks 2.0 blockchain brings (a) scalable transactions and (b) general-purpose smart contracts to Bitcoin without modifying Bitcoin. Stacks miners use Bitcoin to mine newly minted Stacks, while Stacks holders can lock their STX in consensus to earn Bitcoin, making STX a unique crypto asset that is natively priced in BTC and distributes BTC earnings. - -Further details: The Clarity language, a secure and predictable smart contract language, goes live with Stacks 2.0 mainnet launch. It was developed by Princeton and MIT scientists over the last two years. Clarity makes it much harder to have smart contract bugs and allows developers to write logic around Bitcoin state directly. We believe bringing smart contracts directly to Bitcoin can make BTC more valuable as it can be put to productive use instead of being a passively held asset. - -**What can I do with STX?** - -STX are consumed when apps interact with [Clarity](https://clarity-lang.org/) smart contracts and users register blockchain-based names across hundreds of Blockstack apps. You can also Stack STX tokens to receive BTC rewards in a process called Stacking. - -## Stacks Wallet - -**What happened to STX through the transition from Stacks 1.0 to Stacks 2.0?** - -All data from Stacks 1.0 including prior token purchases and accounts were translated to Stacks 2.0. Now that the network has upgraded, you will need to download the [new Stacks wallet](https://www.hiro.so/wallet) to send Stacks. - -Upon downloading the new desktop wallet, STX holders will need to restore their holdings from your wallet seed phrase — either a 12 or 24 word phrase used to initially set up your wallet. - -You can always view your address balances at the [Stacks explorer](https://explorer.stacks.co/?chain=mainnet) as well. - -**What hardware wallets are compatible with the Stacks wallet?** - -Ledger is currently the only hardware wallet option supported. Trezor hardware wallets are no longer supported. - -The Stacks software wallet offers a software wallet option, but hardware wallets are generally recommended for security. Several other entities in the Stacks ecosystem are working on wallets, like [Secret Key Labs](https://www.secretkeylabs.com/), [Cerebro Wallet](https://cerebrowallet.com/) and the [Boom Wallet](https://boom.money/). - -Trezor hardware wallet users will have 3 options: - -1. Do nothing. Your Stacks will remain safe. You won't be able to send your Stacks until you upgrade to the new version of the wallet and recover your wallet from seed phrase OR transfer to Ledger. -2. [Recommended, Low Risk] Purchase a Ledger (Nano S or X) device and [restore it](https://support.ledger.com/hc/en-us/articles/360005434914-Restore-from-recovery-phrase) using the same seed phrase as on your Trezor. Then install the Stacks app from the Ledger Live app. -3. [High Risk]: It is also possible to recover your Trezor funds by using a software wallet. Be warned: it is not a recommended security practice to enter your hardware wallet seed phrases to a software wallet. Only use this method if you have removed all other funds from your Trezor device first. - -**Will BTC still be needed to transact on Stacks?** - -In the past, users have needed both STX and BTC to transact on Stacks. Upon Stacks 2.0 launch, only STX will be required for transacting in the STX ecosystem. - -Folks that held bitcoin in the Stacks 1.0 wallet can still access their Bitcoin via the [Stacks 1.0 wallet](https://www.hiro.so/questions/how-can-i-withdraw-the-btc-ive-deposited-into-the-stacks-wallet-v3-x) and are encouraged to send it elsewhere at their convenience. - -**View the full Stacks wallet FAQ at https://www.hiro.so/wallet** - -## Stacking - -**What is Stacking?** - -Stacking is the first consensus mechanism between two blockchains - in this case, the Bitcoin blockchain and Stacks blockchain. Stacking rewards network participants a base cryptocurrency, like Bitcoin, for locking up a newer cryptocurrency, like STX. Stackers participate in PoX consensus by sending useful information to the network in Stacking transactions. - -Further details: We encourage you to read the technical overview available in the [whitepaper](https://gaia.blockstack.org/hub/1AxyPunHHAHiEffXWESKfbvmBpGQv138Fp/stacks.pdf) and to review this [blog post](https://blog.blockstack.org/stacking-earnings-model/) with a breakdown of potential earnings. An overview of Stacking can be viewed at stacks.org/stacking - -**What is the minimum to participate in Stacking?** - -Stacking minimums are dynamic minimum based on participation levels. There are also several options for Stacking. See stacks.org/stacking for more info on Stacking partners, or visit Hiro.so/wallet to Stack via the Stacks wallet. - -- Users can pool their STX together to meet the minimum threshold using the delegate transactions. (Note that the minimum is dynamic and subject to change.) For example, third parties like OKCoin, Staked, and others anticipate enabling users to participate in Stacking even if they don't individually own the minimum threshold amount of STX. More info available on Stacks.org/stacking. - -- For further info on Stacking protocol minimums via the wallet, see the [Stacking summary page](https://github.com/stacks-network/stacks/blob/master/stacking.md) and [SIP-007](https://github.com/stacks-network/stacks-blockchain/blob/master/sip/sip-007-stacking-consensus.md) - -**When do Stacking rewards start?** - -Stacking rewards will be initiated following the first stacking cycle on the Stacks network, around end Jan. 2021 and paid out mid Feb. 2021. - -Further details: Upon launch, STX holders will be able to participate in the first Stacking cycle to test setup. BTC rewards are anticipated to start in following rewards cycle starting around the end of Jan. 2021. During the first reward cycle the network essentially getting up to speed and an anticipated beginning phase for the network. - -## Exchanges - -**What will happen to STX tokens held on exchanges and custody providers?** - -In the process of the hardfork from Stacks 1.0 to Stacks 2.0, users might see some expected impacts on exchange activity. Users with STX on exchanges or custody providers should refer to updates from respective exchanges and custody providers on how the network upgrade impacts them. - -We're providing all resources possible to make it a seamless experience for exchanges, custody providers, and their users. - -**Are Stox and Stacks the same?** - -Stox and Stacks are not related whatsoever and are two completely independent blockchain projects. Stox is a prediction market platform, currently with minimal usage. They also have a token with the ticker $STX, but with almost nonexistent volume and a market cap under $1M USD. - - -## **Stacks Mining** - -**Why would a miner spend BTC to mine STX?** - -Simple arbitrage between the value of STX on exchanges and STX minted by mining. - -Earlier this year we introduced a limited mining bonus that gives early miners even more than 1000 STX/block in the early weeks of the system. Specifically the STX mining schedule is: -- Years 0-4: 1000 STX/block -- Years 4-8: 500 STX/block -- Years 8-12: 250 STX/block -- Years 12+: 125 STX/block - -See the [Whitepaper](https://gaia.blockstack.org/hub/1AxyPunHHAHiEffXWESKfbvmBpGQv138Fp/stacks.pdf) for updated token economics. - -**How can I calculate the amount of BTC required for mining for one week?** - -See this community built [calculator](https://friedger.github.io/mining-calculator). There are lots of moving parts, but this calculator should help you get the gist of it. - -**What are the minimum hardware requirements for mining?** - -Just about any VPS or home PC will work - “mining” is not a compute intensive operation for stacks. That said, you need at least enough storage (currently 350GB) to hold bitcoin mainnet and 5GB/ish +/- per day in bandwidth. - 1. Stacks-node hardware requirements - 2. Bitcoind hardware requirements - -**Where can I learn more about STX mining?** - -- [Mining Docs](https://docs.stacks.co/start-mining/mainnet) -- https://stacks101.com/stx-mining-faq/ -- Comprehensive document of community-compiled [mining questions](https://paper.dropbox.com/doc/Stacks-2.0-Mining-Questions--BDjmfvyQCysQI_2cIuhmmi0GAg-63CU2wD4zQsiiU6XPUtlr) - -## Accessing Stacks 2.0 Apps - -**How will the launch of Stacks 2.0 impact Stacks applications?** - -In the immediate term, users’ experiences with Stacks login, usernames, and existing applications may be impacted. That is, users may be asked to authenticate their Stacks IDs and log back into apps at some point. However, the launch of Stacks 2.0 will generally result in several upgrades to Stacks applications, including improvements to the Stacks login and wallet experiences. More info on developer upgrades in progress [here](https://forum.stacks.org/t/apps-support-upon-launch-of-stacks-2-0-mainnet/11526/2). - -Note this is an *ongoing Stacks FAQ* and can continue to be updated by various community and entity leaders. Please feel free to add question and answer suggestions via GitHub issues in the Stacks repository here - thanks! - -Also see [Stacks docs](https://docs.stacks.co/understand-stacks/overview), [Forum](https://forum.stacks.org/), and [Discord](https://discord.gg/C8ycHu4)! diff --git a/Stacks Overview - Nov. version.pdf b/Stacks Overview - Nov. version.pdf deleted file mode 100644 index dcb41e8..0000000 Binary files a/Stacks Overview - Nov. version.pdf and /dev/null differ diff --git a/archive/FAQs.md b/archive/FAQs.md deleted file mode 100644 index 11c6d76..0000000 --- a/archive/FAQs.md +++ /dev/null @@ -1,6 +0,0 @@ -# FAQs - -For the latest Blockstack FAQs, see this page: - -[https://blockstack.org/faq] - diff --git a/archive/engineering/README.md b/archive/engineering/README.md deleted file mode 100644 index f086c78..0000000 --- a/archive/engineering/README.md +++ /dev/null @@ -1,182 +0,0 @@ -# Blockstack Engineering Handbook - -Welcome to the Blockstack Engineering Handbook! This is our attempt at building an engineering process as we build a new internet for decentralized apps. - -Here you'll find notes, checklists and knowledge that we've compiled during our journey. We'd love your thoughts, feedback, and, most importantly, your participation! - -## Table of Contents - -- [Sprints](#sprints) -- [Pull Requests](#pull-requests) -- [Repository Management](#repository-management) -- [Planning](#planning) -- [Meetings](#meetings) - -## Sprints - -We operate with 2 week sprints. At the beginning of each two week sprint, we have a weekly meeting followed by breakout sessions for the product and engineering teams where user stories and sprint items are generated. - -Mid-sprint, we have a weekly meeting and prune tasks from the sprint. - -### Sprint management - -We create a new Github organization kanban for each sprint with 5 columns: -* User Stories -* To Do -* Doing -* Delivered -* Accepted - -#### User Stories - -Create an issue for each user story in this column. The title of the story should generally be in the format 'As a `` I can ``. - -Each user story is assigned to a team member who is the owner of that user story for the sprint. The owner of the user story is responsible for breaking the user story into discrete tasks. Each of these tasks should be linked from the user story. These tasks are added to the To Do column of the sprint board. - -#### To Do - -**Responsible party:** User story assignee - -Tasks that need to be completed to satisfy the user stories belong here until someone starts working on them. - -This column uses the "To Do" Github automation enabling the options to put newly opened issues and reopened into this column automatically. - -#### Doing - -**Responsible party:** Issue assignee - -Move issues from the To Do to column into this column when you're working on them. - -#### Delivered - -**Responsible party:** Issue assignee - -When you believe you've completed an issue, mark it as closed and move it to this column. You should also send a pull request for the issue to `develop` or `master` as appropriate and place that pull request in this column. - -#### Accepted - -**Responsible party:** Pull request reviewer - -The reviewer of a pull request moves the pull request and any issues that it satisfies to the Accepted column when the pull request is approved. - -Issues that don't pass review should be moved by the pull request reviewer back to the To Do column. - - -## Pull Requests - -### Creating a pull request - -**Responsible party:** Issue assignee - -Pull requests are made from topic (feature, hotfix, etc) branches to `develop` or `master`. We never commit directly to these two branches. - -#### Checklist -- [ ] A description of what is included in the pull request -- [ ] Links to any other pull requests in other repos that are required for this pull request -- [ ] Instructions on how to test this pull request -- [ ] Links to the github issue(s) this pull request addresses -- [ ] Assigned to & review request from the person responsible for acceptance testing -- [ ] Tests written for all new or modified functionality -- [ ] Lint free -- [ ] Type declarations written for all modified files (JavaScript) -- [ ] Comments for any public functions - -*After successful review, the assignee merges the PR.* - -## Reviewing a pull request - -**Responsible party:** Reviewer - -Pull request reviews are conducted when a pull request is made from a feature or hotfix branch to `develop` or `master`. We do a single code review by a colleague who also works on the same codebase for most things. For anything that involves cryptography, secrets or consensus, we require at least 2 reviews by different people. - -#### Review checklist - -Below is a basic checklist of items that should be checked during a pull request code review. - -- [ ] Does the code work and does it perform its intended function? -- [ ] Is all the code easily understood? Do variable and function names clearly communicate their function? -- [ ] Is there properly formatted (eg. jsdoc for JavaScript) documentation for public and private API methods? -- [ ] Does any code duplicate functionality? -- [ ] Are there any global variables that can be removed? -- [ ] Is there any commented out code? -- [ ] Is there any logging or debugging code that isn't using a logger that can be removed? -- [ ] Do tests exist and do they adequately cover the changed behavior? -- [ ] Is the code being tested by any linter or type checking tools and does it pass? - - -## Repository management - -We generally use the [git flow](http://nvie.com/posts/a-successful-git-branching-model/) git repository workflow. - -The `develop` branch contains the latest delivered and accepted features. New features are generally developed against the `develop` branch unless they depend on the work done in another feature branch that has yet to be accepted and merged into `develop`. - -The `master` branch contains the most recent shipped release. - -## Planning - -- [ ] Before Thursday Engineering meeting: Each team member collects notes on their top priorities for the coming week, progress on existing items, concerns etc.. -- [ ] Thursday Engineering meeting: team members discuss their priorities and concerns along with those of the community. -- [ ] Meeting deliverable: consensus on a few bullet point priorities for the following week that will be presented to co-founders. These should be listed at the top of the agenda document and link to github issues if they exist. -- [ ] Co-founders & team members consider these proposed engineering priorities before the weekly team meeting. -- [ ] Co-founders present their priorities for the upcoming week having taken into account the engineering teams priorities & team discusses. -- [ ] After the weekly team meeting, there is an engineering & product breakout meeting to discuss implementation of the priorities and division of tasks. - -## Meetings - -Meetings are expensive, especially for creative people like designers and engineers. A 15 minute meeting can mean an hour or more of lost productivity. Meetings are also synchronous and mean that only those that can be available at that certain time have a chance to give input into the discussion. As such, we prefer to default to conducting discussions on github issues or in the forum and to minimize meetings whenever possible. - -We have a 45 minute weekly engineering meeting on Thursdays at 09:00 EST/EDT and generally try to fit items that need to be discussed in person as a group for that time as opposed to calling additional meetings. - -### Meeting rules - -- [ ] Meetings always begin on time: starting late penalizes the punctual and rewards the tardy. You should connect to the meeting conference call or arrive in the conference room a few minutes before the start time. -- [ ] Meetings always end on time: our team member and community member time is very valuable and they have other commitments. Disciplined meetings can cover the required topics within the allocated time. -- [ ] No meeting shall proceed without a written agenda: if it's not important enough to create an agenda, it's not important enough to hold a meeting -- [ ] Each meeting should have a stated goal, deliverable or outcome. This helps keep the meeting on track. - -### Calling a meeting - -*Responsible person:* Person who called the meeting (or delegate) - -- [ ] Create a forum post in the [meetings category](https://forum.blockstack.org/c/meetings) in the meetings category with date, time, agenda & zoom meeting link* -- [ ] Confirm attendee availability -- [ ] Send a calendar invite that includes the zoom meeting link & link to agenda - -** *Public meetings only* - -### Agenda contents - -*Responsible person:* Person who called the meeting (or delegate) - -- [ ] Items to be discussed -- [ ] Desired outcome or deliverable -- [ ] Links to any relevant previous meeting notes -- [ ] Links to any github issues or other items that provide background info so that attendees can be up to speed - -#### Proposing agenda topics - -Anyone can propose an agenda topic by replying to a meeting post with a post in the following format: - -``` -Topic: -Owner: -Priority: -Description: -Desired outcome: -``` - -### Holding meetings - -*Responsible person:* Person who called the meeting (or delegate) - -- [ ] At meeting start, paste link to forum meeting post in slack #engineering channel* -- [ ] Nominate a person to take notes -- [ ] Quick intros: Name, affiliation, location, one interesting or relevant fact (2 sentences per person max)* -- [ ] Record attendees -- [ ] Discuss agenda items recording notes in paper document including: -- [ ] Record key decisions -- [ ] Record actions items & parties responsible for executing on each item -- [ ] At conclusion of meeting, the note taker pastes the contents of paper doc as a reply to the forum meeting post -- [ ] Create relevant github issues for action items and link them from the forum meeting post - -** *Public meetings only* diff --git a/archive/evangelists/README.md b/archive/evangelists/README.md deleted file mode 100644 index 553ef0a..0000000 --- a/archive/evangelists/README.md +++ /dev/null @@ -1,7 +0,0 @@ -# Become a Blockstack Community Evangelist - -Information on becoming a Blockstack evangelist can be found here: - -[https://community.blockstack.org/evangelists] - - diff --git a/archive/events/README.md b/archive/events/README.md deleted file mode 100644 index 13ea308..0000000 --- a/archive/events/README.md +++ /dev/null @@ -1,5 +0,0 @@ -# Blockstack Events - -For information on Blockstack events, see this page: - -[https://community.blockstack.org/events] diff --git a/archive/events/slides/2015_09_blockstack_summit_jude.pdf b/archive/events/slides/2015_09_blockstack_summit_jude.pdf deleted file mode 100644 index 5f0f367..0000000 Binary files a/archive/events/slides/2015_09_blockstack_summit_jude.pdf and /dev/null differ diff --git a/archive/events/slides/2016-10-11-sf-meetup.pdf b/archive/events/slides/2016-10-11-sf-meetup.pdf deleted file mode 100644 index 1cacded..0000000 Binary files a/archive/events/slides/2016-10-11-sf-meetup.pdf and /dev/null differ diff --git a/archive/events/slides/2016_12_google_meetup_muneeb.pdf b/archive/events/slides/2016_12_google_meetup_muneeb.pdf deleted file mode 100644 index 0f0b6bb..0000000 Binary files a/archive/events/slides/2016_12_google_meetup_muneeb.pdf and /dev/null differ diff --git a/archive/events/slides/2016_6_dccl_virtualchain.pdf b/archive/events/slides/2016_6_dccl_virtualchain.pdf deleted file mode 100644 index 11e93a6..0000000 Binary files a/archive/events/slides/2016_6_dccl_virtualchain.pdf and /dev/null differ diff --git a/archive/events/slides/2017_03_princeton_meetup_jude.pdf b/archive/events/slides/2017_03_princeton_meetup_jude.pdf deleted file mode 100644 index fb8a507..0000000 Binary files a/archive/events/slides/2017_03_princeton_meetup_jude.pdf and /dev/null differ diff --git a/archive/events/slides/blockstack-summit-ryan-july27.key b/archive/events/slides/blockstack-summit-ryan-july27.key deleted file mode 100644 index b1c9774..0000000 Binary files a/archive/events/slides/blockstack-summit-ryan-july27.key and /dev/null differ diff --git a/archive/events/slides/source/2015_09_blockstack_summit_jude.odp b/archive/events/slides/source/2015_09_blockstack_summit_jude.odp deleted file mode 100644 index c26f216..0000000 Binary files a/archive/events/slides/source/2015_09_blockstack_summit_jude.odp and /dev/null differ diff --git a/archive/newsletters/README.md b/archive/newsletters/README.md deleted file mode 100644 index 67c67e2..0000000 --- a/archive/newsletters/README.md +++ /dev/null @@ -1,6 +0,0 @@ -# Newsletters - -The latest updates on Blockstack can be found at: - -[https://blockstack.org/updates] - diff --git a/archive/newsletters/newsletter-01-2018.md b/archive/newsletters/newsletter-01-2018.md deleted file mode 100644 index 8b13789..0000000 --- a/archive/newsletters/newsletter-01-2018.md +++ /dev/null @@ -1 +0,0 @@ - diff --git a/archive/newsletters/newsletter-02-2017.md b/archive/newsletters/newsletter-02-2017.md deleted file mode 100644 index 836cf7c..0000000 --- a/archive/newsletters/newsletter-02-2017.md +++ /dev/null @@ -1,36 +0,0 @@ -This month, there was an announcement of the new #DecentralizeTheWeb Challenge, a new release of Blockstack Core with code reorganization, a new private developer release of the Blockstack Browser, and a new release of the [blockstack.org](blockstack.org) website. In addition, Mediachain is now building on Blockstack and Blockstack was covered in MIT Tech Review, CoinDesk and TechCrunch. - -## #DecentralizeTheWeb Challenge - -We're announcing a new worldwide online event on February 12th called the #DecentralizeTheWeb Challenge. To participate, develop a demo or concept of a decentralized, server-less application that can be built using blockstack.js, then submit an application along with a proof of concept. The winner will get an Oculus Rift. Apply here. - -## Blockstack Core Reorganization - -[Blockstack Core](https://github.com/blockstack/blockstack-core) is undergoing a code reorganization that will make it easier for developers to run a Blockstack Core node. Formerly, there were two separate repositories comprising Blockstack Core - one for the blockchain indexer and one for the daemon, client, and storage drivers. Now they are being combined into a single repository, after code overlap and opportunities for simplification became clear. Now there's just one repository for the Blockstack Core reference implementation and running a node is cleaner and simpler than ever. - -## Blockstack Browser v0.2 Alpha - -This week, the Blockstack team came out with a new developer release of the [Blockstack Browser](https://github.com/blockstack/blockstack-browser) (codenamed Burgundy), which includes a brand new layout and a macOS application. Linux and Windows apps are coming soon and consumer versions of the browser will be distributed in future releases. - -## New blockstack.org Layout - -The Blockstack website got a new layout this week, with a new landing page, a new intro page for Blockstack basics, a new blog page (we're migrating away from Medium), and a new layout for the videos page. That said, the new site isn't done yet, as a new design will be applied to the new layout in the next release. - -## Mediachain Builds on Blockstack - -The Mediachain project, which provides a shared database for media content, [released a new version of their software with Blockstack support](https://blog.mediachain.io/blockstack-mediachain-6a505e2c4ef1). Medichain has integrated Blockstack DNS/naming and Blockstack Identity so that content creators on the system can tag their content and prove their identities. - -## Top Forum Posts - -[Blockstack for Mac Alpha](https://forum.blockstack.org/t/blockstack-for-mac-alpha/528) -[How does Blockstack scale for things like replacing the current DNS system as whole?](https://forum.blockstack.org/t/how-does-blockstack-scale-for-things-like-replacing-the-current-dns-system-as-whole/533) -[Incentives to run a Blockstack node](https://forum.blockstack.org/t/incentives-to-run-a-blockstack-node/503) -[Blockstack, Onename, and future applications](https://forum.blockstack.org/t/blockstack-onename-and-future-applications/529) -[Blockstack Core Architecture Diagram](https://forum.blockstack.org/t/blockstack-core-architecture-diagram/489) - -## Press Coverage - -[One Startups' Vision to Reinvent the Web for Better Privacy](https://www.technologyreview.com/s/603352/one-startups-vision-to-reinvent-the-web-for-better-privacy/) - MIT Technology Review, Jan 13th -[Hardly Anyone Seems to Be Using Zcash's Anonymity Features](http://www.coindesk.com/hardly-anyone-is-using-zcashs-anonymity-features-but-we-couldnt-tell-if-they-were/) - CoinDesk, Jan 13th -[Bitcoin-Powered Internet Advances With $4 Million Blockstack Funding](https://techcrunch.com/2017/01/05/blockstack-formerly-called-onename-just-raised-4-million/) - CoinDesk, Jan 6th -[Blockstack, formerly called Onename, just raised $4 million](https://techcrunch.com/2017/01/05/blockstack-formerly-called-onename-just-raised-4-million/) - TechCrunch, Jan 5th diff --git a/archive/newsletters/newsletter-03-2017.md b/archive/newsletters/newsletter-03-2017.md deleted file mode 100644 index d382dc2..0000000 --- a/archive/newsletters/newsletter-03-2017.md +++ /dev/null @@ -1,50 +0,0 @@ -# #DecentralizeTheWeb Challenge Winners - On February 16th Blockstack announced the submissions and winners of the [#DecentralizeTheWeb](https://twitter.com/hashtag/DecentralizeTheWeb?src=hash) challenge. The goal of the event was to get the Blockstack community involved in the creation of serverless apps and concepts. With only a few weeks heads up, we received some great submissions. Check out the recap [here](https://forum.blockstack.org/t/the-decentralizetheweb-recap/746)! - -# Blockstack CLI Video Tutorial Series - Like having your own personal instructor for every basic command for the Blockstack CLI. Learn how to install the CLI & use commands like $ renew, $ update, and $ register step by step with Blockstack core contributor, Jude Nelson! Get started today by clicking [here](https://www.youtube.com/playlist?list=PLXS8JJHIn4nGCU2uW85dHXpkQJ7QA5JkX). - -# Release of the New Blockstack Explorer - In case you missed our earlier announcement, we launched [Blockstack Explorer](https://explorer.blockstack.org/), a service for looking up info on Blockstack names and their associated addresses and transaction histories. Explorer gives a global view of all activity happening on the Blockstack network. It makes ownership of domains transparent and makes it easy for anyone to see the history of all domain name operations. Read the recent [announcement](http://blockstack.us14.list-manage1.com/track/click?u=394a2b5cfee9c4b0f7525b009&id=4c40716416&e=a5f3df994e) blog post and try it out yourself by looking up your registered name in the .id namespace. - -# AWS & FastSync - -@Muneeb A let me know whether we’ll have this - -MA: This is TBD given Amazon’s turn around time. I can work on the blog post and use my contact at AWS to speed things up. - -# Search Integration - -@Muneeb A - -MA: This is ready to be included. I can write a short description here. - -# v0.14.1 Update - Release 0.14.1 brings many incremental improvements over 0.14. -- *Fast Sync* - In its default setting, Blockstack needs to index the underlying blockchain in order to construct its name database and Atlas state. This can take days. To improve the user experience, 0.14.1 adds a fast_sync command that allows the user to fetch, verify, and bootstrap off of an existing node's recent state. Synchronizing with fast_sync takes only a few minutes. -- *Zone file wizard* - The CLI interface in 0.14.1 comes with an interactive zone file wizard that makes it easy to add, remove, and change the priority of URLs to off-chain data. Before, users were expected to craft new zone files by hand, which proved tedious and error-prone. - - For the full release notes, including *Upgrade Notes* and *Selected Bugfixes & Fixes* see the latest [release notes](https://github.com/blockstack/blockstack-core/blob/rc-0.14.1b/release_notes/changelog-0.14.1.md). -- ~~Premiere of FastSync (@Jude N can you add a sentence here?)~~ -- ~~Premiere of RESTful API (@Jude N can you add a sentence here?)~~ -- ~~Alpha of Storage API (@Muneeb A should this be included?)~~ - -_MA: Let’s take both the storage API and RESTful API out (RESTful can be separate release, it’s probably a blog post and the API is not defined/ready yet). We can give a summary of the v14.1 release notes and then link to the release notes on Github._ - -# Top Forum Posts -- [What's the Difference between Blockstack and Ethereum](https://forum.blockstack.org/t/what-is-the-difference-between-blockstack-and-ethereum/781/5) -- [How Blockstack Could Address Amazon S3 Outages](https://forum.blockstack.org/t/how-blockstack-could-address-amazon-s3-outages/773/6) -- [Cloudbleed: When Hidden Trust Parties Leak Your Data](https://forum.blockstack.org/t/cloudbleed-when-hidden-trusted-parties-leak-your-data/757) -- [PoS Blockchains Require Subjectivity to Reach Consensus](https://forum.blockstack.org/t/pos-blockchains-require-subjectivity-to-reach-consensus/762) -- [Getting High-Quality Engineers Interested in the Blockchain Space](https://forum.blockstack.org/t/getting-high-quality-engineers-interested-in-the-blockchain-space/749) -- [Update for OpenBazaar Users](https://forum.blockstack.org/t/update-for-openbazaar-users/688) -- [How Does Blockstack Scale for Replacing the Current DNS](https://forum.blockstack.org/t/how-does-blockstack-scale-for-things-like-replacing-the-current-dns-system-as-whole/533) -- [Blockstack + Lightning](https://forum.blockstack.org/t/blockstack-lightning/689?u=larry) - -# Press Coverage -- Mar 2, Harvard Business Review [How Blockchain Applications Will Move Beyond Finance](https://hbr.org/2017/03/how-blockchain-applications-will-move-beyond-finance) -- Feb 27, CampaignLive [Blockchain set to move intermediary brands that 'add no value'](http://www.campaignlive.co.uk/article/blockchain-set-remove-intermediary-brands-add-no-value/1425502#bgF4o1fOCacJEQuf.99) -- Feb 21, Coindesk [Coindesk: Decentralized Web Gets Visual Aid With New Blockstack Explorer](http://www.coindesk.com/decentralized-web-gets-visual-aid-new-blockstack-explorer/?utm_content=buffer7d93f&utm_medium=social&utm_source=twitter.com&utm_campaign=buffer) -- Feb 21, Data Center Journal [Data Center Journal: WWW Creator Calls for Internet Decentralizations & Encryption](https://www.datacenterjournal.com/world-wide-web-creator-calls-internet-decentralization-encryption/) -- Feb 17, Coindesk [3 Big Blockchain Ideas MIT is Working on Right Now](http://www.coindesk.com/3-big-blockchain-ideas-mit-working-right-now/) - diff --git a/archive/newsletters/newsletter-05-2017.md b/archive/newsletters/newsletter-05-2017.md deleted file mode 100644 index 52740ff..0000000 --- a/archive/newsletters/newsletter-05-2017.md +++ /dev/null @@ -1,41 +0,0 @@ -*Blockstack Storage and Atlas Network Whitepaper* - -At Blockstack, we’ve been (quietly) building a new internet that has been running in production for over 3 years now. Our design removes any trust points from the middle of the network. This internet allows for true decentralization, as envisioned by Sir Tim Berners-Lee and Vint Cerf. - -We’ve been refining the design of our blockchain, peer network, and storage over the last years of production experience and today, we’re excited to announce the details of these systems in a [Blockstack whitepaper](***Insert_URL-here***). - -*Decentralized Summer* - -The core team is proud to announce a new developer program, "Blockstack's Decentralized Summer", running from June 1st to August 31st. The focus is on building decentralized applications that use identity, storage, and payments on the decentralized internet powered by Blockstack. - -During this time you will build one of the first ten apps, like a decentralized twitter, uber, or voting system, that will be featured to over 70,000 decentralized app users. The Blockstack core team will work with you step-by-step via slack and weekly check-ins while you'll receive $6,000/mo. If you or someone you know is interested, visit [the Decentralized Summer page](https://www.eventbrite.com/e/blockstacks-decentralized-summer-tickets-34395687427). - -*Tor Integration* - -Blockstack now has the ability to resolve Tor hidden services using human-readable names. For example, instead of going to `3g2upl4pq6kufc4m.onion`, users can go to `duckduckgo_tor.id` to get to DuckDuckGo. - -We have released a proof-of-concept here: https://github.com/blockstack/blockstack-tor - -*New Blockstack Meetups* - -Say hello to brand new meetup groups: [Blockstack Cuba](https://www.meetup.com/Blockstack-cuba/), run by organizer Olemis Lang, and [Blockstack Portland](https://www.meetup.com/Blockstack-Portland/), organized by Dan Trevino. The core team is looking forward to visiting both locations for their inaugural meetups! - -*Popular on the Forum* - -- [Diploma Project about Blockstack authentication protocol](https://forum.blockstack.org/t/diploma-project-about-blockstack-authentication-protocol/850) -- [Tor Project considering Blockstack for `.tor` TLD](https://forum.blockstack.org/t/tor-project-considering-blockstack-for-tor-tld/919) -- [Blockstack on Mobile](https://forum.blockstack.org/t/blockstack-on-mobile/804) -- [Blockstack on iOS Constraints](https://forum.blockstack.org/t/blockstack-on-ios-constraints/898) -- [Protecting Core from malicious apps](https://forum.blockstack.org/t/protecting-core-from-malicious-apps/911) -- [Blockchain Agility, ASICBOOST & Building on the Strongest Chain](https://forum.blockstack.org/t/blockchain-agility-asicboost-building-on-the-strongest-chain/923/2) -- [Zone file contents and blockstack update command](https://forum.blockstack.org/t/zone-file-contents-and-blockstack-update-command/616/6) - -*In the News* - -- May 1, Nasdaq, [How Blockstack Uses Bitcoin as the Base for Their Decentralized App Ecosystem](http://www.nasdaq.com/article/how-blockstack-uses-bitcoin-as-the-base-for-their-decentralized-app-ecosystem-cm782165) -- Apr, 27, Foundation for Economic Education, [Six Companies That Are Quietly Securing Our Identities](https://fee.org/articles/six-companies-that-are-quietly-securing-our-identities/) -- Apr, 24, The Bitcoin Game, [The Bitcoin Game: Ryan Shea, Blockstack for Beginners](https://letstalkbitcoin.com/blog/post/the-bitcoin-game-44-ryan-shea-blockstack-for-beginners) -- Apr, 17, Lunduke Hour, [Decentralized Internet w/ Blockstack](https://youtu.be/i1fThdPbAEA?t=3m46s) -- Apr, 15, Brave New Coin, [Tor May Use Bitcoin to Enable User-Friendly Onion Addresses](https://bravenewcoin.com/news/tor-may-use-bitcoin-to-enable-user-friendly-onion-addresses/) -- Apr, 14, Cryptocoins News, [Blockstack Co-Founder: Segwit is More Than Malleability Fixes & Scaling](https://www.cryptocoinsnews.com/blockstack-co-founder-segwit-is-more-than-malleability-fixes-scaling/) -- Apr, 3, Tor Project [Cooking With Onions: Names for your onions](https://blog.torproject.org/blog/cooking-onions-names-your-onions) diff --git a/archive/newsletters/newsletter-09-2017.md b/archive/newsletters/newsletter-09-2017.md deleted file mode 100644 index 2127935..0000000 --- a/archive/newsletters/newsletter-09-2017.md +++ /dev/null @@ -1,60 +0,0 @@ -**Blockstack is now a Public Benefit Corp** - -As we’re building towards a larger ecosystem, we want to better align the structure of our for-profit corporation with our mission of enabling an open, decentralized internet. We have done that by transitioning to a Public Benefit Corporation. - -A Public Benefit Corp (PBC) is a for-profit company that is obligated to uphold certain commitments for the public good and not just stockholder interests. - -The mission of Blockstack PBC is to enable an open, decentralized internet. Blockstack PBC is committed to: - -a) keeping the core Blockstack software open-source, and -b) supporting the decentralization of the Blockstack network. - -Read more about the Public Benefit Corp designation [here](https://blockstack.org/blog/public-benefit-corp) - -**Announcing Signature Bounties** - -We are excited to announce the first global app bounty from the Blockstack Signature Fund: a $15,000 bounty led by our partner, Compound VC, to build a private and secure cryptocurrency portfolio management app using Blockstack for storage and identity. - -Signature Bounty winners (to be announced Nov 1) may receive follow-on funding from top venture capitalists and be asked to present at one of our upcoming events around the world. For more details go to the bounty sign up page to register: tokenportfolio.eventbrite.com. - -**IMPORTANT: Future Announcements about the Blockstack Token** - -We will announce more details about the token sale in the coming weeks. - -From what we've seen with previous projects, we expect a number of phishing sites to pop up. Imposters will announce details around the timing and location of fake token sales. - -With this in mind, it's extremely important to be careful with any communication related to the Blockstack sale. When the sale is set to start, we will give ample advanced notice and will never ask you to click a link. We will instead direct you to type "blockstack.org" directly into your browser. Further, it's important you do not trust any information related to the token sale unless it's (1) published on https://blockstack.org (2) published on our github at github.com/blockstack (3) confirmed by @Blockstack and @muneeb and @ryaneshea on Twitter. - -**New Windows Support for Blockstack Browser** - -We've shipped a [developer release](https://github.com/blockstack/blockstack-browser/releases) of Blockstack Browser for Windows. Now Windows users will have an automated installer which sets up an environment for them to explore the new decentralized web. Be sure to let us know how it works for you! - -**New Blockstack Meetups** - -New meetups announced in [Japan](https://www.meetup.com/Blockstack-Japan/), [Buenos Aires](https://www.meetup.com/Blockstack-Buenos-Aires/), [Melbourne](https://www.meetup.com/Blockstack-Melbourne/), [Brisbane](https://www.meetup.com/Blockstack-Brisbane/), and [Bangalore](https://www.meetup.com/Blockstack-Bangalore/). A Recent meeup in SF featured Lightning's Olaoluwa Osuntokun who talked on HTLC-DASH: Micropayments for Decentralized Media Streaming ([slides here](https://twitter.com/roasbeef/status/911415042368614400)). - -If you are looking to start a meetup, join the #evangelists channel in [chat.blockstack.org](chat.blockstack.org) or simply follow the instructions in the evangelist [github repo](https://github.com/blockstack/blockstack/blob/master/evangelists/meetup.md). We'd love to have you involved in growing the Blockstack ecosystem. - - -**Popular on the Forum** - -- [Annual Hard Fork](https://forum.blockstack.org/t/annual-hard-fork-2017/1618/6) -- [New Features Enabled by a Layer 2 Token](https://forum.blockstack.org/t/new-features-enabled-by-a-layer-2-token/1327/11) -- [Bringing Decentralized Governance & Incentive Protocols to Blockstack](https://forum.blockstack.org/t/bringing-decentralized-governance-incentivized-protocols-to-blockstack/1315/7) - - -**In the News** - -* Sep 5, 2017 - **Forbes** - [Blockstack On Getting Independence From Google, Facebook And Amazon](https://www.forbes.com/sites/laurashin/2017/09/05/blockstack-on-how-to-take-control-from-google-facebook-and-amazon/) -* Sep 5, 2017 - **Unchained Podcast** - [Blockstack On Getting Independence From Google, Facebook And Amazon](http://unchained.forbes.libsynpro.com/blockstack-on-getting-independence-from-google-facebook-and-amazon) -* Sep 2, 2017 - **CoinDesk** - [Blockstack Today: 5 Apps Already Being Built on the Decentralized Web](https://www.coindesk.com/building-blockstack-five-firms-show-us-just-platform-capable/) -* Aug 18, 2017 - **MIT Media Lab** - [Back to the Future of The Decentralized Web](http://dci.mit.edu/decentralizedweb) -* Aug 16, 2017 - **Wall Street Journal** - [Blockstack Launches $25 Million Fund for Blockchain Startups](https://www.wsj.com/articles/blockstack-launches-25-million-fund-for-blockchain-startups-1502883001) -* Aug 16, 2017 - **Axios** - [Blockstack debuts $25 million fund to invest in blockchain apps](https://www.axios.com/blockstack-debuts-25-million-fund-to-invest-in-blockchain-apps-2473465582.html?utm_source=twitter&utm_medium=twsocialshare&utm_campaign=organic) -* Aug 16, 2017 - **CoinDesk** - [Investor Albert Wenger to Fund 'XPRIZE' for Blockchain-Powered Blogs](https://www.coindesk.com/investor-albert-wenger-to-fund-xprize-for-blockchain-powered-blogs/) -* Aug 16, 2017 - **CoinDesk** - [Investor Naval Ravikant Wants to Disrupt Twitter With Blockchain 'XPRIZE'](https://www.coindesk.com/investor-naval-ravikant-wants-disrupt-twitter-blockchain-xprize/) -* Aug 16, 2017 - **CoinDesk** - [ICO Meets VC: Blockstack Raises $25 Million for Decentralized Internet Fund](https://www.coindesk.com/ico-meets-vc-blockstack-raises-25-million-decentralized-internet-fund/) -* Aug 16, 2017 - **Bitcoin Magazine** - [Blockstack Partners with VCs to Launch $25 Million Blockstack Signature Fund](https://bitcoinmagazine.com/articles/blockstack-partners-vcs-launch-25-million-blockstack-signature-fund/) -* Aug 16, 2017 - **VentureBeat** - [Blockstack announces $25 million fund to rebuild the internet for a blockchain world](https://venturebeat.com/2017/08/16/blockstack-announces-25-million-fund-to-rebuild-the-internet-for-a-blockchain-world/) -* Aug 16, 2017 - **International Business Times** - [Why You Should Be Excited About Blockstack And The Decentralization Movement](http://www.ibtimes.com/why-you-should-be-excited-about-blockstack-decentralization-movement-2579340) -* Aug 17, 2017 - **The Next Web** - [How blockchain solves the complicated data-ownership problem](https://thenextweb.com/contributors/2017/08/17/blockchain-solves-complicated-data-ownership-problem/#.tnw_3Wix5qOC) diff --git a/archive/papers/README.md b/archive/papers/README.md deleted file mode 100644 index bfb3065..0000000 --- a/archive/papers/README.md +++ /dev/null @@ -1,4 +0,0 @@ -# Papers - -This directory is purely archival. For the latest versions of -Blockstack whitepapers, see [https://blockstack.org/papers] diff --git a/archive/papers/blockstack_login16.pdf b/archive/papers/blockstack_login16.pdf deleted file mode 100644 index dbaf3d0..0000000 Binary files a/archive/papers/blockstack_login16.pdf and /dev/null differ diff --git a/archive/papers/blockstack_usenix16.pdf b/archive/papers/blockstack_usenix16.pdf deleted file mode 100644 index 53f59ec..0000000 Binary files a/archive/papers/blockstack_usenix16.pdf and /dev/null differ diff --git a/archive/papers/feedback/README.md b/archive/papers/feedback/README.md deleted file mode 100644 index 2c2f990..0000000 --- a/archive/papers/feedback/README.md +++ /dev/null @@ -1,20 +0,0 @@ -### Giving feedback on Blockstack whitepapers - -We love getting feedback from our open-source community on the whitepapers. The two papers we're currently most interested in getting feedback on are: - -1. Blockstack [technical whitepaper](../whitepaper.pdf) -2. Blockstack [token whitepaper](../tokenpaper.pdf) - -To give your feedback, follow these instructions: - -1. Fork this repo. -2. Add a new .md file in the papers/feedback directory with a name like tokenpaper_feedback_muneeb_oct_2017.md -3. Fill out your comments. Make sure to include page numbers for specific comments. -4. Submit a pull request. - -We'll generally accept most/all pull requests for feedback. Sending negative feedback is totally fine just please be polite. -The only exception for not accepting a feedback pull request is if someone is spreading misinformation. - -If you prefer to submit your feedback privately, you can email it to token@blockstack.com. - -This directory can also help us acknowledge and thank people. Feel free to ask any questions and thanks for taking the time to help improve the whitepapers! diff --git a/archive/papers/feedback/tokenpaper_feedback_martinb_20171017.md b/archive/papers/feedback/tokenpaper_feedback_martinb_20171017.md deleted file mode 100644 index 69c62ba..0000000 --- a/archive/papers/feedback/tokenpaper_feedback_martinb_20171017.md +++ /dev/null @@ -1,3 +0,0 @@ -The first paragraph of page 8, "Atomic swaps with a native Blockstack token do not require third-party services and can more expressive conditions for exchange of assets." is missing a word after "services and can". - -Perhaps you mean "Atomic swaps with a native Blockstack token do not require third-party services and can enable more expressive conditions for exchange of assets."? \ No newline at end of file diff --git a/archive/papers/tokenpaper.pdf b/archive/papers/tokenpaper.pdf deleted file mode 100644 index 4f3462b..0000000 Binary files a/archive/papers/tokenpaper.pdf and /dev/null differ diff --git a/archive/papers/virtualchain_dccl16.pdf b/archive/papers/virtualchain_dccl16.pdf deleted file mode 100644 index ed0160f..0000000 Binary files a/archive/papers/virtualchain_dccl16.pdf and /dev/null differ diff --git a/archive/papers/whitepaper.pdf b/archive/papers/whitepaper.pdf deleted file mode 100644 index 75e5e37..0000000 Binary files a/archive/papers/whitepaper.pdf and /dev/null differ diff --git a/archive/roadmap.md b/archive/roadmap.md deleted file mode 100644 index fee978b..0000000 --- a/archive/roadmap.md +++ /dev/null @@ -1,5 +0,0 @@ -# Roadmap - -For the latest Blockstack roadmap, see: - -[https://blockstack.org/roadmap] diff --git a/archive/tutorials/README.md b/archive/tutorials/README.md deleted file mode 100644 index edc464b..0000000 --- a/archive/tutorials/README.md +++ /dev/null @@ -1,6 +0,0 @@ -# Tutorials - -For the latest tutorials from Blockstack see: - -[https://docs.blockstack.org/browser/hello-blockstack.html] - diff --git a/archive/videos/README.md b/archive/videos/README.md deleted file mode 100644 index 6c0e027..0000000 --- a/archive/videos/README.md +++ /dev/null @@ -1,5 +0,0 @@ -# Videos - -For Blockstack videos see: - -[https://blockstack.org/videos] diff --git a/images/Screen Shot 2020-09-25 at 1.20.10 PM.png b/images/Screen Shot 2020-09-25 at 1.20.10 PM.png deleted file mode 100644 index b401838..0000000 Binary files a/images/Screen Shot 2020-09-25 at 1.20.10 PM.png and /dev/null differ diff --git a/images/Screen Shot 2020-09-25 at 1.33.18 PM.png b/images/Screen Shot 2020-09-25 at 1.33.18 PM.png deleted file mode 100644 index 6968018..0000000 Binary files a/images/Screen Shot 2020-09-25 at 1.33.18 PM.png and /dev/null differ diff --git a/images/krypton.png b/images/krypton.png deleted file mode 100644 index 14d4144..0000000 Binary files a/images/krypton.png and /dev/null differ diff --git a/images/testnet-phases.png b/images/testnet-phases.png deleted file mode 100644 index 904308a..0000000 Binary files a/images/testnet-phases.png and /dev/null differ diff --git a/images/testnetphasesupdated b/images/testnetphasesupdated deleted file mode 100644 index 8b13789..0000000 --- a/images/testnetphasesupdated +++ /dev/null @@ -1 +0,0 @@ - diff --git a/whenmainnet.md b/whenmainnet.md deleted file mode 100644 index 53d3f24..0000000 --- a/whenmainnet.md +++ /dev/null @@ -1,31 +0,0 @@ -UPDATE: Stacks 2.0 was successfully launched by independent miners on Jan 14th, 2021. - -# What is Stacks 2.0? -Stacks 2.0 is a new layer-1 blockchain that uses [Proof-of-Transfer (PoX)](https://blockstack.org/pox.pdf) to connect to Bitcoin. Stacks 2.0 brings apps and [predictable smart contracts](https://clarity-lang.org) -to Bitcoin. Assets and contracts are secured by Bitcoin, and STX holders can earn BTC by participating in consensus. See an [earnings calculator](https://docs.google.com/spreadsheets/d/1OJ_pFQ8njpsBPYtWV9bXRx_aJejeXIkQwwiZzuWhvZQ/edit#gid=505229599) and a [community intro video](http://stacks.zone/#IntroVideo)). - -# When is Stacks 2.0 mainnet launching? - -Stacks 2.0 is currently [being implemented](https://github.com/stacks-network/stacks-blockchain) -in the Rust language, and the mainnet launch is divided into [four testnet phases](https://www.blockstack.org/testnet). - -We're in the home stretch. Stacks 2.0 is on track to reach code completion by Dec 15th. Mainnet launch is set for Jan 14th 2021. Xenon the Stacks 2.0 Phase 4 is currently in the implementation phase. Microblocks is one feature that will be implemented in Phase 4 in addition to testing. Here is a status visual from testnet.blockstack.org (as of Nov 19th): - -Screen Shot 2020-09-25 at 1 20 10 PM - -# What is the status of the final Phase 4 of testnet (Xenon)? - -Phase 4 (Xenon) is currently in the implementation stage. - -You can follow Xenon's progress on [Github here](https://github.com/orgs/stacks-network/projects) and on Discord on the [#stacks-core-devs channel](https://discord.gg/stacks-621759717756370964). -Here is a screenshot of Xenon's status as of Thur Nov 19th: - -Screen Shot 2020-11-19 at 5 42 09 PM - -You can see the status of the currently deployed Phase 3 (Krypton) [here](http://status.test-blockstack.com/). - -Thank you again to all those contributing to Stacks 2.0 and for your patience as we diligently work together toward a quantum leap for the ecosystem. - -# Where do I ask questions? - -You can join the [Stacks Telegram group](https://t.me/BlockstackChat) to ask any further questions!