Product overview
STRIXS is a read-only utility that converts the public onchain history of a Robinhood Chain address into a clear, visual profile.
- Network
- Robinhood Chain mainnet
- Chain ID
- 4663
- Status
- Live MVP
- Access
- Public and read-only
Users can search any valid public address, review activity and assets, inspect deterministic badges, compare two addresses, and download individual or comparison cards. STRIXS does not connect to a wallet, request a signature, move funds, execute trades, or prove who owns an address.
- Turn raw address activity into a human-readable profile.
- Make every result traceable to a public source.
- Create distinctive proof cards from real data.
- Stay safe and lightweight through a read-only, database-free experience.
Public experience
Each public route has one job: help users understand, verify, or share visible onchain activity.
/Homepage
Search a public address, understand the five profile signals, preview comparisons, and enter the Badge Vault.
/address/[address]Wallet profile
Review origin, transactions, qualifying assets, created contracts, Stock Token interactions, badges, evidence, and the proof card.
/compareWallet Compare
Compare two different addresses across five evidence-backed categories. At least three categories must be verified before a trace winner is declared.
/compare/cardComparison card
Generate a 1200 × 630 share card containing both addresses, the score, category results, badges, and verification disclosures.
/badgesBadge Vault
Inspect every deterministic milestone, its threshold, required dataset, evidence source, and possible result state.
/methodologyMethodology
Read how STRIXS validates, filters, caches, retries, bounds, scores, and discloses incomplete public data.
Profiles and comparisons describe public-chain activity only. They do not measure wealth, investment quality, reputation, or control of an address.
Badge system
Badges are generated from fixed rules and are never manually assigned.
| Badge | Rule | Required data |
|---|---|---|
| Pioneer | First confirmed activity on or before May 30, 2026 at 16:52:11 UTC. | First confirmed transaction |
| Active | At least 100 address transactions. | Blockscout address counters |
| Collector | At least 10 current nonzero balances not marked as spam by Blockscout. | Current token balances |
| Builder | At least one successful outgoing contract-creation transaction. | Transaction history |
| Stock Explorer | Interaction with at least three distinct active canonical Stock Token contracts. | Token transfers and Robinhood asset catalogue |
The verified public value meets the published rule.
The dataset is complete, but the threshold is not met.
The required dataset is incomplete, timed out, rate limited, malformed, or otherwise unavailable.
Data sources
Robinhood Chain Blockscout
STRIXS reads address counters, current token balances, token transfers, earliest activity, and contract-creation history. Profile evidence links return users to the public explorer records.
Open Blockscout ↗Robinhood asset catalogue
The public asset feed identifies active canonical Stock Token deployments for chain ID 4663. STRIXS uses the catalogue only for identification—not pricing, trading, recommendation, or custody.
Robinhood Chain docs ↗Data processing and resilience
STRIXS preserves verified sections when an optional public source is incomplete and never turns an unfinished scan into a confident result.
Validation
Inputs must be valid EVM addresses and are normalized to checksum form. Provider responses are schema-validated before entering a profile, and comparison rejects duplicate addresses.
Concurrent retrieval
Independent profile sections are requested concurrently. One failed source does not erase sections that were retrieved and verified successfully.
Timeouts and retries
Each upstream call has a six-second timeout. A transient non-rate-limited failure receives one bounded retry after 150 milliseconds; HTTP 429 responses are reported without an immediate retry.
Caching
Successful wallet data is revalidated every five minutes and the canonical Stock Token catalogue every hour. STRIXS does not use an application database or user-account store.
Bounded scans
Contract creation scans at most 10,000 ascending transactions. Stock Token discovery scans at most five transfer pages and may stop after three canonical matches. Incomplete scans become unavailable, not definitive.
Profile states
Complete means every required section is available. Partial keeps verified data visible while disclosing unavailable sections. Empty means the available sources show no supported activity.