-
Notifications
You must be signed in to change notification settings - Fork 101
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
multi: move more functionality into taroscript, add TxValidator interface #115
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.
LGTM, mostly nits and/or clarification questions 🎉
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 🥦
Changes read well, just one or two minor things re spacing and also the error alias/assignment thing the other reviewer pointed out.
@@ -170,6 +172,9 @@ func initSpendScenario(t *testing.T) spendData { | |||
// Generate matching TaroCommitments. | |||
updateScenarioCommitments(t, &state) | |||
|
|||
// Validator instance needed to call the Taro VM. | |||
state.validator = &taro.ValidatorV0{} |
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.
Doesn't happen rn, but I think this would create a circular dep if/when the main package ever imports taroscript
. Not something we need to worry about rn tho.
8382442
to
d1d1803
Compare
Spun off from ongoing state machine work.
In this PR, we refactor functions from the VM and Address package to resolve underlying dependency issues and potential cycles. We also introduce the
TxValidator
interface, to simplify use of the Taro VM from the send state machine.