5 points: Contract compiles without errors in Remix and deploys successfully. Constructor sets name, symbol, decimals, and totalSupply correctly. Initial balance assigned to deployer.

3 points: Contract compiles with warnings but deploys. Minor issues with constructor parameters (e.g., hardcoded values instead of parameters).

1 point: Contract compiles but does not deploy, or deploys with incorrect initial state.

0 points: Contract does not compile.

6 points: Function correctly:

• Checks sender has sufficient balance using require()
• Deducts amount from sender's balance
• Adds amount to recipient's balance
• Returns true on success
• Emits Transfer event

4-5 points: Transfer works but missing one element (e.g., no return value, or missing event emission).

2-3 points: Transfer partially works but has logic errors (e.g., no balance check, or balance not updated correctly).

0-1 points: Function missing or completely incorrect.

4 points: Function correctly sets the allowance mapping for the spender and emits an Approval event. Returns true.

2-3 points: Approve sets allowance but missing event or return value.

0-1 points: Function missing or does not update allowance correctly.

6 points: Function correctly:

• Checks sender has sufficient balance
• Checks caller has sufficient allowance
• Deducts from sender's balance, adds to recipient
• Decreases the allowance by the transferred amount
• Emits Transfer event

4-5 points: TransferFrom works but missing one check or the allowance is not decreased after transfer.

2-3 points: Partial implementation -- checks balance but not allowance, or does not decrease allowance.

0-1 points: Function missing or completely incorrect.

4 points: Both Transfer and Approval events are properly declared and emitted in the correct functions with correct parameters.

2-3 points: Events declared but not emitted in all required locations, or parameters are incorrect.

0-1 points: Events not declared or never emitted.

9-10 points: Chosen feature is fully implemented and works correctly:

• Burn: Reduces both sender's balance and totalSupply. Uses require() for balance check. Emits event.
• Mint: Increases recipient's balance and totalSupply. Restricted to owner only. Emits event.
• Pause: Boolean flag checked in transfer/transferFrom. Only owner can toggle. Emits event.

6-8 points: Feature mostly works but has minor issues (e.g., burn doesn't reduce totalSupply, or mint has no access control).

3-5 points: Feature partially implemented. Function exists but has logic errors or does not compile.

1-2 points: Feature attempted but non-functional.

0 points: No custom feature attempted.

3 points: Where appropriate, feature uses onlyOwner modifier or require(msg.sender == owner) to restrict access. Owner is set in constructor.

1-2 points: Access control attempted but incomplete (e.g., owner variable declared but not checked in function).

0 points: No access control where it is needed (e.g., anyone can mint tokens).

Note: For burn (which any holder can call on their own tokens), full credit is given if no access control is used, since none is required.

2 points: Student demonstrates the feature working in Remix -- shows before and after state (e.g., totalSupply before and after burn).

1 point: Feature is shown but not fully demonstrated (e.g., claims it works but does not show state changes).

0 points: No demonstration of custom feature.

5 points: Clearly explains:

• What the token does (name, symbol, supply)
• How the custom feature works at a code level
• Why the feature is useful in real-world tokens
• All group members contribute to the explanation

3-4 points: Explanation is mostly clear but lacks code-level detail or real-world connection.

1-2 points: Vague or surface-level explanation. Only one group member speaks.

0 points: No presentation or incomprehensible explanation.

3 points: Shows a live Remix interaction or screenshots proving the contract works. Demonstrates at least one transaction (transfer or custom feature).

1-2 points: Shows Remix but does not execute a transaction, or only shows the code without deployment.

0 points: No visual demonstration.

2 points: Articulates why they chose their feature, what they learned, and what was challenging. Shows genuine reflection.

1 point: Brief or generic reflection ("it was interesting").

0 points: No reflection provided.

Per Additional Feature (+5 points each, max +10):

• Feature compiles and deploys: +1
• Feature logic is correct: +2
• Feature has appropriate access control: +1
• Feature is demonstrated working: +1

Note: Partial credit available for partially correct bonus features. Students who attempt all three features with minor bugs should receive more credit than students who attempt none.