Answers

• Can a token only go up? — A design question with a negative answer, and what the answer leaves you.
• How to tell whether a team can still change the contract — What to look for, in what order, and what each answer actually means.
• What “backed” means, and how to check it yourself — The difference between backing and a promise of backing, in four questions.
• How to prove a document was not rewritten later — Checksums and timestamps, and why a date on a PDF proves nothing.
• Writing the protocol twice — The bug class that no test suite catches, and the cheapest way to find it.
• How to read a token’s supply — Circulating, total, fully diluted — three numbers that are routinely confused, and what each one actually tells you.
• Is a contract really immutable? — A claim that can be checked in a few minutes, and the four places where it usually turns out to be untrue.

Each page answers the question first and names this project last. If a page ever reads the other way round, it is written badly and we want to know.