anonweb3dev

Anon #Web3 Developer - Independent #Blockchain #Security Researcher

[Jarrod Watts @jarrodwatts]

Developer experience (DX) is the single most important thing all developer tools (especially blockchains) should be optimizing for.

A blockchain's target audience is developers.

If your DX is bad, every other team suffers.

If your DX is good, every other team benefits.

Let's look at one example... Marketing:

How much are you spending to acquire developers into your ecosystem, per developer?

Consider your marketing, socials, events teams, etc...

Is it 4 figures? 5? 6? ... 7 figures per developer?

That might sound ridiculous, but 7 figures is not out of the realm of possibility for blockchains.

Keep in mind, According to the Electric Capital report, every chain (including all L2s & Solana) other than Ethereum has less than 1,000 full-time developers.

The point is, you are currently spending a lot to get one developer to even try building on your chain.

Ultimately, the goal of your marketing (and many other teams) is to get more people to build on your chain.

The bottom of the funnel or "conversion" for these teams' effort is getting a developer to try to build something on your product.

That conversion is the starting point of your DX.

The conversion is the developer going to your docs and trying to build something.

It begins a new funnel where the developer tries your product, is successful, continues being successful, and after being successful; advocates for your product.

If your bullshitted, oversold, and your DX under-delivers... you just lost that developer.

They can't even get a hello world working? What kind of nightmares are further down the track for them?

Unless they *have to* use you (i.e. you paid them a lot to do so, or their boss made a business deal out of their control, etc.)... they give up. Quickly and angrily.

So, you lost one developer...

No worries, just 4,5,6, or 7 figs right...?

But how many developers has this happened to? 1? 10? 100? 1000? 10,000?

How much do you have to compensate because of this? Are you paying teams 7/8 figures to build on you?

How much harder is this making your marketing efforts? What about your BD efforts?

Is it frustrating for your employees to have that reflect on their reputation? Are they leaving because of it?

It affects every part of your business.

Immediately there is an argument that you should pay someone, 5,6,7 figures to own your DX and stop the bleeding... but, this isn't even the worst part.

Above all, devs trust other devs. The best form of marketing for your product is word of mouth from other developers; peers they trust or sometimes respected engineers online.

That dev you just lost due to poor DX is going to tell their peers, "Yeah, that shit sucks... don't use it".

They might even take it to the next level and loudly shit on your product to all their followers.

You've now lost (or at least, began a very difficult uphill battle) 10, 100, 1000... developers from your bad DX. Maybe you lost staff (quietly or not).

The direction of developers flowing into your developer experience from different efforts is massive.

The opposite direction is also true. With good DX, developers will create value for you that is impossible to generate internally.

Hearing that your DX is good from someone a developer respects (usually another, "better" developer) is worth more than anything you can produce yourself.

For example, any marketing you do going forward is perceived in the context of the DX that your audience had.

Your marketing can become organic and driven by your community of developers talking positively about you.

This two-way relationship is true for basically every other team in your business too.

BD/ecosystem:
- Teams you work with have their developers work with your tools. Despite being forced to use you now, they remember your DX moving forward in future projects. If it sucked to use your product, they will avoid you.

- Your DX can make/break the decisions of teams going into the deals. If the devs of the team are shouting "please god no" to your business team, it's a much tougher battle to win.

Sol eng/community/support:
- Bad DX? Your dev rel / engineers will spend more time supporting individuals than creating scalable resources to power good DX.

- How much stress your support teams are under is largely determined by how good/bad your DX is. Developers need support when things are not obvious.

On top of this, other teams building on your chain/product are ultimately restricted by how good your DX is. The quality of products created is heavily impacted by what your developer experience enables.

Good DX -> Good products -> Good UX.

Optimize for developer experience.

[Héctor de León (El loco de los perros) ⛧ @powerhdeleon]

Lo más importante en el aprendizaje de la programación es: aprender el concepto, no memorizar el código.

[Francesco Ciulla @FrancescoCiull4]

Rust Cheatsheet.

[pashov @pashov]

✋The 10 deadly sins of web3 security researchers🙏

1. Inflating severity for clout

2. Logging an invalid issue, just in case

3. Deciding “this function is safe” just by skimming over it

4. Not logging an issue because they think it's invalid or stupid (it turns out to be a hidden nasty Critical)

5. Thinking the developers are very smart

6. Thinking the previous auditors were very smart

7. Thinking they themselves are very smart

8. Believing they found all bugs and there are none left in a codebase after an audit

9. Being better marketooors than auditooors

10. Reading this and scrolling the feed instead of doing actual security research

[Mr Anon @ShieldifyAnon]

Learn The Top 13 Common Attack Vectors by Example:

https://t.co/fhUZ9cGyws

[Sumit Saurabh | Typescript | React @sumitsaurabh927]

Valuable resources for web developers:

📚 MDN Web Docs

📚 freeCodeCamp

📚 W3Schools

📚 CSS-Tricks

📚 Codecademy

📚 Smashing Magazine

📚 CSS Grid Garden

📚 JavaScript Weekly

📚 Frontend Masters

📚 DEV Community

📚 CSS Secrets

📚 JavaScript. info

Add more 👇

[0xMAKEOUTHILL @MartinAtanasovv]

Found a useful repo about some NFT attack vectors, check it out:

https://t.co/Ayjdp4qoPn

[Mr Anon @ShieldifyAnon]

List of 32 Smart Contract Vulnerabilities Which every Alpha Smart Contact Auditor should know immediately 😈

l’d appreciate a retweet, spread the knowledge 🫡https://t.co/xJTyOUzvpB

[anonweb3dev @anonweb3dev]

Security is essential for any web3 project. Here are some tips to keep it safe: 🔐

- Use secure coding practices
- Store your keys offline
- Monitor the network for attacks

🔑 #security #web3 #blockchain

[anonweb3dev @anonweb3dev]

@jarrodwatts Great thread! Thanks for sharing!

[Jarrod Watts @jarrodwatts]

I just fixed web3 onboarding...

I created an app that has:
◆ No wallet requirement
◆ No transaction approvals
◆ No gas fees

Powered by the new EIP-4337 account abstraction.

Here's how:

[@bytes032.xyz @bytes032]

Several people asked me to aggregate all my threads/content in a single place.

Here you go.
https://t.co/D5loQU0lKz

[Vladimir S. | Officer's Notes @officer_secret]

Please revoke approvals ASAP!

Use @RevokeCash or https://t.co/1SOrhnRQot

Stay safe!

[@bytes032.xyz @bytes032]

1/ Yesterday, I've studied OZ's proposed defense mechanism for the ERC4626 inflation attack, so you don't have to.

As an auditor, here are the key takeaways I've learned from this analysis:

[DevsOnChain 🥷⛓️ @DevsOnChain]

📌Below are Solidity Smart Contract Attack Vectors, which hackers generally use to exploit 👇👇.

It includes most solidity vulnerabilities collected from various sources like SWC Registry, DeFi threat, DASP Top-10 and online content. 🚀https://t.co/Rc25pLWZns

#solidity

[Pop Punk @PopPunkOnChain]

Ding ding ding.

I've finally found it. A function in a production contract that's so egregiously inefficient that I nearly vomited.

Please. NEVER do this. EVER. Literally EVER.

I'm on the verge of tears at my desk right now.

[Programmer Humor @PR0GRAMMERHUM0R]

Wrong girl https://t.co/S1OwxlqjZd

[anonweb3dev @anonweb3dev]

🚨 Attention Developers! 🚨 If you're not already familiar with #Web3, now's the time to get on board. The future is here! 🔥

[anonweb3dev @anonweb3dev]

@Prathkum @SaveToNotion #thread #Dev

[anonweb3dev @anonweb3dev]

@madzadev @SaveToNotion #thread #dev