Preprocesses manifest in xState to get current Active Positions and Active Security IDs by Stock Class.
Seeding has now been simplified to above diagram. Transactions backfilled in contract don't perform any onchain logic, rather only trigger the right Transaction smart contract
Re-designed parts of the Cap Table Contract to be more efficient, separates activePosition updates and _issueStock and adds helpers strictly for seeding.
Discussion Point
Will backfilling transactions onchain at all be too expensive? It's likely that this will be issuer specific depending on the number of transactions. For now, backfilling should be appropriate.
Close collaboration with @AdamMomen
New Seeding Flow.
Discussion Point