Learning Ethereum, Sui and Solana as a developer from Nepal

By Santosh Poudel · Published

Original illustration of connected blocks in a distributed ledger

I am learning about Ethereum, Sui, and Solana as part of my wider interest in software development. This is a learning journey, not a claim of professional blockchain experience or a list of completed deployments. I want to understand what each ecosystem is designed to do before deciding whether a blockchain is the right tool for a particular problem.

Start with the fundamentals

I am approaching blockchain by learning the basic ideas behind wallets, transactions, smart contracts, networks, and on-chain data. Understanding what users sign, what a transaction changes, and what information becomes public is more useful than starting with a list of tools.

A distributed ledger is not automatically the best place to store data. Public visibility, transaction fees, latency, and irreversible actions all affect how a product should be designed. I want to understand those trade-offs before choosing an implementation.

Compare ecosystems without assuming they are interchangeable

Ethereum, Sui, and Solana are separate ecosystems with different designs and developer experiences. I am learning how their documentation, programming models, tools, and networks differ rather than treating one tutorial as transferable to all three.

The comparison should start with a concrete requirement: what needs to be shared, who needs to verify it, and why an ordinary database or signed record would not be enough. A blockchain is only useful when its properties address a real need.

Build small experiments and record what I learn

My next step is to follow official beginner materials and make small, clearly labeled learning exercises. Before describing any exercise as complete, I will be able to link to its code and explain what it does, what network it uses, and what it does not demonstrate.

I am not presenting this article as a tutorial with tested deployment steps. It records my current learning direction; as I gain hands-on experience, I can publish separate guides with reproducible code and precise setup details.

When blockchain may not be the right choice

A shared ledger can make sense when independent participants need to consult a common record and no single operator should control the only copy. It may add unnecessary complexity when a conventional database already meets the trust, privacy, and performance requirements.

For content authenticity, a timestamp or provenance record does not prove that a claim is true or that a creator is trustworthy. My related writing on digital content provenance explains why records and evidence should be interpreted carefully.

A learning journey, not a credential claim

I am learning Ethereum, Sui, and Solana; I do not claim expertise or professional blockchain work. I will update this page when I have verified projects or practical lessons to share.

For my existing work, see the VerifiAI and DexBotX project pages, or follow my code and learning on GitHub.

Related articles