Our goal has always been to be the go-to blockchain node platform across any chain and environment. Today, that includes the nodes you run on your own hardware. Running your own Ethereum infrastructure should be the basic right of every individual and household. Nodes should be easy. The catch? Self-hosting has always meant complexity. Manual setup, client updates, nodes falling out of sync, moni
In this second week of #100daysofsolana , i got got introduced with the concept of account . I learned it by contrasting with the database of web2 . However , i am aware that Solana's account model is not replacement for web2 database, rather it's solving a different problem: storing state in a system where no single entity has control, reads are public, and writes require cryptographic authoriz
If you’re coming from Web2, identity probably means a username and password. You sign up for a service, create credentials, and the platform stores your data. Whether it’s GitHub, your email, or a banking app, your identity exists because a company manages it. Solana works differently. On Solana, your identity starts with something called a keypair. This is made up of two things: a public key and
I'm doing the 100 Days of Solana challenge by MLH, and Week 2 just changed how I think about blockchain data entirely. Week 1 was about identity — generating keypairs, understanding wallets, getting devnet SOL. That part felt familiar, like setting up a dev environment. Week 2 was different. Week 2 was about reading the chain — and that's where the mental model shift actually happened. I expected
You don't own your Twitter username. The company does. If the platform shuts down tomorrow, that identity is gone — you can recreate it somewhere else, but it's not the same. Your followers, your history, your reputation — tied to a string that a corporation controls. This is a common but mostly ignored problem. And it applies to more than social media. Your GitHub account, your email, your develo
What I Did I used a simple JavaScript script and the @solana/kit library to programmatically generate a new keypair, saved the secret key to a local .json file, and then wrote a second script to extract that seed so I could manually import it into my Phantom wallet extension for devnet testing. The biggest shift from Web2 was realizing that my "identity" is just a cryptographic string of numbers
Introduction Implementing Rock-Paper-Scissors (RPS) on-chain is surprisingly tricky. The moment you choose "Rock" and send a transaction, your opponent can read your move from the public ledger. The game is over before it even starts. I tried implementing a commit-reveal pattern manually, but managing salts, preventing front-running, and ensuring fair judging logic... it quickly became a rabbit
Been spending the last ~10 days getting hands-on with Solana as part of a hackathon. Went in expecting things to feel completely different from what I’m used to. It wasn’t as far off as I thought. What I’ve Done So Far Generated a keypair + airdropped devnet SOL Created a wallet and checked balance programmatically Understood SOL vs lamports Connected a browser wallet Read on-chain data (accounts,