Build · 4 of 4
Examples worth reading
Reading order that matches the stack: single contracts first, token patterns second, multi-actor apps last. "Last push" comes from the daily status data.
| Example | Layer | What it demonstrates | Last push |
|---|---|---|---|
| Silverscript test examples | Silverscript | Small single-purpose contracts — the shortest real code in the ecosystem | 2026-09-09 |
| KCC20 book | Silverscript / KCC-20 | The token patterns: how covenant-native tokens are actually built | 2026-09-09 |
| Argent: tickets | Argent | Actor ownership and state transitions — issue and transfer a ticket | 2026-09-10 |
| Argent: stones & toy_chess | Argent | Coordinated multi-actor games; actor enums | 2026-09-10 |
| Argent: ICC patterns | Argent | Closed and open inter-covenant communication — a KCC-20 asset with a minter | 2026-09-10 |
| Argent playground | Argent | Client-side usage of built artifacts | — |
Curation policy: official repositories only, verified to exist on 2026-09-10. Community projects may join this table with clear labelling once the site's review process for them is set.
That's the build path.
Toolchain → first covenant → testnet → the examples. When something here goes stale, the status board usually shows it first — and the site repo takes corrections.