View All Whitelisted CallerinWhitelisted Caller
Executed
Set Snowbridge-wrapped USDC & USDT as sufficient assets, set their ED to $0.01, and set their metadata on Asset Hub
2 months ago
This is a redo of proposal 1510. There was an oversight on my side on the call. It was using a double wrapped DispatchWhitelistedCallWithPreImage
call and that was wrong. The outer call was whitelisted by the fellowship, but not the inner call. Thus, the execution on chain failed.
This proposal is exactly the same as the old one, but without the "double wrap".
Comments (2)
Proposal Passed
3
of 3Summary
0%
Aye
0%
Nay
Aye (82)0.0 DOT
Support0.0 DOT
Nay (10)0.0 DOT
Voting Data
Approval%
Support%
Threshold0.00%
Threshold0.00%
Many thanks for your proposal, bkchr!
We have carefully reviewed your application and are pleased to share our assessment below, prepared using our standardized evaluation methodology.
Summary of our analysis
■ Impact on the Ecosystem
The proposal enhances Polkadot’s interoperability and user accessibility by enabling Snowbridge-wrapped USDC and USDT as sufficient assets, aligning with strategic goals of cross-chain functionality and adoption. However, it offers limited contributions to long-term security, scalability, or decentralization and does not address specific vulnerabilities or bottlenecks. It delivers broad value to end users, parachains, and developers, fostering ecosystem growth.
■ Governance Compatibility
The proposal is well-suited to the WhitelistedCaller origin, as it involves a technical asset configuration requiring root privileges, adhering to Polkadot’s governance framework. Precedents of similar referenda confirm the correct use of this governance path. The process is used meaningfully, leveraging the origin’s efficiency without bypassing or burdening established procedures.
■ Cost-Benefit Ratio
The risks of spam accounts and stablecoin centralization are proportionate to benefits like increased user adoption and Ethereum interoperability. The minimal technical effort and absence of long-term obligations are justified by significant impacts on accessibility and network activity. The chosen approach appears resource-efficient, with no documented alternatives offering similar effectiveness.
■ Transparency and Traceability
The proposal clearly outlines the systemic changes and goals, with comprehensive technical details enabling validation. However, it lacks explicit success metrics for broader impacts, limiting long-term evaluation. Decision-making and the governance process are transparently documented, though Fellowship review details are not fully public.
■ Record and Credibility
Bkchr, a Rank 6 Polkadot Technical Fellowship member and Parity Technologies developer, has a strong history of successful contributions, including runtime fixes and pallet additions. Their expertise and organizational support ensure capability to implement this technical change effectively.
Conclusion
🔹🔷🔹 vonFlandern 🔹🔷🔹 has therefore voted with: ** AYE **
Our methodology aims to analyze and evaluate OpenGov proposals objectively, effectively, and transparently, establishing clear decision-making foundations for our votes while making our process visible to the community.
For a deeper dive into our evaluation, please see the detailed report here.
Ty