Uncodemy Delhi NCR Campus Blockchain Course Details — Inside

Solidity Basics — what you actually write:
"By the end of this module you will have
written and deployed:

- A storage contract with read/write
- A token contract with transfers and
  approvals
- A simple voting contract with access
  control

Each one is deployed to a testnet, not
just compiled. You verify the source on
the explorer so anyone can read it.

What the trainer checks:
- Naming and readability
- Gas choices (storage vs memory)
- Events for off-chain tracking
- Whether your tests actually cover the
  edge cases"

Security — why it is a separate module:
"Most blockchain losses are not exotic.
They are the same few bugs repeated:
- Reentrancy (the DAO hack pattern)
- Integer overflow (pre-0.8 Solidity)
- Unprotected admin functions
- tx.origin used for auth

What you do in this module:
- Reproduce each bug in a local test
- Write the fix
- Write a test that would have caught it

What the trainer checks:
- Can you explain the attack path?
- Does your fix hold under a test?
- Do you understand why the pattern is
  dangerous, not just how to copy the fix?

That understanding is what interviews test."

Voting dApp — what you build:
"A smart contract that lets an admin
create a proposal, and registered voters
cast one vote each. The contract prevents
double voting and emits events so the
frontend can show live results.

The frontend:
- Connects to MetaMask
- Reads the contract state
- Sends vote transactions
- Shows results as they update

What you can show in an interview:
- The verified contract on the explorer
- The live dApp URL
- A test suite that covers double voting
  and unauthorised access

That is a portfolio piece."

Escrow Contract — what you build:
"A contract that holds funds until two
parties agree, with a dispute path.

What makes it a real project:
- State machine (created → funded →
  delivered → released / disputed)
- Access control for each transition
- Events for every state change
- Tests for every path, including the
  ones that should fail

Why interviews like it:
- It has real money at stake
- It has edge cases (disputes, timeouts)
- It invites questions: 'What if the
  buyer disappears? What if the seller
  never delivers?'

That conversation is the point."

What it includes:
- Portfolio review before you apply
- Resume rebuilt around projects
- Mock interviews with written feedback
- Introductions to hiring partners
- Interview scheduling support

What you should ask:
- How many students finished the last
  batch?
- How many are working in blockchain or
  web3 roles?
- Can I speak to one alumnus?

Any serious placement team answers these
without hesitation."

What it does not include:
- A guaranteed job
- A guaranteed salary
- A guarantee that you will finish
- A guarantee that you will pass the
  interviews

Why it matters:
Placement support makes you hireable. It
does not hire you. The projects and the
interview performance are still yours.

Be sceptical of '100% placement' — the
honest version is:
'We support you until you are hired; the
last batch had 22 students, 14 are
working in web3 roles.'

That is a real number. Ask for it."