User is able to Withdraw the BTC after clicking on the 'Withdraw' button and then refresh the page with SON inactive on the Bitcoin Transaction page.

--dex3--

Browser: Chrome v98.

OS: Windows 10 Pro.

Blockchain Connected: Evans QA environment

Blockchain Version: test-1.5.4-85-g18775061

Dex Version: develop

Pre Condition:

SON network should be down.

Steps:

  1. Open the application URL : 'https://dex3.peerplays.download/'

  2. Login with valid credentials.

  3. Now click on the 'Hamburger' icon and go to 'Bitcoin Transaction' page .

  4. Now enter the Amount in 'Withdraw' field.

  5. Then click on the 'Withdraw' button and unlock the profile.

  6. Now refresh the page.

  7. Verify the result for the deducted BTC.

Expected Result:

User should not be able to Withdraw the BTC after clicking on the 'Withdraw' button and then refresh the page with SON inactive on the Bitcoin Transaction page.

Actual Result:

User is able to Withdraw the BTC after clicking on the 'Withdraw' button and then refresh the page with SON inactive on the Bitcoin Transaction page.

Please consider the below screenshot:

withdraw_test

223232


Notes by @bobinson :

This doesn't look like the "magical" happening of BTC withdrawal without the SONs and a complete breakdown of the multi-signare wallets created. Rather this seems to be that the initial step in BTC withdraw process, ie sending the funds from a peerplays user account to son-account is being carried out. The question is should we consider the SON down state before such an operation is carried and out this should be prevented in the first place. Secondly, If the transfer of pBTC from a user account to son-account happens and if the SONs are down, will the transaction always succeed when the SONs come back ?

@serkixenos @prandnum - Can you guys look into the above scenarios ? This is right now reproducible in @elynch1 's development environment and UI is available in DEX3.Peerplays.download

Edited by Bobinson K B