Skip to main content
Signalite’s partner integration assumes a constrained strategy and explicit operational readiness checks.

​
Asset movement model

At a high level, funds should move only through the supported vault and strategy paths:
  1. User USDC enters the sHLP vault.
  2. Keeper batches vault liquidity into the strategy.
  3. Strategy routes to HLP exposure.
  4. Withdrawals return liquidity to the vault.
  5. User claims or receives USDC from the vault.
The partner API should never ask users to sign transactions to arbitrary recipients.

​
Readiness as security control

/api/v1/health does more than report uptime. It must prove that:
  • The keeper heartbeat is fresh.
  • The keeper is not in dry-run mode.
  • The heartbeat matches the expected vault, strategy, NAV source, and chain.
  • The keeper address has expected roles.
  • The indexer and snapshots are fresh enough for the requested UI.

​
External audit status

The current partner docs are for sandbox integration and internal partner testing. External audit should happen after scope freeze and before broad TVL or public partner distribution.
Do not present these docs as an external audit completion signal.