/explore
|
You are here 
|
mixbytes.io | ||
| | | | |
preethikasireddy.com
Here's something most new Web 3.0 developers have trouble understanding: when you ship code, it can't be patched and updated later. This is a big departure from the iterative development method that we all know and love - where we break development into smaller parts and build it up over many iterations. By adding features one-by-one, we can improve app functionality over time - all while growing a user base. In Web 3.0, this just can't be done. Blockchain changes everything - including the possibility for iterative development. |
|
| | | | | ||
| | | | |
quantstamp.com
Computer scientists say that a procedure is re-entrant if its execution can be interrupted in the middle, initiated over (re-entered), and both runs can complete without any errors in execution. In the context of Ethereum smart contracts, re-entrancy can lead to serious vulnerabilities. |
|
| | | | | ||
| | | | |
justinphu.dev
Exploring the differences between the approaches of implementing fungible tokens in Ethereum and Solana |
|
| | | | | ||
| | | | |
trendless.tech
Computer files don't often stay the same. They're updated with new information, new metadata, things are moved around, glitchy code is patched, updates roll out to handle changes from other software, databases get cleaned up, and so on. Naturally, across a distributed system (such as cloud synchronization), this can pose extremely complicated challenges. There are [...]Read More... from Blockchain: So What's Bitcoin, Anyway? |
|
| | | |||
