Tech Stack

WebRTC

WoStr network uses webrtc behind the scenes. There are typically 3 webrtc architectures and WoStr uses Mesh viaP2P . For more details, check this video.

Maps

WoStr network uses protomaps under the hood and does not rely on a third party mapping provider. This provides advanced capabilities to WoStr to support enhanced features currently and as we progress. Here is some learning about how that mapping system works from its creator Brandon.

Payments

WoStr network uses an independent payment processor, Zaprite for buying Watch Time. This allows the ability to accept the payments in a secure manner. Fiat payments are accepted using credit/debit cards and Crypto payments are accepted as Bitcoin Lightning SATS. For more details, checkout

Server

WoStr tries to onboard the web2 users into web3 in a manner that makes crypto semi-hidden. Only at touchpoints will fiat/kaspa/live tokens be visible. WoStr is sort of a web 2.5 project. bunjs is the server being used due to its performance characteristics and the ability to scale up vertically much more than its alternative node.js. Here is more info about bun.

Web Framework

WoStr uses ElysiaJS web framework for its core functional logic. For more details, check this.

Database

WoStr uses a streak of web2 technologies to engage the traditional users to onboard into web3. The persistent piece in this puzzle is sqlite. The web3 equivalent of that is the the Kaspa's KRC20 LIVE token which the streamer gets ultimately paid out in. For more info, check this...