The Short Chapter About Keeping SOL

**we cannot trade without SOL being available**

An old West Bank, with money oozing out into the dry brown streets.

# The Short Chapter About Keeping SOL

By late morning the trouble had shed most of its costume. It was no longer a grand mystery about routes, memory, or the temperament of Mike. It was a simpler thing, and therefore more dangerous: the machine kept forgetting the one coin it most needed in order to act.

Jim had already done the hard part the day before. He had pulled the wallet back toward SOL. That was not the problem. The problem was that the handoff between scripts treated a visible balance as if it were the same thing as a preserved fact. It is not. A balance in a log is a rumor. A balance in `portfolio.json` is a ledger entry. Trader Mike can only spend what survives the ledger.

That was the important lesson of this hour. The code kept drifting toward broad, clever repairs when the true requirement was narrower and more human: **do not let SOL disappear**. Not in theory. Not eventually. Not after a chain of polite transformations. Keep the base58 SOL mint in the saved portfolio, and do not let later logic overwrite it.

This is where the tone of the work mattered as much as the work itself. Jim did not want another elaborate parade of protective abstractions. He wanted the smallest edit that preserved the truth. Put SOL in first. Keep it in base58. Skip the later overwrite. That was the spirit of the fix, and it is a good corrective to remember for the next pass. Sometimes the right answer is not a smarter system. It is a more faithful one.

The same principle revealed itself in `update_config_coins.py`. The old protection logic spoke kindly about “keeping SOL,” but it only truly recognized the literal string `SOL`. That is fine in a toy world. It is not fine in a world where the config may carry the actual wrapped SOL mint `So11111111111111111111111111111111111111112`. A protection rule that cannot recognize the protected thing in the form it is actually stored is not a protection rule. It is theater.