Skip to content
This repository has been archived by the owner on Dec 13, 2019. It is now read-only.

[node] Decouple deposit commitment from onchain transaction #2516

Open
rhlsthrm opened this issue Oct 15, 2019 · 2 comments
Open

[node] Decouple deposit commitment from onchain transaction #2516

rhlsthrm opened this issue Oct 15, 2019 · 2 comments

Comments

@rhlsthrm
Copy link
Collaborator

rhlsthrm commented Oct 15, 2019

User story (Mosendo use case):

As a user, I need to have a deposit address that allows my money to be instantly spendable offchain when funds are transferred to it asynchronously. This is complicated by the fact that I might sometimes use Sendwyre and other services that can deposit at any time, any arbitrary amount into the address. I want to be able to log into my wallet and spend these funds instantly after the transaction is complete.

Proposed solution/discussion:

The prerequisite to making this work is to split up the deposit commitment from the deposit transaction.

However, this does not solve the case where funds are transferred to the deposit address asynchronously when the client is offline.

One thought to solve the above is to assume that any "unallocated" funds (i.e. not free balance, not in apps), can be "claimed" by either party. We can make this opinionated in our client-hub implementation by assuming that the hub will never asynchronously deposit, and we will always accept the client's request to claim the unallocated funds.

@snario
Copy link
Contributor

snario commented Oct 18, 2019

Discussed this with @cf19drofxots and we think we have an approach, will put up a draft PR soon.

@rhlsthrm
Copy link
Collaborator Author

@snario can we get a status update on this?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants