Quick Buy is gone from the token sheet, and the AI reviewer got a rulebook
On 15 October one Rainbow developer merged two changes sixteen seconds apart. The first one will be noticed by anyone who opens a token sheet. The second will be seen by nobody: it is about how Rainbow reviews code.
One section less in the token sheet
Change #7882 is a deletion: ten files, one line added, three hundred and fifty-five removed.
- What is gone. The collapsible "Buy {token}" section with preset fiat amounts. It appeared in two places: right under the chart for tokens you don't own, and after Market Stats for the ones you do. The reason is stated plainly — it was barely used.
- What stays. The Buy and Sell buttons at the bottom of the sheet work as before and open Swaps. What disappeared is not the ability to buy, but the shortcut with amounts already filled in.
- An analytics property went with it. Only those preset buttons populated
quickBuyMetadata, and the change pulls it out along the whole path. The author says so without softening it: the charts tracking it will go to zero. That is more honest than leaving a field quietly sending nothing.
- And a helper function. A separate function rounded amounts to neat numbers — 1300 to 1500, 1800 to 2000. It worked for those buttons only and left with them.
A rulebook for the AI reviewer
Change #7883 is a single file of eighteen lines. For this to make sense: at Rainbow the code in a pull request is reviewed not only by a person but also by an AI program called cubic. It leaves comments, and the developer decides whether to fix or decline them.
- The count came first, the rules second. The author did the arithmetic: across the fifteen most recent pull requests cubic opened 73 discussions, about fifty led to fixes and about twenty-one were declined. Almost a third of the comments were empty.
- Overstated severity. Half of the top-severity findings were wrong — guesses about backend behaviour and about failures the interface cannot reach. Top severity now requires a concrete, reachable path, and a guess is filed as a question.
- Scope creep. Demands to also handle what the ticket explicitly excludes. A separate instructions file already forbade this, and it did not help.
- Clashes with repository conventions. Four of them written down plainly: interface strings go into the English file only, the project has no harness for a certain kind of test, and so on.
- What was left alone. Comments about the quality of the tests themselves: a test that cannot catch the regression, a mock that misleads. In the author's words — "mostly valid".
He designed the verification to be just as measurable: rerun the reviewer on an older pull request and compare whether the declined findings dropped out and the accepted ones remained.
Is this in the app
The Quick Buy removal is not, yet: the latest released version is 2.0.46 from 8 October, and the change was merged on the 15th. Which version it will appear in, Rainbow does not announce in advance. The second change will never reach the app at all — that settings file lives only in the repository.
What is changing in the wallet's code — at rnbw.wiki/pulse
$RNBW #RNBW