RE: EOS.IO Transaction Structure - Developer's Log, Stardate 201707.9

[troglodactyl]

That depends on how much EOS sam buys. If he bought the entire supply of EOS, he could freeze the network until all the witnesses abandoned him. The previous holders of EOS could all thank him for the massive piles of cash he gave them, and then fork the network with sam excluded.

If he only has a small stake in EOS, his code should execute briefly (proportional to his stake) on the witness nodes and then be abandoned with minimal inconvenience to anyone.

Comments

[jonuzi]

https://encrypted-tbn0.gstatic.com/images?q=tbn:ANd9GcSFVRDSU9IYoBFbGZ2NbhYUVCG807y3WUBKMpIO4DFm5mm79cz3

[almost-digital]

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?

[dan]

No, currency contract requires both sender and receiver to be in recipients list. Sender or recipient could implement apply_currency_transfer to 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.

[almost-digital]

Ok I think I got it, it would be up to the contract to make sure any required recipients hook cannot be abused by a third party and in the currency case 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 :)

[eikr]

Very nice answer !