The problem UZUMETA solves

Decentralizing and automating the scholarship program in web3 games

According to the report from DApp Radar, games are leading the usage and adoption of blockchain based on the number of unique active wallets, dominating 42% of all UAW.

However, there is a big blocker for new users to buy a NFT when they want to play a game and participate in its ecosystem. For example, when StepN was launched on January of 2022, a user had to buy shoes which costed at least $500 to participate in StepN. So a few blockchain games developed and operated a scholarship program, which was rental and revenue sharing mechanism.

However, the scholarship programs are not decentralized and automated, which has a trust problem between manager and scholar. That is, a scholar has to depend on a manager for the distribution of the earnings, which is not a trustless UX at all.

Therefore, UZUMETA solves the problem of the current scholarship program based on the smart contract of ERC-4907 and help gamers share revenues in an automated and trustless way.

Challenges we ran into

ERC4907 Smart contracts integration with games

• We developed ERC4907 Scholarship contract, which is the extension of ERC4907 standard. As our contract works as a NFT game scholarship protocol, we had to connect our contract to any on-chain game to demonstrate our project. We chose a sample P2E game from thirdweb. It was quite challenging to integrate their codes, which were implemented using thirdweb SDK, to our contract. Our project would be further developed to work as a seamless integration tools for scholarship systems.

Testnet network issues

• We had to send lots of transactions to interact with our deployed contracts. (e.g. minting different game item NFTs) However, the network status of Polygon mumbai testnet, where we deployed our contracts was bad. It took lots of times to simply send transactions to the network.

Huddles for registering World ID

• The application ‘Worldcoin’ was not supported from the Play/App Store in Korea. So we need to change the developer’s account to US.
• While registering with World ID, the device ‘Orb’ was needed to register the World ID. Since we could not have the device, we could not test the registration process thoroughly.