deal manager secondary trades#109
Merged
Merged
Conversation
17cf059 to
e82f873
Compare
6c8ecf5 to
01e6fed
Compare
… Add tests against real CyberAgreementRegistry
…ry. Misc housekeeping to library interfaces & dependencies
a3839a2 to
25787d7
Compare
…ger-secondary-trades
…econdary trading
…dger building. Misc fixes. Add more tests
…with scripify events
…ger-secondary-trades
…nes, and unit reservation should be managed end-to-end by secondary transfer controller (aka deal manager) itself
merisman
approved these changes
Jul 3, 2026
merisman
left a comment
Contributor
There was a problem hiding this comment.
Reviewed, submitted 4 issues via dm. Going to merge and fix on feat/legion branch.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
TODO
Added
Updated
Spec: decided not to extend
LexScroWLitewith secondary trade logic because the overlaps between primary and secondary trades turns out to be too small to worth sharing the same base contractLexScroWLite, they will be mostly non-overlapping if...else branches. Why risking re-auditLexScroWLiteif most of its codes are re-written?DealManagerthrough a dedicated storageSecondaryTradeStorage; this way we don't need to deploy a new manager (and its factory)Refactoring: convert
LexScroWLiteinto a pure library by merging it withLexScrowStorage. This is for reducing DealManager contract size. No behavioral changes, no ABI changes, no migration neededLexScroWLitealone is stateless: all its app data is already stored inLexScrowStorageand will continue be so after the refactoring