> ## Documentation Index
> Fetch the complete documentation index at: https://docs.aifinpay.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Network inventory and readiness

> How AiFinPay distinguishes source support, deployments, verified runtime profiles and payment-live routes.

AiFinPay is multichain by design, but **network inventory is not production
readiness**. A logo, contract address, historical transaction or merged source
tree must not be presented as a live payment rail.

## One economics model on every chain

| Route | Settlement semantics | AiFinPay fee | Creator fee |
| - | - | -: | -: |
| AIFP-1 | gross-inclusive; merchant 99% | 1% | 0% |
| AIFP-2 / x402 | provider receives 100% | 0% | 0% |

Network gas is separate in both routes.

## Readiness states

| State | Meaning |
| - | - |
| `source` | Canonical implementation exists and its unit tests pass. |
| `deployed` | An address exists, but runtime/profile evidence may still be missing. |
| `verified` | Address, chain ID, runtime hash, version and BPS profile match the reviewed release. |
| `payment-live` | Verified route also passed controlled paid E2E and final security gates. |
| `legacy` | Historical implementation with incompatible economics or ABI; must not be selected by SDK/backend. |

## Current release boundary

* EVM, Solana and Casper have canonical source release candidates.
* Current payment signing remains fail-closed until the exact deployment,
  runtime hash/profile and paid E2E evidence are pinned.
* Historical Polygon v1.1/v1.2 splitters and the historical Solana Seat gate are
  not canonical AIFP-1 or AIFP-2 payment routes.
* Bitcoin, Avalanche, Sui, Stellar, Tron, NEAR and Aptos repositories are
  inventory/legacy until each is reconciled and independently verified.
* AIFP-3 Agent Passport identity records are separate from AIFP-1/AIFP-2
  settlement and do not make a chain payment-live.

## Required release evidence

For each enabled chain publish the chain ID, canonical address/program ID,
artifact version, runtime/code hash, on-chain profile, supported assets, audit
commit, paid E2E transaction and activation date. If any field is missing, the
route remains disabled.

See [Pricing, units and limits](/reference/pricing-and-limits) for the exact
economic vectors.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.