According to Subscan, there has been 129 successful create_pure call on Polkadot Relay Chain and 89 on Kusama Relay Chain
I think it is also worth noting that over 50% of the top 20 accounts on both polkadot and kusama are likely pure proxy accounts. I say “likely” because there is no easy ways to check whether these accounts are really pure proxy, so I just assumed all accounts that have 0 extrinsics activity but some proxy activity are pure proxy accounts, which is in line with @tbaut 's estimation.
I’m Archana, a Polkadot Blockchain Academy Singapore graduate.
I set my on-chain identity in May 2024 before PBA and submitted my judgment request to Registar 2. However, after 3 months, I’m still waiting for a judgment, and my DOT is reserved with no progress. I’ve attempted to cancel my judgment request and clear my identity multiple times, but I keep encountering a system.CallFiltered error.
Could this issue be related to the migration of identities? Are the identity pallet calls currently frozen?
I would appreciate any assistance or insights regarding this matter.
Identity is being migrated from relay chain to system parachain(People chain) so its not possible to setIdentity and that’s why you are getting the error. Check here for more details People Chain Migration and Release
Also Joe has added the details if you scroll up to the beginning.
Hi! Yeah, it’s currently an issue for us at Polkadot Hungary Team. We created our “keyless” flexible multisig, which connected with an Any Proxy to our basic multisig on Polkadot Relay. The Pure Proxy doesn’t have the on-chain ID. We would like to set up now. But unfortunately we can not set because we can’t submit extrinsics as there is no establish proxy connection between our basic multisig and the pure proxy multisig on the People Chain, only on the Relay Chain. How can we fix this?
A solution would be to create an on-chain ID to our basic multisig and give a sub-identity to our Pure Proxy flexible multisig. Can you recommend other solutions?
Thanks in advance for the reply! (BTW the People Chain is cool, we like it! )
I already had an on-chain identity on Polkadot Relay Chain and had it configured in Polkassembly.
But now on People Chain that is live my account balance has 0.3973 DOT, where 0.2018 DOT is reserved, and I think that some of it was airdropped.
But although it says my account is verified at User Profile | Polkassembly, it won’t let me post in some Polkassembly referenda such as JAM0 Event @ Devcon 7 - November 11-16, 2024 | Polkassembly because it displays “Comments have been disabled for non verified users.” and requires me to set an on-chain identity again and says I have “Insufficient available balance”.
Unfortunately I think it’s a Polkassembly issue.
Even after increasing my balance on People Chain it still doesn’t recognise my identity to allow me to post on that referendum. I tried using the latest version of Brave and Chrome, both had the same issue.
I’ve updated the Polkassembly issue that I raised here with the latest issues I encountered https://polkassembly.featureos.app/p/unable-to-recognise-my-polkadot-on-chain-identity
This limitation is a problem for the system that will use this pallet. I understand that we can put a hash to verify those, but that’s not how people are using it or any of the current identity frontends.
People use the field as plain hex encoded strings, and if we expect that information to be public and without the need to fetch from a centralized system the real information, I believe the two fields should have their type changed to Bytes instead of Data.Raw