You are viewing a single comment's thread from:
RE: EOS.IO Transaction Structure - Developer's Log, Stardate 201707.9
I was thinking more along the lines of that he could block any transfers involving him, but I reread that part and it seems the sender could just exclude him from the recipients list and still have the transfer go through?
No,
currencycontract requires both sender and receiver to be inrecipientslist. Sender or recipient could implementapply_currency_transferto auto reject every transfer.An exchange would only block transfers that exceed user's balance with exchange contract, meanwhile other contracts may block all incoming transfers that they do not expect.
Ok I think I got it, it would be up to the contract to make sure any required
recipientshook cannot be abused by a third party and in thecurrencycase it's not a problem if either of the parties would like to stop the transaction from happening.That's really powerful! I can't wait to try this stuff out on the testnet :)