-
Notifications
You must be signed in to change notification settings - Fork 11
Add MetaClient verification #188
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
base: develop
Are you sure you want to change the base?
Conversation
info := params["info"] | ||
if len(info) != 2 { | ||
return nil, fmt.Errorf("incorrect size for info: %v", info) | ||
} | ||
to := common.HexToAddress(info[0]) // metacall address | ||
dApp := common.HexToAddress(info[1]) |
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.
Are we sure that an array of strings is the best design here? The worry about this design is that the positional requirements in the array are hard to validate and track across deployment systems and tooling.
One alternative could be to use a TOML table with named params for to
and dApp
, maybe like the below?
[relayConfig.dualTransmission.meta.info]
to = "0x000000..." # metacall address
dApp = "0x000000..."
No description provided.