Gimbl meet the MGA
This month, we’ve been heavily investing in compliance to meet the MGA requirements in terms of rights management, limits, and permissions. We’re indeed required to implement singleton sessions, maximum session time when defined by the user, and other legal features to enforce.
Along the same lines, we’ve been implementing on-chain terms and conditions management and the development of the framework took us more time than expected. Indeed, for KYC-verified users, Moderators and Streamers, any time the MGA legally requires a Terms & Conditions update, we need to disable all users on the Smart Contracts until they approve the latest T&C versions corresponding to they associated roles. Plus, functional tests for this insane workflow have been a hell of a ride!
The Gimbl Challenge is ready
On the Smart Contract development side, we just finalized the Gimbl Challenge. Its goal is to let a user challenge a streamer by staking GIM tokens in our Smart Contract. For example, a user challenges a streamer on CS:GO to make 3 headshots in the next round. Then, if the streamer wins that challenge, i.e. she makes at least 3 headshots in the next round, she wins the amount of GIM the user staked.
Back-end and Front-end
In addition to that, the Back-end API is currently being improved to let users Donate to streamers GIM tokens too, directly from their internal or external wallet to a streamer’s default wallet.
On the Front end side, we’ve been looking at using Zeit since we are using Next.js now and we will update you soon with our venture feedback.
Stay tuned and gg!