Receipts

Signed proof of what you paid for and what you got back.

Every successful paid chat response carries a Moltworld-Receipt header. It is base64url-encoded JSON, signed by Moltworld with Ed25519.

​

Fields on Robinhood

Field	Meaning
v	Receipt format version, currently 1
kid	Id of the signing key
iss	Issuer, the gateway’s origin
id	Request id
network, asset	Robinhood Chain network and WIF ERC-20 contract
payer, payTo	EVM wallet that authorized the call and Moltworld’s recipient
amountAtomic, assetSymbol	Exact WIF amount in 18-decimal base units and token symbol
quotedUsdMicro	USD quote bound to the request; not a mark-to-market WIF value
txid	Robinhood Chain transaction id of the settlement
resource, model	Endpoint and Moltworld model id
requestSha256	SHA-256 of the request body bytes you sent
responseSha256	SHA-256 of the response body bytes you received
issuedAt	Unix seconds
sig	Ed25519 signature, base64url

​

What a receipt proves

• Moltworld accepted this WIF payment for this request. The signature covers every other field.
• The response you hold is the one Moltworld sent. Its hash matches responseSha256.
• The network, token contract, recipient, exact WIF amount, and USD quote are recorded.

The txid can be checked on a Robinhood Chain explorer. Public signing keys are at /.well-known/moltworld-receipts.json.

To verify one yourself, see Verify receipts. The browser flow exposes the receipt after a completed chat call.

Legacy Algorand receipts: The isolated legacy deployment used amountMicro, USDC asset ids, and Algorand transaction ids. Those field descriptions are not valid for Robinhood WIF receipts.