signaldocs Open Signal

Build with Signal

Deployments and versions

Network: HyperEVM mainnet, chain ID 999. Reviewed 21 September 2026.

Standard 75/25 curves

ComponentAddress
Ramses Curve factory0xbb3ae37f06b6843ce26b5bd5d49b34c2e078347e
Project X Curve factory0x7db2876f10469bcdb7969a49ed3e8a401dff0e1b
Shared Pair Router0x537e9c7e0674ee6135e759556f8ddf8726b8bcc1
Project X V2 venue adapter0x0181e0ce8512b2a08c4d173be05d57d25da37726
WHYPE0x5555555555555555555555555555555555555555

These are separate from a token's individual curve, pool and processor addresses. The native_router field in current configuration identifies the user-facing Pair Router; a row's router can identify a venue router or adapter. Do not approve a spender simply because its field is named router.

Historical 80/20 curves

ComponentAddress
Ramses factory0x00d1e27aa2b004e25b7a9a7233b38670aec01117
Project X factory0x06f73cbde29fdc13b46da9bb0892ed6b8a2b81b2
Pair Router0xa1ee808e35de59cad03dd8e03e49a130061b97d5

Historical addresses remain relevant for existing tokens. The current ABI/example bundle does not authorize treating every historical or strategy deployment as equivalent.

Machine-readable records

A snapshot records what was observed, not perpetual availability. Its source hashes establish file identity, not an independent security audit. The source manifest's verification fields are publisher-reported; compilation here produces ABIs and does not independently re-prove deployed bytecode equivalence.

Version fields

FieldMeaning
curve_launches.versionConfiguration schema version
factory_versionFactory interface generation
router_versionRouting interface generation
curve_versionSale/pool geometry generation

For older configuration, absent geometry version denotes the original shape. An unsupported or unknown version must not silently use the current adapter. A companion_factory identifies an additional strategy integration requirement; exclude it from a standard spot-only adapter.

Enabled configuration is discovery evidence. Before execution, verify contract code, factory birth, token/curve/quote links, pool identity and fresh state through a trusted RPC at a consistent block. New-launch admission and existing-token exit availability are separate concerns.