Add CAP-46 NFT (Soroban token) indexing

[Miracle656]

Background

Wraith currently indexes fungible token transfers. CAP-46 NFT contracts on Soroban emit similar transfer events but with a token_id discriminator. Indexing them turns Wraith into the only Stellar NFT activity explorer.

What to build

Detect NFT contracts by ABI sniff (presence of metadata/owner_of functions), parse transfer(from, to, token_id) events, and store them in a new nft_transfers table alongside cached metadata.

Key files

• wraith/src/ingester/ — event handler dispatch
• New: wraith/src/ingester/nft.ts
• New: migration adding nft_transfers and nft_metadata

Suggested execution

git checkout -b feat/nft-indexing

1. After fetching a contract's events, sniff its ABI to decide token type (fungible vs NFT)
2. For NFT contracts, decode transfer(from, to, token_id) events
3. Lazy-load metadata via metadata(token_id) call when first seen — cache it
4. Expose /nfts/transfers?contract=…&token_id=… and /nfts/owners/:contract/:token_id
5. Add tests with a known NFT contract on testnet

Example commit message:
feat(ingester): add CAP-46 NFT indexing with metadata caching

Acceptance criteria

• NFT contracts auto-detected
• Transfers persisted with token_id
• Metadata cached after first fetch
• Two new REST endpoints work end-to-end
• Tests pass against testnet

---

Drips Wave · Complexity: High · 200 points
Comment below to request assignment. PR must include Closes #[this issue].

[Ipramking]

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

Hey, I'd love to be assigned to this one.

This feature genuinely excites me because it's not just an incremental change, it's what turns Wraith into something unique in the Stellar ecosystem. There's no solid NFT activity explorer on Stellar right now and this is exactly the kind of work that fills that gap.

On the experience side, I've worked with Soroban event parsing before and have a decent understanding of how transfer events are structured at the contract level. I've also built TypeScript ingestion pipelines with similar dispatch patterns to what's already in the ingester folder, written database migrations for indexer schemas with caching layers, and done ABI sniffing to tell contract types apart by their exported functions. I've tested against Soroban testnet as well so the integration test piece is familiar territory.

For my approach I'd follow the suggested execution pretty closely. Sniff the ABI when a contract is first fetched, decode the transfer events with the token id, lazy load metadata on first sight and cache it, then wire up the two endpoints. I'd also make sure to handle contracts that look like NFTs but don't fully follow the spec since that kind of edge case tends to cause silent failures in indexers.

Let me know if you'd like me to share a more detailed plan before I start. Happy to do that.

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

[drips-wave]

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

🧑‍💻 @Ipramking: 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 🌊