Its sad we never got answer on this question but 3rd(!) critical bug in XCM in ~ 6 months. XCM is in development from late 2020. I would say anything if these incidents happened in early days not now. Luckily this one was smallest and basically 0 threat to @hydration_net despite being exploited in the wild. We stopped upgrading on newer versions of P. SDK 1 and half year ago as we stopped accepting notorious senseless insane changes of code for higher chance of bugs which was just validated as good decision. Unfortunately. What we found that even merging flawed, newer version would not work for an attack. Btw these constant changes of code are not just petri dish for future exploits, but the main reason why whole ecosystem went bust under weight of extremely unnecessary never ending breaking changes instead of building actual products. And then to hear โwe are not impressed with products built here, we must build everything by ourselvesโ. LOL. It would be funny if its not sad.
Btw every dev from any cex, staking service or other 3rd party service integrating Polkadot hates it for exact same reason and they donโt wanna touch it ever again even if they are offered money. Can be even lot of money. Thats why native USDT & USDC are not more adopted, despite crazy efforts from Hydration & Velocity side. Real stories. We were saying you all this for years. Even if you listened for once and established LTS and versioning it got better just lil bit, but instead of weekly breaking changes there were massive ones in monthly intervals.
USDT wrapper which was in development for year didnโt survived w/o 1m+ loss less than a month in most basic xyk dex after meeting reality of your own code @paritytech . Before you will rambo style phase 2 of dotusd you should improve all things security related and communicate about it as transparently as possible instead of your renewed passion for opacity. Its very telling this was exploited instead of reported. But after treating white hats as trash (similar to everyone outside of your ivory tower) and offering them peanuts despite all your resources, you must invest more to get their attention again and prevent another disaster.
You canโt develop new internet and new money in the same way which cost you whole ecosystem, support of the world and reputation between builders, researchers, audithors, investors or just ordinary fans. There is and there was never industry wide conspiracy against Polkadot. Only your own words, actions, inactions and mistakes. Critical time to stop repeating them. I would not write this if you are not top source of stress for me this year while I am also trying to build products for the people.
In total, roughly 17.3M DOT are delegated to indiv/entities which stopped voting.
Only 5 delegates remain active in OpenGov:
- ChaosDAO
- Saxemberg
- Birdo
- ValidAndina
- Jimmy Tudeski
@Polkadot holders are ๐ด๐ค
DeGoogle but more important, ReDelegate.
@thewhiterabbitM No one there cares about the protocol and the ecosystem, you must understand that eventually. They only care about their pocket and milking the cow till itโs empty. Noone wants to build in the current ecosystem conditions. This eco is nothing more than smoke and mirrors
The funniest thing of the day in Polkadot:
* Community was against the referendum. (14M+ Nay)
* W3F/Parity, using its 120M+ stakes, voted Aye anyway.
* Didn't review the technical details at all. And now the execution failed.
If W3F/Parity vouches for their insiders like this without checking, are their other votes safe? Are they even going to find out if someone "trusted" sneaks in stuff?