Conversation
Moved out of IGP-139 Action 2, which reverted the Foundation grant on execution. Two fixes over the original: Vault auth now goes through VAULT_FACTORY_WRAPPER_OWNER instead of the vault factory. setVaultAuth is onlyOwner on the factory and the factory is owned by the wrapper, so the direct call reverted UNAUTHORIZED for the timelock. This matches how every payload since IGP-130 sets vault auth. The pre-setup asserts vault 182 is deployed on the fork rather than assuming it. The vault landed on mainnet at block 25,789,585, hours after the IGP-139 simulation forked, and the Liquidity Layer rejects configs for an address with no code, so the original run died on the address-is-contract check before it ever reached the auth call. Limits are unchanged from the original action ($7k withdrawal, $7k/$9k borrow, 50% over 6h). Prices are refreshed, so the token amounts differ. Verified against mainnet that all three calls succeed from the timelock, and that the vault is deployed but still unconfigured at the Liquidity Layer.
… ~$1M Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Governance Simulation Completed - IGP-140Payload Contract: Proposal Actions
📊 Transaction Summary
Proposal Creation TransactionTransaction Hash: Tenderly Dashboard: View Transaction Raw Transaction DataLinks |
… team MS dex auth Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…xpansion Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…lock Appointing a class-1 schedule writer on FluidUsEquityMarketHours is currently an instant Team Multisig action. It moves behind the 24h FluidTimelockController instead, with the multisig dropped to class 2 so a session correction inside the 5h pinned window stays immediate. Both calls verified against mainnet from the governance timelock; the same call from the multisig reverts, confirming updateAuth is governance-gated.
IGP Validation Failed - IGP-140The IGP structure does not meet the required standards for automated simulation. Validation ErrorsWarnings:
Required StructureMandatory Requirements:
Optional but Recommended:
Next Steps
Automated IGP validation via GitHub Actions |
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
IGP Validation Failed - IGP-140The IGP structure does not meet the required standards for automated simulation. Validation ErrorsWarnings:
Required StructureMandatory Requirements:
Optional but Recommended:
Next Steps
Automated IGP validation via GitHub Actions |
Vaults 78/79 already carry the dust-ceiling config, so both calls were no-ops. Vault 6 holds ~640 weETH, where a flat $10k base would fall below live supply and activate the 10%/6h rate limit -- the exit friction the action exists to remove -- so it takes a 700 weETH base. "Paused" reworded to "deprecated": the helper writes debt ceilings, never calls pauseUser, and ceilings are checked on borrow only.
IGP Validation Failed - IGP-140The IGP structure does not meet the required standards for automated simulation. Validation ErrorsWarnings:
Required StructureMandatory Requirements:
Optional but Recommended:
Next Steps
Automated IGP validation via GitHub Actions |
The unanchored regex took the first "contract <word>" anywhere in the file, so IGP140's NatSpec mentioning a "schedule contract the oracles read from" resolved the name to "the". 48 of 133 payloads trip it.
bergben
requested review from
bergben and
thrilok209
and removed request for
bergben
September 9, 2026 12:46
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Moved out of IGP-139 Action 2, which reverted the Foundation grant on execution. Two fixes over the original:
Vault auth now goes through VAULT_FACTORY_WRAPPER_OWNER instead of the vault factory. setVaultAuth is onlyOwner on the factory and the factory is owned by the wrapper, so the direct call reverted UNAUTHORIZED for the timelock. This matches how every payload since IGP-130 sets vault auth.
The pre-setup asserts vault 182 is deployed on the fork rather than assuming it. The vault landed on mainnet at block 25,789,585, hours after the IGP-139 simulation forked, and the Liquidity Layer rejects configs for an address with no code, so the original run died on the address-is-contract check before it ever reached the auth call.
Limits are unchanged from the original action ($7k withdrawal, $7k/$9k borrow, 50% over 6h). Prices are refreshed, so the token amounts differ. Verified against mainnet that all three calls succeed from the timelock, and that the vault is deployed but still unconfigured at the Liquidity Layer.
IGP Actions