Please note that we’ve modified the above plan since posting it on Friday in the following ways:
In regards to bullet point #2, all apps that have previously integrated Blockstack Connect will continue to work with the authenticator available at app.blockstack.org. However, we are not going to update the code hosted there with the new Stacks Wallet. Rather, we will commit only the minimum changes needed to that code for upgrading it to the Stacks 2.0 network with existing functionality, mainly in support of BNS.
This code freeze means that any developer who wants to take advantage of the new Stacks Wallet and its expanded functionality (namely, a complete wallet UI and robust transaction signing against the Stacks 2.0 Mainnet), will need to upgrade to the latest version of Stack.js connect (to be released later this week).
That version of Stacks.js connect will also not support hosted authentication for any users, even if they visit apps from browsers other than Chrome or Firefox with extension support. As such, upgrade to this latest version only if your app requires the new Stacks Wallet functionality and is suitable only for users with Chrome or Firefox on desktop devices.
If you don’t upgrade, your app will continue to operate as normal on Stacks 2.0 as it has on Stacks 1.0, apart from the temporary lack of new username registration support as already noted. We will restore username registration for both the new Stacks Wallet and the version frozen on app.blockstack.org once a subdomain registrar is available again.
Thanks for your understanding with these modifications, which were made with security in mind since it’s important that users transition to installed authenticators and wallets for Stacks 2.0 now that they’ll be handling STX within the context of apps.
On a related note, the Stacks documentation for building apps has recently been improved with new guides for authentication, transaction signing and data storage.
Check out the documentation for the updated guidance on integrating Stacks into apps.