Local-first, read-only operator tool for observing BankrBot-pattern launch activity on Base.
Remy observes how launches are first observed, whether they surface, what on-chain role references appear, and what changes over the next 24–48 hours. Remy is not a token call, not a trading signal, and not a safety-verdict engine. Current surfaces are aggregate public briefs and private operator-reviewed launch-path dossiers.
Remy maintains local lifecycle memory for BankrBot-pattern launches and tracks surfaced candidates through a delayed observation window so operators can review material before any buyer-facing output is produced. It supports Narrative Surface Enrichment for publicly linked project metadata and produces source-linked Observed Launch Path Dossiers under operator review.
- Aggregate public/free briefs
- 24h/48h delayed surface watch
- Private Observed Launch Path Dossiers
Operators review surfaced candidates, approve public aggregate briefs, and review private source-linked dossiers before buyer-facing use. Operator review is required before export or sharing. No external posting, x402 delivery, or Bankr API automation is in scope for the current direction.
Local operator workflow and development commands remain available for approved internal use. Legacy/internal utilities may exist, but they are not the current Remy product surface.
Public output is aggregate-only and contains no raw identifiers, URLs, token names, or repo names. Private dossiers may include public on-chain identifiers only as evidence references, and these are not identity attribution. Operator review is required before any private material is shared.
- Not a token scanner or ranking service
- Not a buy/sell/hold recommendation source
- Not a safety, legitimacy, or risk-verdict engine
- Not a price prediction or market signal tool
- Not an identity attribution or wallet labeling system
- Not a public automation, auto-posting, or Telegram push service
- Not an x402/Bankr API endpoint or paid access layer
- Not production-ready; operator review gates apply before buyer-facing use
Active development. Current focus:
- Airlock / BankrBot lifecycle memory
- 24h/48h delayed surface watch
- Surfaced candidate tracking and delayed surface watch
- Narrative Surface Enrichment design
- Source-linked Observed Launch Path Dossiers
- Public aggregate-only output
- Unified 47-candidate index implementation — HOLD
- DEXSC metadata enrichment for remaining candidates — HOLD
- Operator review workflow finalization — HOLD
Not yet production-ready. Operator review gates apply before any buyer-facing use.
Legacy local scan modules and internal utilities exist but are not the current Remy product surface.
- Read-only. Remy does not submit transactions, execute swaps, or modify on-chain state.
- Local-first. All data stays on your machine. No cloud dependency, no telemetry, no third-party storage.
- Operator-controlled. Every dossier approval and export action requires explicit operator action.
- Conservative defaults. Unknown data produces UNKNOWN outputs, not invented safety signals.
- Human-approved workflow. Operator review is required before any buyer-facing or shared output.