1. What happens to your coins during a hard fork?
✅ You suddenly hold coins on both chains

2. What hidden danger can appear when a blockchain forks?
✅ Replay attacks, where a transaction on one chain can be copied on the other

3. Which methods can provide replay protection?
✅ Unique chain IDs, special signature rules, or different transaction formats

4. What should you always check when a fork occurs?
✅ Whether the new chain has replay protection and if your wallet is updated

5. Why might replay protection not always be present?
✅ Because some forks happen in a rush or under controversial circumstances

6. What's a big risk for users who ignore wallet updates during a fork?
✅ They might be exposed to replay attacks without knowing it

7. What’s the basic idea of a replay attack?
✅ A transaction you make on Chain A can be copied onto Chain B without permission

8. Why are replay attacks considered dangerous?
✅ They can drain funds from chains you never even touched

9. In the replay attack example, what happens if you send 1 coin on Chain A?
✅ The same transaction can be replayed on Chain B, draining your funds

10. What tool do developers add to stop replay attacks?
✅ Replay protection

11. What's the main lesson about forks and replay attacks?
✅ Treat forks as opportunities, but don't let your guard down—without protection, your “bonus” coins could become a trap

12. Why are transactions vulnerable right after a fork?
✅ Because both chains share the same history up to the split

1. 093101
2. 455142
3. 581912
4. 322792
5. 129837
6. 912367
7. 128931
8. 981237
9. 192371
10. 981273
11. 761239