Finalise the design (including API definition) for Settlement V3, and implement for the existing ledger.
It is likely that existing deployments (viz. COMESA/DRPP) will need the settlement V3 functionality before they are ready to adopt any TigerBeetle ledger implementation - and indeed before that implementation is ready for adoption. Consequently, there is a need to prioritise this work, whilst ensuring that (a) any aspect outside the ledger may be ported to the TigerBeetle implementation, and (b) that the elements that are specific to the existing ledger implementation are compatible with the TigerBeetle implementation at the API level.
Finalise the design (including API definition) for Settlement V3, and implement for the existing ledger.
It is likely that existing deployments (viz. COMESA/DRPP) will need the settlement V3 functionality before they are ready to adopt any TigerBeetle ledger implementation - and indeed before that implementation is ready for adoption. Consequently, there is a need to prioritise this work, whilst ensuring that (a) any aspect outside the ledger may be ported to the TigerBeetle implementation, and (b) that the elements that are specific to the existing ledger implementation are compatible with the TigerBeetle implementation at the API level.