Bitcoin Forum
May 28, 2024, 06:00:09 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 [2]  All
  Print  
Author Topic: Ethereum flawed?  (Read 2930 times)
Boussac
Legendary
*
Offline Offline

Activity: 1220
Merit: 1015


e-ducat.fr


View Profile WWW
March 01, 2014, 09:26:56 PM
 #21

How does Ethereum prevent DoS attacks by rogue contractors (contracts taking advantage of Turing-completeness) ?

Fog Fence
Member
**
Offline Offline

Activity: 105
Merit: 10


View Profile
March 10, 2015, 11:04:35 AM
 #22

Interesting. I'm on the fence.
odolvlobo
Legendary
*
Offline Offline

Activity: 4326
Merit: 3241



View Profile
March 10, 2015, 04:17:40 PM
 #23

How does Ethereum prevent DoS attacks by rogue contractors (contracts taking advantage of Turing-completeness) ?

The contract states the amount the sender will pay the miner per cycle and a limit on the number of cycles.

Join an anti-signature campaign: Click ignore on the members of signature campaigns.
PGP Fingerprint: 6B6BC26599EC24EF7E29A405EAF050539D0B2925 Signing address: 13GAVJo8YaAuenj6keiEykwxWUZ7jMoSLt
btchris
Hero Member
*****
Offline Offline

Activity: 672
Merit: 504

a.k.a. gurnec on GitHub


View Profile WWW
March 10, 2015, 04:42:01 PM
 #24

How does Ethereum prevent DoS attacks by rogue contractors (contracts taking advantage of Turing-completeness) ?

The contract states the amount the sender will pay the miner per cycle and a limit on the number of cycles.

I don't know anything about Ethereum, so this is probably a stupid question, but what prevents the contract writer from offering a huge per-cycle fee and then providing an algorithm which (non-trivially) doesn't halt?
odolvlobo
Legendary
*
Offline Offline

Activity: 4326
Merit: 3241



View Profile
March 10, 2015, 05:40:22 PM
 #25

How does Ethereum prevent DoS attacks by rogue contractors (contracts taking advantage of Turing-completeness) ?

The contract states the amount the sender will pay the miner per cycle and a limit on the number of cycles.

I don't know anything about Ethereum, so this is probably a stupid question, but what prevents the contract writer from offering a huge per-cycle fee and then providing an algorithm which (non-trivially) doesn't halt?

The cycles are not free. The success of such an attack is limited by the amount of money the attacker has.

Join an anti-signature campaign: Click ignore on the members of signature campaigns.
PGP Fingerprint: 6B6BC26599EC24EF7E29A405EAF050539D0B2925 Signing address: 13GAVJo8YaAuenj6keiEykwxWUZ7jMoSLt
btchris
Hero Member
*****
Offline Offline

Activity: 672
Merit: 504

a.k.a. gurnec on GitHub


View Profile WWW
March 10, 2015, 05:51:37 PM
 #26

I don't know anything about Ethereum, so this is probably a stupid question, but what prevents the contract writer from offering a huge per-cycle fee and then providing an algorithm which (non-trivially) doesn't halt?

The cycles are not free. The success of such an attack is limited by the amount of money the attacker has.

I was assuming that the attacker need only pay for completed machines (that reach a halted state).

If everyone pays for cycles regardless of whether or not the machines halt, could a malicious miner DOS the network by operating machines up until their final state minus one cycle?

(I'm asking dumb questions that are all answered in the referenced paper, just like ppl do when they don't read the original Satoshi paper, aren't I? Be honest....)
Pages: « 1 [2]  All
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!