Pulsar Stellar
A software project by Emmanuel Itighise (Emeditweb)

Project overview
An open-source toolkit for reading Soroban contract events past the seven-day RPC retention window. A TypeScript SDK, Go indexer, and Next.js explorer make collected history available beyond RPC retention, alongside a reference contract and a Rust decoder crate shared with the Go indexer’s test fixtures.
The problem
Soroban RPC nodes typically keep contract events for about seven days. If an app needs a user’s transaction history from last month, an audit trail, or analytics, RPC alone cannot supply it. Teams end up building and maintaining their own indexer or paying for a hosted service.
Pulsar Stellar fills that gap. It decodes contract events and stores them so collected history does not expire with RPC retention. It preserves events from when collection begins; it cannot recover older events that have already fallen outside the RPC window.
What it is
Three parts work together:
1. TypeScript SDK (@pulsar-stellar/sdk, on npm). Typed access to decoded events. It can read stored history from an indexer or follow live events straight from Stellar RPC. It includes cursor pagination, authenticated writes, and a decoder covering common Soroban value types.
2. Go indexer. A self-hostable daemon that polls Stellar RPC, decodes each event, and stores it in SQLite or Postgres. It serves a REST API and a read-only GraphQL API. Write routes require a bearer token and are rate limited.
3. Web explorer (Next.js). Paste a contract ID and browse its decoded events. It has filters, pagination, an event detail view with a decoded value tree, and JSON export. It went through a WCAG 2.1 AA accessibility pass and includes a live indexer health indicator.
Alongside these, pulsar-core holds a reference Soroban contract in Rust, deployed on testnet. It emits six event shapes and acts as the shared test fixture for the toolkit. It also contains an implemented Rust decoder crate whose output is checked against fixtures shared with the Go decoder.
How it works
The poller asks Stellar RPC for each tracked contract’s events, starting from a stored cursor. Each event goes through the decoder, which turns raw XDR into typed values. The events and the advanced cursor are written in one database transaction. The API and explorer then read from that store.
Design choices worth knowing
Wire-faithful decoding. Events keep the shape they had on the ledger. Mapping helpers convert them to the call-oriented types that generated bindings use, so nothing is converted silently.
No silent data loss. Wide integers come back as strings so JavaScript cannot round them. An unrecognised value type becomes an unknown value with its raw XDR attached instead of an error, so a protocol upgrade does not break stored history.
Reverted calls stay visible. Every event carries an inSuccessfulContractCall flag, so consumers can filter failed calls themselves.
Two database engines. SQLite means zero setup for developers trying the toolkit. Postgres is for production. CI runs integration tests against a real Postgres service.
How it was built
The application repository records 47 numbered architecture decision records (ADRs), as of November 2, 2026. Several capture cases where live testnet data changed the original plan: event ordinals, live RPC cursor behaviour, and timepoint formatting.
The contribution workflow calls for changes to land as pull requests with passing CI and review from a second maintainer. The decisions, tests, and review history explain how the implementation reached its current shape.
Stack
Rust and Soroban for the reference contract and decoder; Go for the indexer; TypeScript and Next.js for the SDK and explorer; SQLite and Postgres for storage; GraphQL for read queries; and GitHub Actions for CI.
Status
Shipped: the SDK on npm, the reference contract on testnet, the Go indexer, the web explorer, the implemented Rust decoder, and a public documentation site. The Rust decoder implementation is distinct from a published crates.io release.
In progress: hosting. The indexer Dockerfile and Postgres verification are complete. A public indexer and explorer deployment remain next, so the project keeps its In Dev badge.
Recognition: the explorer’s accessibility pass was selected for the XERJ Corpus Hub, an open index of worked code solutions for AI coding agents. As of November 2, 2026, the listing is live and its licence is cleared under Apache-2.0 with attribution.
Technologies and tools
- Stellar
- Soroban
- Rust
- Go
- TypeScript
- Next.js
- SQLite
- Postgres
- GraphQL
- GitHub Actions
Explore the project
Emmanuel Itighise, known online as Emeditweb, is a full-stack and AI-native developer based in Lagos, Nigeria. This entry is part of his project portfolio and open-source work.