Open victormimo opened 1 year ago
Wanted to follow up here since this is relevant to us from a gas savings perspective of writing to a blockchain. @JSv4 when we meet over zoom you proposed a work around using issuances I believe. Would you be able to provide a simple example of how that would look?
Much appreciated!
Hey @victormimo, I believe we discussed this live at some point on a call before the last summit on how you could do this. You could transfer the split issuances to a new, consolidated issuance. There may be other implications to worry about there, but that should work. I'm going to close this for now, but please re-open if you have more questions / thoughts.
Perfect, thank you.
Notes from the TWG:
Additional examples where we have encountered other real world many-to-one security scenarios (where we have the documents and stock certs as data points to run off of):
Further discussion on this point - we do need something to consolidate transactions as the only way to do this ATM is to cancel and re-issue, which breaks any structured link between the securities.
Also, as flagged by @arthur-clara, this transaction type will simplify and clarify the validation work. Some of the proposed rules for resulting_security_id
and balance_security_id
fields in Arthur's proposal rely on a Transfer always have the resulting_security_id point to an issuance with a new stakeholder_id
.
Discussed in https://github.com/Open-Cap-Table-Coalition/Open-Cap-Format-OCF/discussions/444