tkoen93
commented
5 years ago Tried to reproduce this (on testnet) to add some logs.
[2019-07-04 19:42:28.469438] [0x00007f3837f0d700] [info] Smart: enqueue payable( = 0.001, bundle = <empty>)
[2019-07-04 19:42:28.469563] [0x00007f3837f0d700] [debug] Smart: {984041.*} is waiting from #984041
[2019-07-04 19:42:28.469580] [0x00007f3837f0d700] [debug] Smart: set running status to {984041.*} containing 1 jobs
[2019-07-04 19:42:28.469596] [0x00007f3837f0d700] [debug] Smart: lock contract AJBsqEoev9phzmrpfPVsVALbLVhJ1FCimByFZbUetcL3
[2019-07-04 19:42:28.469613] [0x00007f3837f0d700] [debug] Smart: {984041.*} is running from #984041
[...]
[2019-07-04 19:42:30.342409] [0x00007f3837f0d700] [info] Smart: {984041.0} is out of fee, cancel the whole queue item
[2019-07-04 19:42:30.342421] [0x00007f3837f0d700] [debug] Smart: {984041.*} is finished on #984042
[...]
[2019-07-04 19:42:31.609749] [0x00007f3837f0d700] [debug] Smart: {984041.*} is finished on #984043
[2019-07-04 19:42:31.609773] [0x00007f3837f0d700] [error] Smart: {0.4294967295} smart contract result packet must contain new state transaction
[2019-07-04 19:42:31.609787] [0x00007f3837f0d700] [debug] Smart: {984041*.} is splitted onto 0 completed + 1 rejected + 0 restart calls
[2019-07-04 19:42:31.609800] [0x00007f3837f0d700] [info] Smart: ====================== SMART-ROUND {0.4294967295} END =====================
[2019-07-04 19:42:31.609813] [0x00007f3837f0d700] [debug] The smartConsensus for {0.65535} is not active
[2019-07-04 19:42:31.616029] [0x00007f3837f0d700] [debug] Node: 1 rejected contract(s) received
[2019-07-04 19:42:31.616089] [0x00007f3837f0d700] [debug] Smart: get reject contract(s) signal
[2019-07-04 19:42:31.616134] [0x00007f3837f0d700] [debug] Smart: 1 contract(s) are rejected
[2019-07-04 19:42:31.719373] [0x00007f3837f0d700] [debug] Node: 1 rejected contract(s) received
[2019-07-04 19:42:31.719451] [0x00007f3837f0d700] [debug] Smart: get reject contract(s) signal
[2019-07-04 19:42:31.719464] [0x00007f3837f0d700] [debug] Smart: 1 contract(s) are rejected
[2019-07-04 19:42:31.731421] [0x00007f3837f0d700] [debug] Node: 1 rejected contract(s) received
[2019-07-04 19:42:31.731501] [0x00007f3837f0d700] [debug] Smart: get reject contract(s) signal
[2019-07-04 19:42:31.731515] [0x00007f3837f0d700] [debug] Smart: 1 contract(s) are rejected
[2019-07-04 19:42:31.749650] [0x00007f3837f0d700] [debug] Node: 1 rejected contract(s) received
[2019-07-04 19:42:31.749725] [0x00007f3837f0d700] [debug] Smart: get reject contract(s) signal
[2019-07-04 19:42:31.749741] [0x00007f3837f0d700] [debug] Smart: 1 contract(s) are rejected
[2019-07-04 19:42:31.763488] [0x00007f3837f0d700] [debug] Node: 1 rejected contract(s) received
[2019-07-04 19:42:31.763573] [0x00007f3837f0d700] [debug] Smart: get reject contract(s) signal
[2019-07-04 19:42:31.763585] [0x00007f3837f0d700] [debug] Smart: 1 contract(s) are rejected
[2019-07-04 19:42:31.865804] [0x00007f3837f0d700] [debug] Node: 1 rejected contract(s) received
[2019-07-04 19:42:31.865876] [0x00007f3837f0d700] [debug] Smart: get reject contract(s) signal
[2019-07-04 19:42:31.865891] [0x00007f3837f0d700] [debug] Smart: 1 contract(s) are rejectedDid not manage to reproduce paralyze the work of absolutely any smart contract in the network. Executing another contract worked fine without any issues, within seconds from the attempt of stopping all contracts.
PresidentNavalny
send on this smart contract 1 cs. in response, the smart contract sends 397 transactions to the smart contract application. as a result, this game smart contract will not respond to anyone until such time as these 397 transactions are rejected.
Describe the bug There is a way to paralyze the work of absolutely any smart contract in the network. Smart contract stops responding to requests of any user (whether it is a smart contract of the game application or any other, it does not matter). If we take the example of gambling application, the player will bet by sending a smart contract Credits coins, but the smart contract will not respond to him, moreover, the sent coins will be in limbo. Smart contract will not be able to get these coins and get back their coins to the user will also fail (coins hang in the air)
To Reproduce Сreate a transaction. enter the address of any smart contract, in the amount field, enter any value 0-0.000...1 cs, then enter in the commission 0.0005 cs and click send transaction. smart contract will not be able to accept these coins, because we have indicated too little сommission for the transfer. at this time, no one will be able to use the application, it simply will not respond to any user until the sending of coins with insufficient commission is canceled(this time varies depending on the speed of creating new blocks, from 1.5 minutes to 4 or more) so you can block the operation of all smart contracts in the network this procedure can be done as many times as you want, even with all smart contracts on the network at the same time during the whole day. no one will be able to use any smart contract in the Credits network all this time. you can permanently block the operation of any smart contract. according to my calculations with this method to block 1 smart contract of the popular application in the Credits network for the whole day, the attacker will need only $0.72) why $0.72? transactions with insufficient commission are rejected within 1.5 minutes and this is the fastest option, when the speed of creating new blocks is about 2 blocks per second. (if the block creation speed is slower, the transaction will be rejected longer). take as a basis of 2 minutes. Provided that the commission in the cs network will be at $0.001, the attacker will need only $0.03 to block the operation of the smart contract for one hour and $0.72 to block for 24 hours In the same way, you can paralyze the transaction of any token in the network. sent to the smart contract of token 0-0.000...1cs, set a commission of 0.0005 cs and then the transaction of this token, in respect of which we have committed this action will be impossible. all transactions with this token will be in the pending status until the Credits coin transaction with insufficient commission is rejected. If desired, as I said, you can permanently paralyze the transfer of all tokens and the operation of all applications in the Credits network. all you need to do is write a bot(or do it all manually), which is every 1.5-2 minutes will send credits coins to smart contracts with insufficient commission. the cost of such an attack on 1 smart contract per day will be only $0.72.