🧑💻 Wishlist: Developers
Counterpart of https://github.com/paritytech/polkadot-sdk/issues/3901
Tracking issues for features that make the life of developers of polkadot-sdk easier.
Post your opinion by commenting “I wish for <issue-url>” (where “<issue-url>” can be in any repository, not just this) and upvote existing ones by putting a 👍 or 👎 on them.
⚠️ Warning: the string in your comment must match the following:
re.compile(r"I wish for:? (https://github\.com/([a-zA-Z0-9_.-]+)/([a-zA-Z0-9_.-]+)/issues/(\d+))")
A single comment can contain multiple wishes.
Ranking
| Feature Request | Summary | Votes | Status |
|---|---|---|---|
| https://github.com/paritytech/polkadot-sdk/issues/5 | Vision for cleaner substrate-node's developer-facing interface | 18 | ✅Closed |
| https://github.com/paritytech/polkadot-sdk/issues/802 | Add ARM binaries to releases | 14 | ✅Closed |
| https://github.com/paritytech/polkadot-sdk/issues/278 | Vision: Redesign Event system | 11 | 👾 Open |
| https://github.com/paritytech/polkadot-sdk/issues/4947 | Remove sequential increment requirements for Child Bounties | 10 | 👾 Open |
| https://github.com/paritytech/polkadot-sdk/issues/328 | Vision: Storage Deposits to be Ergonomic and Automatic | 8 | 👾 Open |
| https://github.com/argotorg/solidity/issues/909 | Enums with data / sum datatype / algebraic datatypes | 8 | 👾 Open |
| https://github.com/paritytech/polkadot-sdk/issues/3594 | Subscribe-able runtime apis | 7 | 👾 Open |
| https://github.com/paritytech/polkadot-sdk/issues/690 | Estimate Fees for XCM | 6 | ✅Closed |
| https://github.com/paritytech/polkadot-sdk/issues/4284 | XCM: Remove require_weight_at_most from Transact |
5 | ✅Closed |
| https://github.com/paritytech/polkadot-sdk/issues/299 | Ease implementation of mock for pallets. | 5 | ✅Closed |
| https://github.com/paritytech/polkadot-sdk/issues/133 | Vision: Repository reorganization | 3 | ✅Closed |
| https://github.com/paritytech/polkadot-sdk/issues/3434 | Better delivery fees: PayFees | 3 | ✅Closed |
| https://github.com/paritytech/polkadot-sdk/issues/644 | Improve XCM debuggability | 3 | ✅Closed |
| https://github.com/paritytech/polkadot-sdk/issues/3672 | A time based scheduler | 3 | 👾 Open |
| https://github.com/paritytech/polkadot-sdk/issues/486 | Runtime API to execute XCM | 3 | ✅Closed |
| https://github.com/paritytech/polkadot-sdk/pull/4079 | [FRAME] Storage derive macro #[frame_support::stored] |
3 | 👾 Open |
| https://github.com/paritytech/polkadot-sdk/issues/5298 | pallet-assets sufficient assets ED should provide same benefits as DOT ED |
3 | 👾 Open |
| https://github.com/paritytech/polkadot-sdk/issues/3581 | [FRAME] Warn when using default SubstrateWeights in production |
2 | 👾 Open |
| https://github.com/paritytech/polkadot-sdk/pull/1493 | Draft benchmark sanity weight test | 2 | ✅Closed |
| https://github.com/paritytech/polkadot-sdk/issues/698 | XCM weight meter | 2 | 👾 Open |
| https://github.com/paritytech/polkadot-sdk/issues/1138 | [FRAME] VersionedCall | 2 | 👾 Open |
| https://github.com/paritytech/polkadot-sdk/issues/349 | Encode required origin for extrinsics in metadata | 2 | 👾 Open |
| https://github.com/paseo-network/paseo-action-submission/issues/103 | Poor DevEx | 1 | ✅Closed |
| https://github.com/paritytech/polkadot-sdk/issues/738 | XCM executor should use transfer over withdraw/deposit | 1 | 👾 Open |
| https://github.com/paritytech/polkadot-sdk/issues/273 | Improved transaction payment pallet | 1 | ✅Closed |
Last updated: 2025-12-07
I wish for https://github.com/paritytech/polkadot-sdk/issues/5
I wish for https://github.com/paritytech/polkadot-sdk/issues/133
I wish for https://github.com/paritytech/polkadot-sdk/issues/328
I wish for https://github.com/paritytech/polkadot-sdk/issues/3581
I wish for https://github.com/paritytech/polkadot-sdk/issues/3594
I wish for https://github.com/paritytech/polkadot-sdk/pull/1493
It will be super useful to make sure parachains don't go to production with bad/dummy weights.
I wish for: https://github.com/paritytech/polkadot-sdk/issues/690
Cross-consensus XCM asset transfers are complicated with currently no way to know/estimate required fees along the path to the final destination.
I wish for: https://github.com/paritytech/polkadot-sdk/issues/3434
XCM delivery fees are currently "magically" subtracted from Origins account outside of XCM execution. The XCM program currently has no control over these transport fees. #3434 attempts to improve/fix that.
This issue has been mentioned on Polkadot Forum. There might be relevant details there:
https://forum.polkadot.network/t/polkadot-digest-4-apr-2024/7234/1
I wish for https://github.com/paseo-network/paseo-action-submission/issues/103
This issue has been mentioned on Polkadot Forum. There might be relevant details there:
https://forum.polkadot.network/t/polkadot-summit-24-boosting-the-developer-experience/7202/5
I wish for #644
I wish for #3672
I wish for #698
I wish for #486
I with for #230
I wish for #738
I wish for #1138
I wish for #273
I wish for #278
I wish for #349
I wish for https://github.com/paritytech/polkadot-sdk/issues/4284
I wish for #4947
I wish for https://github.com/paritytech/polkadot-sdk/pull/4079
I wish for: https://github.com/paritytech/polkadot-sdk/issues/802
I wish for https://github.com/paritytech/polkadot-sdk/issues/5298
I wish for https://github.com/paritytech/polkadot-sdk/issues/299
I wish for https://github.com/argotorg/solidity/issues/909
It would be super useful for interacting with the runtime (Implement scale in solidity) and for developing precompiles with better types.