Docs

You should not need someone's address to send them an on-chain asset. Assetsend turns identities people already have — an X handle, a GitHub username, a Twitch channel, a Google account, an email address — into destinations, and the recipient does not need a wallet before you send.

Every identity maps to a subject string: x:john, github:torvalds, email:john@example.com. That string is the whole addressing layer. A real on-chain wallet is derived from it, and the asset is transferred there with an ordinary ERC-20 transfer — no contract sits in the path.

No platform API is ever called to resolve a handle, which is why sending to someone who has never heard of Assetsend costs nothing and works immediately.

The recipient signs in with the actual provider — OAuth, or a signed link for email. Assetsend then mints a short-lived token whose subject is the same string the wallet was derived from, and the wallet is released to them. They can move the assets anywhere, or leave them.

Assetsend never sees a password, and cannot move assets out of a reserved wallet itself.

This is the one real weakness of routing on handles, so it is worth stating plainly. Handles get renamed, abandoned and resold. Without a guard, whoever holds a handle today could claim everything ever sent to it.

The first successful claim records the provider's immutable account id against that identity, and every claim after must match it. Assets already delivered stay with the account that held the handle at the time.

22 assets are sendable today on Robinhood Chain — tokenized equities, two ETFs, gold and silver, and a stablecoin. Every contract address, decimal count and symbol was read from live chain state on September 6, 2026, not transcribed from documentation. The registry publishes all of them.

Not every tokenized asset can be freely sent. Permissioned instruments — a treasury product whose transfer agent keeps an allowlist, for instance — are refused up front with the reason, rather than broadcasting a transfer the token contract would revert.

A refundable, expiring escrow contract is written and compiles: EIP-712 authorizations, access control, reentrancy protection, and support for ERC-20, ERC-721 and ERC-1155. It is unaudited and not deployed, so the live product uses direct delivery only. Direct delivery is one-way — a sender cannot recover an asset from a handle that never claims it.

The activity feed reads directly from chain logs. Robinhood Chain produces a block roughly every tenth of a second and the public RPC refuses queries matching more than ten thousand logs, so the feed covers a bounded recent window and says which window it got. Deeper history needs an indexer.

Claiming requires that provider's sign-in to be configured on this deployment. The claim page states which providers are available rather than offering a button that cannot complete.