Bug/dead-code: `StreamsModule.callerAddr` is never read and is miscomputed as `ZERO_ADDR` for async wallet adapters

[Jaydbrown]

src/streams.ts:77 declares private readonly callerAddr: string; and :108 sets this.callerAddr = this._signerPublicKey() in the constructor.

• Never read. Every method uses _getSenderAddress() / _resolveCallerAddress() or a local callerAddr. grep -n 'this.callerAddr' src/ shows only the write.
• Miscomputed. _signerPublicKey() (:131-139) calls this.activeWallet.getPublicKey() synchronously and only keeps the result if (typeof pk === 'string'). WalletAdapter.getPublicKey() may return Promise<string> (the async branch in _resolveCallerAddress handles exactly that), in which case _signerPublicKey falls through to ZERO_ADDR.

Impact

Dead field carrying a wrong value. Harmless today only because nothing reads it — a latent trap for anyone who wires it in.

Suggested fix

Delete the field, or make it a lazily-resolved cache that shares _resolveCallerAddress's async path.

[Naajih09]

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

Hi, I'd like to work on this issue. I've gone through the description and acceptance criteria and I'm confident I can deliver it. I'll make sure every acceptance criterion is met and submit a clean, tested PR. Please assign it to me.

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

[olacodes-01]

@olacodes-01 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi Maintainer, I have reviewed this issue and i have relevant experience on it. Please assign to me. I look forward to delivering an excellent work.

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

[TheHalalHunter]

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

Hi maintainer
I’d love to help out with this issue. I’ve checked the current codebase/documentation and know exactly what needs to be updated to make this clearer. I will ensure everything aligns perfectly with your existing contribution guidelines.

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

[0xElyte]

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

I'd love to resolve this issue fast

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

[drips-wave]

Congratulations, @TheHalalHunter! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

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