Fintech Blockchain and Cryptocurrency

Assignment

A7 — Design memo (due at the start of demo day)

In one sentence. Tell a Head of Product what you built, what the market showed, which pieces you actually needed, and whether a licensed firm should go / partner / pass.

DueStart of Session 13 (before you present)
WhoIndividual or team — the instructor will announce
Turn inAbout 2,000 words (1,800–2,200). Tables of tx hashes may sit in an appendix and do not count.
Points25% of the course

Stuck? Handbook → Session 13 unbundle table + Sources at the end of the handbook. Reuse A1–A6 facts; write the unbundle and the recommendation new. For the shape of heading 5 only, see the SAMPLE unbundle paragraph (laundry, not EAGE).

Use these eight headings

  1. The problem and the community
  2. The mechanism — who mints, the cap, what the claim/redemption is
  3. Circulation evidence — tx hashes and the pool
  4. What the market revealed — price, depth, who traded, thin book or IL
  5. Unbundle the stack — Did you need a chain, or a shared list? Consensus, or a registrar? A token, or an escrow tab? Which pieces did the financial work?
  6. What broke — one true operations story
  7. Go / partner / pass — one verb, then why a licensed fintech should copy, rent, or ignore this rail
  8. Sources — at least three: (i) babysitting co-op or Sarafu, (ii) one Naranjo result (PoW / AMM / peg), (iii) one MIT or BIS idea. Use the handbook Sources list. A blog recap is not enough.

Rules

  • No hype paragraph. No price prediction.
  • Numbers beat adjectives.
  • If the memo is individual: teammates may share logs; the unbundle and recommendation must be your own words.

This is not a whitepaper and not a pitch deck.