-
Notifications
You must be signed in to change notification settings - Fork 169
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
Sending and Reiving Tokens #19
Comments
Nicola's problem:
Nicola's possible solution:
|
Not entirely, it is simply not defined right now, as we have not yet defined the permissions of the
Yes, but the system is pretty complicated, and looking at the docs quite easy to get wrong. That said they achieve this through specific methods that are called when transfering money that check if the contract has the correct permissions.
What kind of special? How would this get around the issue?
This would make me very sad, and not necessarily solve the issue as we would run into the 4th issue mentioned in the security considerations from ethereum, as far as I understand. |
Need to do some reading on how, polkadot and tezos do this. |
It would be helpful to have a few sample usecases of "send money to a function call on another actor". This in general isnt really that difficult, its going to be the same sort of logic that multisig wallet contracts in ethereum use to invoke other contracts. |
Sparked by a conversation with @nicola it becomes clear there are more considerations on how the token actor works and sending and receiving tokens should work.
Some notes from ethereum on this
The text was updated successfully, but these errors were encountered: