"Start appeal" function

[0xjona]

Defines a new "origin time stamp" and a possible queuing mechanism

[0xjona]

This a change in when the “round_timestamp” start!
Now it starts when the client creates an “appeal”, but in case referees and leaders are somehow busy we don’t want to punish the provider that might have the file retrievable but not “checked” by the referees network.

The proposal is that the round is processed since the first leader has started the process.

We need a bit more of further discussion @turinglabsorg @nicola

[turinglabsorg]

@0xjona one second, i already added the change here: 30595d0

I added a new field in the struct which is called request_timestamp, this field is not the original one, which was origin_timestamp.

Any of the referees can start the appeal using the startAppeal function, when this function is called the origin_timestamp is set and the rounds starts.

There's no round_timestamp inside the protocol, from where it came?

[turinglabsorg]

Ok, the implementation was done and network upgraded! 🥳

[irenegia]

@turinglabsorg should I procede to update the hackMD then?

[turinglabsorg]

yes @irenegia, let me know if you need something from me, we'll close the issue after hackmd is updated

[irenegia]

hackMD updated, closing this issue!