-
Notifications
You must be signed in to change notification settings - Fork 22
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: nullchain changes for snapshot-compatibility pipeline #8887
Conversation
ef7eef9
to
520c6de
Compare
58720c4
to
a9ff537
Compare
ab4bc94
to
3d54d13
Compare
6e0cd7e
to
2d5bb9e
Compare
} | ||
|
||
var err error | ||
n.ethClient, err = ethclient.Dial(n.ctx, n.conf.Ethereum) |
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.
Not blocking, but worth noting:
Before if a node set up as a validator, and forgot to populate n.conf.Ethereum.RPCEndpoint
it would fail when it tried to dial and the error would be useful, but now I think we'll probably just randomly panic with a nil-pointer the first time the ethClient
tries to be used.
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.
We will not Dial when the n.conf.Ethereum.RPCEndpoint
is empty.
2d5bb9e
to
1df38fd
Compare
close vegaprotocol/devops-infra#1531 .
Changes
Vega code disables some functionalities when we use null chain it causes an inability to use genesis where We have the ERC20 tokens - this means We cannot use the mainnet genesis. A very similar situation was with some of the snapshot items. Vega loads snapshots differently when We want to use the null chain.
I have removed branches for the null chain and now the null chain should behave in the same way as tendermint.
Triggered runs:
Related PRs