robinhood-trading-tools README

The project's README from github.com/casatrickdev/robinhood-trading-tools. As one markdown file: README.md.

Pons SDK

Robinhood Chain trading tools for Pons. TypeScript SDK for token launches, a historical indexer, and research for a Robinhood copy trading bot. A Robinhood sniper bot and Robinhood bundler are on the roadmap and are not live.

Typed access to Pons factory contracts, token launches, and TokenLaunched events with viem queries.

Site: casatrickdev.github.io/pons-sdk

Write-up: Pons SDK on Robinhood Chain

This package is read-only. It does not sign transactions, hold keys, or execute trades.

This is a client for Pons on Robinhood Chain. It is not Pons Network (@pons-network/pons.js) or the Pons microkernel SDK.

Features

Installation

pnpm add pons-sdk

Peer runtime: Node.js 20+ and viem.

Quickstart

import { PonsClient } from "pons-sdk";

const pons = new PonsClient();

const launches = await pons.getLaunches({
  fromBlock: 8_991_118n,
  toBlock: "latest",
});

for (const launch of launches.slice(0, 10)) {
  console.log(launch);
}

The public Robinhood Chain RPC times out on wide eth_getLogs ranges. The SDK splits requests into bounded chunks (2,000 blocks by default). A full backfill from the V1 start block still takes time against the public endpoint; prefer a tighter toBlock while developing.

Override the RPC when you have a dedicated provider:

const pons = new PonsClient({
  rpcUrl: "https://your-robinhood-rpc.example",
});

Reading a launch

import { PONS_REFERENCE, PonsClient } from "pons-sdk";

const pons = new PonsClient();

const launch = await pons.getLaunch(PONS_REFERENCE.token, {
  version: "v1",
  includeLegacy: true,
});

const graduation = await pons.getGraduationStatus(PONS_REFERENCE.token, {
  includeLegacy: true,
});

V1 and V2 factories have different TokenLaunched ABIs and different getLaunchedToken records. The SDK models them as separate types instead of collapsing incompatible fields.

const v2Launches = await pons.getLaunches({
  fromBlock: 55_400_000n,
  toBlock: "latest",
  version: "v2",
});

const canLaunch = await pons.canLaunch("0x...");

Event filtering

token and deployer are indexed on both factory generations and can be passed through to eth_getLogs:

const launches = await pons.getLaunches({
  fromBlock: 8_991_118n,
  toBlock: 8_993_118n,
  token: "0x39dBED3a2bd333467115dE45665cC57F813C4571",
});

pool is not an indexed TokenLaunched argument on V1, and V2 has no pool field on that event. The SDK does not pretend those filters exist at the RPC layer.

Architecture

Robinhood Chain
      ↓
Pons Contracts
      ↓
Events
      ↓
Pons SDK
      ↓
Historical Indexer / SQLite
      ↓
Future Analytics / Scanner
Layer Responsibility
chain/ Robinhood Chain definition and default public RPC
contracts/ Official factory addresses and verified ABI fragments
events/ Block-range chunking, log fetch, TokenLaunched decode
launches/ Normalized launch objects and verified contract reads
client/ Developer-facing PonsClient
indexer/ Historical TokenLaunched sync, cursor, and queries
storage/ SQLite schema and launch persistence

Contract addresses and event signatures come from the official Pons documentation and the ponsdotdev/ponsfamily repository. They are not invented and are not taken from a third-party SDK.

Contracts

Generation Role Address Start block
V1 Active factory 0xA5aAb3F0c6EeadF30Ef1D3Eb997108E976351feB 8,991,118
V1 Legacy factory 0x0c37a24F5D23A486FA692d1500881d698B1F77a4 8,600,612
V2 Factory 0x7eD598BcEf8bd9Edd8C97A195C6d13f40801EC7e —

The official PONS reference token (0x39dBED3a2bd333467115dE45665cC57F813C4571) was launched through the V1 legacy factory. Use includeLegacy: true when you need that history.

Milestone 1

Milestone 1 is the read-only data layer: connect to Robinhood Chain, talk to the official Pons V1 and V2 factories, and turn real TokenLaunched logs into typed objects.

Robinhood Chain
      ↓
Pons Contracts
      ↓
Onchain Events
      ↓
Typed SDK

Shipped in this milestone:

The next milestone after this read layer is persistent historical state. Milestone 2 (the SQLite indexer) is included in this package.

Full write-up: Building a Pons SDK on Robinhood Chain.

Historical Indexer

Milestone 2 turns decoded TokenLaunched events into local, queryable history.

Pons contracts
      ↓
TokenLaunched events
      ↓
Pons SDK
      ↓
Historical indexer
      ↓
SQLite
      ↓
Queryable launches

The indexer uses the SDK's getLaunches() and splitBlockRange() helpers. It does not send transactions. Blockchain integers are stored as decimal strings.

Re-processing the same block range does not create duplicate events. Identity is transactionHash + logIndex, enforced by a SQLite unique constraint. The indexer can safely replay a range. It does not unwind chain reorganizations.

import { PonsClient, PonsDatabase, PonsIndexer } from "pons-sdk";

const indexer = new PonsIndexer({
  client: new PonsClient(),
  database: new PonsDatabase("pons-indexer.sqlite"),
});

await indexer.sync({
  fromBlock: 8_963_000n,
  toBlock: 8_965_000n,
});

const launches = indexer.getLatestLaunches(20);

Resume after a stop by omitting fromBlock. The cursor only advances after the chunk is committed.

pnpm indexer:sync --from 8963000 --to 8965000
pnpm indexer:latest

Copy-Trading Research

This module detects and evaluates wallet activity but does not execute trades.

Copy-trade domain logic is tested against normalized synthetic domain fixtures. Real Pons wallet/swap ingestion will be connected when the indexer supports those events. Token addresses used in tests can still come from live Robinhood Chain reads.

Pons Events
     ↓
Indexer
     ↓
Wallet Activity
     ↓
Trade Detection
     ↓
Filtering
     ↓
Risk
     ↓
Copy-Trade Signal
     ↓
Execution Adapter
        X
   Disabled

Research-only: mode is research. Constructing live throws. Signals use a deterministic id (transactionHash + logIndex). Filtering and risk are separate deterministic layers. No private keys. No live execution. engine.execute() throws Live execution is disabled in research mode. NoopExecutionAdapter returns not_executed.

import { CopyTradeEngine } from "pons-sdk";

const engine = new CopyTradeEngine({
  mode: "research",
  policy: {
    allowedWallets: ["0x..."],
    minTradeSize: 1n,
  },
});

const signal = engine.process(activity);
console.log(engine.explain(signal));

Robinhood copy trading bot, sniper bot, and bundler

This repo is the open-source foundation for Robinhood Chain trading tools:

Tool Status
Robinhood copy trading bot Research pipeline only. Detects and scores wallet activity. Does not copy trades.
Robinhood sniper bot Not implemented. Planned after swap indexing and a real-time event stream.
Robinhood bundler Not implemented. Planned after paper execution.
Other Robinhood trading tools Launch indexer and read-only SDK are available now.

Live copy-trading, sniping, bundling, and fund execution are disabled. There is no environment flag that turns them on.

Real trading is not implemented. If it is added later, do not use the public Robinhood Chain RPC (https://rpc.mainnet.chain.robinhood.com). Live reads and execution need a dedicated paid RPC such as Alchemy or QuickNode, passed as rpcUrl on PonsClient.

Roadmap

[x] Robinhood Chain client
[x] Pons V1/V2 contracts
[x] Contract reads
[x] TokenLaunched decoding
[x] Launch queries
[x] SDK tests
[x] Live RPC tests

[x] Historical indexer
[x] Persistent indexed state
[x] Copy-trading research architecture
[x] Read-only signal pipeline

[ ] Real-time event stream
[ ] Wallet activity indexing
[ ] Wallet intelligence
[ ] Copy-trading backtesting
[ ] Paper execution
[ ] Live execution
[ ] Scanner
[ ] Bundler
[ ] Sniper
[ ] Additional Robinhood Chain launchpads
[ ] Swap indexing

Development

pnpm install
pnpm lint
pnpm typecheck
pnpm test
pnpm build

Read-only integration tests hit the public Robinhood Chain RPC and never require a wallet:

pnpm test:integration

Run the example:

pnpm example:launches
pnpm indexer:sync --from 8963000 --to 8965000
pnpm indexer:latest

Safety

This package is data infrastructure and copy-trading research only.

On-chain values stay as bigint / addresses. The SDK does not convert token amounts to floating-point numbers.

License

MIT

robinhood-trading-tools (casatrickdev/robinhood-trading-tools)

Searching Database…

119 ·GitHub
Robinhood-trading-tools
Что это?Это TypeScript SDK и набор инструментов для Pons на Robinhood Chain: типизированный доступ на чтение к фабричным контрактам Pons и запускам токенов, исторический SQLite-индексатор событий TokenLaunched и инструменты для будущего Robinhood-бота копитрейдинга.
Это торговый бот, который я запускаю напрямую, или библиотека, на которой я строю своё?Это библиотека/SDK только для чтения, а не запускаемый бот: он никогда не подписывает транзакции, не хранит ключи и не исполняет сделки, так что свои инструменты вы строите поверх его PonsClient.
Как добавить это в проект?Добавьте пакет в проект на Node.js 20+ с viem как peer-зависимостью, импортируйте PonsClient для запросов запусков и запустите приложенный пример командой 'tsx examples/read-launches.ts'.
Что нужно установить перед использованием?Нужны Node.js 20+ и библиотека viem как peer-зависимости; историческому индексатору дополнительно требуется better-sqlite3 для локального хранения событий.
Позволяет ли это прямо сейчас заниматься копитрейдингом, снипингом или бандлингом на Robinhood Chain?Нет — снайпер-бот и бандлер ещё не реализованы, а живые копитрейдинг, снипинг, бандлинг и исполнение отключены, без переменной окружения для их включения; публичный RPC также падает по таймауту на широких запросах логов, поэтому SDK режет запросы на диапазоны по 2000 блоков.
Трогает ли он мой кошелёк или приватные ключи?Нет — в SDK нет подписания транзакций и хранения кошельков, а его адаптер исполнения — жёстко зашитая заглушка, которую невозможно активировать.
Что на самом деле делает модуль исследования копитрейдинга?Он находит и оценивает активность кошельков через детерминированную фильтрацию и правила риска только в режиме исследования; вызов engine.execute() бросает исключение, так что пути к живому исполнению сделок нет.
Почему SDK разбивает запросы к блокчейну на куски?Публичный RPC Robinhood Chain падает по таймауту на широких диапазонах eth_getLogs, поэтому SDK по умолчанию забирает события TokenLaunched ограниченными кусками по 2000 блоков, с возможностью передать выделенный RPC для более быстрой докачки истории.
Что хранит исторический индексатор?Он сохраняет декодированные события TokenLaunched в локальную базу SQLite, дедуплицирует по transactionHash плюс logIndex и может возобновить синхронизацию, опустив fromBlock, без создания дубликатов.
Откуда берутся адреса контрактов и ABI?Они взяты прямо из официальной документации Pons и репозитория ponsdotdev/ponsfamily, а не получены реверс-инжинирингом и не позаимствованы из стороннего SDK.
What are similar projects?pons-sniper-bot, pons-copy-trading-bot, robinhood-meme-token-stock-launchpad, rh-swap, nuvex-services, stellar-trade, robinhood-lp-bot, Trpjan-solana-trading-toolkit
Which topics is it in?robinhood-chain, evm, crypto-trading, dapp, defi, smart-contracts, trading, cryptocurrency, web3, blockchain, finance, sqlite
Creator
casatrickdev
Size
0.4 MB
Stars
119
Updated
CommitSep 15
Age
1mo
Commits · 90 Days