• Actionable: Thom Ivy has pointed out that as a community we need to figure out the answers to our security policy, please give your feedback and ideas. You can do so in the discord / telegram builders chat or better yet on github.

Create SECURITY.md by thomivy · Pull Request #6 · edgeware-network/edgeware-node

We need to figure out the answers to our security policy as a community.

GitHubedgeware-network

High Priority

• Actionable: Councilmember Remz has shared their work reviewing the Wako release after continued work by Drew and Raymond.  They document several of their findings on Github, but they involve repairing unintended changes to network parameters. When this upgrade is ready and deployed successfully, EDG will have a stable EVM platform. Developers and validators are requested to review these changes, provide their thoughts on parameters and fixes, and otherwise test and run this node release and report bugs to the Github repo. Additionally, you can participate at the Builders channel in Discord at edgeware.chat

+ Reverted the bonding duration to 2 weeks (was changed to 24 weeks)

+ Reverted slash duration to 1 week (was changed to 6 weeks) 

+ Changed the vote locking period back to 1 week. This one was changed from 1 week to 1 day on last upgrade, as an unwanted result of changing the voting enactment time. The change is probably uncontroversial (the parameters now just don't make sense), but would need to be mentioned when deploying launching the upgrade for good order.

+ Reverted GAS_PER_SECOND to 8_000_000, which was the previous value intended for mainnet instead of 40_000_000. The EVM is untested in production and there isn't much value in deploying with a massive gas capacity before getting any usage. We can scale this number up as we get more confident over time. 

+ Removed the dumplicate definition of EthApi.There were two identical enum definitions in different files, with one mapping all elements to the other on funcction call to avoid type mismatch. Why it was done that way is a mystery, but functionalities shouldn't be affected by the change. It needs to be tested for good order."

Status updates

• Cohort Session 2: We're looking for ambitious learners that would like to grow with Edgeware, and become a core part of our community. The Edgeware cohort program is a new program that will educate individuals on the structure and operations of Edgeware, Substrate, and blockchain technology, and provide the skills necessary to contribute to the evolution of Edgeware's ecosystem. The first cohort session will be limited to 10 spots. There are still a few spots left no to late to join. Next one is December 1st, 11:00 AM EST in the Voice-Builders voice channel on the Edgeware discord.
• You can listen to the first cohort session here!
• Bi-weekly Builder's Call + Community Hackday: December 7th, 2:00 PM EST in the Voice-Builders voice channel on the Edgeware discord. Every other Tuesday at 2p EST. Bring questions, projects to show off, and ideas!
• You can listen to the recording of the last builders call on November 23rd here!
• During the Sub0 conference, the Edgeware agency took notes! You can check them out here. You can read through and get the main points and the slides of each presentation. It is not fully completed we will add to it over time as we finish watching the intermediate and advanced presentations.

Ecosystem Headlines

Substrate

• A new series: Rust techniques every substrate developer should understand part 1 - Macros. This article goes over what you need to know about using Rust macros in your substrate code.

"This is the first part of a series where I take a deep dive into some rust techniques that you’ll need to understand in order to write a more elegant and hassle-free substrate code."

• Next Substrate Seminar Dec 14th.

"Shelven, the Lead Researcher of Phala Network, will demonstrate how to to build a BTC price oracle with a Telegram bot in 50 lines of code in Phala's native Fat Contract (confidential ink! smart contract). In this workshop, you will learn how to leverage Fat Contract’s unique features like asynchronous HTTP request and computation-intensive tasks in ink! language."

Core Stack

• A bug with off chain workers where their http agent couldn’t parse http2 returns is now fixed.
• Every single Substrate pallet has been migrated to the newer `!pallet` macros from the “old” approach of writing pallets. A monumental achievement!
• Substrate’s JSON RPC server will now fall back to a random port if the default fails.
• Users have been complaining that the AllowDeath flag on crowdloan contributions is unexpected and has been eating dust out of accounts when users do not contribute the full amount into the crowdloan. This PR changes the AllowDeath flag on contribute to KeepAlive, which forces the user to keep the existential deposit of funds in their account after the crowdloan contribution. As an alternative option, users can now also call contribute_all, which automatically calculates the full balance available to transfer from the user, and contributes that to the crowdloan while allowing death of the account.
• It looks like Parity will be taking over and leading the development of the sub-bounties extension for the Bounty pallet.
• Substrate nodes would store private keys in the somewhat insecure 644 mode on the filesystem they run on. This has now been fixed to be mod 600 (read/write owner only).

Tools

• Polkadot JS API 6.8.1 is out with some low-priority performance fixes and other minor updates.
• Polkadot JS API 6+ will soon have improved type generation, so that the promise of auto-built types from Substrate nodes can finally become a reality.
• Substrate API Sidecar 11.3.0 is out with low upgrade priority, minor bug fixes.