
November 19, 2020
Stacks 2.0 To Reach Code Completion by December 15th, January 14th Launch
Thanks to the hard work of engineers at PBC, the Stacks Foundation, and community contributors, the Stacks 2.0 blockchain is on target to reach code completion by December 15th. After discussing with exchanges, launch partners, and potential miners we can now set a launch date of January 14th. This date is the recommendation by PBC after consultation with other entities; miners will ultimately decide exactly when and how the launch happens. Stay tuned for other significant news in the coming weeks and thank you for your support!
Read the full update 
Register for launch events 
1 Million STX For Miners
More good news: To celebrate code completion and community momentum, the Stacks Foundation is putting up 1 million STX to be won in an upcoming mining challenge hosted by Daemon Technologies. The mining challenge will follow code completion on Dec 15th.
Independent miners will be the ones to launch the network, so this will be a great way for prospective miners to learn the final system before that and to celebrate their key role in enabling the user-owned internet on Bitcoin.
Register for the challenge 
7 Weeks Into Krypton
Hi Friends! Time for your weekly Stacks Snack. We’ve got a downpour of updates this week as we come off of a sensational Docs Week that exceeded all of our expectations! A big thank you goes out to every community member that helped tidy up the documentation, and made it even easier for newcomers to learn the tech and build on Stacks 2.0. We’re also starting to see some pull requests trickle in configuring the launch of mainnet!
Don’t forget there’s still time to get involved in the HackDeFi hackathon, and the deadline has even been extended to December 4th to give you time to finish up those rockstar DeFi projects.
For a more detailed overview of recent developments, check out the technical updates on Github from the past week:
stacks-blockchain
Version: v23.0.0.11-krypton
- Some minor event dispatcher updates. → Github
- Added event_index for ordering events (the dispatch matrix scrambles the event order).
- Add locked_address field to stx_lock_event.
- These will ultimately allow the Explorer & Wallet to show more stacking info.
- Fixed issues (with miners reusing microblock public key hashes) by mixing the burn block height into the microblock private key rotation. → Github
- This had been troublesome when upgrading the stacks-node software without a chain reset (so your node would have to catch up from other nodes on the network).
- Added burn_block_height field to /new_burn_block event-dispatcher endpoint. → Github
- [Stacks v1 → v2 Upgrade] Export names, namespaces, subdomains and zonefiles. → Github
- Implemented Stacking Operations via Bitcoin transaction. → Github
- This PR introduces two new Bitcoin ops: PreStackStx and StackStx.
- More details in forum post. → Forum
- This PR adds an integer binary logarithm function (log2 n) to Clarity. It also updates the costs boot contract to use said function. → Github
- Clarity defined Cost Functions. → Github
- New boot contract containing cost functions for every native Clarity function.
- Refactored CostTracker to include compute_cost function, which can compute costs via supplied clarity contracts.
- Refactored LimitedCostTracker impl to keep track of a mapping relating cost function names to a QualifiedId, and a cache of cost contracts.
- Replace runtime_cost! macro with runtime_cost function which uses updated CostTracker.
- Git clone efficiency in readme. → Github
- Reduces disk usage and network download time by around 80%.
stacks-blockchain-api
Version: v0.31.3
- The Stacks Blockchain API was extended to fully support Coinbase’s Rosetta Standard. → Blog Post
- This pull request adds a docker file to meet Rosetta’s requirements. It includes instructions on how to run rosetta-cli against it to test the implementation. → Github
- Three Rosetta fixes: API_TAG in stx-rosetta, contract function args, and fees calculation. → Github
- v2/info documentation maintenance and adding descriptions for the fields. → Github
- Stacking lock event processing. → Github
- Expose STX lock up events
- Fixes long standing out-of-order event index bug.
- Upgrade to es2020 from es2019, and nodejs v14 (LTS) from v13. Full native bigint support!
- Fixed bug with rosetta endpoints not being included in openapi definition.
- Stub response for the /new_burn_block event. Allows the sidecar to run with latest core-node. → Github
- There is also a PR in flight that uses this to expose some really useful information. → Github
- Updated the Miner STX reward event handling to fix an issue where the balance reported by the API did not match the balance reported by miner/follower. → Github
- The client lib generation process was outputting tens of thousands of lines, making Github actions almost impossible to read and debug. Output has been drastically reduced. → Github
- Contract names were previously required to be at least 5 chars long. This is not the case with the pox contract, and perhaps no longer the case at all in core. Either way, the restriction was unnecessary and lifted. → Github
- Transaction broadcasting fixes. → Github
- Use a Blob for posting transactions instead of string.
- Use a string as result type for posting transactions instead of void.
docs
- This PR updates next.js to version 10, and removes our cool but ultimately flawed deploy script. This means we will now only rely on the vercel plugin until we can perhaps sort out the issues of deploying forked PRs. → Github
- The stacks burn height has been added to the Stacking guide. → Github
- Big naming update for Stacks rebrand. → Github
- Fixed broken Clarity language reference redirection links in 3 pages. → Github
- Added a helpful “Technical Specs” page to the docs with useful info like coinbase reward schedule, stacking details, and more. → Github
- Added instructions for running the testnet node (Both follower and miner node) on Windows from the binary available. → Github
- Mining Guide has been updated. → Github
- Added a guide for dealing with Clarity values in JS. → Github