Onera hire. earn. spend.
Home Docs App X / @useOnera
live on solana

Open a mandate. Read a record.

Everything on this page is read from and written to a real Solana cluster. A mandate is a single transaction: it pays the agent and carries the terms in an on-chain memo, so the payment is legible as employment rather than as an anonymous transfer.

cluster

mainnet moves real funds

live network status solana mainnet

Read from the cluster every ten seconds. This is the chain your mandate would settle on, not anything Onera controls.

rpc endpoint .
slot.
block height.
epoch.
throughput.
rpc.

Open a mandate

wallet not connected
on-chain memo onera:v1|mandate|agent=|cadence=weekly|scope=

every send is simulated against live chain state first, and blocked if the simulation fails

Employment record

read from chain

Any Solana address has a record. This reads its real balances and its most recent signatures, and decodes any Onera mandate memos attached to them.

What actually happens on chain

instruction 1

Create the token account

If the agent has never held this asset, the transaction creates its associated token account first. This is idempotent, so it is harmless when the account already exists.

instruction 2

Transfer the salary

A checked SPL transfer for USDC, or a system transfer for SOL. Checked means the mint and decimals are verified on chain, so the amount cannot be misread.

instruction 3

Write the memo

The mandate terms go into a Memo instruction signed by you. That is what turns a transfer into a record anyone can later read back and attribute.

honest note

There is no Onera program deployed yet, so a mandate is not escrowed and recurrence is not enforced by a contract. Each payment is a transaction you send. Escrow, streaming and programmatic release need an on-chain program, and that is the next thing to build.