Robinhood Chain

Token locks & vesting on one token — live locked / next unlock / 7d & 30d schedule (PRO+)

Every lock / vesting contract on one Robinhood Chain token with a live derived view: what is still locked right now (deposited − unlocked-so-far by the schedule), what unlocks next, the 7d / 30d unlock schedule and whether the locker can cancel — 'did the team lock, how much, until when'. summary covers the token-subject rows (counts by family / kind, distinct depositing wallets and locker contracts, locked / deposited raw + ui + usd + % of supply, unlocking_7d_* / unlocking_30d_*, nearest next_unlock, active_cancelable_by_sender); LP locks on the token's pools are listed under subject=lp and counted apart (lp_lock_count, lp_lock_active_count) because their amounts are pair / liquidity units. Rows are active-first, largest locked first. token.facts_resolved is false when decimals are unknown — every ui / usd / pct field is then null. Same create-only caveat as the feed (coverage.withdrawals_tracked: false): an unlocked-but-unclaimed balance counts as unlocked. Tier: PRO+.

get/rhc/tokens/{address}/locks

Request

  • Base URL: https://madeonsol.com/api/v1
  • URL: https://madeonsol.com/api/v1/rhc/tokens/{address}/locks
  • Auth: HTTP bearer

Path parameters

addressstring required

Query parameters

status'active' | 'completed'
familystring
subject'token' | 'lp' | 'all'
limitinteger

Rows returned; the summary always covers every row on the token (up to 5000).

Response

OK.

chain'robinhood'
token_addressstring
locksobject[]
coverageobject
metaobject

Changes

No recorded changes to this operation across all 1 revision of this API.