21–30 of 35 posts
UC Berkeley DeFi Mooc https://youtube.com/channel/UCB67PxhB5LAWEbI4etQS7aw
Smart contract security auditing https://secureum.substack.com/archive
Tim Roughgarden, Foundations of Blockchains https://youtube.com/playlist?list=PLEGCF-WLh2RLOHv_xUGLqRts_...
Typing from phone but here are some resources that really helped me: Blockchain Fundamentals: https://github.com/ethereumbook/ethereumbook Practical Solidity: https://solidity-by-example.org/ Crypto Zombies is an amazing beginner step by step course to build a blockchain game: https://cryptozombies.io/ Finally, ethernaut is a series of increasingly difficult security challenges to learn about risks, exploits, info se…
Solid advice! and to add, If you are looking to learn solidity and get a job the best option is metana.io - they will teach solidity comprehensively, help you build your dapp portfolio and also make sure you land a job in web3 development as well.
No decimals, no patches or point upgrades to deployed smart contracts (for the most part anyway), constructor event only gets called once during deploy, code implicitly has "owners" with specific execution rights, etc.
But this is what I have found to be the strangest part:
On most worldwide public blockchains, your programs are deployed to run on servers supplied by other people. They expect to be compensated for supplying this CPU power. Your programs are charged gas and mining fees when they execute. This is usually paid for by the person initiating the transaction with your program.
This produces two weird side effects:
1) Your development environment (e.g. hardhat, ganache) will "charge" you the same fees, even when you are running entirely on your own laptop. Many times when you hit the deploy button, your own laptop will puke because your dev wallet doesn't have enough coin in it to pay the compile fees. ON YOUR OWN MACHINE!
2) When optimizing your code, you no longer refactor to improve speed or code maintainability, but mainly to reduce the fees charged when executing. Solidity even has a "price sheet" of fees for operations like addition, subtraction or allocating memory. This new way of thinking can seem strange to experienced devs because of all the easy fixes you plainly see that have to be left in the code base. Counter-intuitive.
Two things really helped me. First was the series "Ethereum from scratch" by Matt Thomas on YouTube. Second was gitcoin.co. I would pick up random bounties on there, often slightly beyond my skill level so that I would learn faster. You quickly build relevant skills and just as importantly you are building working relationships with companies and peers whilst getting paid to write open source software. To start out I…
Earlier quoted context omitted.
As is machine learning, cryptography, learning Cantonese and snorting cocaine. Is it special in any way though?
You do know that most faang employees work on methods to maximize ad revenue right, because last I checked google or Facebook weren't in the business of trying to cure cancer? What about Lockheed-martin or other companies making missiles that kill civilians for their oil? Blockchain is just a technology, one shouldn't have such strong feelings against it just because one is a contrarian and lots of idiots are shoutin…
I am definitely a cryptocurrency contrarian, so I was going to stay out of this thread - it wouldn't help OP to have people questioning his fairly straight-forward request.
But I don't think there is such a thing as "just a technology". Technology comes out of people's desires, and you can't disentangle it from the context it's created in. You can argue that blockchain is just an append-only database, but that ignores all sorts of externalities its adoption is causing.
Make sure you are paid in actual dollars or euros.
From a traditional Dev perspective, blockchain programming can seem really weird. No decimals, no patches or point upgrades to deployed smart contracts (for the most part anyway), constructor event only gets called once during deploy, code implicitly has "owners" with specific execution rights, etc. But this is what I have found to be the strangest part: On most worldwide public blockchains, your programs are deploye…
That makes me think of the game Shenzhen I/O: each component cost money, each executed line of code draw power, you have to optimize your circuit to match your assigned power and price goals.
Two things really helped me. First was the series "Ethereum from scratch" by Matt Thomas on YouTube. Second was gitcoin.co. I would pick up random bounties on there, often slightly beyond my skill level so that I would learn faster. You quickly build relevant skills and just as importantly you are building working relationships with companies and peers whilst getting paid to write open source software. To start out I…
Are you working in the blockchain space now? If yes, can you share how your experience is like? Type of projects, pay, opportunities etc
Typing from phone but here are some resources that really helped me: Blockchain Fundamentals: https://github.com/ethereumbook/ethereumbook Practical Solidity: https://solidity-by-example.org/ Crypto Zombies is an amazing beginner step by step course to build a blockchain game: https://cryptozombies.io/ Finally, ethernaut is a series of increasingly difficult security challenges to learn about risks, exploits, info se…
Like I think one thing it has in there, for example, is when you push an item onto an array it returns that item, so they have you initialize a variable to that push. The very next version of Solidity changed push so it's a void return, so you can't do that outside of the Crypto Zombies tutorials.
Most of the changes are small enough to not be a big deal, just keep in mind that some things you're being taught are probably not the way things are done now.
Best practices have changed a lot since Crypto Zombies too, especially if you want to support new ideas like Omnichain or save gas using contracts like ERC-721A.