Stellar Wave Program — Phase 1 is open (145 issues, v1.0 track)

[determined-001]

Orbital Stellar is joining the Stellar Wave program 🌊

We have just published 145 open issues covering the full Phase 1 roadmap for our three published packages. Every issue is tagged Stellar Wave and carries a complexity tier and point value — making them easy to filter and claim.

---

What is the Wave program?

The Stellar Wave program rewards open-source contributors for shipping meaningful work on Stellar ecosystem projects. Points convert to XLM grants.

---

What is Orbital Stellar?

Orbital is a programmable event runtime for Stellar's regulated-money economy. It normalises every Horizon and Soroban event into a typed discriminated union, delivers them via hardened webhooks, and surfaces live data through React hooks — all as MIT-licensed npm packages.

Package	What it does
@orbital/pulse-core	Event engine — Horizon SSE + Soroban RPC polling, normalisation, watcher routing
@orbital/pulse-webhooks	HMAC-signed delivery, retry queues, dead-letter store, edge verification
@orbital/pulse-notify	React hooks for live Stellar events

---

Phase 1 scope (issues #288–#432)

Area	Issues	Highlights
pulse-core	64	Soroban subscription, cursor persistence, typed union refinement, ABI Registry client
abi-registry (new package)	16	XDR decoder, TypeScript codegen, well-known token specs
pulse-webhooks	40	Durable retry queues (Redis/Postgres/SQS), DLQ replay, OTel/Prometheus metrics
pulse-notify	25	Connection pooling, offline replay, WebSocket transport, Suspense integration

Complexity breakdown:

• complexity:trivial — 100 pts — well-scoped, great for first contributions
• complexity:medium — 150 pts — standard feature or refactor
• complexity:high — 200 pts — significant design + implementation work

---

How to get started

1. Browse issues labelled Stellar Wave
2. Filter by complexity:trivial + good-first-issue if you are new to the codebase
3. Comment on the issue to claim it, then open a PR referencing it
4. Read CONTRIBUTING.md for setup and code conventions

---

Questions?

Drop them in the Q&A discussion or comment directly on the issue. We review PRs promptly and are happy to pair on tricky bits.

Happy building! 🚀