built, checked, still imperfect
Projects.
Four things that exist. Each one says what it is, how it works, and where it breaks — because a project page that only sells is a project page you cannot learn from.
- what it is
- A page that moves a small amount of SOL into a program account and lets you withdraw it to a fresh address, breaking the on-chain link between the two.
- how it works
- Your wallet signs a deposit into a program account you control with a secret note; the withdrawal is signed by a freshly generated key. The RPC is checked before anything is signed, and the page refuses to sign outside mainnet.
- where it breaks
- The note is the money. Lose the backup and the funds are gone — there is no support desk and no recovery. This is an experiment, not an audited wallet.
- what it is
- A label for any text or file: you paste it, you get the SHA-256, and you can hand that number to someone else as proof of what you had.
- how it works
- The digest is computed locally with the Web Crypto API. Nothing is uploaded, and no blockchain is involved — which is exactly the point worth learning.
- where it breaks
- A hash proves the content existed, not when it existed. Anyone can compute the same digest, and a timestamp would need a source outside this page.
- what it is
- The house newsletter: what broke, what held, and one concept explained properly, with the links to check it.
- how it works
- A subscription form writes to a mailing list; unsubscribing is a link in the email itself. No tracking pixel, no email open rate used to sell anything.
- where it breaks
- There is no editorial calendar. Editions arrive when something worth explaining exists — not on a schedule that gets padded to keep it going.
- what it is
- Each article, lab sheet and lesson is one Markdown file in a repository. Publishing is writing a file; reviewing is reading a diff.
- how it works
- A static build reads the files and generates the pages. The labs are client-side code, so the tools keep working with the network cut.
- where it breaks
- No comments, no accounts, no search. If you need to correct something, the newsletter is the only channel — the text can be fixed, but the conversation is one-way.
no client logo, no invented metric, no success story with a round number. the code is private; the behaviour of what runs in your browser is not.