2022-01-26
1902
#blockchain
Frank Joseph
89467
Jan 26, 2022 â‹… 6 min read

Ethereum vs. Flow blockchain for NFT development

Frank Joseph I'm an innovative software engineer and technical writer passionate about the developer community. I'm interested in building applications that run on the internet.

Recent posts:

Leveraging React Server Components In Redwoodjs

Leveraging React Server Components in RedwoodJS

RedwoodJS announced support for server-side rendering and RSCs in its Bighorn release. Explore this feature for when it’s production-ready.

Stephan Miller
May 6, 2024 â‹… 9 min read
Exploring The Aha Stack: Astro, Htmx, Alpine — A Complete Tutorial With A Demo Project And Comparison To Other Stacks

Exploring the AHA stack: Tutorial, demo, and comparison

The AHA stack — Astro, htmx, and Alpine — is a solid web development stack for smaller apps that emphasize frontend speed and SEO.

Oyinkansola Awosan
May 3, 2024 â‹… 13 min read
Comparing Hattip Vs Express Js For Modern Application Development

Comparing Hattip vs. Express.js for modern app development

Explore what Hattip is, how it works, its benefits and key features, and the differences between Hattip and Express.js.

Antonello Zanini
May 2, 2024 â‹… 8 min read
Using React Shepherd To Build A Site Tour

Using React Shepherd to build a site tour

React Shepherd stands out as a site tour library due to its elegant UI and out-of-the-box, easy-to-use React Context implementation.

Onuorah Bonaventure
May 1, 2024 â‹… 14 min read
View all posts

2 Replies to "Ethereum vs. Flow blockchain for NFT development"

  1. Errors:

    1. “Anonymous: all participants on the blockchain are anonymous or identified by a pseudonym” Not true, some go as far as proving their identity using it
    2. “Security: All records on the blockchain are encrypted” Not true, they are all cleartext by default, encrypting on chain records is considered an incredibly poor security practice
    3. “All network participants have a record of every transaction” Not true at all, most just keep track of the state and use it as part of the transaction execution process but the tx themselves are not stored, in the case of Flow, most don’t even do that.
    4. “Immutability: Transactions on the blockchain network are irreversible and cannot be changed” not always true on the tx side, but also not true at all in the execution side as that is determined by the SmC
    5. “Timestamp: Every transaction is recorded with the time the transaction occurs” The transactions don’t hold timestamps, the blocks where they are organized do
    6. “Distributed: Every participant agrees to the validity of each record on the network” That’s not what distributed is, but also not always, IE: most modern Bitcoin transactions lead to different executions to different nodes, forks, consensus updates etc. And they don’t agree on validity, they agree on the rules to be followed.
    7. “Programmable: All blockchains are programmable. Ethereum use Solidity, Flow uses Cadence, and Bitcoin uses Bitcoin Script to build smart contracts” This is not true, Ethereum can use several languages, but also Bitcoin is not programmable, you can build off chain SmCs but not modify the state to add execution logic like Ethereum or Flow.
    8. “An NFT is a unique, irreplaceable, and non-interchangeable token” None of those are inherently true and there are examples of NFTs that don’t meet that criteria
    9. “NFTs are cryptographic assets with a unique identity on the blockchain” Only the most basic standard follows this
    10. “NFTs are a digital representation of real-world objects, like artwork or real estate” Not true, we can have digitally native assets

    IDK man, every 2 sentences there is incorrect stuff, even painting flow worse than it is, we need to strive to do better, you should get someone technologically competent to review before spreading misinformation like this

Leave a Reply