Signalite should separate technical integration from commercial attribution. The API and SDK make the user flow possible; partner revenue requires a clear attribution and settlement model.
Partner revenue sharing is not live until the referral or attribution system is explicitly implemented and published. Do not promise partner commissions from the current API alone.
Reference models
| Model | How it works | Signalite fit |
|---|
| Builder code | Integrator passes a code during deposit | Good for direct attribution if added to quote/build payloads |
| Offchain attribution | Track wallet, transaction, and time-weighted deposits | Good first partner-sandbox model |
| Fee wrapper | Deposits route through a wrapper that collects yield share | More complex, requires contract work |
| Onchain splitter | Fees are split by contract | Best transparency, highest implementation cost |
Proposed sandbox model
For early partners:
- Assign each partner a
partnerId.
- Allow partner apps to pass
partnerId in action quote metadata once implemented.
- Index deposits and wallet positions by partner attribution.
- Calculate time-weighted attributed TVL.
- Settle referral or performance-fee share offchain until onchain splitting is implemented.
Data required
| Data | Why |
|---|
| Partner ID | Attribution |
| User wallet | Position and lifecycle tracking |
| Deposit tx hash | Verifiable source event |
| Deposit amount | Revenue share base |
| Share balance over time | Time-weighted TVL |
| Fee accrual | Commission calculation |
Future API shape
const quote = await shlp.quoteDepositAction({
amount: parseUsdc("100"),
account: userAddress,
receiver: userAddress,
slippageBps: 50,
partnerId: "partner_mobile_app",
});
Partner docs rule
Until attribution is live, document this as a roadmap feature, not as a currently available SDK field.