mirror of
https://github.com/corda/corda.git
synced 2024-12-19 04:57:58 +00:00
10e7c07c11
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. |
||
|---|---|---|
| .. | ||
| dependency-checker | ||
| api-current.txt | ||
| check-api-changes.sh | ||
| ci-gradle-build-cache-init.sh | ||
| kill_corda_procs.cmd | ||
| README.md | ||
!! DO NOT MODIFY THE API FILE IN THIS DIRECTORY !!
The api-current.txt file contains a summary of Corda's current public APIs,
as generated by the api-scanner Gradle plugin. (See here for a detailed description of this plugin.) It will be regenerated and the copy in this repository updated by the Release Manager with
each new Corda release. It will not be modified otherwise except under special circumstances that will require extra approval.
Deleting or changing the existing Corda APIs listed in api-current.txt may
break developers' CorDapps in the next Corda release! Please remember that we
have committed to API Stability for CorDapps.