szymonsztuka 10e7c07c11
CORDA-2577 Disable or delete the no-downgrade rule (#4741)
With (Contract JARs) rolling upgrades the downgrade rule cannot be effectively check as the platform can't tell the difference between a transaction that's downgrading because of an attack, vs a transaction that's downgrading because Alice has upgraded but Bob hasn't yet. During a rolling upgrade we would expect state versions to fluctuate up and down as data gets read/written by a mix of nodes. With the feature as implemented Alice will upgrade and start trading with Bob. Bob will be able to read and process the states Alice sent him, but the moment he tries to consume such a state he will fail. This will result in cascading flow deaths and a hung business network the moment an upgrade starts.
2019-02-13 11:36:43 +00:00
..
2019-02-11 10:56:02 +00:00
2018-05-22 15:38:43 +01:00
2019-02-06 12:49:47 +00:00
2018-11-05 15:51:42 +00:00
2019-01-31 14:11:09 +00:00
2019-01-08 15:52:24 +00:00
2019-01-10 10:10:10 +00:00
2019-01-08 15:52:24 +00:00
2018-07-20 16:21:24 +01:00
2017-09-29 17:42:49 +01:00
2019-01-14 10:07:51 +00:00
2019-01-08 15:28:21 +00:00
2019-01-29 13:26:28 +00:00
2019-01-14 10:07:51 +00:00
2019-01-14 10:55:39 +00:00
2018-11-05 15:51:42 +00:00