You can use this transaction blueprint to teleport WND from Westend Asset Hub to Westend Asset Hub Next. Steps Use the link above to acquire the transaction data, it should be 0x1f0904010100311104000101006c9e3102dd2c24274667d416e07570ebce6f20ab80ee3fc9917bf4a7568b8fd20404010000070010a5d4e80000000000. Change the Receiver address to your hex public key. You can use Subscan to convert an SS58 to hex. The prefilled address 0x6c9.. is mine :) Change the amount; the prefilled amount is 1 WND (1e12). Send the transaction. Check your account balance on Westend Asset Hub Next :tada: Screenshot 2025-03-07 at 12.42.28

TLDR: A historic bug caused the Total Issuance tracking to deviate from the actual Issuance. I propose a whitelisted call to re-align them. The underlying issue has already been resolved. There was an issue discovered on Kusama that the sum of all accounts' balances does not match the Total Issuance stored in pallet-balances. This is a serious issue, since third parties rely on its accuracy for tracking the total amount of existing tokens. The underlying problem was fixed by #1222 and #3707. The TI has not drifted further, but the same problem is present on Polkadot. The Difference First, it is necessary to measure the exact drift between the expected and the actual Total Issuance. This can be done by querying a node at a fixed block height. Two things have to be queried: all account entries and the TI variable from the balances pallet.Conveniently, this script does both. The exact numbers were determined by running these commands against a Kusama archive RPC: python3 check-ti-complete.py --url <RPC> block --trace 24407008 python3 check-ti-complete.py --url <RPC> block --trace 23780225

Tutorial on how to remove a current Head Ambassador. They need to appear in this list for it to work. Note that they can immediately re-apply after being removed. 1. Prepare the Preimage on the Collectives Chain Go to PolkadotJS and decode this extrinsic. Click on Submission to modify the parameters: Screenshot 2024-06-11 at 10.17.50 Replace the addess who with the HA that you want to remove. Copy the encoded call data (not the hash!) Screenshot 2024-07-16 at 20.06.02 This will look different for everyone.

These are the steps necessary to start a referendum to be included into the intitial seeding list of the Ambassador Program as Head Ambassador. 1. Prepare the Preimage on the Collectives Chain Go to PolkadotJS and decode this extrinsic. Click on Submission to modify the parameters: Screenshot 2024-06-11 at 10.17.50 Replace the addess in both fields with your address. Copy the encoded call data (not the hash!) Screenshot 2024-06-11 at 10.18.45 This will look different for everyone.

This document proposes to the Polkadot tokenholders the inception of a new System Collective: The Polkadot Tooling Collective (PoToC). After a formation period to establish members and display effectiveness, the collective will request funds from the main treasury to support a salary structure and sub-treasury. These ideas are laid out in the Phases section. Context The Polkadot Core Fellowship is currently the only System Collective for developers. This makes it the go-to spot for new developers who want to join Polkadot - regardless of the field in which they want to work. The scope of the Core Fellowship is rather narrow, focusing primarily on implementations of the Polkadot Host and runtime code. But many developers are working on tools related to making Polkadot successful, both the maintenance and development of the core protocol and the libraries and abstractions for dApp developers. These developers often find that their contributions are not recognized within the mandate of the Core Fellowship. But the system can host many collectives. The Core Fellowship should be just one of many Collectives that serve Polkadot in different ways. Each has its own set of members, scope, and expertise levels.

where money The following must be fulfilled in order to reap payout for a salary cycle. If one step fails, it could be that you already did it. Just try the next one: At least Rank I You imported yourself into the Fellowship (FellowshipCore.import). You inducted yourself into the Salary Pallet (FellowshipSalary.induct) You need to wait until the next registration starts if you just inducted yourself (15-30 days) before proceeding: