A .NET Dinosaur in Web3. Day 8 — Reading & Writing — WishList Chain
The article discusses the author's experiences on Day 8 of exploring Web3 development. It highlights the differences between reading from and writing to the blockchain, emphasizing the complexities involved in user interactions and transaction confirmations. The author reflects on the challenges faced, including the need for careful address verification when sending transactions.
- ▪Reading from the blockchain is similar to calling a regular API, while writing involves user confirmations and network processing.
- ▪Building a UI for Web3 requires handling uncertainty and external events, making it more complex than traditional development.
- ▪The author experienced issues with transactions being sent to the wrong contract address, illustrating the importance of double-checking addresses.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3908355) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Alena Posted on May 21 • Originally published at Medium A .NET Dinosaur in Web3. Day 8 — Reading & Writing — WishList Chain #web3 #dotnet #beginners #ethereum A .NET Dinosaur in Web3 (8 Part Series) 1 A .NET Dinosaur in Web3. Day 1 - First Smart Contract 2 A .NET Dinosaur in Web3. Day 2 - Access Control ... 4 more parts... 3 A .NET Dinosaur in Web3. Day 3 - Voting, Sybil Attacks and Identity 4 A .NET Dinosaur in Web3.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
