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

# Production Readiness

> The checklist Sweepr and partners should complete before enabling Partner V2 in production.

# Production Readiness

Use this checklist before enabling Partner V2 for a live integration.

## Sweepr Platform Checklist

### Backend

* Run the latest Prisma migration.
* Set `SWEEPR_EVM_BUILD_MODE=v5_partner_fees`.
* Set `SWEEPR_V2_PLATFORM_FEE_BPS=75`.
* Set `SWEEPR_V2_INDEXER_ENABLED=true`.
* Set `SWEEPR_V2_BUILD_THROTTLE_LIMIT` and `SWEEPR_V2_BUILD_THROTTLE_TTL_MS`.
* Configure `SWEEPR_FEE_SIGNER_PRIVATE_KEY`.
* Configure `SWEEPR_PROTOCOL_FEE_RECIPIENT`.
* Configure `SWEEPR_V5_CONTRACT_BASE`.
* Configure at least one Base fallback RPC with `SWEEPR_RPC_FALLBACKS_BASE`.
* Keep `SWEEPR_EVM_BUILD_MODE=v4_fallback` available for rollback.

### Partner Profile

* Partner profile is active.
* API key is active.
* Public browser keys have allowed origins.
* Server keys are shared only through a secure channel.
* EVM payout wallet is correct.
* Partner fee share is approved.
* Daily quota matches launch expectations.
* Production backend rejects missing API keys on non-public routes.

### Contract Configuration

* Base V5 is deployed or selected.
* V5 owner is the expected Safe or operational owner.
* V5 fee signer matches the backend fee signer address.
* V5 router allowlist matches backend router allowlist.
* V5 Permit2 address is canonical.
* V4 fallback remains callable.

### Checks

Run these from the backend repository:

```bash theme={"dark"}
npm run partner:v2:check
npm run partner:v2:contract-check
npm run partner:v2:router-drift
```

Expected result:

* Base is ready for V5 builds.
* Router checks pass.
* Fee signer check passes.
* Any missing non-Base V5 contracts are expected until those networks are launched.

## Partner Integration Checklist

* Install `@sweepr/sdk`.
* Use `version: 'v2'` for Base Partner V2.
* Build sweeps with the Sweepr-issued API key.
* Never send partner id, payout wallet, or fee share in the request body.
* Verify fee authorization before requesting a Permit2 signature.
* Check or request Permit2 token approval when needed.
* Ask the user to sign Permit2 typed data.
* Send the V5 sweep transaction.
* Call confirm with the submitted transaction hash.
* Poll status until `completed`, `failed`, or `expired`.

## Smoke Test

Before launch, run a real Base smoke test:

1. Use a funded Base wallet with one small ERC-20 input token.
2. Build a V2 sweep.
3. Verify fee authorization in the SDK.
4. Approve Permit2 if needed.
5. Sign Permit2.
6. Send the V5 transaction.
7. Confirm the sweep with Sweepr.
8. Confirm status returns `completed`.
9. Compare the displayed fee split with the V5 event values.

## Rollback

If Partner V2 needs to be paused, Sweepr can switch the backend build mode:

```txt theme={"dark"}
SWEEPR_EVM_BUILD_MODE=v4_fallback
```

Partners should continue calling the same high-level SDK methods where possible. Sweepr will coordinate any integration-specific changes if the fallback path is required.

## Not In First Production Scope

These are intentionally not required for the first Partner V2 launch:

* partner self-service dashboard
* partner-generated API keys
* webhooks
* Solana trustless split
* cross-chain sweeps
* broad full-chain indexing
* all-network V5 rollout