Polkadot News

Motion 39 by Subscan for operating expenses has passed: https://polkadot.polkassembly.io/motion/39

Motion 41 to cancel an (ancient) erroneous proposal is being voted on: https://polkadot.polkassembly.io/motion/41

Dia is planning to begin its Polkadot integration: https://medium.com/dia-insights/hello-polkadot-dia-begins-cross-chain-integration-200a16b69a8c

Motion 40 (https://polkadot.polkassembly.io/motion/40) by Patract Labs for Redspot's v0.3 milestone, has passed.

Bruno Škvorc explains all the ways to get your Web3 project funded: https://www.crowdcast.io/e/web3funding

Referendum 12 (https://polkadot.polkassembly.io/referendum/12) to move a DOT claim to another Ethereum address still has no explanation and is thus unlikely to pass. At 0.17% turnout, it's sitting at 99.9% Nay votes.

There’s a handy list of teams building DeFi on Polkadot: https://www.reddit.com/r/dot/comments/jw1i83/defi_on_polkadot_a_list_of_teams/

An Unable To Reset Device error (https://github.com/polkadot-js/apps/issues/4049) has been plaguing Polkadot JS Apps users lately. This has been fixed in the most recent version of Apps, available at polkadot.js.org/apps now, and coming soon to dotapps.io.

Tips and Tricks

Remember that when nominating, you're not supposed to send money to the validator! Instead, look for nominate, deposit, or "select validator" options in your wallet of choice.

Developing a Substrate chain? There is now a runtime-migration label on Github that indicates when a pallet may have changed enough to warrant a migration, so you don't trap your chain by blindly upgrading runtimes: https://github.com/paritytech/substrate/labels/D1-runtime-migration

Keep up to date with the news on Polkadot with Twitter, Telegram or Element.