manual sidechain withdrawal transaction does not accomplish withdraw to hive #327

Closed
opened 2022-03-18 12:03:30 +00:00 by pavel.baykov · 8 comments
pavel.baykov commented 2022-03-18 12:03:30 +00:00 (Migrated from gitlab.com)

after execution cli_wallet command from issue 314,
son-account received funds but does not send it into HIVE network

after execution cli_wallet command from issue 314, son-account received funds but does not send it into HIVE network
pavel.baykov commented 2022-03-18 12:03:31 +00:00 (Migrated from gitlab.com)

assigned to @pavel.baykov

assigned to @pavel.baykov
pavel.baykov commented 2022-03-18 12:15:21 +00:00 (Migrated from gitlab.com)

after command executed, evaluator do_evaluate, succeed, do_apply executed next
but actual transfering does not happening: in regular way it should execute:

sidechain_net_handler_hive.cpp
bool sidechain_net_handler_hive::process_withdrawal(const son_wallet_withdraw_object &swwo)

after command executed, evaluator do_evaluate, succeed, do_apply executed next but actual transfering does not happening: in regular way it should execute: sidechain_net_handler_hive.cpp bool sidechain_net_handler_hive::process_withdrawal(const son_wallet_withdraw_object &swwo)
pavel.baykov commented 2022-03-21 16:34:37 +00:00 (Migrated from gitlab.com)

Need to use procedure from 314 ticket and multiple invocations, based on expected_reports:

sidechain_withdrawal_transaction sonaccount01 327 4 peerplays-50eea5c23c6ee2f466ed85be1036ba69bde34508-0 50eea5c23c6ee2f466ed85be1036ba69bde34508 1.2.52 5 account01 HIVE 50

sidechain_withdrawal_transaction sonaccount02 327 4 peerplays-50eea5c23c6ee2f466ed85be1036ba69bde34508-0 50eea5c23c6ee2f466ed85be1036ba69bde34508 1.2.52 5 account01 HIVE 50

sidechain_withdrawal_transaction sonaccount03 327 4 peerplays-50eea5c23c6ee2f466ed85be1036ba69bde34508-0 50eea5c23c6ee2f466ed85be1036ba69bde34508 1.2.52 5 account01 HIVE 50

sidechain_withdrawal_transaction sonaccount04 327 4 peerplays-50eea5c23c6ee2f466ed85be1036ba69bde34508-0 50eea5c23c6ee2f466ed85be1036ba69bde34508 1.2.52 5 account01 HIVE 50

sidechain_withdrawal_transaction sonaccount05 327 4 peerplays-50eea5c23c6ee2f466ed85be1036ba69bde34508-0 50eea5c23c6ee2f466ed85be1036ba69bde34508 1.2.52 5 account01 HIVE 50

sidechain_withdrawal_transaction sonaccount06 327 4 peerplays-50eea5c23c6ee2f466ed85be1036ba69bde34508-0 50eea5c23c6ee2f466ed85be1036ba69bde34508 1.2.52 5 account01 HIVE 50

sidechain_withdrawal_transaction sonaccount07 327 4 peerplays-50eea5c23c6ee2f466ed85be1036ba69bde34508-0 50eea5c23c6ee2f466ed85be1036ba69bde34508 1.2.52 5 account01 HIVE 50

Need to use procedure from 314 ticket and multiple invocations, based on expected_reports: sidechain_withdrawal_transaction sonaccount01 327 4 peerplays-50eea5c23c6ee2f466ed85be1036ba69bde34508-0 50eea5c23c6ee2f466ed85be1036ba69bde34508 1.2.52 5 account01 HIVE 50 sidechain_withdrawal_transaction sonaccount02 327 4 peerplays-50eea5c23c6ee2f466ed85be1036ba69bde34508-0 50eea5c23c6ee2f466ed85be1036ba69bde34508 1.2.52 5 account01 HIVE 50 sidechain_withdrawal_transaction sonaccount03 327 4 peerplays-50eea5c23c6ee2f466ed85be1036ba69bde34508-0 50eea5c23c6ee2f466ed85be1036ba69bde34508 1.2.52 5 account01 HIVE 50 sidechain_withdrawal_transaction sonaccount04 327 4 peerplays-50eea5c23c6ee2f466ed85be1036ba69bde34508-0 50eea5c23c6ee2f466ed85be1036ba69bde34508 1.2.52 5 account01 HIVE 50 sidechain_withdrawal_transaction sonaccount05 327 4 peerplays-50eea5c23c6ee2f466ed85be1036ba69bde34508-0 50eea5c23c6ee2f466ed85be1036ba69bde34508 1.2.52 5 account01 HIVE 50 sidechain_withdrawal_transaction sonaccount06 327 4 peerplays-50eea5c23c6ee2f466ed85be1036ba69bde34508-0 50eea5c23c6ee2f466ed85be1036ba69bde34508 1.2.52 5 account01 HIVE 50 sidechain_withdrawal_transaction sonaccount07 327 4 peerplays-50eea5c23c6ee2f466ed85be1036ba69bde34508-0 50eea5c23c6ee2f466ed85be1036ba69bde34508 1.2.52 5 account01 HIVE 50
pavel.baykov commented 2022-03-21 16:37:04 +00:00 (Migrated from gitlab.com)

block number should be next to block of transfer transaction

block number should be next to block of transfer transaction
pavel.baykov commented 2022-03-21 16:38:37 +00:00 (Migrated from gitlab.com)

transaction_id should be taken using : get_transaction_id «transaction JSON from next get_block of next block number»

transaction_id should be taken using : get_transaction_id «transaction JSON from next get_block of next block number»
pavel.baykov commented 2022-03-22 07:44:30 +00:00 (Migrated from gitlab.com)

mentioned in issue #314

mentioned in issue #314
serkixenos commented 2022-03-23 12:43:11 +00:00 (Migrated from gitlab.com)

assigned to @prandnum

assigned to @prandnum
pavel.baykov commented 2022-03-30 06:09:37 +00:00 (Migrated from gitlab.com)

verified manually worked fine with develop branch

verified manually worked fine with develop branch
pavel.baykov (Migrated from gitlab.com) closed this issue 2022-03-30 06:09:41 +00:00
Sign in to join this conversation.
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Peerplays_Blockchain/peerplays_migrated#327
No description provided.