Members of the Fellowship Collective involved in projects flagged by the OG tracker should provide a proper explanation, return the funds to the Treasury, or face expulsion.
Back to General Admin
Timed Out
#52 Make chaos | for testing some abnormal situation of Gov V2
Description
AI Summary
Votes Bubble
Timeline
Evaluation
On Chain Info
Stats
Happy New Years, all Dotsama community members!
After a holiday we've seen a lot of community discussion and voting, I'm sorry for not clarifying in time and causing confusion! At the same time, we are very grateful to every community member for actively voting and expressing opinions . We are so lucky to develop in such an active, friendly and responsible ecosystem!
The submission of this proposal is because Subscan is developing Gov V2 related functions. We found that there are some abnormal situations that are not described in detail in the document, and there is not enough on-chain data - we desperately need a "REAL" test environment. Based on Kusama is an Expect Chaos network, we made a bold attempt. We have already realized that this is not a responsible behavior, however, based on the existing process , it may not be an accident in the future that the community have to vote for proposals that lacks value - this proposal has not added the decision deposit - just my personal opinion, welcome to discuss :)
At present, the explorer functions related to Gov V2 have basically been developed, we will complete the test ASAP and cancel this proposal (this is also a part of the test). Related functions will be officially released next week, welcome to experience, give feedback and discuss with us!
BTW, as many friends have noticed, the type of this proposal is identity.addRegistrar. It’s no coincidence and it’s already on our to-do list for 2023, perhaps that’s why it popped into my head first when I submitting the proposal and choosing the origin. Subscan hope to provide the community with a more convenient, cheaper, and more decentralized identity service. Currently, the relevant plan is being revised and will be officially announced in due course!
Cheers for Chaos!
Best wishes,
Yakio｜Subscan
Show More
Please Log In to comment
Users are saying...
Based on all comments and repliesOverall 100 % of users are feeling neutral. A community member is voting 'aye' on Subscan becoming a registrar, despite lacking information about the referenda and anticipating it might be cancelled. Another user expresses curiosity over whether the proposal will execute successfully and suggests that more background information may influence their vote. They also request additional details from Subscan regarding identity fields support and fees.
AI-generated from comments
7Comments
DFuQ...v46E
Hello there!..
Is there any description / explanation available for this referenda?
Please kindly advise!
Thanks!..
Milos
GP7L...po99
I vote nay until a description is available. Concerning that so many have voted aye when no description is available. What am I missing here?
DFuQ...v46E
HqRc...fVZn
Topic aside, I'm not sure if this is the right track for this. It might require root.
GP7L...po99
If you look at Polkadot.js under Governance/Rerenda it is currently labelled:
14/general admin-origin for managing the registrar
Therefore, this is probably the correct track. I still need more background before I can change my vote to aye.
HqRc...fVZn
I think a code review might be better than just reviewing this by label.
HERT...afdU
Voting Nay for now until details are posted.
HqRc...fVZn
I am voting Aye appreciating that this request was issued by Subscan (a known player in the ecosystem) and with anticipation that they'll add context soon.
My curiosity as-to whether this will execute still exists.
FLKB...svZR
I asked them for details as I know a person close to the team. Let's see what they tell us.
GqC3...m8Jj
@paradox was wondering if this would execute successfully. While I don't understand the full context of the code, it appears this line of code ensures that the RegistrarOrigin is either Root or GeneralAdmin. I believe it will execute successfully, though I might be missing something that indicates that it wouldn't work.
As for the proposal, I'm all for adding another reputable registrar. I believe Subscan is more than capable of maintaining a good registrar for Kusama, though I would like to know what identity fields they indent to support and what their fee will be.
HqRc...fVZn
Thanks Adam, I was looking at this line . I didn't notice the line you pointed out and now that I've seen it I believe that it would execute successfully.
DFuQ...v46E
Hello Yakio,
Many thanks for your description,
The community will definitively benefit from Subscan as a registrar, so voting Aye on this, even if it's just for test and it is ultimately cancelled.
All the best
Miloš
Discover similar proposals
#509
E5qF...tqrg
Deciding
KSM RFP #1 - Shielded Kusama Hub Transfers - $50k Total Prize!
See More
Treasurer
Treasurer
#509 KSM RFP #1 - Shielded Kusama Hub Transfers - $50k Total Prize!
E5qF...tqrg
This RFP was adapted over several weeks on AAG to turn a treasury proposal in discussion to an RFP with refined scope and oversight.
To apply for the prize pls fill out this form.
Prize Pool: $43,000
Finder’s Fee: $2,000 **
Supervisors: $5,000
Supervisors (Bounty Curators)
- Flipchan
- Byte (Erin)
- James Slusser
Excess or unused funds will be returned to the treasury by Bounty Curators.
Timeline
Monday, March 17 - AAG Discussion & this forum post! ✅
Monday, March 24 - Single-ref Bounty + Curators ✅
4 Weeks after Bounty Funding - Submission Deadline Thursday
July 31 - Project Completion (Pending Kusama Hub Launch)
Project Scope
Smart Contract Development
- A Solidity-based smart contract deployed on Kusama Hub
- ZK enabled for private deposits & withdrawals
- Compatibility with all Kusama Hub assets
User Interface
- Browser-based, mobile-ready UI hosted on IPFS
- Support for: Deposits, Withdrawals, Transfers, XCM Transfers
- Compatible with popular ecosystem wallets (Nova Wallet, Talisman, Subwallet)
Anti-correlation Attack Mitigations:
- Fixed deposit amounts (e.g. 1, 10, 100, 1000 units)
- Batch payouts for withdrawals to multiple users
Interoperability - Ability to receive assets via XCM from any Kusama-connected parachain and transfer them to Kusama Hub for use in shielded pool.
Open-Source Delivery
- All code (smart contracts and UI) published under the MIT license
- Publicly accessible repositories Project updates shared transparently via Polkassembly, Subsquare, or Polkadot Forum from Team with Milestone deliveries
- Developer & User documentation
Milestones
Milestone 1, Initial Pools & Basic UI:
$16,200 USD
1 month
- Tests - Smart contract test
- Smart contract - ZK shielded smart contract with KSM and multi asset support on Westend or Paseo
- Basic UI - A basic UI for interacting with the smart contract
Milestone 2, UI + XCM:
$9,900
1 month
- Tests - tests for all features
- User interface design - UI design
- XCM transfers - XCM transfer assets in UI
- Fixed amount transfer only - Allow fixed amount transfers in the UI
Milestone 3, Mainnet Deployment:
$16,900
1 - 1.5 months
- Contract Migration to Kusama Assethub - Migrate contract from Testnet to Kusama Hub
- Public documentation - Documentation for using Kusama shield and developer integration documentation
- Test - tests for contract
- V1 UI - User tested & something we can be proud of
** re: Finder’s Fee: this payment is set aside to incentivize a broad search for the right implementor. Finder’s Fees are paid out at time of team engagement. Teams that submit themselves can collect their own Finder’s Fee at completion of project.
See More
Deciding
