Transferability and Redenomination Public Notice

2020-08-18 in  Polkadot, Redenomination
Avatar by Polkadot
Image

Token transferability was enabled, exactly at block number 1,205,128 on August 18th at 16:39 UTC. This will not change the denomination of DOT (old) which still represents 10**12 Planck.

The redenomination will occur approximately 3 days later, at around 16:40 UTC on the 21st August,  exactly at block number 1,248,328 where each New DOT will represent 10**10 Planck, 100 times less of an amount.

Do not be fooled by suspiciously low DOT prices. Though most exchanges will represent DOT accurately, there is a chance that some unscrupulous exchanges may choose to enact the redenomination prior to the date agreed by the Polkadot community, and thus report the apparent price at approximately 100 times lower than the actual market price.

We believe such action is irresponsible, possibly constituting fraud through deceptive advertising and certainly puts Polkadot stakeholders at risk. As a responsible member of the Polkadot ecosystem, Web3 Foundation will make such a proposition as unattractive as possible, however, since Polkadot is now decentralized and permissionless, and since this change is a purely off-chain "visual" alteration, we can do little against a determined and centralized off-chain service abusing the trust of their users. As always, we urge the Polkadot community to be careful, vigilant, and communicative.


See the Polkadot blog post for more information.‬

arrow_upward
Related articles
Polkadot
Writing History: The First Teams Submit Their Proposal to the Polkadot Treasury

To make sure the teams building on Polkadot have all the support they need, it is paramount that they understand the funding alternatives available. One good funding option is the Polkadot Treasury, which is already supporting a wide range of projects....

Kusama
Swisscom Blockchain to develop Kubernetes Operator for Kusama and Polkadot

Swisscom Blockchain AG has received a Wave 5 grant from Web3 Foundation to develop a Kubernetes Operator for sentry nodes and validators for both Kusama and Polkadot....

Kusama
GRANDPA Equivocation and sysinfo Process Collection Results In Slashing on Kusama Network: a Post-Mortem.

Multiple bugs in code resulted in nodes dropping out from Kusama network and losing the database that stores which blocks they validated. Consequently, the same nodes double-signed those blocks on restart. The slashes caused by this issue have been reverted via Kusama Council motions....

Subscribe to the newsletter to hear about updates and events.
mail_outline
* To see how we use your information, please see our privacy policy.