Marketplace dapp is not just an opportunity for data monetization but also a content discovery tool, and publishers of open data are welcome to wrap their streams as free products on the Marketplace to showcase the content. This kind of content will become more common via upcoming Web3 collaborations. Featuring such open content will also feel more natural in the next iteration of Streamr dapp frontends, where the Marketplace and Core dapps will merge into Streamr Hub in advance of the Tatum milestone next year.

Data Union 3.0 framework changes
The upgrade makes things simpler for builders, and also achieves a similar strategic benefit as the Marketplace: the new architecture allows the Data Union DAO to partner with and expand the framework to various L1 and L2 chains in the future, tapping into the developer communities of each platform.

In a nutshell, the Data Union framework has streamlined. The 2.x versions involved the Mainnet and Gnosis chains for each Data Union, with complex bridging of tokens and messages across chains. The 3.0 release introduces Data Unions that exist on a single chain instead of two. On the other hand, for deploying a Data Union there is now a free choice of (that single) chain, allowing each Data Union project to deploy on the chain they prefer!

(So curiously, individual Data Unions changed from cross-chain to single-chain, while the framework itself went multi-chain! 🤯)

The Data Union framework also now has its own, dedicated client library available from npm! Consequently, starting from Streamr client version 7.0 (not yet released at the time of writing), the Streamr client will no longer contain the Data Union-related methods.

For more details about the Data Union 3.0 update, check out the Data Union DAO blog! twitter @Streamr