Closed crazybuster closed 6 years ago
We're going to throw a version field on the Listing contracts. Eventually we'll have to support multiple contract versions simultaneously.
In addition to the contract ABIs, the listing schemas are also pieces of data that will require versioning... there will probably be cases where two versions aren't backwards compatible (like major and minor versions of software).
Since this data is also used by multiple components (currently origin-js, bridge server, dapps) there could be the need for a synchronization mechanism in the future.
It'd be good to have somewhere, some tag/version mapping of which version of origin-js the contracts of bridge server is built again. If not, there could be definitely be mismatches of what contracts are running on origin-js and what the bridge-server is listening for.
Not at all sure what this should look like. Maybe just an entry in the README? We don't have a monolithic run script.