Skip to main content

​
Monaco Protocol SDK v1.0.2

This release ships PitPass TraderCodes — Monaco’s referral program — alongside the full tiered-fee system. Every user gets a unique referral code; rewards accrue from referred users’ trading activity up to three levels deep, funded from net protocol fees and instantly transferable into any trading balance.

​
Added

​
PitPass TraderCodes

Every Monaco wallet now has a unique TraderCode. Share it to earn a share of the net protocol fee generated by referred users’ trades — up to three levels deep. How rewards work: Rewards are computed on the realized net fee at fill time (taker fee minus maker rebate) and credited instantly to a per-user rewards bucket. The bucket is app-agnostic — rewards accumulate regardless of which Monaco application generated the trade. New endpoints:
  • REST / TypeScript SDK / gRPC — GET /api/v1/pitpass/codes/me — return the authenticated user’s TraderCode
  • REST / TypeScript SDK / gRPC — GET /api/v1/pitpass/codes/{code} — public lookup to validate a referral code at signup
  • REST / TypeScript SDK / gRPC — GET /api/v1/pitpass/rewards/balance — read accrued rewards across all reward tokens
  • REST / TypeScript SDK / gRPC — POST /api/v1/pitpass/rewards/transfer — move rewards into a trading balance (ledger-only, no gas, immediately tradeable)
Auth verify — new optional field: POST /api/v1/auth/verify now accepts an optional referralCode field. When a new user provides a valid code on first sign-in, a referral relationship is recorded atomically. Invalid codes and codes supplied for returning users are silently ignored and never block sign-in.

​
Tiered fees

Fee tiers are now applied per-user based on a 14-day rolling weighted volume (14d perp + 2.5 × 14d spot). Six tiers are available. Volumes are recomputed daily at 00:00 UTC. The current tier and the volume needed to reach the next tier are returned by GET /api/v1/fees/tier (added in v0.8.18).

​
Upgrade

The new pitpass namespace is additive. Auth verify gains one optional field (referralCode). All other existing endpoint shapes, field names, and authentication requirements are unchanged.