Replies: 2 comments
-
Interesting idea. In practice, the way this would work is that we build a simple UI for recovering lost funds, UI which performs the necessary approvals and calls the appropriate smart contract in the backend. I like this and the mere existence of this possibility makes me hesitant to march on with the rescuers (sablier-labs/v2-core#155) proposal. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Closing as we have decided to make the withdraw function publicly callable: |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
During a recent discussion we touched upon relayers a.k.a. other people paying gas for someone's withdrawals. Up until now we were thinking of relayers as possible rescuers (#155), whitelisted by the Sablier contracts through a permissioned system.
Why not split these two concepts and create a standalone, permissionless relayer system.
Idea
Create a helper contract that implements a flash-relay method. For the lifetime of one block, the contract will
As a pre-requirement, you (the holder) would have to allow this contract to transfer the NFT. This way, someone running a "keeper" could become the caller of this relaying contract. Should we also add an embedded fee here?
Beta Was this translation helpful? Give feedback.
All reactions