Web3 wingB05
Blockchain development since 2024. Members deploy smart contracts to a test network, and the next class tries to break them.
When a transaction is final
You sign the transaction on your own machine with your private key. Nothing has been sent yet.
It waits in the mempool, a public queue that anyone can see. Others can pay more to go ahead of you.
It is included in a block. That is one confirmation, but it is one block producer's view, not yet agreed by the network.
A competing block wins this slot. Your block is dropped, the transaction goes back to the queue, and the confirmations drop to zero.
It is included again two slots later. Nothing was lost, but anyone who acted on the first confirmation acted too early.
Enough of the network has confirmed it that reversing it would cost more than it is worth. Only now is it final.
Events
Best known for
24–30hours
The wing's main hackathon: a day and a night, in teams of up to four. There are two tracks: blockchain, for decentralised apps and smart contracts, and ML, for data-driven apps. It is open to first-years, and for most of them it is the first thing they build against a deadline.
12hours
Twelve hours, teams of three, and a trail of clues where each one leads to the next. It is about speed, not polish. Most trails ended with a technology nobody had used before that morning.
1day
A one-day sprint in pairs, set up as a trail where each clue leads to a new challenge. By the end of the day you have worked with a stack you did not know that morning.
Files
No class files yet.
Class log
Team
2 coordinators · 3 senior members · 3 members
