You're about to run forge script --broadcast. The command needs a private key. The options that come to mind first all share the same problem: paste it into the terminal and it ends up in .bash_history or .zsh_history. Put it in .env and it's one accidental git add away from the repo. Hardcode it in the deploy script and it's in version history the moment the file is committed. These aren't theoretical risks — they're how keys get exposed.

You're about to run forge script --broadcast. The command needs a private key. The options that come to mind first all share the same problem: paste it into the terminal and it ends up in .bash_history or .zsh_history. Put it in .env and it's one accidental git add away from the repo. Hardcode it in the deploy script and it's in version history the moment the file is committed. These aren't theoretical risks — they're how keys get exposed.

Designing a scoring system after the build is convenient. The dimensions settle around what you happened to encounter; the weights drift toward what turned out to matter. The score feels right because the rubric was shaped around the result. This one was fixed before Week 1 started.

Designing a scoring system after the build is convenient. The dimensions settle around what you happened to encounter; the weights drift toward what turned out to matter. The score feels right because the rubric was shaped around the result. This one was fixed before Week 1 started.

The app deployed cleanly. I ran the function. Nothing happened. I stared at the terminal for a moment, then at the Anvil output. The contract was there — address confirmed, bytecode matching, tests passing 14/14. I had called sendSupport. Nothing moved.

The app deployed cleanly. I ran the function. Nothing happened. I stared at the terminal for a moment, then at the Anvil output. The contract was there — address confirmed, bytecode matching, tests passing 14/14. I had called sendSupport. Nothing moved.

The decision that forced everything else was the Solana week. Once I knew there would be a non-EVM chain mid-series — a week using Rust and Anchor instead of Solidity and Foundry — a dozen downstream decisions snapped into place. What frontend framework to use. How to handle wallet connectors. Which hosting platform made sense for weekly chain swaps. Almost nothing about the technical stack was chosen independently of the chain lineup.

The decision that forced everything else was the Solana week. Once I knew there would be a non-EVM chain mid-series — a week using Rust and Anchor instead of Solidity and Foundry — a dozen downstream decisions snapped into place. What frontend framework to use. How to handle wallet connectors. Which hosting platform made sense for weekly chain swaps. Almost nothing about the technical stack was chosen independently of the chain lineup.