SON transaction signing taking more than 3 block time #86

New issue

Closed

opened 2021-04-26 11:48:38 +00:00 by prandnum · 3 comments

prandnum commented

2021-04-26 11:48:38 +00:00

(Migrated from gitlab.com)

Testcase reference: https://peerplays.atlassian.net/browse/SON-357
signing-speed.txt

Issue Seen: To move from valid to complete the total time taken is more than 9s. I am giving the command(get_son) every second and as you can see it took 9 iterations(if you include manual delay it should be more than 9s) Testcase reference: https://peerplays.atlassian.net/browse/SON-357 [signing-speed.txt](/uploads/5612b4a415ccb96627d8cf1872f1c05b/signing-speed.txt)

prandnum commented

2021-04-26 11:49:16 +00:00

(Migrated from gitlab.com)

@bobinson @serkixenos @sierra19XX

CC: @hbelakon

@bobinson @serkixenos @sierra19XX CC: @hbelakon

serkixenos commented

2021-04-27 10:38:43 +00:00

(Migrated from gitlab.com)

Block X - sidechain transaction is created
Block X+1 - sidechain transaction is visible to all SONs, and they are creating signature proposals
Block X+2 - signature proposals are visible to all SONs, and they are inspecting and approving the proposals
Block X+3 - proposals are executed
Block X+4 - signed sidechain transaction is visible to all SONs, and the scheduled SON will broadcast it

Test instructions are a bit outdated, as the block propagation is not taken into account. There are no guarantees that any SON operation will complete in any time, there are best case scenarios where we can estimate minimal needed time. This is the current workflow: - Block X - sidechain transaction is created - Block X+1 - sidechain transaction is visible to all SONs, and they are creating signature proposals - Block X+2 - signature proposals are visible to all SONs, and they are inspecting and approving the proposals - Block X+3 - proposals are executed - Block X+4 - signed sidechain transaction is visible to all SONs, and the scheduled SON will broadcast it

prandnum commented

2021-05-03 13:44:11 +00:00

(Migrated from gitlab.com)

closing as per above comment.

prandnum (Migrated from gitlab.com) closed this issue

2021-05-03 13:44:12 +00:00