Game3.js Newsletter #11
A Sneak Peek at Game3.js / OP Arcade v2 and Today's Explorable: Liquidity Pools
Welcome to Issue #11 of the
We started Game3.js with a vision:
5 to 10 years from now, what will fully realized Web 3.0 games look like?
Today’s blockchain games are just the early iterations of Web 3.0 games. A fully realized Web 3.0 game will need to be more compelling than web, mobile, console, and VR games. Their virtual economies will need to have the same utility as those of sovereign fiat currencies. They will need to provide more meaning in people’s lives than just being a vehicle for intrusive ads and forced in-app purchases.
To achieve this vision, we need to bring in more builders, and make it as easy as possible for them to start building games in this new Web 3.0 world.
Game3.js aspires to be the game framework that will lead the way 🔥
Thank you for joining us in this quest!
A Sneak Peek at Game3.js / OP Arcade v2
In our previous newsletter we discussed breaking down Game3.js into more manageable components to improve the developer experience. Work continues on that front, and one of our challenges has been architecting the SDK to be as engine and stack agnostic as possible. We have settled on our initial architecture, and are plugging in the pieces one by one. We’ll update our documentation as more components come online.
Overview Diagram of the SDK’s npm run scripts
OP Arcade is our showcase of what Game3.js can provide game developers, where we already provide tournaments with crypto payouts. We’ve started building a v 0.2 of OP Arcade alongside the SDK, and we’re excited to show more in the next few weeks and months! Here’s another sneak peek of our prototype screens below.
Early version of OP Arcade v2’s Mockups
Today’s Explorable: Liquidity Pools
At the end of every newsletter we’ll dive deeper into Web 3.0 using explorables.
There are a lot of concepts in Web 3.0 such as Non-fungible Tokens (NFTs) and Decentralized Finance (DeFi) that may be new to game developers, and there’s no better way to become more familiar with them than through play 🎮
On the last newsletter we discussed Order Books, a record of buy and sell requests for one asset in exchange for another.
We used the Zagreus Trading Card (ZTC) and $ as the assets for our Order Book, based on the Steam Community Market example.
There’s one important thing to note when we use an Order Book system for handling trades: A trade won’t happen unless a buyer is matched with a seller.
In Web 3.0, Automated Market Makers like Uniswap solve this issue by using Liquidity Pools.
A Liquidity Pool is simply a pool of two kinds of assets. It can be drawn from so that traders can instantly convert their asset to the other, without needing a specific buyer or seller to trade with. The conversion rate is determined by an algorithm which the market maker wants to use.
For this observable we’ll use the algorithm used by Uniswap, which is:
Token1Supply * Token2Supply = CONSTANT
We've illustrated the pool below, along with a graph showing the pricing curve that corresponds to the algorithm.
We can use the sliders to see how the price of $ / ZTC changes as we adjust the variables.
Check out the source code here!
Thank you for reading! If you would like to contribute to game3.js, do check us out on Gitcoin Grants. You can also reply to this e-mail, or reach out via Github or Gitter.
We’d also love it if you’d share this newsletter to anyone who wants to know more about games and Web 3 🎮
Cheers and see you next issue!