LOCKS & STREAMS.
THE CONTRACT RULES.
ERC-20 time locks, NFT custody, vesting and Merkle distribution on Elysium Testnet. Public records are available without signing in.
Contracts
Chain 99801. Gas is paid in HYPE. Testnet tokens have no real value.
| Contract | Configured address | Interface |
|---|---|---|
| RaqioVault | Not configured | Download ABI |
| RaqioAirdrop | Not configured | Download ABI |
| RaqioScore | Not configured | Download ABI |
A configured address is not an audit or deployment-verification claim. Verify the source and network before using a public deployment.
Create and manage a lock
- Open Lock, choose ERC-20 tokens, ERC-20 LP tokens, an ERC-721 position, or a vesting stream.
- Connect a wallet on Elysium Testnet. Enter the token contract, amount and beneficiary. Token amounts use on-chain decimals.
- Approve only the deposit or NFT being locked. Confirm the vault transaction. The lock ID is read from the confirmed event.
- Share the public proof. Only the beneficiary can claim; only the owner can manage permitted settings.
Time locks can be extended, never shortened. Adding ERC-20 tokens and transferring ownership are supported. Transferring ownership does not change the beneficiary. Vesting schedules cannot be extended. Cancelable streams pay vested tokens to the beneficiary and return unvested tokens to the current owner.
Supported tokens and fees
Use standard, non-rebasing ERC-20 tokens. Deposits that arrive short because of transfer taxes are rejected. A token with custom transfer restrictions may still revert. Generic ERC-721 custody is supported, including token ID zero; it does not verify pool identity or provide Uniswap V4 hook or fee-collection support.
The deployment script sets a 25bps fee on ERC-20 lock and stream creation. The fee is capped at 50bps and changes wait 48 hours. NFT custody and additions to an existing time lock do not charge that creation fee. Forms read the actual current fee from the vault.
Airdrop allocation proofs
Create an allocation JSON array with an address and an integer amount string for each recipient. Amounts are base units, not display units. The browser builds the root and a proof for every allocation. Download the proof manifest and distribute individual entries to recipients; only the root is stored on-chain.
Leaves use a double hash of ABI-encoded address and uint256 amount. Sibling hashes are sorted; odd tree nodes are promoted. Each wallet can claim once per campaign. With vesting enabled, the claim creates a vault stream owned by the campaign creator and payable to the claimant. The current vault fee is deducted from the gross allocation when that stream is created.
After expiry, the creator can recover only that campaign's remaining unclaimed deposit. It cannot use another campaign's balance. Stream cancellation is available only when enabled by the creator and preserves vested recipient entitlement.
Open airdrops ↗Reading the commitment score
The scorer reads the vault, rather than accepting a reporter's invented score. It combines locked supply, amount-weighted remaining duration, registered LP locks, active vesting and cancellation history. Only owner-registered ERC-20 LP relationships contribute LP points. NFT positions are excluded.
Scores are not security ratings. Token code, mint permissions, pool identity, price, off-vault positions and owner identity are not established by the number. Anyone can create a lock, so permissionless history can be influenced by third parties. A token with more than 256 vault records receives an explicit unavailable result until a scalable indexer/aggregation design is implemented.