Repository navigation
amazing a few questions #4
Description
Hello Brice, I am just discovering this through Rozar’s fork: Lightning payments on Stacks—genius work - in mijoco's words.
I’m curious whether this can be extended to other use cases, and if so, which ones you see as most promising? Also, how do you suggest addressing potential issues like message loss, and are there any other challenges you foresee?
Thanks in advance for any insights or guidance!
https://x.com/RaphaStacks/status/1892281757585531109
Activity
obycode commentedon Feb 28, 2025
Hey @Rapha-btc! Not sure why I missed this issue until now. There's definitely a lot of directions that this concept can be extended.
Regarding message loss, that is up to the individual to manage their own tracking of signatures. With is a situation where the increased functionality comes with increased responsibility. Many users would probably opt for a solution where they're paying some intermediary to actually run their server that tracks the signatures for them. That's the goal of the agent that is defined in the contract -- to authorize another principal to take actions on your behalf. The agent can do all of the reactive tasks, but it can't initiate new actions (withdraws, transfers, etc).
I think the other concerns about "Practical Custody" in your post apply to Rozar's custodial version but not to StackFlow.
I'd be happy to answer any other questions you might have. And I think I'm setup now to notice new issues/comments quickly.