Empties the token-bound account of any RH Machine you own, without this site.
reads from — · verify this page
Machines are found by reading the transfer log for Machines sent to your address, then confirming each one is still yours. If the endpoint refuses that query, type the ids instead.
Or work on token-bound accounts directly, whatever token they belong to. Anything you can execute on, you can empty; anything you cannot will fail the simulation before it costs you a fee.
Contracts are discovered from the block explorer, then every balance is read again from the chain — the explorer is asked what to look for and is never trusted for a number. Anything it misses, paste here.
Nothing on chain can say which token ids an address holds, so the explorer is the only way to find them — and every one it names is checked against the chain before it appears here.
Nothing below is a claim about this page. It is this page examining itself in front of you, and you can check every answer by reading the source.
Compare these with the values published for the release you meant to be running. If they differ, this is not that file — stop and get a fresh copy.
Reads go here, and you can point them anywhere. Writes go through your wallet, which uses whatever endpoint it is configured with — so changing this changes what you are shown, never what you sign. The block explorer is contacted for one thing only: the list of contracts to look at.
Every withdrawal is one transaction per machine, sent to that machine's own account, calling: execute(address to, uint256 value, bytes data, uint8 operation) with data set to transfer(YOUR ADDRESS, the whole balance). ETH is the same call with value set and empty data. Deploying a missing account calls createAccount(tokenId) on the Machines contract, which anyone may call for any Machine and which moves nothing. The recipient is always the wallet you connected with. There is no field for a different one, which the scan above checks rather than asserts.