Weekly Stacks 2.0 Progress Thread

Each week progress on Stacks 2.0 will be published below:

2.24.2020

  • Proposed an update to SIP-007 that would make the threshold level of STX holdings required to participate in Stacking dependent on the level of participation. The update also includes a time-windowing proposal for Proof of Transfer. → Details on Github
  • Implemented the Clarity Smart Contract traits to enable Dynamic Dispatch, and the issue is now under review to be merged. → Details on Github
  • Finished an issue to enable transactions to be stored that are received from the peer test network. This will allow a transaction mempool on the upcoming STX Mining test net. → Details on Github
  • The team is currently considering building support for pooling/delegation for stacking as a native feature of the protocol. This could remove the need to give up custody or use a smart contract to pool. We are still very early in this process, and if we do decide to build any delegation capability we will first circulate a SIP with details.

To receive updates on Stacks 2.0 Progress and the upcoming launch of the STX Mining and Stacking test net, sign up for the PoX mailing list here

Important disclaimer

Blockstack PBC is not registered, licensed, or supervised as a broker dealer or investment adviser by the Securities and Exchange Commission (SEC), the Financial Industry Regulatory Authority (FINRA), or any other financial regulatory authority or licensed to provide any financial advice or services.

Forward-looking statements

This communication contains forward-looking statements that are based on our beliefs and assumptions and on information currently available to us. In some cases, you can identify forward-looking statements by the following words: “will,” “expect,” “would,” “intend,” “believe,” or other comparable terminology. Forward-looking statements in this document include, but are not limited to, statements about our plans for developing the platform and potential mining operations. These statements involve risks, uncertainties, assumptions, and other factors that may cause actual results or performance to be materially different. We cannot assure you that the forward-looking statements will prove to be accurate. These forward-looking statements speak only as of the date hereof. We disclaim any obligation to update these forward-looking statements.

2 Likes

3.2.2020

  • The update to SIP-007 is in QA Review. This would make the threshold level of STX holdings required to participate in Stacking dependent on the level of participation. The update also includes a time-windowing proposal for PoX. → Details on Github
  • The team finished implementing dynamic cost tracking for runtime and analysis for the Clarity VM. The SIP this is included in can be seen in detail here.
  • The team is working on an issue that enables the Genesis Block of the Stacks 2.0 test net, which will better enable testing token transfers on test net. → Details on Github
1 Like

Thanks @xan

3.9.2020

  • Addition of native support for Stacking Delegation to SIP-007: This will allow any STX Holder to delegate the requirements to Stack to a third party, without losing custody or making a transfer of their STX Tokens. This may lower the barrier for individuals to build delegation services for STX Holders and for institutional providers to integrate them.
    Details on Github

3.16.2020

Stacks 2.0 Weekly Update: Testnet Coming Soon!

Welcome back, this week’s edition is particularly exciting as there are new details available on the upcoming launch of the public Stacks 2.0 tesnet. Projected for the week of March 30th, the testnet will operate in several phases in preparation for a successful mainnet launch.

→ Learn more about the Stacks 2.0 testnet in this forum post.

Keep watching these updates for new information, we’ll be sending important information leading up to the testnet going live and you’ll receive a notification when it’s publicly accessible.

In addition to working on the testnet, here is what the Stacks blockchain developers have been focused on this past week:

Welcome back to the weekly update on the anticipated Stacks 2.0 protocol upgrade, including PoX. Please be sure to join the Blockstack Community Townhall on March 25th (9:30am EDT). The focus will be the soon-to-launch Stacks 2.0 testnet previewed in this post last week.
→ Register

Here are some highlighted technical updates from this past week:

2 Likes

3.30.2020

Welcome back to the weekly update on the anticipated Stacks 2.0 protocol upgrade, including PoX. The biggest update is that the STX Mining testnet launch has been pushed back to the middle of April. We will follow up with an exact launch date as soon as possible.

Here are some highlighted technical updates from this past week:

  • Merged a PR to implement admission checks for transactions into the testnet mempool. This will enable checks to ensure transactions are parsed correctly, have paid fees, paying accoutns have enough funds, and more. The full PR can be seen here.
  • PR for block downloader in review. Right now, nodes will already handshake with one another and fetch the other’s neighbors to build a view of the peer graph. This PR extends this to asking those neighbors for block inventories, and to fetch blocks it does not know about from neighboring inventories via HTTP, and implements a DNS resolver that the p2p network thread can issue requests to and from. The full proposal can be seen here.
  • Proposed a refactor of Clarity Values in order to better represent Clarity Values with Typescript. The full proposal can be seen here .
  • A transaction page for the Stacks explorer has been proposed and is currently a work in progress. The full proposal can be seen here .

4.6.2020

Welcome back to the weekly update on the anticipated Stacks 2.0 protocol upgrade, including PoX. Here are some highlighted technical updates from this past week:

  • Implemented events and improved the developer experience for testnet. This includes the addition of a socket in local testnet, testnet genesis block configuration, and an upgrade of logs to show artifacts of executed transactions. The full PR can be seen here .
  • Implemented block downloader logic. Now, once a node has neighbors, it will ask them for their block inventories, then confirm blocks it does not already know via HTTP. The full PR can be seen here .
  • Merged a PR to enforce memory limits on Clarity Smart Contract run time. The full PR can be seen here.
  • Added the ability to specify post conditions when building the following transaction types: 1) STX token transfers 2) Contract deploys 3) Contract function calls. The transaction builder API has also been refactored to use an options object for some parameters to make it easier to use. The full PR can be seen here.

4.14.2020

Welcome back to the weekly update on the anticipated Stacks 2.0 protocol upgrade, including PoX. Here are some highlighted technical updates from this past week:

  • Added support for contract Principals in token transfer transactions. Principals are a Clarity native type that represents a spending entity. Previously, the token transfer transaction type only supported transferring tokens to another STX address, but not to another contract. This removes that limitation. Documentation on Principals is here and the merged PR is on Github.
  • Proposed a PR that sets an initial/draft block limit for the testnet. This is the maximum number of operations per block, or, put differently, the total amount of computation and storage that can be performed in a single block. This will change as we get closer to mainnet due to real data, but the limit is initially determined using benchmarks detailed in the PR on Github.
  • Proposed a PR to implement the transaction mempool and block, microblock, and relay logic. A microblock is essentially a single transaction that becomes an addendum to a block. The full details of the 4 inter-related changes this PR makes can be seen on Github.
  • Proposed a PR to add the ability to broadcast transactions to the network, which will be essential for the testnet. The full details can be seen on Github.

4.20.2020

Welcome back to the weekly update on the anticipated Stacks 2.0 protocol upgrade, including PoX. We’re only a few days away from the launch of the testnet! Here are some highlighted technical updates from this past week:

  • Added a code of conduct to the stacks-blockchain repo. It’s highly recommended everyone read this heading into the testnet period. View and comment on Github.
  • Merged a PR to implement the transaction mempool and block, microblock, and transaction relay logic for testnet. This will make it possible to see and use transactions from the mempool to propose a block to mine, as well as adding the necessary support for blocks and microblocks to occur and that information be relayed to the rest of the network. The full issue can be seen on Github.
  • Merged PRs to make it easier to find and analyze transactions on testnet. These included fixing how meta tags are managed to improve accessibility, adding a ‘transactions not found’ component, and adding a transaction page header.
  • Made improvements to performance and concurrency issues with the on-disk representation of chain state. → More on Github
  • Reviewing work that addresses a host of networking performance related issues for testnet. → More on Github
  • Updated Clarity documentation, find the latest docs here.

Join the Community Townhall on April 24th to learn more about the anticipated Stacks 2.0 testnet, ask questions, and connect with the global community → RSVP

1 Like

4.27.2020

Welcome back to the weekly update on the anticipated Stacks 2.0 protocol upgrade, including PoX. The Neon phase of the testnet went live last week. Here are some of the highlighted technical updates and fixes from the first week of Neon:

  • Added a better Genesis sequence and improved Verifiable Random Function key management for the testnet. This will help the first block to be mined more easily and allow testnet STX Mining to begin. The full PR is on Github.
  • Improved block relay and download performance. The full PR is on Github.
  • Fixed an issue with how Neon nodes were generating block commits. In particular, the miner would send bad commits if a sortition was missed and then never recover. The full PR is on Github.
  • Added the ability to broadcast transactions to the Neon network. The full PR is on Github.
  • Added support for finding a Clarity smart contract by searching for the transaction ID on the test network. The full PR is on Github.
  • Additional initial bug fixes related to the Neon testnet can be seen here.

Visit testnet.blockstack.org to get started on Neon Testnet and run a Stacks Node.

5.5.2020
Mining Coming Soon!

Welcome back to the weekly update on the anticipated Stacks 2.0 protocol upgrade, including PoX. The Neon phase of the testnet went live two weeks ago with work since focused on eliminating bugs and improving overall resiliency.

The team is now primarily focused on opening up mining for everyone (ETA a few days) and readying Argon, the next phase of testnet which will offer a working explorer and Clarity enhancements (tentative ETA, 1 week).

Here are some of the highlighted technical updates and fixes from the second week of Neon:

  • Improved transaction error messaging. This makes error responses better for programmatic usage. → Github
  • Made Neon nodes configurable as a miner/not-miner. This allows someone to start up a node specifically for the purposes of mining. → Github
  • Updated the transaction builder to automatically fetch the account nonce from a Stacks node if a nonce is not specified, making integration easier. → Github
  • Added support for strings to contract principals and asset info IDs, improving the developer experience. → Github
  • Added a fee estimate function to calculate the estimated fee of an STX transaction. This was also added to the Clarity Smart Contract builder, which will set fees automatically if not specified. → Github

Visit testnet.blockstack.org to get started on Neon Testnet and run a Stacks Node.

5.11.2020
Welcome back to the weekly update of the anticipated Stacks 2.0 upgrade, including Proof of Transfer (PoX). The Neon phase of the testnet went live three weeks ago, and we’re only a few days away from the launch of Argon (Phase 2).

Today, the major update is that STX Mining functionality has been added to the testnet!

During this phase, you’ll be able to try ‘basic Proof of Transfer’ mining, which works when miners transfer testnet Bitcoin to a burn address to earn testnet STX. This allows miners to test out basic functionality and serves as a prelude to full Proof of Transfer mining. A more complete version of testnet Proof of Transfer mining will be introduced in phase three, Krypton.

Prospective miners should try out STX Mining by first spinning up a node and then installing the STX Mining package.

Click here to get started testnet mining

2 Likes

5.19.2020
If you’ve been following these weekly updates, you know we’ve been uncovering and fixing issues on the Stacks 2.0 Testnet as they come up — especially reliability and performance issues. This is exactly what we hoped to accomplish with Neon and we thank everyone for testing, providing feedback, submitting bug reports, etc.!

Last week, testnet STX Mining was made available and more functionality is expected soon as part of Phase 2 (Argon). Stay tuned for more on that!

In the meantime, we wanted to make sure you didn’t miss the Clarity Hackathon. Submissions for the first phase of the hackathon can be submitted up until May 29th , so if you’ve been meaning to try out Clarity, now is a great time. You can submit up to 3 smart contracts, with a top prize of $1,000 up for grabs.

The Clarity Smart Contract language is one of the core pieces of the Stacks 2.0 upgrade, so it will be exciting to see what you build. If you’re not too familiar with Clarity yet, check out this introductory post or jump into the docs. There are also a number of workshops and new resources created for the hackathon that should be helpful whether you enter or not.

Learn more about the hackathon
Register

Jump into the Discord channel (#hackathons) or reply to this email if you have any questions.

See you in there!

1 Like