Skip to content

Prepare Pareto FalconX solver onboarding - #121

Open
1kresh wants to merge 3 commits into
stagefrom
codex/pareto-falconx-readiness
Open

Prepare Pareto FalconX solver onboarding#121
1kresh wants to merge 3 commits into
stagefrom
codex/pareto-falconx-readiness

Conversation

@1kresh

@1kresh 1kresh commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

Summary

  • document Pareto AA_FalconXUSDC use of the existing rounding-safe LiquidLane RFQ path
  • add dormant token and minimum configuration examples
  • record the activation requirements without guessing contract addresses

Verification

  • make format
  • make test
  • make lint
  • make build

1kresh and others added 3 commits August 5, 2026 18:52
…ss language.

The Symbiotic ParetoOracle (0xba833D6288aC591BFffbeD16909B8B824e7fA9F2) and
the Pareto account factory/implementation (0xa47cE86c304e251198F1a318c569e5217b694e1F
/ 0xE54219880a1296D028CcD7B3d5a34c65fb0B7CAB) are deployed and verified on
mainnet, so the readiness notes no longer list them as unknown. The oracle is
wired into the rfq-backend and rfq-frontend token entries.

What remains outstanding is instances rather than addresses: the
Keyring-onboarded account proxy, the LiquidLane adapter, the Executor's
authorized caller, and backend token enablement.

Also drops the "new adapter to the dedicated solver instance" and "scope the
new process to the deployed adapter" wording. The numbered solver workloads
differ only by executor and settlement adapter, not by asset, so onboarding a
permissioned token is the permissionedTokens and minAmountsIn edits and
nothing more - matching the corresponding vault-solver-deploy change.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.

1 participant