[GRIN-Wallet] Test Slatepack flow (Text) #17
Assignees
Labels
Comments
Prerequisites:
Step 1 (Wallet 1 : sender side)The send command is the first step of building an interactive transaction. Both wallets will interact in an asynchronous process by exchanging copy-pastable strings called slatepacks. By using --manual flag, the user is deliberately choosing to not attempt to interact via Tor and only output slatepack message. The output slatepack is also encypted for the recipient only, since the sender provided an address (which is a public key) by using the -d flag. Last but not least, the send need to specify the amount to send. Following this command the user needs to enter his password wallet to get the slatepack message displayed on screen and also an output to a .slatepack file. he either have the choice to copy the slatepack message and send it to the receiver or provide him with the slatepack file. Step 2 (Wallet 2 : receiver side):The receiver needs to process the slatepack message using the receive command beside the --manual flag to not attempt to interact via Tor and only output slatepack message. 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 (Wallet 1 : 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 |
|
for the second flow, i found a bug @marekyggdrasil . i will send you a secret gist link |
|
@chandrashekar10 can you please help reproducing? @mojitoo found some problems and he is using Catalina, my wallet doesn't even run since I upgraded to Catalina due to this issue mimblewimble/grin-wallet#554 I saw here you have Mojave and already appropriate testing setup, leave a thumbs up if you are interested and I'll assign you as well and of course you will also be rewarded |
|
I assign myself as well, but just to be clear, I am not participating in the challenge, I will just reproduce the results on Linux so that we have Catalina vs Mojave vs Linux. |
|
Environment I have two wallets The absolute paths of the two wallets are I can reach the default wallet grin wallet from any directory without any problem I could see the 4.97 grin I hold. (b) Now I change my path to the Downloads directory Then I check with the command grin-wallet info command So I can reach the grin-wallet from outside the ./grin-wallet folder. I have tested two condition here Now to check the second wallet in the local directory called newwallet. We can see the contents of the local wallet. |
|
I finished working on reproducing the test and @chandrashekar10 also sent me his findings in a secret gist repository. Great work everyone! |
|
@mojitoo and @chandrashekar10 I forgot to ask, can you please provide versions of your wallets? |
|
The version of wallets used in my test The first wallet grin-wallet version is The second wallet newwallet version is |
|
This was referenced Dec 22, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description:
Test that transacting with Slatepacks works by outputting text.
Slatepack text transacting should work for both flows:
send -> receive -> finalizeandinvoice -> pay -> finalizePrerequisites:
Setup two GRIN-Wallets (1) + (2) and send funds from wallet (1) to wallet (2) via Slatepacks through Text method.
Example:
grin-wallet send --manual -d ....You will create a transaction and check the behavior of wallet (1) and wallet (2) if there is any problems.
Expected result:
You should be able to
finalizethe transaction later on wallet (1) whenever you want, without any problems.Note: More about these flows can be read on:
The text was updated successfully, but these errors were encountered: