LP-share token tracking

[Asheeyah23]

Background

LP shares are non-trivially named; surface them as first-class.

What to build

Decode pool deposits/withdrawals as LP-share transfers tagged with the pool ID.

Key files

• src/indexer/lp-shares.ts (new)

Acceptance criteria

• LP transfers indexed
• Pool ID available on the row

Drips Wave · Complexity: Intermediate · 150 points

---

Required: Before submitting, join the contributor Telegram so your work can be tracked and counted toward the Stellar Wave: https://t.me/+fxHXq8f1SwlkZDBk

[Emoji-dot]

@Emoji-dot has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

I would like to work on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Emoji-dot to this issue.

[githoboman]

@githoboman has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hey, I'd like to take this on.

I've gone through the codebase and have a clear picture of the approach:

• New src/indexer/lp-shares.ts module following the same parser/upsert pattern as host-fn-log.ts and ingester/nft.ts
• Detect LP-share events by contract ID membership (opt-in via LP_POOL_IDS env var) + mint/burn topic shape — avoids false positives against ordinary SAC transfers
• Alias contractId → poolId as a first-class column on a new LpShareTransfer table so consumers can query by pool without knowing the token contract address
• Migration + Prisma model + wired into the main pollOnce loop alongside the existing fungible/NFT paths
• Unit tests for parseLpShareEvent and isLpShareEvent covering deposit, withdrawal, and malformed cases

Expected deliverables: migration, schema model, lp-shares.ts, tests, and indexer wiring. Happy to start immediately — ETA 2–3 days.

Full-stack blockchain dev with active Web3 audit/indexer experience across TypeScript/Soroban stacks. GitHub: githoboman

ℹ️ Repo Maintainers: To accept this application, review their application or assign @githoboman to this issue.

[drips-wave]

Congratulations, @githoboman! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @githoboman: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊