My Zomi (0)
Connecting a wallet is the whole of signing in. There is no account and nothing is stored by this site: what your address holds on Robinhood Chain is what this page shows, and it forgets all of it when you close the tab.
Holdings
read from the contractConnect a wallet to read what it holds. The list is worked out from the contract's own log rather than from an index, so it is what the chain says and nothing else. With no collection deployed there is nothing to hold yet, and this view says that rather than showing an empty grid as if it were a result.
Coupons
claimable after the termA coupon is claimed one token at a time, or several in one transaction, and it pays in ETH to whoever holds the token at that moment. Pending moves with the token when it is transferred, so buying a Zomi buys whatever it has already earned. Nothing can be claimed from a bond before its term is up, which is why a card stays locked until the date it names.
Shielded payout route
validated here, hashed on chainA Sapling address starts zs1 and a unified address starts u1. Both carry a checksum, and this checks it, so one mistyped character is caught here instead of later. Checking shows the hash; setting the route on a Zomi is done from its own card above.
Setting a route writes only a keccak hash of the address to the contract. The address itself never goes on chain, and it never leaves the field it is typed into: this site has no server to send it to, and the transaction carries 32 bytes of hash and nothing else.
Coupons pay in ETH on Robinhood Chain today; the shielded ZEC route is next. Until that rail exists a route is a stored preference and an off chain settler would have to honour it, which is a trust assumption and is written down as one in the contract controls.