Assignment

A2 — Issuance spec and distribution plan (Week 2)

In one sentence. Freeze the house rules on paper before anyone opens Remix. A3 will type this table into the wizard.

Stuck? Handbook → Sessions 3 and 5 (cap, mint, pause). Names must match A1, or add a one-line changelog.

You will not

• deploy anything yet
• invent Solidity
• leave the math so airdrop + pool + treasury exceeds the cap

Part 1 — Rules (1 page)

Write in issuance language, not slogans.

1. Minter — Which role/address may create new units? What happens if that key is lost?
2. Cap — The numeric max supply (or write “uncapped” and why that is dangerous in a class system).
3. Burn / redeem — Who may destroy units, and does that retire a real-world promise?
4. Pause — Who may freeze transfers, under what written trigger?
5. Decimals — 18 (usual on Ethereum) or 0 (like paper vouchers). One sentence on why.

Part 2 — Who gets coins (1 page)

Choose one primary method: airdrop (gift), sale for CLASSUSD, or earn. Then fill:

• Amount each roster address gets at the start
• Amount reserved for the TEAM / CLASSUSD pool (you need this in A4)
• Amount reserved for the team treasury
• May any classmate hold and transfer? Any restriction?
• Why this method is not the same financial object as the two you rejected (gift ≠ ticket booth ≠ paycheck)

Parameter table (required — copy this)

Check before you submit: airdrop × number of people + pool + treasury ≤ cap.