-
Notifications
You must be signed in to change notification settings - Fork 754
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Vision: Delegate Fees and Deposits to Another User #304
Labels
D2-substantial
Can be fixed by an experienced coder with a working knowledge of the codebase.
I5-enhancement
An additional feature request.
T1-FRAME
This PR/Issue is related to core FRAME, the framework.
Comments
kianenigma
changed the title
Delegate Fees and Deposits to Another User
Vision: Delegate Fees and Deposits to Another User
Mar 10, 2023
the-right-joyce
added
I5-enhancement
An additional feature request.
T1-FRAME
This PR/Issue is related to core FRAME, the framework.
D2-substantial
Can be fixed by an experienced coder with a working knowledge of the codebase.
and removed
J0-enhancement
labels
Aug 25, 2023
helin6
pushed a commit
to boolnetwork/polkadot-sdk
that referenced
this issue
Feb 5, 2024
…ch#304) * Sha3 and ECDSA precompiles * Tests for sha3fips * Updates to spec and adds tests * Spacing and formatting * Fmt * Comment out test * Updates * Updates * Update ECRecoverTests.sol * Remove merge conflict * Remove unnecessary yarn file * Uncomment tests * Fix tests * Reset simple-specs.json change * Remove unused frontier-spec.json file Co-authored-by: Wei Tang <accounts@that.world> Co-authored-by: Wei Tang <wei@that.world>
github-merge-queue bot
pushed a commit
that referenced
this issue
Dec 12, 2024
## [0.8.4] - 2024-12-12 This release aims to make the MDNS component more robust by fixing a bug that caused the MDNS service to fail to register opened substreams. Additionally, the release includes several improvements to the `identify` protocol, replacing `FuturesUnordered` with `FuturesStream` for better performance. ### Fixed - mdns/fix: Failed to register opened substream ([#301](paritytech/litep2p#301)) ### Changed - identify: Replace FuturesUnordered with FuturesStream ([#302](paritytech/litep2p#302)) - chore: Update hickory-resolver to version 0.24.2 ([#304](paritytech/litep2p#304)) - ci: Ensure cargo-machete is working with rust version from CI ([#303](paritytech/litep2p#303)) cc @paritytech/networking --------- Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io>
lexnv
added a commit
that referenced
this issue
Dec 12, 2024
## [0.8.4] - 2024-12-12 This release aims to make the MDNS component more robust by fixing a bug that caused the MDNS service to fail to register opened substreams. Additionally, the release includes several improvements to the `identify` protocol, replacing `FuturesUnordered` with `FuturesStream` for better performance. ### Fixed - mdns/fix: Failed to register opened substream ([#301](paritytech/litep2p#301)) ### Changed - identify: Replace FuturesUnordered with FuturesStream ([#302](paritytech/litep2p#302)) - chore: Update hickory-resolver to version 0.24.2 ([#304](paritytech/litep2p#304)) - ci: Ensure cargo-machete is working with rust version from CI ([#303](paritytech/litep2p#303)) cc @paritytech/networking --------- Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io>
dudo50
pushed a commit
to paraspell-research/polkadot-sdk
that referenced
this issue
Jan 4, 2025
## [0.8.4] - 2024-12-12 This release aims to make the MDNS component more robust by fixing a bug that caused the MDNS service to fail to register opened substreams. Additionally, the release includes several improvements to the `identify` protocol, replacing `FuturesUnordered` with `FuturesStream` for better performance. ### Fixed - mdns/fix: Failed to register opened substream ([paritytech#301](paritytech/litep2p#301)) ### Changed - identify: Replace FuturesUnordered with FuturesStream ([paritytech#302](paritytech/litep2p#302)) - chore: Update hickory-resolver to version 0.24.2 ([paritytech#304](paritytech/litep2p#304)) - ci: Ensure cargo-machete is working with rust version from CI ([paritytech#303](paritytech/litep2p#303)) cc @paritytech/networking --------- Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
D2-substantial
Can be fixed by an experienced coder with a working knowledge of the codebase.
I5-enhancement
An additional feature request.
T1-FRAME
This PR/Issue is related to core FRAME, the framework.
Not sure if the title here is the best, but the general idea is that we should figure out a way to support delegating certain fees to different user accounts.
Specifically, when I am initiating a multisig or proxy transaction, sometimes I will need to fund that account in order to make it usable. For example, any transaction that would take a deposit from the calling account requires me to put some funds into the proxy account in order for that call to succeed.
In reality, what I would prefer is to actually just spend funds out of the original dispatcher, and have the proxy simply be a variant of the identity.
This may require a pretty significant overhaul of some of our pallets and storage in terms of tracking the source of deposits to be a different account than the one that started the call. Or by creating some abstraction where any funds of the calling user seem to exist in the proxy accounts and so forth.
In the short term, an idea might be
proxy_with_funding
andmultisig_with_funding
where a user can initiate a call with some funding, the call would first transfer any funds, then execute the operation, and at the end, transfer any funds back.The text was updated successfully, but these errors were encountered: