Reasonable Finality Depth about go-perun HOT 4 CLOSED

In case you didn't already plan it this way, I think it should be configurable, maybe as setters on the Adjudicator and Depositor classes. Or as a global variable of the backend/ethereum/channel package?

And does it make sense to use different depths for different events? Waiting for a Deposited event is more similar to the situation of exchanges. On the other hand, if a malicious Registered event is seen, it may make sense to react quicker, that is, to use a lower finality depth.

from go-perun.

In case you didn't already plan it this way, I think it should be configurable, maybe as setters on the Adjudicator and Depositor classes. Or as a global variable of the backend/ethereum/channel package?

I currently use a package variable for all calls, but this is only the first draft for testing.
Deciding how configurable we want/need it is also part of this issue discussion.
I will bring it up in the daily tomorrow, maybe we can make a meeting and sketch it out.

from go-perun.

It should be configurable at instantiation. We can also have a separate meeting to talk through it in detail. Let me know.

from go-perun.

We made it configurable in #245

from go-perun.