Read Soroban contract events past the 7-day RPC retention window.
Stellar RPC keeps about seven days of contract events, so anything older is gone from getEvents. A project that needs its full history ends up writing the same plumbing every time: an XDR decoder, an indexer, and an API on top. Pulsar is that plumbing, built once: it stores every event a contract emits, decodes it into typed data, and serves it to your app or to a browser.
flowchart LR
C["Soroban contracts"] -->|emit events| RPC["Stellar RPC<br/>about 7 days of history"]
RPC -->|getEvents polling| IDX["Go indexer"]
IDX --> DB[("SQLite or Postgres")]
DB --> API["REST and GraphQL"]
API -->|REST| SDK["TypeScript SDK"]
API -->|GraphQL| WEB["Web explorer"]
RPC -.->|live tail, no indexer needed| SDK
The indexer polls RPC, decodes each event, and keeps it for good. The SDK reads that history from the indexer, or tails new events straight from RPC when you don't run one. Both paths return the same event type.
| Repository | What it holds |
|---|---|
| pulsar-app | The TypeScript SDK, the Go indexer, and the Next.js explorer |
| pulsar-core | The Rust event decoder and the reference contract whose events every part is tested against |
| pulsar-docs | The documentation source, published at emeditweb.gitbook.io/pulsar-stellar-sdk |
npm install @pulsar-stellar/sdk @stellar/stellar-sdk@stellar/stellar-sdk is a required peer dependency. Read the documentation for usage.
@pulsar-stellar/sdk0.2.0 is on npm.- The indexer, the explorer, and the Rust decoder are built and tested. The decoder is not on crates.io yet.
- The reference contract is deployed on Stellar testnet.
- Public hosting of the indexer and explorer is in progress. Today you run them yourself.
Contributions start in pulsar-app. Read its CONTRIBUTING.md before opening a pull request.