Skip to main content
This website uses essential cookies required for its operation. Course content and all third-party embedded materials are accessible only to registered users. To manage your consent preferences, please register and log in.
x
Completion requirements

Group Forum Discussion

Scenario:
"A community savings group uses a smart contract where members deposit monthly. The contract has a bug: the withdrawal function doesn't check if the requester is the actual owner – it only checks if the requester's address starts with '0x123'. By chance, an attacker's address matches. They drain 50% of the funds. The community discovers the bug immediately after."

Debate question:
"Should the 'code is law' outcome stand (attacker keeps funds), or should the community hard-fork the blockchain to revert the transaction?"

Requirements:

  • Initial post (150+ words): Your position with clear reasoning
  • One reply (100+ words): Engage with a different position

Guiding Questions:

📜 Immutability: Does reverting the transaction break the promise of blockchain?

🔥 The DAO precedent: Ethereum hard-forked to revert the $60M hack. Is this case similar or different?

⚖️ Intent vs. code: Was the community's intent clearly violated?

🛡️ Precedent: If you revert this, where do you draw the line? What about future "accidents"?

👥 Community governance: Who decides? A vote? A foundation? The developers?

💰 Practicality: Hard forks are disruptive and controversial. Is it worth it for 50% of funds?

Use at least 2 concepts from the lesson in your post.

There are no discussion topics yet in this forum
Credits …
NFT ❯
ⓘ Lab Description