Skip to main content

​
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 every enabled SWEEPR_V5_CONTRACT_<CHAIN> value, including SWEEPR_V5_CONTRACT_BASE.
  • Configure fallback RPCs for enabled EVM chains with SWEEPR_RPC_FALLBACKS_<CHAIN> or SWEEPR_RPC_FALLBACKS.
  • 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

  • V5 is deployed for every enabled EVM chain.
  • V5 owner is the expected Safe or operational owner on every enabled chain.
  • V5 fee signer matches the backend fee signer address on every enabled chain.
  • V5 router allowlist matches backend router allowlist on every enabled chain.
  • V5 Permit2 address is canonical on every enabled chain.
  • V4 fallback remains callable.

​
Checks

Run these from the backend repository:
Expected result:
  • Every enabled EVM chain is ready for V5 builds.
  • Router checks pass.
  • Fee signer check passes.
  • Missing V5 contracts indicate that the chain is not ready for Partner V2 builds.

​
Partner Integration Checklist

  • Install @sweepr/sdk.
  • Use version: 'v2' for EVM Partner V2.
  • Read /v2/status before enabling a chain in your UI.
  • 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 at least one real smoke test on each enabled EVM chain:
  1. Use a funded wallet on the target chain 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:
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
Last modified on July 5, 2026