-
Notifications
You must be signed in to change notification settings - Fork 87
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feat: standalone nep141 legacy #669
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice idea with the flag in the state to indicate if the legacy code can be disabled! I still think a more general solution involving the engine version would be better because it would generalize to other changes we might want to make, but this gets the job done for this case.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah this can work for now. Thank you.
Description
After splitting logic in #607 - Split NEP-141 from Engine,
engine-standalone
requires changes. Sinceengine-standalone
cannot interact with the newaurora-eth-connectpr
contract, the previous NEP-141-related codebase has been moved separately tostandalone-nep141-legacy
. This will ensure thatengine-standalone
works well with historical data.Modules were added:
legacy_connector
fungible_token
Performance / NEAR gas cost considerations
It affects only standalone. So no side effects.
Testing
Tests not changed for standalone. Just restored expected behaviour. For some unknown reason failed function
validate_standalone
, but that function don't affect any test.