Good evening everyone 👋

This week saw the number of hosts connected to v2 grow by a third, and it doesn’t show any sign of slowing down. To everyone who has recently joined the community and has onboarded nodes, we say welcome! And to those of you who have been with us a while and have migrated over from v1, we say thank you.

If you haven’t yet claimed your network contributor badge, please let a member of the core team know. And for those who are just joining us, if you operate one or more nodes you are eligible for a special @Network Contributor role in the community. Those of you who contribute to the open source projects will receive the @Code Contributor role.

What do these roles get me you ask? Kudos in the community. And in time, who knows… perhaps it will unlock additional rewards or recognition too.

This week we opened a new marketing channel in Discord where we saw some great suggestions from the community. We are continuously working on improving and refining the marketing strategy for Edge and want to gather as much input and support as possible to really push Edge forward. So if you’ve got any ideas or feedback, pop over to 📈│marketing and let us know.

This week we saw a number of updates. Index saw a number of releases from v1.15.1 up to v1.15.4, introducing the ability to resolve stakes by their hash (in addition to their IDs) including historical hashes, essential to the earnings process where stakes can change over time. These updates also included adding more information to the output of the stakes as well as the wallet balances endpoint (more on that next week!).

Explorer v1.12.3 was deployed to mainnet today fixing an issue with pending transactions not refreshing once confirmed. You should now be able to watch pending transactions as they are confirmed, which is nice. We’ve also added more information to the Wallets page so now you can see the total number of transactions, stakes, and the total amount staked, along with the balance.

Wallet also saw a couple of updates, with v1.12.5 fixing a UX issue with wallet creation, splitting private keys over two lines. This evening v1.13.0 was deployed, introducing the ability to create, unlock, and release stakes from the comfort of your own browser:

Stargate v2.3.1-133 was deployed to mainnet, along with Gateway v2.2.0-79. These two updates include a number of features, from certificate management and service integration support through to protocol improvements. In addition to optimizing some latency issues, periodic checks were also introduced to ensure devices whose stakes become invalidated are removed from the network.