Skip to content
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

Wire solana #53

Open
wants to merge 34 commits into
base: ops/deploy-standalone-frxUsd-lockbox-for-solana-testing
Choose a base branch
from

Conversation

dhruvinparikh
Copy link
Contributor

No description provided.

package.json Outdated
"@nomicfoundation/hardhat-ethers": "^3.0.5",
"@nomiclabs/hardhat-ethers": "^2.2.3",
"@nomiclabs/hardhat-waffle": "^2.0.6",
"@openzeppelin/contracts": "^5.0.2",
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This upgraded dependency will cause breaking changes in the OFT imports as the OFT uses 4.x.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

noted

peerArray[2] = peer.sFrxEth;
peerArray[3] = peer.frax;
peerArray[4] = peer.frxEth;
peerArray[1] = peer.sFrxEth; // TODO: modify to sfrxUSD
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: can remove TODO

bytes32 frxEth;
bytes32 fxs;
bytes32 sFrax;
bytes32 sfrxUSD;
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note the difference between this line and the next of sfrx and sFrx. Execution would be the same either way due to sorting, no change needed.

@pegahcarter
Copy link
Collaborator

I've confirmed the msig txs.

Question I have: what will the operations look like to add support to a new chain (say Base)? I noticed that in each wire commit (for example 303e427), the address in deployments/{ChainName}/FraxOFTUpgradeable.json was changed to the corresponding OFT. Would address need to be again re-configured for each chain for each OFT?

Copy link
Collaborator

@pegahcarter pegahcarter left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great! We can update the README with the new solana addresses.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants