-
Notifications
You must be signed in to change notification settings - Fork 4
Adds zap contract address to getHyperdrive #1778
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
Conversation
Co-authored-by: Danny Delott <DannyDelott@users.noreply.github.com>
|
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
6 Skipped Deployments
|
| const accountTxHashes = transfersSentToZap.map( | ||
| ({ transactionHash }) => transactionHash, | ||
| ); | ||
| // Fetch CloseLong events emitted by the auxiliary contract in the relevant block range. |
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.
nit: auxiliary contract -> zap contract
| drift: getDrift({ chainId: hyperdrive.chainId }), | ||
| earliestBlock: hyperdrive.initializationBlock, | ||
| zapContractAddress: | ||
| appConfigForConnectedChain.zaps[hyperdrive.chainId].address, |
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.
Since zaps is only configured for the fork chain, we need to do ?.address everywhere, right?
This PR adds the zapContractAddress param to each instance of getHyperdrive.