Preethi Kasireddy

Before investing time in learning how to program on ethereum, one should first assess the engineering feasibility of it's blockchain: https://medium.com/@preethikasireddy/how-does-ethereum-work-anyway-22d… Take a look at their github and how the overwhelming majority of users can't run a full node (If you can't run a full node, you rely on an intermediary, you are not decentralized). I'm not sure if the "marketing team behind a decentralized project" is still doing it but they used to be continuing to market ethereum as an immutable blockchain which is patently false due to their roll back of the DAO.

Checkout what https://twitter.com/iam_preethi is tweeting about these topics. Really liked her last article about Etherum: https://medium.com/@preethikasireddy/how-does-ethereum-work-anyway-22d…

I suggest your read this: https://medium.com/@preethikasireddy/how-does-ethereum-work-anyway-22d… Quote: But unless a node needs to execute every transaction or easily query historical data, there’s really no need to store the entire chain. This is where the concept of a light node comes in. Instead of downloading and storing the full chain and executing all of the transactions, light nodes download only the chain of headers, from the genesis block to the current head, without executing any transactions or retrieving any associated state. Because light nodes have access to block headers, which contain hashes of three tries, they can still easily generate and receive verifiable answers about transactions, events, balances, etc. The reason this works is because hashes in the Merkle tree propagate upward — if a malicious user attempts to swap a fake transaction into the bottom of a Merkle tree, this change will cause a change in the hash of the node above, which will change the hash of the node above that, and so on, until it eventually changes the root of the tree.