@CryptoGuideDev - smart contract dev news @CryptoGuide_Dev

Guides to writing smart contract code on the blockchain. Aimed at developers. (#solidity #evm #blockchainengineering) cryptoguide.dev Spain Joined August 2022

Tweets

148
Followers

143
Following

816
Likes

5

Laura Wendel @Lauramaywendel

2 years ago

The most effective software engineers I know always had a tendency to revert to writing "C" style code. Nothing seems to come close in terms of readability / maintainability.

210 500 5K 963K 754

Download Image

DopamineChaos @DopamineChaos

2 years ago

HOW TO BUY $OXBT BRC-20 token on Bitcoin. On @Apple iOS 👇 for beginners

103 344 1K 301K 879

Download Image

chrisdior.eth @chrisdior777

2 years ago

One beautiful trick that I have learned from @0xWeisss : 1/4 Isn't it annoying when you have to read the contracts in etherscan like that:

20 57 218 37K 173

Download Image

Anyone else not going to sleep tonight because Ben's $PSYOP token contract is adding an additional unnecessary ~2,000 gas to every single token transfer? Here's his contract: etherscan.io/address/0x3007… And here's a quick side by side of his function vs. a better one (simplified):

27 6 104 26K 11

Download Image

MevRefund @MevRefund

2 years ago

Timeline is flooded with auditoooors, and yet ...

24 9 246 50K 22

Download Image

cygaar @0xCygaar

2 years ago

Seeing a potential re-entrancy exploit with the @SteadyStackNFT contract. Looks like anyone on the goldlist can re-use their signatures to mint as many NFTs as they want. There's no supply check on this function so someone could mint out the remaining supply (limited by gas).

45 25 316 88K 51

Download Image

cygaar @0xCygaar

2 years ago

If anyone knows the people that run the @WaltsVault_NFT project, I have a list of improvements they should make to their smart contract. I don't normally do public audits before a mint, but the code is already live so why not 🫡

42 35 396 145K 71

Download Image

porter | ZKsync ∎ @portport255

2 years ago

My favorite ZK books: 1. The MoonMath Manual by @LeastAuthority 2. Proofs, Args, and ZK by @SuccinctJT 3. The Halo2 book by @Zcash

9 59 297 34K 303

Vlad B. (∎, ∆) @vladbochok1

2 years ago

1/12 I have found a bit of time to make the another disclosure of my finding, so here's the 2nd issue I've identified in the @OpenZeppelin library!

11 30 176 39K 77

Pop Punk @PopPunkOnChain

2 years ago

🪂 Sending Tokens Efficiently 🪂 The bull market is coming and gas prices are pumping. You shouldn’t be over paying for gas and spending more than you need to, costing yourself thousands of dollars. Here’s a tool that can you save you money when sending tokens in bulk. 1/16

13 21 118 24K 76

Download Image

Owen | Guardian @0xOwenThurm

3 years ago

28 ways to miss vulnerabilities in an audit 🧵

12 38 131 16K 115

@bytes032.xyz @bytes032

3 years ago

Allow me to unveil the enigmatic concept of read-only-reentrancy. Recently, a new exploit utilizing this vulnerability came to light, spurring me to dedicate the last 48 hours to curating an enlightening 🧵 for the benefit of the entire community to grasp its nuances.

23 90 384 65K 254

Andy Li @andyfeili

3 years ago

Want to find your first high severity issue on @code4rena to get +backstage role? This is one of the most common and easy to spot bug on c4. What is the problem here?

16 36 268 50K 180

Download Image

Intigriti @intigriti

3 years ago

Can you spot the vulnerability? 🔎 Show us how you'd get a victim to change their email! 👇 The best explanation gets a 25€ SWAG voucher!🎫

36 51 391 106K 80

Download Image

prady @prady_v

3 years ago

Let's talk about Panic vs Error. A 🧵 to create some Panic.

2 18 61 9K 41

Download Image

chrisdior.eth @chrisdior777

3 years ago

📝Tips for smart contract auditing approach✅ Part 1 of 3 posts: 1/ Read the project's docs, specs, and whitepaper to understand what the smart contracts are meant to do.