Tech Community @ BMSIT&M
Buildbeyondthe classroom
A community for developers, designers, researchers and innovators to learn, collaborate and build real-world impact.
Code, Connect, Create
A student-driven tech community at BMSIT&Mfor builders, creators and curious minds.
Built on the stacks
that matter.
Ethereum, Solana, Sui and the tooling around them — Solidity, Move, Rust, TypeScript, wallets and indexers. We learn the systems underneath, then build on whichever chain the idea needs.
LockKeyChain
From lock to ledger.
Three objects. One idea: trust you can check.
A lock opens for one code. A key belongs to whoever holds it. A chain is only as strong as every link. Put the three together and you have a blockchain — and that's what we learn to build.
It starts with a lock
01The lock · Hashing & cryptography
Sealed by math.
A lock that opens for one code — and nothing else.
A combination lock answers to exactly one code. A hash does the same for data: run a block through SHA-256 and out comes a fingerprint that changes completely if a single bit does. That seal is what makes a blockchain tamper-evident. We learn how the math holds up — and try to break our own code before anyone else can.
- Hash functions — SHA-256, Keccak-256
- Signatures, encryption and zero-knowledge proofs
- Every contract reviewed and tested before it ships
A lock is only as safe as its key
02The key · Wallets & private keys
Not your keys, not your coins.
A wallet doesn't hold money. It holds a key.
Your private key signs every transaction you make, and whoever holds it owns everything behind it. Most hacks don't break the cryptography — they steal the key. So we learn to guard it: seed phrases, hardware wallets, multisig, passkeys, and wallets that can recover without a single point of failure.
- Private keys, seed phrases and signing
- Hardware wallets, multisig and MPC
- Passkeys, account abstraction and social recovery
Every key signs a block on the chain
03The chain · Blockchain
Every link remembers.
Break one link, and every link after it breaks too.
Each block carries the hash of the block before it, so the whole history is chained end to end. Change one block and every block after it stops matching — nobody can quietly rewrite the past. We learn what keeps a chain honest: consensus, finality, and the bridges between chains.
- Blocks, Merkle trees and consensus
- Finality, forks and reorgs
- Bridges and cross-chain security
And every link is out in the open
Built in public
Transparent by default.
Scan NODE — there's nothing hidden inside.
On a blockchain anyone can read every block; that's where the trust comes from. We work the same way: every line we write is on a public repo, everything we build ships to a public testnet, and what we learn goes out in the open.
Engineering, not speculation — we never give trading or investment advice.