The short answers.

No. They need an account on a platform we can resolve, which today means GitHub. The wallet is created for them when you send, and they find out it exists whenever you tell them.

They sign in with the same account. That is the entire claim: the wallet was bound to that account before it existed, so proving the account is theirs proves the wallet is. Nothing moves on-chain, and there is no gas to pay.

Nothing happens, forever. The tokens sit at their address. There is no expiry, no clawback, and no way for us to take them back. If they sign in five years from now it is still there.

No. Wallets are created through Privy, which splits the key so no single party ever holds a whole one and releases control to the person once they prove the account is theirs. We cannot move, freeze or spend what is in them.

No, and you are never asked to sign anything. You get a deposit address and a QR code, and you send from whatever wallet you already use. The cost of that choice, stated plainly: we never learn who paid, so the ledger records a send, not a sender.

28 Robinhood Stock Tokens on Robinhood Chain. Every address in the registry was checked against the contract itself, because a token with the right ticker at the wrong address is not the real one.

An ERC-20 token whose value tracks a real share the issuer holds against it. It follows the price; it does not carry voting rights or a direct claim on the company. What matters for this app is whether transfers are gated: an issuer that only lets wallets it has KYC’d hold the token would make this impossible, because a wallet made for a handle nobody has claimed could never be on that list. Robinhood’s Stock Tokens are not gated that way, which is what makes sending one to a handle work.

Nothing. The wallet is bound to the platform’s permanent numeric user id, never to the handle string. Renaming, selling or squatting a username moves no shares, which is the single most important decision in this app.

GitHub and X. Creating a wallet for someone needs their platform’s immutable numeric user id, and those are the two we can look up: GitHub publishes it, and X answers for it too. Discord, Telegram, Twitch and the rest want a bot inside a shared server or a paid tier, so they stay greyed out until that is wired up. Each is one resolver function away.

In two places, and that is deliberate. A wallet is bound to one account on one platform, so signing in with GitHub shows what was sent to your GitHub handle and signing in with X shows what was sent to your X handle. Sign out and back in with the other one to see the rest.