# 1. Introduction Institutional algorithmic trading has always operated behind closed doors. The infrastructure that powers systematic hedge funds, coordinated specialist agents, attributable decisions, auditable track records, and live risk enforcement, has never been accessible to anyone outside of a prime brokerage relationship or a quant team. maicrotrader brings that infrastructure on-chain. At the center of the platform is the **Strategy Builder**: a tool that lets users configure multi-agent trading vaults, run them against historical market data, and deploy them with full decision attribution logged on every trade. Depositors who prefer not to build can allocate capital through an **Allocation Trading Agent (ATA)**, a cross-strategy optimization layer that dynamically manages exposure across multiple deployed vaults based on live performance and the depositor's own risk parameters. This is on-chain wealth management, not passive exposure to a single opaque strategy. The engine beneath both surfaces is the **Multi-Agent Engine (MAE)**: a structured system where each vault runs a coordinated team of four specialist AI agents. A Quant Agent generates signals. A Portfolio Agent manages allocation. A Risk Agent enforces hard limits and holds veto authority over every trade. An Execution Agent routes orders on-chain. A Master Agent orchestrates the full workflow and validates every output against the vault's deployed policy. These agents do not operate in isolation. They hand off to each other in a defined sequence, and every decision is logged, attributed, and auditable. maicrotrader was built by a team with deep roots in institutional finance and blockchain infrastructure. That background shapes the product directly: the agent architecture mirrors how a systematic fund desk is organized, the risk controls are drawn from institutional practice, and the performance reporting is designed to be auditable rather than decorative. The platform is currently in **Open Beta**, a live single-vault trading system running on the MAE under real capital conditions. The Strategy Builder is in active development. # 2. Vision and Goals ### The Convergence Thesis Two worlds are colliding. Traditional finance built the most rigorous risk infrastructure in history systematic processes, specialist teams, auditable decisions, institutional accountability. Web3 built the most open financial infrastructure in history self-custody, transparent settlement, permissionless access, composable primitives. Neither is complete on its own. TradFi's rigour runs on opacity and gatekeeping. DeFi's openness runs on single-agent black boxes and unverifiable backtests. maicrotrader is built at the intersection. The thesis is direct: institutional-grade trading infrastructure belongs on-chain, operating transparently, in the custody of the people deploying the capital. # 2.1 Why Now Three converging forces make this the right moment. **AI coordination has crossed a threshold.** Specialized agent systems now reliably outperform single generalist models on structured, multi-step tasks. The architecture that powers a systematic fund, with specialist roles, defined hand-offs, and formal risk checks, can now be encoded in software that runs continuously, cheaply, and on-chain. **DeFAI has proven demand but failed on credibility.** Single-strategy agent vaults have attracted significant capital. But the category is littered with opaque decisions, collapsed tokens, and backtests that never held under live conditions. The market is ready for a platform that treats transparency and auditability as core product requirements, not marketing claims. **Self-custody infrastructure has matured.** Non-custodial vault standards, on-chain policy registries, and decentralized execution venues have reached the point where the full institutional workflow, configure, backtest, deploy, monitor, attribute, can execute entirely on-chain without a trusted intermediary holding keys. # 2.2 Goals maicrotrader aims to: Establish the Strategy Builder as the definitive configuration and deployment tool for multi-agent trading vaults, making institutional-grade strategy infrastructure accessible without requiring a quant team, a prime broker, or a trusted intermediary. Build the Permissionless Vault Network as the first strategy marketplace where every published vault carries a mandatory live seasoning record and an on-chain track history, so depositors can evaluate real performance before allocating capital. Launch ATA-based on-chain wealth management, giving depositors a single interface to hold a dynamically optimized portfolio of strategies, with full attribution across all positions. Set a new standard for auditability in on-chain trading: every trade traceable to its originating signal, every deployment policy-hashed on-chain, every strategy's track record immutable and publicly verifiable. # 3. How maicrotrader Works ## The Multi-Agent Engine (MAE) The Multi-Agent Engine is the trading infrastructure that runs every vault on the platform. It is not a single AI model making decisions. It is a structured system of four specialist agents, each with a defined role and scope, coordinated by a Master Agent that validates every output against the vault's deployed policy before any action reaches execution. The architecture deliberately mirrors how a systematic hedge fund desk is organized: | Agent | TradFi Counterpart | Role | | --------------- | ---------------------------------- | ------------------------------------------------------------------------------------------------------------ | | Master Agent | Chief Investment Officer | Orchestrates the full workflow, validates consistency, enforces policy compliance | | Quant Agent | Research Desk | Signal generation via technical indicators, funding rates, volatility, on-chain liquidity, and ML adaptation | | Portfolio Agent | Portfolio Manager | Asset selection, diversification, rebalancing, cash buffer management | | Risk Agent | Risk Officer (with veto authority) | VaR enforcement, drawdown circuit breakers, stress testing, position sizing, hedging | | Execution Agent | Trading Desk | Order routing, slippage optimization, timing, TWAP for large positions | Every agent action is logged, timestamped, and tagged to the signal or condition that triggered it. This event log is what makes full decision attribution possible: every trade in the platform's history can be traced back to the specific agent, signal, and risk check that produced it. The Risk Agent holds structural veto authority. No trade reaches the Execution Agent without passing a risk check. This is not a soft alert. It is an architectural constraint. # 3.1 Strategy Trading Agents (STAs) An STA is a deployed trading vault running on the MAE. Each STA is an independent instance: its own configuration, its own policy hash stored on-chain, its own capital, its own track record. When a user builds and deploys an STA via the Strategy Builder, they are configuring the policy that governs each of the four sub-agents: which signals the Quant Agent monitors, how the Portfolio Agent manages concentration and rebalancing, what hard limits the Risk Agent enforces, and how the Execution Agent routes trades. That policy is hashed and recorded on-chain at deployment. It cannot be silently changed. STAs that meet the seasoning requirements, a minimum period of live operation with real capital, can be published to the Permissionless Vault Network, where other users can deposit directly into their strategy. # 3.2 Allocation Trading Agents (ATAs) An ATA is the on-chain wealth management layer for depositors who want managed exposure across multiple strategies rather than direct configuration of a single vault. A depositor sets their risk parameters once, including target allocation, maximum drawdown tolerance, and acceptable strategy types, and the ATA dynamically manages their capital across the available pool of published STAs. It reallocates based on live performance, drawdown signals, and correlation between active strategies. The ATA is how maicrotrader functions as an on-chain wealth management platform rather than a single-strategy product. Strategy creators get a distribution channel. Depositors get a portfolio rather than a position. The MAE runs the logic for both. # 4. Open Beta The Open Beta is a live trading vault operating on the MAE under real capital conditions. It is not a simulation or a demo. It is the proof that the Multi-Agent Engine works. The current vault runs a delta-neutral strategy on perpetual futures, managed by all four specialist agents operating under the architecture described above. Every trade is executed on-chain. The decision log is live. Performance statistics are public. **What the Open Beta demonstrates:** The MAE runs continuously without human intervention. The Risk Agent's veto authority is live: trades that breach policy parameters do not reach execution. The full decision attribution pipeline is instrumented and producing data. The vault has operated under live market conditions including significant volatility periods. **What the Open Beta is not:** It is not the final product. It is one proprietary strategy running as a single configured instance of the MAE. The Strategy Builder, the surface that lets users configure their own STAs with their own policies, is what converts the engine into a platform. **Traction to date:** * Over $3M in cumulative trading volume processed through the vault * Peak TVL of $70K reached within two weeks of public launch, with no paid liquidity incentives * 90+ consecutive days of live operation * $MAICRO token live on-chain, tracked on CoinGecko and DexScreener * 22% of token supply in native staking at time of writing The Open Beta is the engine running in one configuration. The Strategy Builder is the interface that makes the engine configurable by anyone. # 4.1 Live Strategy Overview Rather than taking a bet on whether crypto markets (or a specific coin) will go up, we are taking a bet that some coins will do better than others. Built by two Finance PhDs with extensive quantitative trading experience and published research, the **system addresses a fundamental challenge in digital asset markets: generating consistent returns in both bull and bear market conditions.** Whereas the price of any given cryptocurrency may be determined, for example, by conditions in the overall stock market, monetary policy or general investor sentiment, we are betting instead that certain crypto are going to perform relatively better or worse. Thus, even if the markets fall as a whole, the strategy may continue to perform consistently. Of course, if the crypto markets face a bull market, the hedged exposure means that our strategy may not catch that uptrend, instead profiting only on differences between different cryptocurrencies. In either case, our thesis is that if our trading strategy performance behaves like its backtest period, the strategy should consistently deliver returns in bull and bear markets. While all investors would benefit from being buy-and-hold investors in crypto (as well as other assets), the returns of this strategy should be highly complementary to a buy-and-hold strategy and should see attractive diversification benefits in their portfolio. # 4.2 Random Forest Methodology ## Our Goal Our goal is to model the relationship between certain predictors and future cryptocurrency price movements. In machine learning, this boils down to projecting returns onto different variables or ”features” that can be used to describe the relationship between data and returns. ### The Model We utilize a random forest model. Traditional econometric approaches fail to capture these non- linearities due to their parametric assumptions and inability to model higher-order feature interactions. [**Random Forest**](#user-content-fn-1)[^1] represents a significant advance in machine learning, leveraging bootstrap aggregation and random feature subsampling to construct a collection of decorrelated decision trees. Each tree in the forest is trained on a bootstrap sample of the historical data and considers only a random subset of features at each split node. This dual source of randomness serves two critical functions: * it reduces overfitting through variance reduction * enables the capture of complex feature interactions that would be computationally intractable in traditional models. The algorithm’s power emerges from its non-parametric nature. Unlike linear models that impose rigid functional forms, each decision tree recursively partitions the feature space based on variance reduction, automatically discovering threshold values and interaction effects. The ensemble aggregation, through averaging of individual tree predictions, provides robust return estimates that are invariant to outliers and capable of modeling arbitrary non-linear response surfaces. In the context of financial time series, Random Forest excels at identifying regime-dependent patterns. The algorithm can simultaneously model scenarios where momentum indicators drive return magnitudes while liquidity, volatility and microstructure signals determine return distributions. This adaptive capacity is particularly valuable in cryptocurrency markets where regime shifts occur frequently and unpredictably. [^1]: Random forests or random decision forests is an [ensemble learning](https://en.wikipedia.org/wiki/Ensemble_learning) method for [classification](https://en.wikipedia.org/wiki/Statistical_classification), [regression](https://en.wikipedia.org/wiki/Regression_analysis) and other tasks that works by creating a multitude of [decision trees](https://en.wikipedia.org/wiki/Decision_tree_learning) during training. # 4.3 Dual-Model Architecture Our system ”ensembles” two Random Forest models operating on distinct temporal resolutions, one derived using **intraday features calculated from hourly bars** and **intraday features across days**. * The intraday model processes hourly data, developing metrics that quantify aggressive trading behavior, volume price divergences, and cross-venue arbitrage signals. * The daily model operates on lower-frequency data, identifying persistent trends and structural shifts in market dynamics. Its feature set encompasses multi-period momentum indicators, volatility regime metrics, and cross-asset correlation structures. At the time of writing, we have over 20 different variables that we combine in the modeling exercise across the **intraday** and **daily** frequencies. Going forward, we will continue to update the list of predictors that enter our model. The prediction target is formulated as the return: $$ r\_{i,t+1} = \frac{P\_{i,t+1}}{P\_{i,t}} - 1 $$ \ \ with the Random Forest out-putting continuous return predictions: $$ \hat{r}\_{t+1} = f(\mathbf{X}\_t) $$ where ***X****t* represents the feature vector at time ***t***. Feature preprocessing employs rank transformation and winsorization[^1] to mitigate the impact of extreme observations common in cryptocurrency data. The feature engineering emphasizes normalized measures that remain stationary across varying market conditions. The models undergo periodic retraining on a frequent basis, ensuring adaptation to evolving market conditions while maintaining sufficient historical context for robust pattern recognition. We set our hyperparameters for the models to be conservative. **After both models are trained separately, the models are combined through a risk parity framework that allocates weights such that both the intraday and daily models contribute equally to portfolio risk, preventing dominance by the more volatile predictions.** [^1]: # 4.4 Performance/Backtest Below we present the results of the standard backtest using data **from the end of 2024 to June 2025**. ### Assumptions 1. We model **transaction costs with taker fees** and the **assumption that we are paid the funding rate to short and pay the funding rate to go long**, **trading at end of day**. 2. We select only the most liquid contracts on Hyperliquid, where we plan to trade. We are running this at low leverage, even though in principle Hyperliquid perpetual futures permit us to scale up exposure as desired. ### Results **The turnover is around 60% and the after-cost Sharpe ratio is 2.61 using Hyperliquid’s prices**, **earning 94.1% annualized over the sample period**. Below, we plot the profit and loss curve of the hypothetical long-short portfolio. Some appealing aspects of the strategy: * Heightened performance during the month of April 2025, during which we see a large period of aggregate market turmoil. * This highlights the advantages of a long-short strategy - when cryptocurrencies melt down, the performance of the strategy remains resilient to directional market movements since the marketwide-induced fall in the long leg is offset by a corresponding move in the short leg. While past performance does not guarantee future performance, the strategy exhibits attractive performance over the sample period.

Figure 1: Hypothetical growth of 1$ invested

# 5. The Strategy Builder The Strategy Builder is maicrotrader's core product. It is the interface for configuring, backtesting, and deploying STAs, multi-agent trading vaults running on the MAE, without requiring a quant background, a developer, or a prime broker relationship. The central design principle: **show your work**. Every template ships with a real on-chain track record. Every backtest shows funding rate drag, slippage, and regime breakdown, not just the headline return. Every deployed vault generates a per-agent attribution feed that explains every trade in plain terms. The Strategy Builder is in active development. The sections below describe the confirmed product specification. # 5.1 Builder Modes The Strategy Builder offers three progressive depth modes. Users start at the level that matches their experience and move deeper as needed. **Mode A: Template** Select from a curated set of maicrotrader-built STAs with proven live capital track records. No configuration required. Choose a template, name the STA, set deposit size, review the mandatory backtest preview, and deploy. Each template card displays: live Sharpe ratio, maximum drawdown, and the number of months the strategy has operated under real capital. The core discipline: every template ships with a track record from the platform's own capital, not a synthetic backtest. There are no unverified presets. **Mode B: Guided Widget Form** Structured configuration per agent. Each sub-agent, Quant, Portfolio, Risk, and Execution, has its own configuration panel with labeled sliders, dropdowns, and number fields. No free-text prompts. No LLM-generated strategy code. Two complexity levels within Mode B: Simple (three to four essential parameters per agent, safe defaults everywhere else) and Advanced (full parameter set exposed). The interface defaults to Simple. A live risk preview updates as parameters change: "At this drawdown limit with this leverage cap, your estimated maximum loss on a $50K deposit is $7,500." **Mode C: Policy DSL (V1.1+)** A structured, constrained scripting interface for users who need to express logic that widget forms cannot capture, including agent hand-off conditions, composite signal rules, and custom rebalance triggers. Token-gated at the \[TBC] $MAICRO staking tier. Mode C is deliberately deferred to V1.1. The rationale: widget users will reveal the specific friction points they cannot navigate through sliders and dropdowns. Mode C is designed around those observed gaps, not hypothetical power-user needs. #### Pre-Deploy Backtest Gate The backtest is not optional. Every STA must clear it before deployment. The output shows: cumulative return, Sharpe ratio, maximum drawdown, regime-by-regime breakdown (including known stress periods), estimated fee and funding rate drag, and a plain-English risk summary. Results below configurable thresholds route back to the configuration step with specific parameter suggestions. #### Deploy Confirmation At deployment, the STA policy is hashed and recorded on-chain. A plain-English summary describes exactly what the vault will do. A seven-day cooldown applies to policy changes after initial deployment. This prevents mid-cycle interference with open positions. # 5.2 Live Vault Dashboard The dashboard is where a deployed STA is monitored. The design philosophy is a **trading floor desk view**, not a crypto portfolio tracker. **Living org chart**, the central visual element. Four agent nodes displayed in the coordination structure, each showing: current state (Running / Watching / Standby), last action with timestamp, and individual PnL contribution. **PnL attribution bar**, which splits total vault returns, by agent contribution: * Quant Agent: signal-driven alpha contribution * Portfolio Agent: rebalancing value * Risk Agent: avoided drawdown value (the losses prevented are the contribution) * Execution Agent: slippage savings versus market order baseline This is how a multi-strategy fund reports to LPs. It is the only surface in on-chain trading that attributes returns to specific decisions rather than showing a single net number. **Decision attribution feed**, a chronological log of every agent action, formatted as: *"Execution Agent filled ETH long 0.42 ETH, limit order, 0.09% slippage, funding window avoided. Risk Agent approved (VaR post-trade 3.2%, within policy limit). Outcome: +$18.40"* Every trade has an entry. Every entry shows which agent acted, what data triggered it, what the risk check produced, and the post-hoc P\&L result. # 6. Security and Auditability **maicrotrader treats auditability as infrastructure, not a feature.** **Self-custody architecture:** Users retain full custody of their funds at all times. No private keys are held by the platform. Vault contracts are non-custodial by design. **On-chain policy hashes:** Every STA's configuration policy is hashed and recorded on-chain at deployment. Any change to the policy generates a new hash and a new on-chain record. There is no mechanism to silently alter a deployed vault's behavior. **Immutable decision log:** Every agent action is recorded in a structured event log: `signal_emitted`, `risk_check_passed`, `risk_check_blocked`, `order_submitted`, `order_filled`, `rebalance_triggered`. This log is the basis for the attribution feed visible in the dashboard and cannot be retroactively modified. **Risk Agent veto by architecture:** The Risk Agent's authority is not a soft check. No trade can reach the Execution Agent without passing a Risk Agent validation against the vault's deployed policy parameters. This is enforced at the system level, not the UI level. **Smart contract audits:** The vault contract infrastructure is subject to independent security audit prior to the Strategy Builder launch. Audit reports will be published publicly. **Seasoning-gated vault network:** Strategies must demonstrate live performance under real capital before being published to the vault network. The seasoning record is on-chain and verifiable by any depositor before allocating capital. The combination of non-custodial architecture, on-chain policy records, immutable decision attribution, and mandatory seasoning is what makes "auditable" a structural claim rather than a marketing claim. # 6.1 External Audit **maicrotrader's first vault is audited by Quill Audits.** \ Announcement: \ Audit report: # 7. Roadmap The roadmap reflects the current build sequence: the MAE Transition (converting the single-vault monolith into a formally modular multi-agent system) is the prerequisite for a Strategy Builder that is genuinely configurable, not a UI over a hardcoded engine. **Closed Beta (Q1 2026, Completed)** Launched proprietary trading vault with initial MAE architecture. Seeded TVL from core team. Deployed initial agent performance dashboard. Completed external security audit. **Open Beta / Public Onboarding (Q2 2026, Live)** Opened vault access for $MAICRO holders. Enabled USDC deposits. Shipped vault statistics dashboard with Sharpe, drawdown, and PnL attribution. Live: over $3M trading volume, $70K peak TVL. **MAE Transition (In Progress)** Converting the current single-vault monolith into a properly modular multi-agent system with formal agent boundaries, typed event logs, per-agent attribution instrumentation, and the policy configuration layer that the Strategy Builder requires beneath it. This is the engineering prerequisite for the Strategy Builder to be real. **Strategy Builder V1 (Q3 2026 Target)** Shipping the Strategy Builder with: STA configuration UI (Modes A and B), runtime agent attribution dashboard, pre-deploy backtest gate, permissionless vault network with seasoning gate, and $MAICRO staking tiers. **Governance and Staking (v0.3)** $MAICRO staking for protocol governance. Token holders vote on platform features and fee structures. Advanced vault diagnostics and metrics for depositors and strategy creators. **Permissionless Vault Network (v1.0)** Full public vault network with creator bonding, seasoning-gated publishing, and depositor-facing copy-allocation infrastructure. **ATA Wealth Management Layer (v2.0)** Allocation Trading Agents enabling depositors to allocate across multiple published STAs with dynamic rebalancing based on live performance and user-set risk parameters. The full on-chain wealth management surface.
# 8. $MAICRO Token: Full Tokenomics ### Overview $MAICRO is the utility and alignment layer for the maicrotrader platform. Total supply is 980,000,000 tokens (1,000,000,000 original supply minus 2% burned by Virtuals during fee restructuring). The token is live and actively traded, currently tracked on CoinGecko and DexScreener. Token demand is structurally tied to platform activity, not speculation. The three mechanisms that make this true are staking tiers, creator bonding, and the fee buyback loop. Each is described in full below. *** ### Token Distribution | Allocation | Tokens | % of Supply | State | | ------------- | --------------- | ----------- | ---------------------------------------------------------------------- | | Public | 840,000,000 | 86% | In market, actively traded | | Team | 70,000,000 | 7% | 3-year vesting, 6-month cliff from January 2025, linear from July 2025 | | R\&D | 30,000,000 | 3% | Research and protocol development | | Investor Pool | 20,000,000 | 2% | Reserved for investors and advisors | | Rewards | 10,000,000 | 1% | Campaigns, content, referrals, community rewards | | Reserve | 10,000,000 | 1% | Held for ecosystem growth and key adoption moments | | **Total** | **980,000,000** | **100%** | | # 8.1 Staking Tiers and Capabilities Staking $MAICRO unlocks progressively deeper capabilities in the Strategy Builder. Tiers are tied to genuine capability expansion, not arbitrary feature paywalls. The core product is accessible without staking. Deeper configuration depth and the ATA allocation layer require skin in the game. | Tier | Stake Required | Vault Fee Rebate | Base APY (fee-driven) | Capabilities Unlocked | | ----------------- | ---------------- | ---------------- | --------------------- | ---------------------------------------- | | Analyst | 10,000+ $MAICRO | 0.020% | \~5% | Governance vote access | | Trader | 50,000+ $MAICRO | 0.018% | \~10% | Priority vault execution | | Portfolio Manager | 100,000+ $MAICRO | 0.016% | \~15% | Exclusive agent pool access | | Fund Manager | 200,000+ $MAICRO | 0.013% | \~20% | Higher ATA allocations | | CIO | 500,000+ $MAICRO | 0.010% | \~25% | First access to new agents, council seat | #### Lockup Multipliers Time-locked staking earns bonus APY on top of the base tier rate: | Lockup Duration | APY Multiplier | | --------------- | --------------- | | 30 days | 1.0x (no bonus) | | 90 days | 1.2x | | 180 days | 1.4x | #### Staker Yield Formula The staker APY is fee-driven, not inflationary. It derives entirely from platform trading activity: ``` Staker_APY = (Platform_Fee_Revenue × Buyback_Rate × Staker_Share) / Total_Staked_Value ``` Where: * `Platform_Fee_Revenue` = aggregate of all trading fees and vault performance fees generated across deployed STAs * `Buyback_Rate` = 0.60 (60% of the 0.7% trading fee flows to buybacks) * `Staker_Share` = 0.25 (25% of bought-back tokens are distributed to stakers; 75% are permanently burned) * `Total_Staked_Value` = current market value of all $MAICRO in staking contracts As platform TVL and deployed STA volume grow, fee revenue grows proportionally, increasing staker yield without any new token issuance. # 8.2 Fee Structure maicrotrader generates fees from two sources: #### Trading Fee (0.7%, paid in cbBTC) The primary fee on all vault trades, collected in cbBTC. | Allocation | Share | Use | | ----------------- | ----- | -------------------------------------------------- | | Buybacks | 60% | Purchase $MAICRO from open market | | Team (Operations) | 30% | Held in cbBTC, funds audits, liquidity, operations | | Treasury | 10% | Additional buyback, held in $MAICRO | #### Vault Trade Fee (0.02%, paid in USDC) A smaller fee on individual vault-level trades. | Allocation | Share | Use | | ---------------------------- | ----- | ------------------------------------------------- | | Team | 50% | Held in USDC | | Staker and depositor rebates | 30% | Buybacks shared with stakers and vault depositors | | Treasury | 20% | Held in USDC | #### Buyback Mechanics Of all $MAICRO purchased via buybacks: * 75% is permanently burned, reducing circulating supply * 25% is distributed to active stakers as yield #### Dynamic Scaling The buyback intensity is designed to scale with market conditions: ``` Buyback_Intensity(t) = Base_Rate × (Target_MC / Current_MC)^α ``` Where `α` controls the scaling aggressiveness. At low market cap relative to target, buybacks are aggressive, compressing supply. As market cap grows toward target, the system normalizes, shifting weight from burns toward larger staker rewards and treasury growth. This prevents the protocol from burning aggressively at a point when supply reduction has diminishing return. # 8.3 Liquidity Mining Program (Open Beta) \[Concluded] ### Liquidity Mining Program (Open Beta) 10,000,000 $MAICRO tokens (1% of supply) were allocated as rewards for vault depositors during the Open Beta, across three monthly seasons. | Season | Dates | $MAICRO Allocated | Share of Pool | | -------- | ------------------------- | ----------------- | ------------- | | Season 1 | March 3 to March 31, 2026 | 5,000,000 | 50% | | Season 2 | April 1 to April 30, 2026 | 3,000,000 | 30% | | Season 3 | May 1 to May 31, 2026 | 2,000,000 | 20% | Rewards are distributed proportionally to each depositor's share of vault TVL per season. Season 1 depositors earned 2.5x more $MAICRO per dollar than Season 3 depositors at equal TVL, because the Season 1 pool was 2.5x larger. #### Vesting Schedule for Mining Rewards | Phase | % of Rewards | Date | Notes | | --------------- | ------------ | ------------------------- | --------------------------------------------------------------- | | Proof-of-Reward | 5% | April 1, 2026 | Small unlock at end of Season 1, immediately claimable | | Growth Lock | 0% | April to May 2026 | No tokens claimable during Seasons 2 and 3 | | Vesting Cliff | 25% | June 7, 2026 | First major unlock, one week after program end | | Linear Vesting | 50% | June 7 to August 30, 2026 | Daily linear unlock over 12 weeks | | Loyalty Unlock | 20% | August 30, 2026 | Final unlock, requires maintaining vault deposit through period | # 8.4 Flywheel Mechanics ### Flywheel Mechanics The token economy compounds through five interlocking loops. Each loop reinforces the others. **Loop 1: Fee Flow** Vault deposits generate trading volume. Volume generates fees. Fees fund buybacks. Buybacks reduce circulating supply and reward stakers. **Loop 2: Burn Loop** As platform usage grows, 75% of each buyback is permanently removed from supply. Deflationary pressure increases as TVL and STA count scale. The token becomes structurally scarcer as the platform becomes more successful. **Loop 3: Staker Yield** Staking locks tokens from circulation, reducing float. Stakers earn fee-derived yield without new issuance. Higher yield attracts more stakers, which reduces float further, which increases price support per unit of buyback spend. **Loop 4: Creator Loop** Creators bond $MAICRO to publish strategies. Successful strategies attract depositor capital. More capital generates more fees. Fees pay creator royalties and fund buybacks. Successful creators build reputation, attract more depositors, deepening the loop. **Loop 5: Demand Loop** Capability tiers require staking. As the Strategy Builder adds more configuration depth and ATA access, the value of being at higher tiers grows. Demand for staking positions grows with platform capability, independent of speculative price action.
#### Formal Flywheel Equation The flywheel's self-reinforcing property can be expressed as: ``` TVL(t+1) = TVL(t) × (1 + g_strategy + g_depositor) where: g_strategy = new STA deployments × average capital per STA g_depositor = ATA inflow driven by published track records Fee_Revenue(t) = TVL(t) × Fee_Rate Buyback_Volume(t) = Fee_Revenue(t) × Buyback_Rate Burn_Rate(t) = Buyback_Volume(t) × 0.75 Circulating_Supply(t+1) = Circulating_Supply(t) - Burn_Rate(t) Staker_Yield(t) = (Buyback_Volume(t) × 0.25) / Total_Staked(t) ``` The key property: as long as TVL grows, fee revenue grows, buyback volume grows, burn accelerates, and staker yield improves, all simultaneously. The loops do not compete. They compound. *** ### Supply Trajectory At current burn mechanics and projected usage growth, the circulating supply declines monotonically as long as the platform is generating fees. The loyalty unlock model (20% of mining rewards requiring sustained vault deposits) also reduces sell pressure at each vesting cliff by ensuring the final and largest tranche only reaches depositors who are still engaged with the platform. Team tokens vest linearly from July 2025 to July 2028, with a 6-month cliff. No team tokens enter circulation before July 2025. The vesting schedule is on-chain and verifiable. *** *Exact staking tier thresholds and bond rates are pending final confirmation and will be published prior to Strategy Builder launch.* # 9. Team Core Team **Khing Oei, Founder** Khing spent over two decades in institutional finance before building maicrotrader. His career spans Goldman Sachs Special Situations, Fortress Investment Group, and Bardin Hill, culminating in the founding and operation of Eyck Capital, an independent hedge fund. He is also the founder of Treasury, a Netherlands-based Bitcoin treasury company backed by Winklevoss Capital and Nakamoto, planned for listing on Euronext Amsterdam. The architecture of the Multi-Agent Engine, with specialist agents, formal risk veto authority, and attribution-first reporting, is drawn directly from how institutional systematic desks are organized. **Temo Bezhiashvili, Co-Founder and CEO** Temo brings over seven years of blockchain infrastructure experience to maicrotrader. He co-founded a blockchain development firm and has worked with MIT Media Lab and government-level blockchain initiatives. He is the founder of Bitnet, a Georgian cryptocurrency exchange. His background spans the full Web3 stack: protocol design, product development, and exchange infrastructure. **Ken Hung, CTO** The CTO brings seven-plus years of experience architecting blockchain platforms, IoT products, and mobile applications. He led the technical build of a $50M+ NFT staking and GameFi platform, and developed a decentralized prediction market selected for the Draper University accelerator, one of 20 projects accepted from over 400 applicants. He has shipped IoT products with over 100,000 registered devices. Core stack: Rust, Flutter, Swift. Deep expertise in DeFi protocol design, smart contract development, and scalable backend systems. # 10. Official Links 🔗 Follow our X: 💬 Join our Community: 📣 Join our Updates Channel: 📈 DexScreener: 🦎 CoinGecko: 💰 $MAICRO Hydrex LP: ⚖️ CA: 0xE74731ba9d1Da6Fd3C8c60Ff363732bebAc5273E # 11. Glossary **ATA (Allocation Trading Agent):** The cross-STA capital optimization layer. An ATA dynamically manages a depositor's capital across multiple published STAs based on live performance and user-defined risk parameters. The on-chain wealth management surface for depositors who do not want to configure individual strategies. **Backtest Gate:** The mandatory pre-deployment simulation step in the Strategy Builder. Every STA must pass a historical performance simulation before deployment is permitted. Results show cumulative return, Sharpe ratio, maximum drawdown, regime breakdown, and estimated fee and funding rate drag. **Creator Bonding:** The mechanism by which strategy creators stake $MAICRO as a slashable bond to publish an STA to the Permissionless Vault Network. The bond is subject to slashing if the strategy is found to have been misrepresented. **DeFAI:** Decentralized Finance AI. The category describing AI-native protocols that operate autonomously on-chain, distinct from AI tools that assist human traders. **Execution Agent:** The MAE sub-agent responsible for order routing, slippage optimization, timing decisions, and trade execution on-chain. **MAE (Multi-Agent Engine):** The trading infrastructure beneath every vault on the platform. Comprises four specialist agents (Quant, Portfolio, Risk, Execution) coordinated by a Master Agent. **Master Agent:** The orchestrating agent in the MAE. Validates consistency across sub-agent outputs, enforces policy compliance, and manages workflow sequencing. **Permissionless Vault Network:** The strategy marketplace where published STAs are available for third-party deposits. Entry requires completion of the seasoning period. All track records are on-chain and verifiable. **Policy DSL:** Mode C of the Strategy Builder. A constrained, structured scripting language for expressing agent hand-off conditions and composite signal logic that widget forms cannot capture. Token-gated at the Power staking tier. **Policy Hash:** A cryptographic hash of an STA's deployed configuration, recorded on-chain at deployment. Any configuration change produces a new hash and a new on-chain record. **Portfolio Agent:** The MAE sub-agent responsible for asset selection, position sizing, diversification, rebalancing, and cash buffer management. **Quant Agent:** The MAE sub-agent responsible for signal generation via technical indicators, funding rates, volatility analysis, on-chain liquidity data, and ML-driven adaptation. **Risk Agent:** The MAE sub-agent responsible for VaR enforcement, drawdown circuit breakers, stress testing, and position-level risk controls. Holds structural veto authority over every trade before it reaches the Execution Agent. **Seasoning:** The mandatory live operation period an STA must complete before it can be published to the Permissionless Vault Network. Requires real capital deployment over a minimum number of days. **STA (Strategy Trading Agent):** A deployed trading vault running on the MAE. Each STA has its own configuration policy, on-chain policy hash, capital, and immutable track record. **Strategy Builder:** The core product surface for configuring, backtesting, and deploying STAs. Offers three depth modes: Mode A (templates), Mode B (guided widget form), Mode C (Policy DSL, V1.1+). # Terms and Conditions *Last updated: February 28, 2026* These Terms and Conditions ("**Terms**") govern your access to and use of the maicrotrader website, documentation, web application/terminal, related services, and any associated content (collectively, the "**Services**"). By accessing or using the Services, you agree to be bound by these Terms. If you do not agree, do not use the Services. These Terms should be read together with our [Privacy Policy](https://docs.maicrotrader.com/privacy-policy), [Cookie Policy](https://docs.maicrotrader.com/cookie-policy), and [Disclaimer](https://docs.maicrotrader.com/disclaimer). *** ### 1. Operator and Contact The Services are operated by **Temo Bezhiashvili** ("**we**", "**us**", "**our**"), doing business as **Mairo** / **maicrotrader**. **Email:** *** ### 2. Eligibility You must be at least **18 years old** (or the age of majority in your jurisdiction, whichever is higher) and have the legal capacity to enter into these Terms. You are responsible for ensuring that your use of the Services complies with all laws and regulations applicable in your jurisdiction. The Services are not available to persons or entities subject to international sanctions or located in jurisdictions where the use of such services is prohibited. *** ### 3. No Investment Advice The Services may provide information, analytics, automation tools, AI-powered trading agents, or software enabling interaction with third-party protocols. **Nothing in the Services constitutes investment advice, financial advice, legal advice, tax advice, or a recommendation** to buy, sell, or hold any digital asset. Past performance, historical results, backtests, simulations, or example outcomes are **not indicative of future results** and do not guarantee profitability. You are solely responsible for your own investment decisions and activities. You should obtain independent professional advice where appropriate. *** ### 4. High-Risk Warning Digital assets and related markets are **highly volatile and speculative**. You may lose some or all of the funds you use in connection with the Services. Use only funds you can afford to lose entirely. Risk factors include, but are not limited to: market volatility, liquidity constraints, smart contract vulnerabilities, protocol exploits, regulatory changes, network congestion, oracle failures, MEV extraction, sandwiching attacks, funding rate fluctuations, and liquidation mechanics. *** ### 5. Non-Custodial Nature and Third-Party Protocols Unless explicitly stated otherwise in writing: * We do **not** take custody of your assets at any time. * You interact with **third-party wallets, smart contracts, blockchains, networks, and protocols** entirely at your own risk. * We do not control blockchains, validators, third-party protocol operators, or decentralized governance processes. Blockchain transactions may be **irreversible**. You are responsible for verifying all addresses, parameters, and transaction details before confirming any transaction. *** ### 6. AI-Powered Trading Agents and Automation The Services include AI-powered trading agents and automation features that may execute trades, manage capital allocation, and perform portfolio rebalancing within vaults autonomously. By using these features, you acknowledge and agree that: * Trading decisions within vaults are made by automated AI systems based on quantitative models and market data, without manual human intervention for each trade. * Automated systems may behave unexpectedly due to market conditions, data anomalies, software errors, or unforeseen interactions with third-party protocols. * Slippage, liquidity constraints, MEV/sandwiching, oracle issues, funding rates, liquidation mechanics, and other market factors can cause losses even when the system operates as designed. * We do not guarantee any profit, yield, return, or specific performance outcome from any strategy, agent, or vault. * You are responsible for understanding the risks of automated trading before depositing funds into any vault. *** ### 7. Vault Interactions and HyperLiquid Vault functionality within the Services operates on **HyperLiquid** and potentially other third-party decentralized protocols. By depositing into or interacting with vaults, you acknowledge that: * Vault performance depends on market conditions, protocol functionality, and the behavior of AI trading agents. * HyperLiquid is a third-party protocol with its own terms, risks, and governance. We do not control HyperLiquid's infrastructure, smart contracts, or operational decisions. * Deposits, withdrawals, and trade executions are subject to the rules, fees, and mechanics of the underlying protocol. * Protocol-level risks include smart contract bugs, exploits, governance changes, downtime, network congestion, and liquidation events. *** ### 8. Service Availability and Changes We may modify, suspend, or discontinue any part of the Services at any time, with or without notice. We do not guarantee uninterrupted availability or that the Services will be error-free, secure, or free from vulnerabilities. Scheduled or unscheduled maintenance, upgrades, or protocol changes may temporarily affect your ability to access the Services or interact with vaults. *** ### 9. User Accounts and Wallet Connections You may need to connect a wallet or use third-party authentication services (including **Privy**) to access certain features. You are responsible for: * Maintaining the security of your devices, wallet keys, seed phrases, and authentication credentials * All activity conducted through your wallet connection or authenticated session * Ensuring that your wallet software and connected devices are secure and free from malware We are not responsible for losses caused by compromised wallets, phishing, malware, SIM swaps, social engineering, key mismanagement, or user error. *** ### 10. Prohibited Uses You agree not to: * Use the Services for any unlawful purpose or in violation of any applicable law or regulation * Attempt to interfere with, disrupt, or compromise the integrity or security of the Services * Reverse engineer, decompile, scrape, or abuse the Services, except as permitted by applicable law * Transmit malware, viruses, or engage in fraudulent, deceptive, or manipulative activity * Violate sanctions, export-control laws, or anti-money laundering regulations * Use the Services to manipulate markets or engage in wash trading, spoofing, or other forms of market abuse * Circumvent any access restrictions, rate limits, or security measures We may restrict or terminate access if we reasonably believe prohibited use is occurring. *** ### 11. Token-Gated Features Certain features of the Services (such as premium support, vault access, or terminal functionality) may require meeting specific conditions, including holding a specified amount of a token or staking requirements. Any such requirements will be described within the Services. We reserve the right to change feature requirements, access rules, and eligibility criteria at any time. *** ### 12. Fees If fees apply (including performance fees, service fees, management fees, or protocol-level fees), they will be described in the Services or associated documentation. Third-party protocols may independently charge fees, including gas fees, trading fees, funding rates, and withdrawal fees, which are outside our control. *** ### 13. Intellectual Property We and our licensors own all rights in the Services, including software, algorithms, models, text, graphics, branding, and documentation, except where otherwise stated. You receive a limited, non-exclusive, non-transferable, revocable license to access and use the Services for lawful purposes in accordance with these Terms. This license does not grant you any rights to our intellectual property beyond what is necessary to use the Services. *** ### 14. User Content and Feedback If you submit content to us (including support messages, bug reports, or feedback), you grant us a worldwide, royalty-free, perpetual, irrevocable license to use, reproduce, modify, and incorporate that content to operate, improve, and support the Services. Do not submit confidential information you do not wish to share with our team. *** ### 15. Third-Party Services The Services may integrate with or link to third-party services, including wallets, exchanges, protocols, authentication providers, and analytics tools. We are not responsible for third-party services, their availability, security, or performance. Your use of third-party services may be governed by their own terms and policies. Key third-party services integrated with the Services include: * **Privy** — authentication and wallet connection * **HyperLiquid** — vault execution and trading infrastructure * **Framer** — website hosting * **GitBook** — documentation hosting *** ### 16. Disclaimers TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, THE SERVICES ARE PROVIDED **"AS IS"** AND **"AS AVAILABLE"**. WE DISCLAIM ALL WARRANTIES, WHETHER EXPRESS, IMPLIED, OR STATUTORY, INCLUDING WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, NON-INFRINGEMENT, AND ANY WARRANTIES ARISING FROM COURSE OF DEALING OR USAGE OF TRADE. We do not warrant that: * The Services will meet your requirements or expectations * The Services will be uninterrupted, timely, secure, or error-free * Any results, outputs, trading performance, or AI agent behavior will be accurate, reliable, or profitable * Defects will be corrected in a timely manner *** ### 17. Limitation of Liability TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW: WE WILL NOT BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES, OR ANY LOSS OF PROFITS, REVENUE, DATA, GOODWILL, OR DIGITAL ASSETS, ARISING OUT OF OR IN CONNECTION WITH YOUR USE OF THE SERVICES. WE WILL NOT BE LIABLE FOR LOSSES ARISING FROM: * Market volatility, adverse trading conditions, or investment losses * Third-party protocol failures, governance changes, or smart contract bugs or exploits * Network outages, congestion, reorganizations, or transaction failures * MEV extraction, sandwiching attacks, or front-running * Oracle failures or data inaccuracies * Liquidation events * AI agent errors, unexpected behavior, or suboptimal performance * User error, compromised wallets, phishing, malware, or key mismanagement IF LIABILITY IS FOUND NOTWITHSTANDING THE ABOVE, OUR TOTAL AGGREGATE LIABILITY FOR ALL CLAIMS ARISING OUT OF OR RELATED TO THESE TERMS OR THE SERVICES IN ANY 12-MONTH PERIOD SHALL NOT EXCEED THE GREATER OF: (A) THE FEES ACTUALLY PAID BY YOU TO US FOR THE SERVICES DURING THAT PERIOD, OR (B) **USD 100** (OR ITS EQUIVALENT), UNLESS APPLICABLE LAW REQUIRES OTHERWISE. *** ### 18. Indemnification You agree to indemnify, defend, and hold harmless Temo Bezhiashvili and any affiliates, contributors, or service providers from and against any claims, damages, losses, liabilities, costs, and expenses (including reasonable legal fees) arising out of or related to: * Your use of or access to the Services * Your violation of these Terms * Your violation of any applicable law or any third-party rights * Any dispute between you and a third party relating to the Services *** ### 19. Dispute Resolution #### Informal Resolution Before initiating any formal proceeding, you agree to contact us at and attempt to resolve the dispute informally for at least **30 days**. #### No Class Actions TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, YOU AGREE THAT ANY DISPUTES WILL BE RESOLVED ON AN INDIVIDUAL BASIS. YOU WAIVE ANY RIGHT TO PARTICIPATE IN A CLASS ACTION, COLLECTIVE ACTION, OR REPRESENTATIVE PROCEEDING. *** ### 20. Governing Law These Terms are governed by and construed in accordance with the laws of **Georgia**, without regard to conflict-of-law principles. *** ### 21. Force Majeure We shall not be liable for any failure or delay in performing our obligations under these Terms where such failure or delay arises from circumstances beyond our reasonable control, including but not limited to: natural disasters, acts of government, blockchain network failures or congestion, protocol-level outages or exploits, internet disruptions, cyberattacks, power failures, pandemics, or acts of war or terrorism. *** ### 22. Severability If any provision of these Terms is found to be invalid, illegal, or unenforceable by a court of competent jurisdiction, that provision shall be modified to the minimum extent necessary to make it enforceable, or if modification is not possible, it shall be severed. The remaining provisions shall continue in full force and effect. *** ### 23. Entire Agreement These Terms, together with the Privacy Policy, Cookie Policy, and Disclaimer, constitute the entire agreement between you and us regarding the Services and supersede all prior agreements and understandings. *** ### 24. Termination We may suspend or terminate your access to the Services at any time, with or without notice, if we believe you have violated these Terms, pose a security risk, or if required for legal or regulatory reasons. You may stop using the Services at any time. Upon termination, provisions that by their nature should survive (including disclaimers, limitation of liability, indemnification, and dispute resolution) shall remain in effect. *** ### 25. Changes to These Terms We may update these Terms from time to time. When we make changes, we will update the "Last updated" date at the top of this page. Your continued use of the Services after changes are posted constitutes your acceptance of the updated Terms. If you do not agree to the updated Terms, you must stop using the Services. *** ### 26. Contact **Temo Bezhiashvili** **Email:** # Privacy Policy *Last updated: February 28, 2026* This Privacy Policy explains how **maicrotrader** (also referred to as, "**we**", "**us**", "**our**") collects, uses, shares, and protects personal data when you use: * maicrotrader.com * app.maicrotrader.com * docs.maicrotrader.com (collectively, the "**Services**"). This policy should be read together with our [Cookie Policy](https://docs.maicrotrader.com/cookie-policy) and [Terms and Conditions](https://docs.maicrotrader.com/terms-and-conditions). *** ### 1. Data Controller **Data Controller:** Temo Bezhiashvili **Email:** *** ### 2. What Personal Data We Collect #### A) Data You Provide * Contact details (e.g., email address, Telegram handle) when you contact support, join waitlists, or create an account * Messages and support requests, including any content you send to us * Preferences such as language, theme, notification, or marketing preferences #### B) Data Collected Automatically * Device and technical data, including IP address, browser type and version, operating system, device identifiers, and screen resolution * Usage data, including pages visited, features used, clicks, scroll depth, error logs, and performance metrics * Approximate location derived from your IP address * Referral source (how you arrived at the Services) #### C) Authentication and Wallet Data * Wallet address(es) you connect through Privy or other supported authentication methods * Authentication tokens and session data managed by Privy to maintain your logged-in state * Embedded wallet data, if you create a wallet through Privy's embedded wallet feature * Login method metadata (e.g., whether you authenticated via email, social login, or external wallet) #### D) Web3 and Blockchain Data * Public on-chain transaction data associated with your connected wallet address(es), as available on public blockchains * Interaction data with smart contracts and protocols, including deposits, withdrawals, and trade execution events on HyperLiquid and other integrated platforms, to the extent linked to your wallet **Note:** On-chain data is publicly available on the blockchain and is not controlled by us. We cannot modify or delete blockchain records. *** ### 3. How We Use Personal Data We use personal data to: * Provide, operate, and maintain the Services, including wallet authentication and vault interactions * Process transactions and execute trading strategies through our AI-powered systems * Maintain security, prevent fraud and abuse, and protect users * Respond to inquiries and provide customer support * Improve, debug, and optimize the Services through analytics and performance monitoring * Communicate service updates, security notices, and operational information * Comply with legal obligations and enforce our Terms and Conditions If we send marketing communications, you can opt out at any time by following the unsubscribe instructions in the communication or by contacting us. *** ### 4. Legal Bases for Processing Where applicable (including under the GDPR and similar data protection laws), we rely on the following legal bases: * **Contract:** To provide the Services you have requested, including account creation, wallet connection, and vault access. * **Legitimate interests:** For security, fraud prevention, service improvement, internal analytics (where permitted), and protecting the rights and safety of our users and the Services. * **Consent:** For non-essential cookies, optional analytics or marketing communications, and other processing where consent is required by law. * **Legal obligation:** To comply with applicable laws, respond to lawful requests from authorities, and fulfill regulatory obligations. *** ### 5. Automated Decision-Making The Services use AI-powered trading agents that execute trades and manage capital allocation autonomously within vaults. These systems make automated decisions regarding trade execution, risk management, and portfolio rebalancing based on quantitative models and market data. These automated processes operate on aggregated market and vault-level data. Individual user deposits into vaults are managed collectively, and automated trading decisions are not made on the basis of individual user profiling. You are not subject to decisions based solely on automated processing that produce legal effects or similarly significantly affect you as an individual. If you have questions or concerns about automated processing, please contact us at . *** ### 6. Cookies and Tracking We use cookies and similar technologies as described in our [Cookie Policy](https://docs.maicrotrader.com/cookie-policy). Where required by law, we request your consent before setting non-essential cookies. *** ### 7. How We Share Data We may share personal data with the following categories of recipients: **Service providers and processors** who process data on our behalf, including: | Provider | Purpose | | ------------------------- | -------------------------------------------------------------- | | **Privy** | User authentication, wallet connection, and session management | | **Framer** | Website hosting and delivery (maicrotrader.com) | | **GitBook** | Documentation hosting (docs.maicrotrader.com) | | **HyperLiquid** | Vault execution and on-chain trading infrastructure | | **Analytics provider(s)** | Usage analytics and performance measurement | **Other recipients**, where necessary: * Professional advisers (legal counsel, auditors) where required * Law enforcement or regulatory authorities, if required by law or to protect rights and safety * Parties involved in a business transfer (e.g., merger, acquisition, or restructuring), subject to appropriate protections We do **not** sell personal data. *** ### 8. International Transfers Personal data may be transferred to and processed in countries outside your country or region of residence. Where such transfers occur, we use appropriate safeguards as required by applicable law, including contractual protections and reasonable security measures, to ensure your data remains protected. *** ### 9. Data Retention We retain personal data only as long as necessary for the purposes described in this policy. Our general retention periods are: * **Account and authentication data:** For the duration of your active use of the Services, plus 12 months after last activity * **Support communications:** 24 months from resolution * **Security and fraud prevention logs:** 12 months * **Analytics data:** 14 months * **Legal and compliance records:** As required by applicable law We may retain data for longer periods where necessary to establish, exercise, or defend legal claims, or to comply with legal obligations. On-chain data exists permanently on public blockchains and cannot be deleted by us. *** ### 10. Your Rights Depending on your location, you may have the right to: * **Access** your personal data and obtain a copy * **Correct** inaccurate or incomplete data * **Delete** your data (subject to limitations, including the inability to modify on-chain records) * **Restrict** or **object to** certain processing activities * **Data portability** — receive your data in a structured, commonly used format * **Withdraw consent** at any time where processing is based on consent * **Lodge a complaint** with a data protection supervisory authority in your jurisdiction To exercise any of these rights, contact us at . We will respond within the timeframe required by applicable law (typically 30 days). *** ### 11. Security We implement reasonable technical and organizational measures designed to protect personal data against unauthorized access, loss, misuse, or alteration. These measures include encryption, access controls, and regular security reviews. However, no system can guarantee absolute security. *** ### 12. Children The Services are not intended for individuals under **18** years of age (or the age of majority in your jurisdiction). We do not knowingly collect personal data from children. If we become aware that we have collected data from a child, we will take steps to delete it promptly. *** ### 13. Third-Party Links and Protocols The Services may contain links to third-party websites, wallets, exchanges, decentralized protocols, or other external services. We are not responsible for the privacy practices of these third parties. We encourage you to review their privacy policies before providing any personal data. Key third-party services integrated with the Services include: * [Privy](https://www.privy.io/privacy-policy) * [HyperLiquid](https://hyperliquid.xyz) * [Framer](https://www.framer.com/privacy/) * [GitBook](https://policies.gitbook.com/privacy-and-security/statement) *** ### 14. Changes to This Policy We may update this Privacy Policy from time to time to reflect changes in our practices, technology, legal requirements, or for other operational reasons. When we make material changes, we will update the "Last updated" date at the top of this page. We encourage you to review this policy periodically. *** ### 15. Contact Us If you have any questions about this Privacy Policy or our data practices, please contact: **Temo Bezhiashvili** **Email:** # Cookie Policy *Last updated: February 28, 2026* This Cookie Policy explains how maicrotrader (also referred to as "**we**", "**us**", "**our**") uses cookies and similar technologies on: * maicrotrader.com * app.maicrotrader.com * docs.maicrotrader.com (collectively, the "**Services**"). This policy should be read together with our [Privacy Policy](https://docs.maicrotrader.com/privacy-policy). *** ### 1. Data Controller **Data Controller:** Temo Bezhiashvili **Contact email:** *** ### 2. What Are Cookies and Similar Technologies? Cookies are small text files placed on your device when you visit a website. We also use similar technologies, including: * Local storage and session storage * Pixel tags and web beacons * SDK identifiers (where applicable) For simplicity, we refer to all of these collectively as "**cookies**" throughout this policy. *** ### 3. Why We Use Cookies We use cookies to: * Operate the Services and deliver core functionality * Authenticate users and maintain secure sessions * Maintain security and prevent fraud or abuse * Remember your preferences and settings * Measure and improve performance through analytics * Measure marketing effectiveness (only where enabled and consented to) *** ### 4. Cookie Categories #### A) Strictly Necessary Cookies *(always active)* These cookies are essential for the Services to function and cannot be disabled. They include cookies used for: * Security, including bot protection and abuse prevention * Load balancing and basic site operation * Storing your cookie consent preferences * User authentication and session management * Wallet connection sessions via Privy (see Section 5) **Legal basis:** Legitimate interest — these cookies are required to provide the Services you have requested. #### B) Functional / Preference Cookies These cookies remember choices you make, such as language, region, theme, and UI settings. Disabling them may cause some features to not work as intended. **Legal basis:** Consent (EU/EEA/UK) or legitimate interest (other regions). #### C) Analytics Cookies These cookies help us understand how visitors interact with the Services so we can identify issues and improve the user experience. For users in the EU/EEA/UK, we only set analytics cookies after you provide consent, unless a lawful exemption applies under local law. **Legal basis:** Consent (EU/EEA/UK) or legitimate interest (other regions). #### D) Marketing Cookies Marketing cookies help us measure campaign performance and may support retargeting or advertising. These cookies are only placed after you provide consent where required by applicable law. **Legal basis:** Consent. *** ### 5. Third-Party Cookies Certain third-party services integrated into the Services may set their own cookies on your device. We do not control the cookies set by these third parties. Below is a summary of the key third-party services that may place cookies: | Provider | Purpose | Cookie Type | | ------------------------- | ------------------------------------------------------------------------------------------ | ------------------------------- | | **Privy** | Wallet connection, user authentication, and session management across app.maicrotrader.com | Strictly Necessary | | **Framer** | Website hosting, performance, and delivery of maicrotrader.com | Strictly Necessary | | **GitBook** | Hosting and delivery of docs.maicrotrader.com | Strictly Necessary / Functional | | **Analytics provider(s)** | Usage analytics and performance measurement | Analytics | Privy may use cookies, local storage, and session storage to manage wallet connections (including embedded wallets), authentication tokens, and session state. These are essential to the functioning of the application and are classified as strictly necessary. For details on how these third parties handle data, please refer to their respective privacy policies: * [Privy Privacy Policy](https://www.privy.io/privacy-policy) * [Framer Privacy Policy](https://www.framer.com/privacy/) * [GitBook Privacy Policy](https://policies.gitbook.com/privacy-and-security/statement) *** ### 6. Cross-Domain Tracking The Services operate across multiple subdomains (maicrotrader.com, app.maicrotrader.com, docs.maicrotrader.com). Some cookies — particularly those related to authentication and session management via Privy — may be shared across these subdomains to provide a seamless user experience. We do not use cross-domain tracking for advertising purposes. *** ### 7. Cookie Retention * **Session cookies** expire when you close your browser. * **Persistent cookies** remain on your device for a set period or until you delete them. Retention periods vary by cookie but typically range from 30 days to 12 months. * **Authentication tokens** managed by Privy persist for the duration of your active session and may be refreshed automatically while you remain logged in. The specific retention period for each cookie is displayed in our cookie banner or preference center, where available. *** ### 8. Your Choices and How to Manage Cookies #### Cookie Banner / Preference Center Where required by law, we request your consent before placing non-essential cookies (analytics and marketing). You can change your preferences at any time by: * Clicking the "**Cookie Settings**" link in the website footer (where available) * Clearing your browser cookies and revisiting the site to reset your choices #### Browser Controls Most modern browsers allow you to view, block, or delete cookies through their settings. Please note that blocking strictly necessary cookies may prevent parts of the Services from functioning correctly. For instructions, consult your browser's help documentation: * [Chrome](https://support.google.com/chrome/answer/95647) * [Firefox](https://support.mozilla.org/en-US/kb/enhanced-tracking-protection-firefox-desktop) * [Safari](https://support.apple.com/guide/safari/manage-cookies-sfri11471/mac) * [Edge](https://support.microsoft.com/en-us/microsoft-edge/manage-cookies-in-microsoft-edge-view-allow-block-delete-and-use-168dab11-0753-043d-7c16-ede5947fc64d) #### Wallet and Session Data To clear authentication and wallet session data set by Privy, you can disconnect your wallet within the application or clear your browser's local storage for app.maicrotrader.com. *** ### 9. Updates to This Policy We may update this Cookie Policy from time to time to reflect changes in the cookies we use or for other operational, legal, or regulatory reasons. When we make material changes, we will update the "Last updated" date at the top of this page. We encourage you to review this policy periodically. *** ### 10. Contact Us If you have any questions about our use of cookies, please contact us at: **Email:**