feat: replace REST API with Raindex market service

[findolor]

Chained PRs

• Depends on feat: add Raindex market SDK #2845, which adds active-order market discovery and the shared SDK read model.
• Followed by feat: show Raindex market data #2848, which makes the webapp consume this service for the Raindex market view.

Summary

• Replace the authenticated take-orders REST API with a public, unauthenticated Raindex market-data service.
• Serve public ticker and executable orderbook endpoints plus the SDK snapshot shape used by the webapp.
• Back reads with the SDK persistent local indexer, a minutely last-good overview cache, and per-market executable-book caches.
• Add the production deployment architecture: OpenTofu-managed DigitalOcean resources, encrypted state, declarative NixOS, deploy-rs profiles, persistent storage, nginx/TLS, bounded logs, and verified GitHub deployments.

Key decisions

• Wait for every configured local index to become ready before warming the first snapshot. RAINDEX_LOCAL_DB_READY_TIMEOUT_SECONDS controls the startup deadline and defaults to 600 seconds.
• GET /tickers publishes required 24-hour fields for every active direct quote market without quoting every order on each minute refresh.
• GET /orderbook?ticker_id=...&depth=... quotes only the requested market and exposes up to a fixed 1,000-level SDK snapshot. Failed RPC quotes or ratio normalization return retryable 503 responses and are not cached.
• GET /v1/markets serves lightweight cached SDK snapshots for the webapp. Filtering by ticker_id adds executable depth and bounded recent trades.
• Keep the optional historical-trades endpoint deferred until the SDK supports arbitrary indexed ranges without silently truncating its 24-hour snapshot.
• Enforce global and per-socket-IP rate limits, request IDs, structured errors, CORS, tracing, and readiness/freshness health checks.
• Emit JSON logs to stdout and daily rotated files with a 14-file retention limit; production also bounds journald to 14 days and 512 MB.
• Treat no discovered markets as a valid, cacheable snapshot: /tickers and /v1/markets return 200 []. Duplicate cross-chain ticker IDs, fatal registry/trade reads, and incomplete executable books remain errors.
• Use reproducible Crane builds, nixos-anywhere bootstrap, a pinned SSH host key, encrypted Terraform variables/state, a persistent DigitalOcean volume, declarative firewall/nginx/systemd configuration, and atomic deploy-rs rollbacks.

Validation

• cargo test -p raindex_rest_api --locked: 26 passed
• cargo clippy -p raindex_rest_api --all-targets --locked -- -D warnings
• nix build .#raindex-api --no-link
• nix flake check --no-build --impure
• nix shell .#opentofu -c tofu -chdir=infra validate
• nix shell .#actionlint -c actionlint .github/workflows/raindex-api.yaml .github/workflows/deploy-raindex-api.yaml
• Local smoke test waited for the Base index, discovered 48 active direct quote markets from local_db, and served healthy overview, ticker, detail, and orderbook responses.

Production prerequisites

• Provision once with the documented tfEditVars, tfPlan, tfApply, and bootstrap commands, then commit the encrypted variables/state and verified host key.
• Point the production hostname at the reserved IP. The default is api.raindex.finance; RAINDEX_API_HOSTNAME overrides it.
• Configure the Production environment with RAINDEX_API_SSH_KEY and, optionally, CACHIX_AUTH_TOKEN and RAINDEX_API_HOSTNAME.

No issue is linked per the implementation scope.

[coderabbitai]

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 Plus

Run ID: f838c829-a36f-4be4-b812-4d7b0f25c7f5

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

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[findolor]

• feat: show Raindex market data #2848
• feat: replace REST API with Raindex market service #2847 👈 (View in Graphite)
• feat: add Raindex market SDK #2845
• 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.

[findolor]

@coderabbitai full review

[coderabbitai]

⚠️ Action not completed

Review rate limited.

---

Your included review limit is currently reached under our Fair Usage Limits Policy. This review may still proceed through usage-based billing if eligible. Your next included review will be available in 51 minutes.

[agryaznov]

LGTM

[github-actions]

@coderabbitai assess this PR size classification for the totality of the PR with the following criterias and report it in your comment:

S/M/L PR Classification Guidelines:

This guide helps classify merged pull requests by effort and complexity rather than just line count. The goal is to assess the difficulty and scope of changes after they have been completed.

Small (S)

Characteristics:

• Simple bug fixes, typos, or minor refactoring
• Single-purpose changes affecting 1-2 files
• Documentation updates
• Configuration tweaks
• Changes that require minimal context to review

Review Effort: Would have taken 5-10 minutes

Examples:

• Fix typo in variable name
• Update README with new instructions
• Adjust configuration values
• Simple one-line bug fixes
• Import statement cleanup

Medium (M)

Characteristics:

• Feature additions or enhancements
• Refactoring that touches multiple files but maintains existing behavior
• Breaking changes with backward compatibility
• Changes requiring some domain knowledge to review

Review Effort: Would have taken 15-30 minutes

Examples:

• Add new feature or component
• Refactor common utility functions
• Update dependencies with minor breaking changes
• Add new component with tests
• Performance optimizations
• More complex bug fixes

Large (L)

Characteristics:

• Major feature implementations
• Breaking changes or API redesigns
• Complex refactoring across multiple modules
• New architectural patterns or significant design changes
• Changes requiring deep context and multiple review rounds

Review Effort: Would have taken 45+ minutes

Examples:

• Complete new feature with frontend/backend changes
• Protocol upgrades or breaking changes
• Major architectural refactoring
• Framework or technology upgrades

Additional Factors to Consider

When deciding between sizes, also consider:

• Test coverage impact: More comprehensive test changes lean toward larger classification
• Risk level: Changes to critical systems bump up a size category
• Team familiarity: Novel patterns or technologies increase complexity

Notes:

• the assessment must be for the totality of the PR, that means comparing the base branch to the last commit of the PR
• the assessment output must be exactly one of: S, M or L (single-line comment) in format of: SIZE={S/M/L}
• do not include any additional text, only the size classification
• your assessment comment must not include tips or additional sections
• do NOT tag me or anyone else on your comment