-
Notifications
You must be signed in to change notification settings - Fork 1
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
[GRIN-Wallet] test late locking #8
Comments
I think it is sufficiently described to get started @MCM-Mike , I'm removing the |
i think that --late-lock flag is only working for flow #1 with send command ? am i right ? |
Prerequisites:
Step 1 (sender side)By using --late-lock flag, no UTXOs will be locked on the wallet. Instead, they will only be locked as late as possible, namely when the transaction is finalized.
by checking the balance using info command, we can see that no UTXOs are locked on the wallet.
Step 2 (receiver side):The receiver needs to process the slatepack message using the receive command. After entering the command, the receiver will be prompted to input the received slatepack. Right after the wallet will output another slatepack message to provide the sender, so he can finalize the transaction.
Step 3 (sender side) :The finalize command is the final step to any slatepack transaction. After entering the command, the sender will be prompted to input the slatepack message provided by the receiver to finalize the transaction
|
@mojitoo looks great! Could you also test the second flow |
sorry for confusion @mojitoo, I think you were right, Reviewed and closing. Thanks! |
@mojitoo I forgot to ask, can you please provide version of the wallet? you can just provide the output
|
|
Description:
Test the new late locking feature in Grin-Wallet in reference to mimblewimble/grin-wallet#530 & mimblewimble/grin-wallet#485
Late locking should work for both flows:
send -> receive -> finalize
andinvoice -> pay -> finalize
Prerequisites:
Setup two GRIN-Wallets (1) + (2) and send funds from wallet (1) to wallet (2) using the late locking feature.
Your wallet needs to be at least
v5.0.0-beta.2
refExample:
grin-wallet send --late-lock -d ....
You will create a transaction and check the behavior of wallet (1) and wallet (2) if there is any problems.
Known problems at the moment: mimblewimble/grin-wallet#541
Expected result:
You should be able to
finalize
the transaction later on wallet (1) whenever you want, without having problems spending more GRINs from your wallet (1) due to the funds being locked.The text was updated successfully, but these errors were encountered: