StreamBuilder: validate C… contract recipient addresses

[Jaydbrown]

Parity with #587 (isValidAddress accepting C...). StreamBuilder should accept and correctly encode a contract recipient, or reject it with a clear message if unsupported.

[ZacLou]

I'd like to work on this issue. I have relevant experience with this tech stack and can deliver a clean, well-tested PR. I can submit within 1-2 days.

[Ranjeet2063]

Hi maintainers, I would love to be assigned to this issue.

I am an active core contributor in the Stellar/Soroban ecosystem (#1 contributor on Mova Store with 28 successfully merged PRs), with deep expertise across Soroban SDK smart contracts, cryptographic access controls, and production test suites.

🎯 Technical Execution Plan for StreamBuilder: validate C… contract recipient addresses:

1. Module & Storage Analysis: Pinpoint the exact contract modules in conduit-protocol/streamFi-sdk handling this logic. Define explicit storage DataKeys, TTL policies, and auth boundaries (require_auth()).
2. Canonical Soroban Implementation: Implement the required state changes, validations, and structured event emissions (env.events().publish(...)) adhering strictly to official Soroban best practices and zero arithmetic overflow/underflow.
3. Exhaustive Unit Test Suite: Build comprehensive tests covering:
   • Happy-path state transitions and expected outputs.
   • Boundary limits, edge cases, and zero/saturating values.
   • Negative tests asserting unauthorized callers (mock_auths(&[])) and invalid parameter reverts with exact ContractError variants.
4. CI & Verification Gate: Verify 100% clean cargo check, zero clippy warnings, and full test suite passing locally before opening the PR.

💡 Why Assigning Me Directly Benefits You:

• Zero Maintainer Overhead: Self-documenting code with exhaustive tests so you don't spend valuable time babysitting, debugging, or fixing CI.
• Fast Issue Closure: Production-grade PR delivered in 12–24h, cleanly clearing this issue off your backlog.
• Proven Reliability: 28 merged PRs as #1 contributor on Mova Store — guaranteed senior-level execution from day one.

[Fading-Dev]

Hi! I'd like to work on this issue.

I'm a software engineer with hands-on experience in testing, debugging, and building reliable features across the stack. I'm confident I can take this on and deliver a solid, well-tested solution that follows the project's existing conventions.

I'll make sure to cover the core functionality as well as relevant edge cases to keep things reliable and regression-resistant.

Let me know if I can get started, and I'll provide updates as I progress.

[Ranjeet2063]

Hello maintainers! 👋

I have submitted a fix in PR #697 for validating and correctly encoding Soroban contract recipient addresses (C...) in StreamBuilder with full parity to #587.

Overview of Changes

• Integrated isValidAddress in StreamBuilder._validateAddress and validatePayload.
• Validates that contract IDs (C...) are properly verified and encoded as ScAddressTypeContract in toContractArgs().
• Rejects malformed contract addresses with clear error messages.
• Added test suite in src/tests/builder-contract-recipient.test.ts with 5/5 passing tests.

PR: #697