Maxx Finance

Social Media Statistic Tracking

Temrite leveraged a python based query stack, implemented by Linux cron jobs to query and store social data to a postgres database back-end once daily. This query stack includes multiple API interactions, a custom discord bot and automated failover, allowing Maxx Finance to rest easy knowing their data will always be available.

Live Medium Article List

On top of the dashboard, Maxx Finance wanted to be able to deliver the latest news about the platform to their community. The most effective way to deliver this information was by using JavaScript to pull information directly from their Medium page. This integration allows them to continue business as usual, posting their updates to Medium and having it shared across the dashboard to all their users.

Web3 Contract Integration

From wallet less web3 connectivity to database queried Merkle tree roots, Temrite has implemented a rock solid Web3 foundation for the platform. Maxx Finance has a total of seven integrated contracts to the front-end, each with their own custom JavaScript files, staggered and gated implementation, and easily updatable logic if the contracts are to ever change. 

WalletConnect Functionality

With what seems like an unlimited number of wallet providers, it is mission critical to accept payment from as many of them as possible. Temrite has implemented not just MetaMask connectivity, but connectivity with any WalletConnect enabled wallet stack. While other projects redirect to YouTube videos on how to use MetaMask, Maxx Finance can focus on what matters. 

Uniswap Trade Integration

On the trading page Maxx Finance wanted the ability to directly trade their token from the dashboard. This was accomplished most effectively by utilizing the Uniswap Widget. This widget allows people using the dashboard to easily buy and sell $MAXX from within the dashboard making it a truly all-in-one place for their token.

Responsive Dashboard

A core requirement of Maxx’s platform is Web3 statistic display, regardless of a Web3 connection by a user. Almost every page of the Maxx platform incorporates an element of wallet less Web3 data displays from custom developed JavaScript. Previous user connections are cached, automatically pre-populating and re-connecting a user on load. 

There are several stages of deployment on Maxx’s roadmap, creating the need for different static displays during each phase for several pages. Temrite has developed a responsive Django rendering system to only paint relevant content to the stage of deployment the Maxx team is on, ensuring there is never any confusion from information presented on their website.

Universal Modal System

Large portions of the staking, amplifier and wallet connectivity displays are reliant on a nested modal structure. While many libraries exist for modals, none function properly for the extended functionality required by the Maxx team. 

Temrite leveraged our extensive web development experience to develop a custom modal library, allowing for several layers of nested functionality, all specific to one of many, many sub panels. This modal system is not just specific to Maxx Finance, so if you’re a prospective client with modal needs, look no further!

Web3 Referral System

Multiple pages of Maxx’s platform required the implementation of a cookie based (client requested cookie based) referral system. The presence of these cookies dynamically paints additional content to several pages, enabling users to extend Web3 functionality and rewards. Custom JavaScript was developed to handle the reading, parsing and caching of these cookies, giving the Maxx team more flexibility and customization options. 

NFT Collection System

Many projects are left waiting months and may never be granted an OpenSea API key. Temrite leveraged the power of local storage and delivery optimizations to curb the need for an OpenSea API key for real time NFT collection displays.

Staking System

Due to the nature of Web3 call interactions and the required functionality of the front-end, Temrite needed to reproduce critical portions of calculations and contract functionality in a secured, self-sustaining back-end loop and for use in front-end user interface implementations.

Again utilizing the power of Linux cron jobs, a fail-over safe back-end stack was implemented to track all stake data, event data, update user data and more, several times per minute. This data is securely serviced to the front-end utilizing local loads, reducing server load and user load times. 

Front-end development for the staking system required the implementation of a comprehensive, multi-layered responsive modal system, filtered database delivery and rendering, and responsive calculations all wrapped into dynamic web3 calls. 

Amplifier System

Utilizing GraphQL data queries, Temrite implemented a responsive dynamic initial content paint. Dynamically painted content also includes panel specific nested modal systems, Web3 interactivity and granular user data displays. Additionally, the Amplifier system required many elements to be nested from the staking system.

Free Claim System

The original design of the FreeClaim system has changed, originally requiring Temrite to hash and store over 60,000,000 Merkle proofs and provide a real time query experience for an end user. This was accomplished by major database pagination, server memory optimizations and customized Postgresql configurations. Regardless of index in the database, Temrite was returning queried stacks in just a few milliseconds longer than a typical API call.

Global API

From granular historic user data to real-time updated staking & user parsing, Temrite has developed and implemented a Postgresql based database system to handle a scalable user load. In addition to the public API, a private dashboard was created to allow updating & accessing of more sensitive data and an easy 30,000 ft overview of the project state. 

Many front-end display hooks are also built reliant on the REST API hooks Temrite created, providing a seamlessly smooth loading and navigation experience while loads are performed locally.