No WebSocket payment mode — incompatible with most AI inference APIs

[winsznx]

Priority: P1 · Area: Ecosystem

mpp-session uses SSE, but most high-value inference providers (OpenAI, Anthropic, Google) stream via WebSocket. An agent running long inference jobs can't use mpp-session without the provider implementing a non-standard SSE wrapper, limiting RouteDock's addressable ecosystem.

Proposed fix: Add an mpp-session-ws mode variant that performs the WebSocket upgrade alongside channel establishment — open the channel, negotiate the voucher, then upgrade the HTTP connection to WebSocket.

---

RouteDock Drip Wave 6 backlog.

[bytebinders]

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

I understand that mpp-session currently relies on SSE, which limits compatibility with major AI inference providers that stream over WebSockets, and you want to introduce an mpp-session-ws mode that negotiates the session via HTTP first, then upgrades to WebSocket so long-running inference streams can be supported more broadly.

And I can deliver this clean and professional 😁😉

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

[bytebinders]

@winsznx can you please assign 😉

[delfinacorr]

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

Hi,i am full stack developer and blockchain ,I would like to apply to resolve this P1 priority issue. As a full-stack developer with experience in Web3 integrations and network architectures, I fully understand how the exclusive use of SSE limits RouteDock's AI agent ecosystem compared to leading providers like OpenAI or Anthropic.

My approach to implementing mpp-session-ws will be:

Hybrid Flow: Maintain the initial channel establishment and Stellar ticket negotiation using traditional HTTP.

Protocol Upgrade: Securely implement the upgrade handshake (Upgrade: websocket) after on-chain credentials are validated.

Bidirectional Streaming: Ensure that the new session handles real-time data transfer identically to standard inference APIs in the market.

Could you please assign me this task? Thank you very much!

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

[Truphile]

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

I'd like to work on this issue.

I've fixed similar overflow and arithmetic-safety issues in Rust and smart-contract codebases where unchecked calculations could trigger runtime traps instead of returning meaningful contract errors. In my experience, these bugs are especially important because they affect both security and user experience.

For this issue, I'll audit the affected multiplication paths, replace them with checked arithmetic, and ensure all overflow conditions return ExtError::InvalidAmount rather than causing host-function traps. I'll also add validation during initialization to prevent invalid configurations from being created in the first place.

In addition to implementing the fix, I'll add the requested regression test (test_overflow_guard_on_large_contribution) and verify normal group creation remains unaffected while ensuring the entire test suite passes without overflow-related panics.

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

[drips-wave]

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

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

[Ce-Royals]

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

I can work on this quickly

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

[0xElyte]

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

GM Ser Tim! I'd love to resolve this fast!

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

[OmniZlatoon]

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

I CAN DELIVER MAINTAINER! PLEASE ASSIGN AND SEE IT WORK

Hi maintainer sir, I'm called Junior Brown , a full-stack and smart contract engineer building on Stellar. I specialize in designing and shipping scalable, secure systems end-to-end, from Soroban smart contracts to production-ready backend infrastructure and user-facing applications.

I’ve worked on complex architectures involving automated agents, cross-chain logic, and data indexing, focusing on reliability, performance, and clean standards. My approach is very product-driven: I don’t just build contracts, I build complete systems that solve real user problems and can scale in production.

I’m especially interested in infrastructure, security, and automation creating tools and frameworks that make it easier for other developers to build safely and efficiently on Stellar.

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