Lock API and events

Locks are public. Every endpoint here is unauthenticated and CORS-open, because a lock is only worth making if a stranger can verify it.

Endpoints

Filters

• token — locks holding one ERC-20.
• wallet with role=depositor|beneficiary|any.
• status=locked|claimable|claimed|all.
• limit (max 200) and offset.

Status is computed, not stored

locked, claimable and claimed are derived at read time from the unlock timestamp and the clock. Nothing flips a stored column when a lock matures, so there is no window in which a matured lock still reports as locked. Treat unlockTime as the authority and compute your own status if you cache.

Amounts

amount is a decimal string in the token's base units, and decimals is supplied when known. Both are strings because a 256-bit integer does not survive JSON numbers. symbol, name and decimals are null for tokens Arcanium did not launch — the locker accepts any ERC-20 and we only know the metadata of our own.

Reading the contract directly

Nothing here requires our API. The locker at 0x0aB1fbD6c01f4908f509746393DE25849aE2a9E7 exposes lockCount(), getLock(id), isClaimable(id), timeRemaining(id) and totalLocked(token). Ids start at 1. Our own pages fall back to these when the indexer is behind, and so should yours.

Events

Both carry indexed fields for the three questions worth asking.

LockCreated also carries the depositor, the amount actually received, the unlock time and the creation time, unindexed.