Tokendesk

• 

  TokenDesk logo

Inspiration

Every great Web3 protocol begins with a design problem: tokenomics layout. Founders and smart contract engineers often rely on fragile, manual Excel spreadsheets to calculate and stress-test initial token supply distributions. A single mistyped formula can result in faulty allocations, rendering a smart contract model logically broken before a single line of Solidity is compiled.

We were inspired to build Tokendesk to create a premium, uncompromised single-screen workspace where architects can input metadata, dynamically manipulate major distribution tracks via synchronized sliders, and validate total protocol allocations instantly. We wanted to strip away the infrastructure bloat and build a high-fidelity utility desk that handles data constraints and session-saving seamlessly.

How We Built It

Tokendesk was built using a rapid, full-stack composition approach within the MeDo environment. We used plain-language prompts to outline strict business logic parameters, interactive states, and database structures.

1. State Engine: MeDo mapped a reactive frontend architecture that bridges bidirectional synchronization between HTML5 range inputs and traditional numeric input forms.
2. Database Layer: We structured a relational persistence context within the AI workflow, setting up user tables for secure authorization alongside a dedicated activity log schema to handle automated project saving and state hydration.
3. Reactive Math: The engine computes distribution allocations continuously using a reactive hook architecture, recalculating absolute supply allocations and validating constraints instantly upon state changes.

Challenges We Faced

Our primary technical challenge lay in constructing defensive logic boundaries within an interactive full-stack workspace. Syncing high-volume UI events (like dragging multiple responsive percentage sliders back-to-back) with instant database calculations can easily trigger state race conditions or float precision rounding errors.

We solved this inside MeDo by enforcing a single source of truth for calculations, wrapping input entries in automatic constraints (clamping values securely between 0% and 100%), and utilizing LaTeX-grade precision to round total integers cleanly before they hit the historical activity log database.

What We Learned

Building with MeDo completely re-engineered our perspective on software prototyping velocity. We learned how to write comprehensive markdown requirement architectures that AI agents can translate into full-stack, deployed code on the first try. More importantly, we realized that handling enterprise features like persistent user authentication and data logging doesn't require weeks of tedious routing infrastructure—it requires clear logic rules and powerful context management.

Mathematical Validation Logic

Tokendesk ensures systemic validation by enforcing that the sum of all core distribution fractions equates to unity:

$$\sum_{i=1}^{n} P_i = 100\%$$

Where $P_i$ represents the individual percentage allocations for our four foundational categories: Core Founders & Team ($P_{\text{team}}$), Ecosystem Treasury & Grants ($P_{\text{treasury}}$), Public Sale/IDO ($P_{\text{public}}$), and Community Rewards ($P_{\text{rewards}}$).

When the model balances perfectly, individual absolute token pool disbursements are dynamically rendered in the dispatch ledger using the target supply variable ($S_{\text{max}}$):

$$T_{\text{pool}} = S_{\text{max}} \times \left( \frac{P_i}{100} \right)$$

Built With

• full-stack-architecture
• localstorage-data-persistence
• medo-ai
• node.js
• product
• react
• tailwind-css
• typescript
• web3