I don't understand why a distributed solution is necessary here. Couldn't you just use a database and a git repo of stored procedures for share creation/dilution?
A database might be susceptible to tampering, etc. It might be simpler to just use the OCF file itself and put it under source control/ledger tracking via git.
I think the base level solution could just be an OCF file and git with some sort of consensus requirement among all partners before a merge to master is allowed.
The key thought is that the OCF file format standard is a great start but for sure other features/tooling around the format could be interesting to drive adoption.
I think the base level solution could just be an OCF file and git with some sort of consensus requirement among all partners before a merge to master is allowed.
The key thought is that the OCF file format standard is a great start but for sure other features/tooling around the format could be interesting to drive adoption.