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

Opcode: STREAMDELETE #138

Open
PaulRBerg opened this issue May 17, 2024 · 0 comments
Open

Opcode: STREAMDELETE #138

PaulRBerg opened this issue May 17, 2024 · 0 comments
Labels
effort: epic Multi-stage task that may require multiple PRs. priority: 1 This is important. It should be dealt with shortly. type: feature New feature or request. work: complex Probe-sense-respond. The relationship between cause and effect can only be perceived in retrospect.

Comments

@PaulRBerg
Copy link
Member

PaulRBerg commented May 17, 2024 •
edited
Loading

Spec

Deletes the stream with the sender msg.sender and the recipient recipient for token with ID token_id.

Input

  • recipient of type `Address
  • token_id of type U256

Output

None.

Receipt

  • New receipt of type StreamDelete
  • Data
    • The new balance of the sender as a U256
    • The new balance of the recipient as a U256

Errors

  • The sender must be solvent by the time the tx is processed.
  • A stream must exist between the sender and the recipient for the provided token ID.

Notes

  • Can be executed either by an EOA via one of the new transaction types or by a contract
  • I went with STREAMDELETE instead of DELETESTREAM so that all streaming-related opcodes can be grouped together
  • The spec assumes that there can be only one stream between users

Tasks

Discussions
@PaulRBerg PaulRBerg added effort: epic Multi-stage task that may require multiple PRs. priority: 1 This is important. It should be dealt with shortly. work: complex Probe-sense-respond. The relationship between cause and effect can only be perceived in retrospect. type: feature New feature or request. labels May 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
effort: epic Multi-stage task that may require multiple PRs. priority: 1 This is important. It should be dealt with shortly. type: feature New feature or request. work: complex Probe-sense-respond. The relationship between cause and effect can only be perceived in retrospect.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@PaulRBerg