Quote from: monsterer2 on February 23, 2018, 11:19:42 AM

Quote from: Blinknet on February 23, 2018, 11:17:07 AM

Quote from: monsterer2 on February 23, 2018, 11:02:20 AM

Quote from: Blinknet on February 22, 2018, 09:52:24 PM

There's no way to create inconsistent transactions like this, the worst that could happen is that a locker signs a valid transaction that doesn't have time to be broadcast to the network.

What happens when lockers aren't available to sign for their allotted accounts?

Say we have 20 transactions from 20 accounts, being allocated to 20 lockers, and 10 of them are offline?

The accounts need to wait for the next round, if the transactions are not signed by the lockers they are invalid and won't be accepted by the network.

So that round closes empty, or we get 10/20 transactions in the round?

Our entire algorithm is focused around the idea that independent transactions can be treated independently. So in that round all the other transactions will be accepted, except those that were performed on accounts which had unresponsive lockers.