Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Support 3rd party beneficiaries for token transferring functions #352

Open
loredanacirstea opened this issue Nov 15, 2018 · 2 comments
Open

Support 3rd party beneficiaries for token transferring functions #352

loredanacirstea opened this issue Nov 15, 2018 · 2 comments
Labels
backlog enhancement New feature or request Needs redeployment The issue/PR results in a breaking change in the precompiled data in `contracts.json` ->redeployment P3 keeping somebody waiting possibly

Comments

@loredanacirstea
Copy link
Contributor

loredanacirstea commented Nov 15, 2018 •
edited
Loading

We currently support:

  • deposits from 3rd parties on behalf of the participant

We should consider supporting:

  • withdrawals in a 3rd party account - we currently send the tokes to the msg.sender
  • settlement transfers in a 3rd party account (uncooperative, cooperative) - we currently send the funds to the channel participants.

Reasons:

  • IoT devices that run a Raiden node, but you want to have a separate account that controls the funds
  • multisig support
  • Raiden nodes that are hubs might want to batch deposit/withdraws transactions for saving gas costs if they need to rebalance their channels - this can be done with a hub smart contract that holds the tokens

Related spec issue: raiden-network/spec#24
@loredanacirstea loredanacirstea added this to the Ithaca milestone Nov 15, 2018
@loredanacirstea loredanacirstea removed this from the Ithaca milestone Jan 7, 2019
@loredanacirstea
Copy link
Contributor Author

Removed this from the Ithaca milestone because we are not optimizing for development adoption or external projects integration in this milestone.

@loredanacirstea loredanacirstea added the Needs redeployment The issue/PR results in a breaking change in the precompiled data in `contracts.json` ->redeployment label Jan 9, 2019
@pirapira pirapira added enhancement New feature or request P3 keeping somebody waiting possibly labels Feb 4, 2019
@pirapira
Copy link
Contributor

Make sure, even if the third party is an Ethereum contract that always fails, this does not block other parties from making some progress.

This was referenced Apr 6, 2020
Closed
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
backlog enhancement New feature or request Needs redeployment The issue/PR results in a breaking change in the precompiled data in `contracts.json` ->redeployment P3 keeping somebody waiting possibly
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@pirapira @loredanacirstea