YieldBricks Community AMA Ep.03/08: MEXC Assesment Zone $ Weekly Updates

The Spaces addressed the project’s unexpected placement into MEXC’s 30-day assessment zone due to a spread requirement breach, despite exceeding other listing metrics. The host explained the timeline (Aug 15–Sep 15, with removal by Sep 18), clarified that API trading and bots are disabled during the period, and outlined short-term impacts on volume, visibility, and third‑party data feeds (CoinGecko/CMC). The team will resolve the spread by tightening order books with its market maker, but the label remains for the full assessment window. They observed healthier, organic trading without bots and will use these insights to plan strategic buybacks and liquidity restructuring across DEX, Ethereum, Arbitrum, and CEX venues. Parallel priorities include launching the revamped website (with metrics, APIs, and documentation), shipping Dashboard 2.0 and features (Treasuries, VIP zone), finalizing legal structure and a property sale to unlock budget within 1–2 weeks, and preparing an equity raise (potential Dubai meetings). A new CTO/lead developer will be onboarded next week, community incentive programs will follow the website release, and the team committed to weekly status updates and tighter exchange coordination to avoid future surprises.

Project Briefing: MEXC Assessment Zone, Operations, Roadmap, and Funding

Context and Speakers

• Host (name not stated): Led the entire briefing, covered exchange status, operations, roadmap, and funding.
• Noah: Core developer referenced by the host; credited with having delivered ~90–95% of past features (except the “Treasures” module).

Executive Summary (Key Takeaways)

• The token’s pair on MEXC was labeled into the “assessment zone” without prior notice; root cause is a spread requirement miss, not liquidity or holder count.
• The label persists for a standard 30-day assessment window (Aug 15–Sep 15), irrespective of early remediation; earliest removal expected by Sep 18.
• API trading (market makers, bots, arbitrage) is disabled during the period; CMC/CG data feeds may be partially impacted. Expect lower reported volume and some friction for new entrants.
• Remediation is straightforward: compress the order-book spread below 2% by placing additional bids/asks; plan coordinated with market makers (MMs).
• Strategy pivots short term: legal finalization and property sale to unlock budget; website and Dashboard 2.0 launch; measured buybacks first, then gradual liquidity deployment; marketing after foundational elements are in place.
• Team: recruiting a new CTO/main developer next week to stabilize and accelerate delivery.
• Community: imminent incentive programs, structured comms, and content overhaul post-website release.

MEXC Assessment Zone: What Happened and Why

• Trigger: On Thursday, an email (to their market maker) indicated the pair would be placed into MEXC’s assessment zone. The team initially assumed a misfire (as happened 2–3 times previously), but MEXC later confirmed the action.
• Internal report (received Friday night) shows project exceeds MEXC minimums in 3 of 4 tracked areas:
  • Holders on MEXC: Minimum 100; project has ~600.
  • Token value held on MEXC: Minimum >$50k; project ~<$200k across MM and related wallets.
  • Liquidity: No deficiency flagged.
  • Spread: The only metric missed; requirement is spread below 2%. This will be fixed by adding more layered orders on both bid/ask sides.
• Assessment window: Aug 15–Sep 15, with up to 3 days for finalization; target delabel by Sep 18.
• No exception policy: Even if spread is fixed immediately, label remains until window closes. MEXC indicated they do not make exceptions.

Operational Impact of Assessment Label

• Trading/API effects:
  • API trading blocked: Affects the project’s MM, exchange’s own bots, and arbitrage bots.
  • External data feeds: CoinGecko and CoinMarketCap APIs may be partially blocked/limited on the MEXC side; external tracking might be unreliable for up to four weeks.
• Market effects:
  • Likely lower visible volume and reduced attractiveness to new investors during the period.
  • Counterintuitive positive signal observed: With bots off, there has been virtually no selling over ~48 hours and organic volume looks cleaner, offering better insight for upcoming buybacks and budgeted injections.

Remediation Plan and Exchange Communication

• Immediate fix: Compress spread below 2% by adding more resting bids/asks; plan is agreed with MMs and should be executable within days.
• Timeline reality: Label remains throughout assessment (cannot be shortened), so focus shifts to communications and optics while the fix is in place.
• Communications gap with MEXC:
  • Team had no prior visibility into the exchange’s internal metrics since listing (~10 months). They are pushing for periodic reporting/access to avoid surprises.
  • Goal: Establish a process to monitor key MEXC metrics (holders, token value on exchange, spread) to stay safely above thresholds.

Liquidity, Buyback, and Market Strategy

• Sequence and rationale:
  • First: secure legal clarity and close the property sale to unlock budget.
  • Then: execute buybacks and clear residual sell pressure.
  • Liquidity: add gradually and strategically across venues once buybacks and legal are squared away; avoid heavy, premature liquidity which would cap upside and self-suppress a potential reversal.
• Venues and distribution:
  • Plan to rebalance across DEXs, Ethereum, Arbitrum, MEXC, and potential new CEXs.
  • Final liquidity plan depends on buyback capacity (e.g., $10k vs $100k scenarios lead to different structuring). Expert inputs (MMs) will drive final allocations.
• Observations with bots disabled:
  • Organic flow reveals minimal remaining sell pressure.
  • Provides cleaner inputs for budgeted injections and supports a phased liquidity strategy.

Product, Website, and Data

• Website (No. 1 near-term priority):
  • Status: Minor update was pushed Friday; full content polishing and finalization underway. Target release: as soon as Monday/Tuesday (exact hour TBD due to workload and calls with MMs/devs).
  • Goals: Clear, up-to-date, single-source hub with metrics, APIs, forms, exchange links, FAQs, blogs, legal docs, roadmap, and onboarding content. Better first-contact experience to match the true scope of the business.
  • Metrics visibility: External MEXC-linked data may be limited during assessment; internal metrics approach will be reviewed next week once behavior is confirmed. Worst case, full fidelity returns after Sep 15.
  • Socials: Updating outdated cover images and assets across channels alongside website launch.
• Dashboard 2.0 and features:
  • Post-website, the team will release Dashboard 2.0 and integrate sub-features including “Treasures” and VIP-zone-specific functions.
  • A detailed tutorial roadmap will accompany releases to clarify next steps for users.

Legal, Funding, and Runway

• Legal structure: In final third-party review. All internal tasks completed last week. Final revision of legal documentation expected by Wednesday.
• Property sale: Agreements aligned for 4–5 weeks; after final docs, the remaining payment will be requested. Close estimated within ~1 week thereafter. This unlocks operational budgets and reduces day-to-day cash prioritization stress.
• Prospective raise (Dubai trip): Host is arranging 3–4 high-value meetings; if confirmed, travel next week; otherwise the following week. A successful raise would “unlock on a whole other level” (expand portfolio, increase marketing and team budgets). Not a main urgency now but strategically important.

Team and Delivery

• CTO/Main Developer upgrade:
  • Timeline: Next week; final internal decision in the coming days. One meeting deferred due to the MEXC situation.
  • Profile sought: Not perfection, but reliable delivery, strong alignment with business/legal, willingness to stretch, and solid communication skills (important for a remote-first team).
  • Risks to avoid: Misalignment leading to rework (experienced previously when developers optimized for ease rather than alignment with evolving legal/architecture).
• Developer credits: Noah delivered ~90–95% of existing features; “Treasures” remains the notable exception.
• Delivery philosophy: Tighten deadlines, avoid missed commitments, ensure legal-technical consistency before shipping.

Community and Marketing

• Marketing pacing: Broad campaigns deferred until legal clarity, website, and priority features are in place—to avoid expensive churn from premature exposure.
• Community incentive programs:
  • Launch immediately after the website (forms/links hosted there).
  • Multiple roles with appropriate rewards; two experienced community managers will coordinate.
  • Reboot “rating/engagement” channels with more advanced and broader RWA/community-keys coverage.
• Targeting: Narrow, high-intent audiences first; retain newcomers with better onboarding and content before scaling.

Risks, Unknowns, and Mitigations

• MEXC data/API behavior during assessment: Potential CMC/CG sync limitations; internal metrics impact unknown—will be validated in the next 3–5 days. Worst case, wait until Sep 15.
• Exchange exceptions: None expected; assessment window is fixed. Comms are slow but ongoing.
• Operational hiccups: An internal OTC distribution mis-copy sent tokens to three wrong wallets; identified and corrected. Emphasis on tightening internal processes during restructuring.

Near-Term Timeline and Milestones

• Aug 15–Sep 15: MEXC assessment window (label persists regardless of early spread fix). Sep 18 latest to be delabeled.
• Monday–Tuesday: Website content finalization and release target (time TBD). Post-launch: community incentive programs go live.
• Next week:
  • Introduce new CTO/main developer and resume Dashboard 2.0 + “Treasures”/VIP feature rollout plan.
  • Final legal documentation review by Wednesday; proceed with property sale close and budget unlock steps.
  • Publish finalized MM plan for spread compression and liquidity roadmap.
• Funding: Dubai meetings next week (or the week after) contingent on confirmations.
• AMA cadence: Next AMA likely mid-week (host has a weekend wedding), then weekly/biweekly updates on the assessment status and other milestones.

Closing Notes from the Host

• The assessment label is not a fundamental negative; it will be resolved by spread compression and time.
• Development, legal, and structural priorities continue on track.
• Community sentiment is improving; the team is focused on durable delivery and clear communication through the restructuring phase.