Deployment: AutoRange (ReClamm) Pool Factory V3

[EndymionJkb]

Deployment: AutoRange (ReClamm) Pool Factory V3

There is a small code change. Turns out there was an error in the input.ts that I needed to fix. (It actually worked accidentally, but I wanted it to be correct. If we ever changed the flags to non-false it would break.)

I got quite an education in how HyperEVM works. There's some setup needed to start deploying with a new account. See PR #397 for scripts to automate that next time. (I've also updated our internal deployment docs with all this information.)

It would not automatically verify on Plasma. It said it succeeded: but was lying. It was not verified in the UI. Plasma and X-Layer aren't supported in Etherscan V2, so I had to use --v1 to go through RouteScan; probably something dropped there.

Anyway I had to verify it manually, and included the JSON to upload for all three contracts (and the constructor args as a string). Thought I might as well include that, in case we add it to another chain and have similar issues.

Deployment tasks checklist:

• Contract(s) deployed to all target networks / testnets
• TX IDs are properly generated
• Action IDs are generated after deployment (if applicable)
• If a governance proposal is required, Action IDs have been sent to the Maxis
• Outputs for all target networks are generated, and linked in the task readme
• Addresses files are up to date with the new deployment
• Contracts are verified in every network
• Deployments CHANGELOG is updated
• There are no code changes of any kind

Issue Resolution

[joaobrunoah]

LGTM!