feat: add --tokens flag to list deployment-specific tokens by hardyjosh · Pull Request #2549 · rainlanguage/raindex

hardyjosh · 2026-04-14T16:53:32Z

Motivation

Non-interactive strategy-builder users need the valid token addresses for a deployment to populate --select-token KEY=<address> flags. The webapp resolves this dynamically by reading the registry's token-list; CLI users currently have no equivalent.

Inlining the full token list in --describe output was considered and rejected: a registry can have hundreds of tokens and the list is typically only needed for the one deployment the caller is working with.

Solution

Add a --tokens flag that scopes to a single strategy + deployment and emits a markdown table of the tokens the registry has registered for that deployment.

raindex strategy-builder --tokens \
  --registry <url> --strategy <key> --deployment <key>

Output:

# Available tokens — `fixed-limit` / `base`

14 tokens. Use any address as the value of a `--select-token KEY=<address>` flag.

| Symbol | Name | Address | Decimals |
|--------|------|---------|----------|
| `wtIAU` | Wrapped iShares Gold Trust ST0x | `0x1E46...` | 18 |
...

Any ERC20 address is accepted for --select-token; the list is a curated convenience subset. --describe links to this command so agents fetch scoped lists on demand.

Checks

made this PR as small as possible
unit-tested any new functionality
linked any relevant issues or PRs
included screenshots (if this involves a front-end change)

hardyjosh · 2026-04-14T16:53:53Z

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

feat: template fallback operator ${expr || 'default'} #2551 : 2 dependent PRs (#2548 , #2552 )
feat: add --tokens flag to list deployment-specific tokens #2549 👈 (View in Graphite)
feat: add interactive mode to strategy-builder CLI #2546
feat: add strategy-builder CLI subcommand #2544
Consolidate JS API gui module into common crate and rename GUI to OrderBuilder #2479
main

How to use the Graphite Merge Queue

Add the label Raindex-queue to this PR to add it to the merge queue.

You must have a Graphite account in order to use the merge queue. Sign up using this link.

_{An organization admin has enabled the Graphite Merge Queue in this repository.} _{Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.}

This stack of pull requests is managed by Graphite. Learn more about stacking.

coderabbitai · 2026-04-14T16:56:39Z

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 75644f24-e533-4340-b85f-5ff4b03033ea

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests
Commit unit tests in branch list-tokens

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

hardyjosh · 2026-04-15T20:30:28Z

@coderabbitai review

coderabbitai · 2026-04-15T20:30:34Z

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

hardyjosh · 2026-04-15T21:37:27Z

@coderabbitai review

coderabbitai · 2026-04-15T21:37:33Z

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

hardyjosh · 2026-05-11T09:38:12Z

Merge activity

May 11, 9:38 AM UTC: A user started a stack merge that includes this pull request via Graphite.
May 11, 9:39 AM UTC: Graphite couldn't merge this pull request because a downstack PR Consolidate JS API gui module into common crate and rename GUI to OrderBuilder #2479 failed to merge.
May 11, 10:02 AM UTC: hardyjosh added this pull request to the Graphite merge queue.
May 11, 2:09 PM UTC: The Graphite merge queue removed this pull request due to downstack failures on PR #2544.
May 11, 2:09 PM UTC: The Graphite merge queue removed this pull request due to downstack failures on PR #2544.

## Motivation The Raindex orderbook protocol has a rich GUI builder flow in the webapp for configuring and deploying strategies. There is currently no way to do the same from a terminal or from a non-interactive agent — the webapp is the only entry point. That forces anyone automating a deployment (CI, scripts, AI agents) to either drive the browser or hand-roll the calldata. ## Solution Add a `strategy-builder` subcommand to the raindex CLI that generates deployment calldata from a remote registry strategy. ``` raindex strategy-builder \ --registry <url> \ --strategy <key> \ --deployment <key> \ --owner <0x-address> \ [--select-token KEY=ADDRESS ...] \ [--set-field BINDING=VALUE ...] \ [--set-deposit TOKEN=AMOUNT ...] ``` Outputs one `<address>:<calldata>` line per transaction on stdout — approvals first, then the deployment multicall, then optional metaboard meta emission. Each line is one signable transaction. Implementation reuses `RaindexOrderBuilder` from the common crate (same object the webapp drives) and `DotrainRegistry` from the js_api crate, so the CLI and webapp use identical resolution semantics. Follow-up PRs in this stack add `--interactive` (#2546), `--tokens` (#2549), the template-fallback operator (#2551), and `--describe` (#2548). ## Checks - [x] made this PR as small as possible - [x] unit-tested any new functionality - [x] linked any relevant issues or PRs - [ ] included screenshots (if this involves a front-end change)  ## Summary by CodeRabbit * **New Features** * Added a new `strategy-builder` command that generates deployment calldata from registry strategies with configurable field bindings, token selections, and deposit amounts. * **Improvements** * Token logo URIs are now optional, improving compatibility with token data sources.

## Motivation Non-interactive `strategy-builder` users need the valid token addresses for a deployment to populate `--select-token KEY=<address>` flags. The webapp resolves this dynamically by reading the registry's token-list; CLI users currently have no equivalent. Inlining the full token list in `--describe` output was considered and rejected: a registry can have hundreds of tokens and the list is typically only needed for the one deployment the caller is working with. ## Solution Add a `--tokens` flag that scopes to a single strategy + deployment and emits a markdown table of the tokens the registry has registered for that deployment. ``` raindex strategy-builder --tokens \ --registry <url> --strategy <key> --deployment <key> ``` Output: ``` # Available tokens — `fixed-limit` / `base` 14 tokens. Use any address as the value of a `--select-token KEY=<address>` flag. | Symbol | Name | Address | Decimals | |--------|------|---------|----------| | `wtIAU` | Wrapped iShares Gold Trust ST0x | `0x1E46...` | 18 | ... ``` Any ERC20 address is accepted for `--select-token`; the list is a curated convenience subset. `--describe` links to this command so agents fetch scoped lists on demand. ## Checks - [x] made this PR as small as possible - [x] unit-tested any new functionality - [x] linked any relevant issues or PRs - [ ] included screenshots (if this involves a front-end change)

## Motivation The Raindex orderbook protocol has a rich GUI builder flow in the webapp for configuring and deploying strategies. There is currently no way to do the same from a terminal or from a non-interactive agent — the webapp is the only entry point. That forces anyone automating a deployment (CI, scripts, AI agents) to either drive the browser or hand-roll the calldata. ## Solution Add a `strategy-builder` subcommand to the raindex CLI that generates deployment calldata from a remote registry strategy. ``` raindex strategy-builder \ --registry <url> \ --strategy <key> \ --deployment <key> \ --owner <0x-address> \ [--select-token KEY=ADDRESS ...] \ [--set-field BINDING=VALUE ...] \ [--set-deposit TOKEN=AMOUNT ...] ``` Outputs one `<address>:<calldata>` line per transaction on stdout — approvals first, then the deployment multicall, then optional metaboard meta emission. Each line is one signable transaction. Implementation reuses `RaindexOrderBuilder` from the common crate (same object the webapp drives) and `DotrainRegistry` from the js_api crate, so the CLI and webapp use identical resolution semantics. Follow-up PRs in this stack add `--interactive` (#2546), `--tokens` (#2549), the template-fallback operator (#2551), and `--describe` (#2548). ## Checks - [x] made this PR as small as possible - [x] unit-tested any new functionality - [x] linked any relevant issues or PRs - [ ] included screenshots (if this involves a front-end change)  ## Summary by CodeRabbit * **New Features** * Added a new `strategy-builder` command that generates deployment calldata from registry strategies with configurable field bindings, token selections, and deposit amounts. * **Improvements** * Token logo URIs are now optional, improving compatibility with token data sources.

## Motivation Non-interactive `strategy-builder` users need the valid token addresses for a deployment to populate `--select-token KEY=<address>` flags. The webapp resolves this dynamically by reading the registry's token-list; CLI users currently have no equivalent. Inlining the full token list in `--describe` output was considered and rejected: a registry can have hundreds of tokens and the list is typically only needed for the one deployment the caller is working with. ## Solution Add a `--tokens` flag that scopes to a single strategy + deployment and emits a markdown table of the tokens the registry has registered for that deployment. ``` raindex strategy-builder --tokens \ --registry <url> --strategy <key> --deployment <key> ``` Output: ``` # Available tokens — `fixed-limit` / `base` 14 tokens. Use any address as the value of a `--select-token KEY=<address>` flag. | Symbol | Name | Address | Decimals | |--------|------|---------|----------| | `wtIAU` | Wrapped iShares Gold Trust ST0x | `0x1E46...` | 18 | ... ``` Any ERC20 address is accepted for `--select-token`; the list is a curated convenience subset. `--describe` links to this command so agents fetch scoped lists on demand. ## Checks - [x] made this PR as small as possible - [x] unit-tested any new functionality - [x] linked any relevant issues or PRs - [ ] included screenshots (if this involves a front-end change)

## Motivation The Raindex orderbook protocol has a rich GUI builder flow in the webapp for configuring and deploying strategies. There is currently no way to do the same from a terminal or from a non-interactive agent — the webapp is the only entry point. That forces anyone automating a deployment (CI, scripts, AI agents) to either drive the browser or hand-roll the calldata. ## Solution Add a `strategy-builder` subcommand to the raindex CLI that generates deployment calldata from a remote registry strategy. ``` raindex strategy-builder \ --registry <url> \ --strategy <key> \ --deployment <key> \ --owner <0x-address> \ [--select-token KEY=ADDRESS ...] \ [--set-field BINDING=VALUE ...] \ [--set-deposit TOKEN=AMOUNT ...] ``` Outputs one `<address>:<calldata>` line per transaction on stdout — approvals first, then the deployment multicall, then optional metaboard meta emission. Each line is one signable transaction. Implementation reuses `RaindexOrderBuilder` from the common crate (same object the webapp drives) and `DotrainRegistry` from the js_api crate, so the CLI and webapp use identical resolution semantics. Follow-up PRs in this stack add `--interactive` (#2546), `--tokens` (#2549), the template-fallback operator (#2551), and `--describe` (#2548). ## Checks - [x] made this PR as small as possible - [x] unit-tested any new functionality - [x] linked any relevant issues or PRs - [ ] included screenshots (if this involves a front-end change)  ## Summary by CodeRabbit * **New Features** * Added `strategy-builder` command to the CLI for generating deployment calldata from registry-based strategies. The command accepts required parameters for registry URL, strategy identifier, deployment address, and owner. Users can further customize strategy deployments with repeatable options to set field bindings, select tokens, and configure deposit amounts, enabling streamlined deployment workflows. [![Review Change Stack](https://storage.googleapis.com/coderabbit_public_assets/review-stack-in-coderabbit-ui.svg)](https://app.coderabbit.ai/change-stack/rainlanguage/raindex/pull/2544)

This was referenced Apr 14, 2026

Consolidate JS API gui module into common crate and rename GUI to OrderBuilder #2479

Merged

feat: add strategy-builder CLI subcommand #2544

Open

feat: add interactive mode to strategy-builder CLI #2546

Open

hardyjosh mentioned this pull request Apr 14, 2026

feat: add --describe flag to strategy-builder CLI #2548

Closed

4 tasks

hardyjosh mentioned this pull request Apr 15, 2026

feat: template fallback operator ${expr || 'default'} #2551

Open

4 tasks

hardyjosh marked this pull request as ready for review April 15, 2026 12:48

hardyjosh force-pushed the list-tokens branch from 38992d1 to 129f279 Compare April 15, 2026 12:55

hardyjosh force-pushed the interactive-strategy-builder branch from 5b81496 to 09b6e85 Compare April 15, 2026 15:46

hardyjosh force-pushed the list-tokens branch from 129f279 to 3a71fdf Compare April 15, 2026 15:47

hardyjosh force-pushed the interactive-strategy-builder branch from 09b6e85 to 9a36b8f Compare April 15, 2026 20:50

hardyjosh force-pushed the list-tokens branch from 3a71fdf to 114798b Compare April 15, 2026 20:50

hardyjosh force-pushed the list-tokens branch from 114798b to f4146a3 Compare April 15, 2026 22:06

hardyjosh mentioned this pull request Apr 16, 2026

feat: add --describe flag to strategy-builder CLI #2552

Open

4 tasks

hardyjosh force-pushed the interactive-strategy-builder branch from 3188bcf to 70bd12e Compare April 30, 2026 17:34

hardyjosh force-pushed the list-tokens branch from f4146a3 to 2a60ff7 Compare April 30, 2026 17:34

hardyjosh requested review from 0xgleb, JuaniRios and alastairong1 April 30, 2026 17:50

JuaniRios assigned hardyjosh May 1, 2026

JuaniRios approved these changes May 1, 2026

View reviewed changes

graphite-app Bot force-pushed the interactive-strategy-builder branch from 70bd12e to 064b102 Compare May 11, 2026 10:04

graphite-app Bot force-pushed the list-tokens branch from bd81bf6 to 48231b5 Compare May 11, 2026 10:05

graphite-app Bot force-pushed the interactive-strategy-builder branch from 064b102 to 42d4024 Compare May 11, 2026 12:28

graphite-app Bot force-pushed the list-tokens branch from 48231b5 to 077e453 Compare May 11, 2026 12:28

graphite-app Bot force-pushed the interactive-strategy-builder branch from 42d4024 to b71ab0d Compare May 11, 2026 12:32

graphite-app Bot force-pushed the list-tokens branch from 077e453 to 545edb8 Compare May 11, 2026 12:32

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

feat: add --tokens flag to list deployment-specific tokens#2549

feat: add --tokens flag to list deployment-specific tokens#2549
hardyjosh wants to merge 1 commit into
interactive-strategy-builderfrom
list-tokens

hardyjosh commented Apr 14, 2026 •

edited

Loading

Uh oh!

hardyjosh commented Apr 14, 2026 •

edited

Loading

Uh oh!

coderabbitai Bot commented Apr 14, 2026 •

edited

Loading

Review skipped

Uh oh!

hardyjosh commented Apr 15, 2026

Uh oh!

coderabbitai Bot commented Apr 15, 2026

Uh oh!

hardyjosh commented Apr 15, 2026

Uh oh!

coderabbitai Bot commented Apr 15, 2026

Uh oh!

hardyjosh commented May 11, 2026 •

edited by graphite-app Bot

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Conversation

hardyjosh commented Apr 14, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Motivation

Solution

Checks

Uh oh!

hardyjosh commented Apr 14, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

How to use the Graphite Merge Queue

Uh oh!

coderabbitai Bot commented Apr 14, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Review skipped

Uh oh!

hardyjosh commented Apr 15, 2026

Uh oh!

coderabbitai Bot commented Apr 15, 2026

Uh oh!

hardyjosh commented Apr 15, 2026

Uh oh!

coderabbitai Bot commented Apr 15, 2026

Uh oh!

hardyjosh commented May 11, 2026 • edited by graphite-app Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Merge activity

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

hardyjosh commented Apr 14, 2026 •

edited

Loading

hardyjosh commented Apr 14, 2026 •

edited

Loading

coderabbitai Bot commented Apr 14, 2026 •

edited

Loading

hardyjosh commented May 11, 2026 •

edited by graphite-app Bot

Loading