Skip to content

Add Forked Mainnet Simulations to v0#253

Open
jribbink wants to merge 3 commits intov0from
jribbink/fork-tests-v0
Open

Add Forked Mainnet Simulations to v0#253
jribbink wants to merge 3 commits intov0from
jribbink/fork-tests-v0

Conversation

@jribbink
Copy link
Copy Markdown
Contributor

@jribbink jribbink commented Apr 6, 2026

Description

Cherry picks fork tests from main to v0, and updates to latest block heigth including PYUSD0 debt type.

Because these tests rely on mainnet contracts, it makes sense to have them on the v0 branch instead of main, given that this is what is actually deployed.


For contributor use:

  • Targeted PR against master branch
  • Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
  • Code follows the standards mentioned here.
  • Updated relevant documentation
  • Re-reviewed Files changed in the Github PR explorer
  • Added appropriate labels

@jribbink jribbink force-pushed the jribbink/fork-tests-v0 branch 16 times, most recently from 64a3a31 to 4047356 Compare April 7, 2026 23:13
jribbink and others added 2 commits April 7, 2026 16:26
Co-authored-by: Leo Zhang (zhangchiqing) <zhangchiqing@gmail.com>
Co-authored-by: Raymond Zhang <zhangraymond05@gmail.com>
Co-authored-by: Leo Zhang (zhangchiqing) <zhangchiqing@gmail.com>
Co-authored-by: Raymond Zhang <zhangraymond05@gmail.com>
@jribbink jribbink force-pushed the jribbink/fork-tests-v0 branch from 4047356 to 8fc1faf Compare April 7, 2026 23:26
@jribbink jribbink changed the title Jribbink/fork tests v0 Add Forked Mainnet Simulations to v0 Apr 7, 2026
@jribbink jribbink marked this pull request as ready for review April 7, 2026 23:33
@jribbink jribbink requested a review from a team as a code owner April 7, 2026 23:33
@jribbink jribbink force-pushed the jribbink/fork-tests-v0 branch 3 times, most recently from c17f944 to 736acdb Compare April 8, 2026 16:43
@jribbink jribbink force-pushed the jribbink/fork-tests-v0 branch from 736acdb to 53c05b6 Compare April 8, 2026 17:08
)

// TODO: closeYieldVault currently fails due to precision issues
// closeYieldVault(signer: user, id: yieldVaultIDs![0], beFailed: false)
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Can we try close the vault on this branch?

I think the issue has been fixed on v0 branch, right?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Good point, looks like it 🥳 will remove

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