
By Rumble Fish Software Development - RFP

While all Stellar block explorers have good support for classic assets, Stellar block explorers do not have good support for Soroban assets. This dampens growth, because Soroban allows for DeFi, collectibles trading, and other emergent use cases. Not having a block explorer that displays Soroban events and transactions legibly makes it harder for you to engage with new apps, which limits innovation. For that reason, a block explorer that supports displaying Soroban and classic operations in human-readable and context-rich formats will enhance trust in what’s happening on-chain.
$131.2K
this field doesn't seem relevant for RFP submission of a new system
LedgerCloseMeta XDR files to S3every ~5–6 seconds. Lambda Ledger Processor triggered per file, parsing and writing
ledgers, transactions, operations, Soroban invocations, and CAP-67 events to a dedicated
RDS PostgreSQL database. Historical backfill from Soroban mainnet activation ledger
(late 2023) to genesis of new architecture. NestJS API scaffolding with core modules
(Transactions, Ledgers, Network stats, Contracts). OpenAPI specification. AWS CDK
infrastructure-as-code. CI/CD pipeline (GitHub Actions → cdk deploy). CloudWatch
dashboards and ingestion lag alarms.
1. S3 bucket contains consecutive LedgerCloseMeta files with timestamps matching
mainnet ledger close times (verifiable by inspector script provided in repo)
2. RDS ledgers table contains all ledgers from backfill start through current tip with
no gaps (verified by: SELECT COUNT(*) ... WHERE sequence BETWEEN X AND Y)
3. RDS soroban_events table contains CAP-67 events for known Soroswap/Aquarius/Phoenix
transactions (spot-checked by transaction hashes provided by reviewer)
4. cdk deploy from a clean AWS account produces the full working stack with no manual
steps (README instructions verified)
5. CloudWatch dashboard accessible; Galexie lag alarm fires when S3 file is artificially
delayed in staging
ledgers (list + detail), accounts (detail + history), contracts (detail + invocations +
events), search (exact match + prefix). Human-readable event interpretation for known
patterns (swaps, transfers, mints) on transaction detail pages. React SPA deployed via
CloudFront with all pages: Home, Transaction List, Transaction Detail, Ledger Detail,
Account Detail, Contract Detail, Search. Rate limiting (per-IP and API key tiers) and
response caching configured on API Gateway.
1. All API endpoints return schema-valid responses for a set of mainnet entity IDs
provided by the reviewer (or taken from public Stellar mainnet)
2. Soroban invocations on Contract Detail page show function name, arguments, and return
value (not raw XDR) for at least 3 known Soroswap/Aquarius contract transactions
3. CAP-67 events appear on Transaction Detail page under Events tab with decoded topics
and data fields (not raw XDR)
4. Global search returns correct entity type and redirects to detail page for an exact
transaction hash, account ID, and contract ID provided by the reviewer
5. React frontend is publicly accessible at staging URL; all pages render live mainnet
data without errors in browser console
parsing correctness, API endpoint responses, and event interpretation logic. Load test
results documented (1M baseline, 10M stress). Security audit checklist (OWASP Top 10,
CORS, IAM least-privilege, no public RDS endpoint). Monitoring dashboards and alerting
active and accessible to Stellar team. Full API reference documentation published. GitHub
repository made public with architecture docs, local dev setup, and deploy instructions.
Professional user testing completed. 7-day post-launch monitoring report.
1. Block explorer publicly accessible at announced production URL, showing live mainnet
data with ledger sequences matching network tip within 30 seconds
2. GitHub repository public; cdk deploy from README works in a fresh AWS account
(verified by reviewer or documented in screen recording)
3. CloudWatch dashboard accessible to Stellar team (read-only IAM role); all alarms in
OK state at launch; Galexie ingestion lag shown to be <30 s from network tip
4. Load test report provided: p95 <200 ms at 1M requests/month equivalent load; error
rate <0.1%
5. Security checklist signed off: no wildcard IAM permissions, RDS has no public
endpoint, all secrets in Secrets Manager, all API inputs validated
6. 7-day post-launch monitoring report: uptime %, API error rate, p95 latency, Galexie
ingestion lag per day
Rumble Fish is a 26-person software house, founded in 2017, that has done blockchain work since its first year. Five of us are dedicated to Stellar work. We have built on Stellar since January 2026, starting with a Soroban smart-contract migration for Merkl that Stellar referred to us. Since then we have received three SCF Build awards, for the Soroban Block Explorer and the Prices API (both live, both open source) and the x402 facilitator, and an SCF Public Goods award. Our SCF work is public at github.com/rumblefishdev.
The engineers who built that work are listed below. This award is sized for about two engineers, who will come from this group depending on timing at kickoff:
Karol Kowalczyk (github.com/karolko9): lead developer of the Soroban Block Explorer, our largest Stellar codebase, and a core contributor to the x402 facilitator.
Oskar Karcz (github.com/karczuRF): lead developer of the Prices API and contributor to the x402 facilitator; built this proposal's evidence repository (corpus entries, generator, the #729 reproduction).
Stan Królikiewicz (github.com/stkrolikiewicz): works across the Block Explorer, the Prices API and the x402 facilitator; author of our internal write-up of the production ingestion failures listed in Traction Evidence.
Adam Kot (github.com/adamkoot): Prices API and x402 facilitator.
Filip Mazur (github.com/Efem67): Soroban Block Explorer.
Marek Kowalski (github.com/kowalski) coordinates our SCF work and is the point of contact.
Both indexers read LedgerCloseMeta straight from Galexie, decode it with rs-stellar-xdr in production, and have had to survive every protocol upgrade since launch, so we have hit the bug classes this RFP targets first-hand (listed in Traction Evidence).

