cryptocurrency

2921 readers

1 users here now

The largest cryptocurrency community on the Fediverse!

Lemmy community dedicated to cryptocurrency news, technicals, education, memes and so more!

💬 Chat on Community Improvements and Development

Community Knowledge Base:

Be nice, have fun.

Community rules:

No Spam
No ads
No aggressive coin promotion or attacks on others
No ICOs / IEOs / STOs / token (pre)sales / scam schemes promotion
No trading/buying crypto discussions
No promotion of trading groups, courses, signal groups, or other trade groups
No pumping and shilling
No casinos, giveaways, faucets, begging
No price speculation posts
No trolling

General lemmy.ml instance rules applicable here too.

Ugly brother of this community: bωockchain

For a community devoted to cryptography itself, visit c/cryptography

founded 6 years ago

MODERATORS

tracyspcy@lemmy.ml

mlsuyt@lemmy.ml

Challenge: Can you identify what is wrong with this simple Solidity guessing game contract that makes it easy to cheat? (lemmy.ml)

submitted 2 years ago by tracyspcy@lemmy.ml to c/crypto@lemmy.ml

3 comments fedilink hide all child comments

top 3 comments

sorted by: hot top controversial new old

[–] tracyspcy@lemmy.ml 1 points 2 years ago

BTW @cypherpunks@lemmy.ml was right. Anyone can view the contract deployment transaction and see the value of secretNumber that was passed as an argument to the constructor.

[–] Lixen@lemmy.world 1 points 2 years ago (1 children)

For those that want to have an actual go at it: when deploying it with hardhat for example, you can pass in Math.floor(Math.random()*1000) as the constructor argument and then see if you can derive the number on the first guess.

[–] tracyspcy@lemmy.ml 1 points 2 years ago

The formula will return a specific result of uint256 type which will be used in constructor on deployment, right? 😉