A door for Solana has appeared in Rainbow's code

On 5 October at 23:18 UTC a twenty-three-line change landed in the main branch. By size, a trifle. By meaning, the largest thing we have covered.

What was actually done (PR #7865)

Two switches for Solana were put in place:

• SOLANA — an experimental flag in developer settings, off by default
• solana_enabled — a remote flag in the server-side config, false by default

Plus a hook that combines them: either one is enough. The comment in the code says it outright — in production Solana is gated by the remote flag, and the experimental one is a local override for developers.

Why it matters

Rainbow has been an EVM wallet from the start: Ethereum, Base, Arbitrum, Optimism and the rest. They all share an address format and a virtual machine, so adding one more such network is routine work.

Solana is built on entirely different principles: different addresses, different keys, a different virtual machine. This is not a twenty-fifth network on the list — it is a step outside the family the wallet was designed for.

What this code does NOT do yet

There is not a single line of actual Solana work here — no keys, no transaction signing, no requests to its network. A directory src/features/solana/ was created, and it holds one file: the switch. This is groundwork for future work, not the work itself.

One detail that says more than the rest

There are two flags, and the second is remote. That means they intend to turn Solana on from the server, without an app update. That is what you do when a feature is being readied for real users and you want to roll it out gradually.

For contrast: the side drawer from our last piece is gated by a local flag only — developers alone can see it. The remote kind we have met before, at Rainbow Cash: cash_enabled and cash_balance_enabled. Now solana_enabled stands beside them.

An honest caveat. This is preparation, not an announcement. Experimental branches at Rainbow do not always survive to release, and no timeline can be promised from three files of code. Exactly one thing is certain: the door is in the code, and it opens from the server.

What's happening in the wallet's development: rnbw.wiki/pulse

These entries go out in the channel @RNBWwiki.