PRE-TESTNET • SEPTEMBER 2026

BASED MOER
DOCUMENTATION.

Based Moer is a pixel-first onchain ecosystem built around original IP, holder experiences and proprietary market intelligence. These docs explain the current product, how the major systems connect, what is already available, and which safety gates remain before testnet execution and later production releases.

VIEW RELEASE STATUSBACK TO WEBSITE

1. Overview

Based Moer combines the Moerverse pixel-art IP with Moe AI, NFT-gated experiences, education, games and Base-native infrastructure. The goal is one connected creator ecosystem rather than a collection of unrelated tools.

Core architecture: Moe owns the intelligence, strategy, safety rules, product experience and identity. Base provides secure onchain account, permission and execution infrastructure underneath it wherever technically sensible.

2. Product Map

MoerverseStory/IP layer connecting characters, collections, products and holder experiences.
Based Ape PunksCurrent Base NFT access collection and animated Moerverse travelers.
Bald MoeGenesis character and hand-drawn 1/1 identity/lore collection.
Moe Scanner v3.1Versioned proprietary setup intelligence and signal lifecycle.
Moe Token RadarRolling discovery and research for emerging tokens and Base-native intelligence.
Moe AgentRisk-controlled paper/shadow agent designed to execute only Moe-approved decisions.
Moer Academy24-module education system connected to Passport progression and MOER XP.
Arcade + Moer FlipHolder games and progression experiences inside the Moerverse.
Passport / Profile / XPWallet-bound holder identity and non-transferable progression for titles and cosmetic unlocks.
Base App SurfacePrepared distribution path for Base Account-first access and future Base ecosystem discovery.

3. Moe Intelligence

Scanner

Moe Scanner remains the project’s proprietary decision engine. External wallet, Base or Coinbase tooling must not replace its strategy version, confidence thresholds, setup validity, signal lifecycle or risk logic.

Token Radar

Radar discovers and studies assets using market, liquidity, security, holder and Base-native observations. New research inputs cannot affect production score simply because they look interesting.

collect → measure → fixed-horizon forward test → qualification → time-split out-of-sample validation → human review → explicit scoring change

Current research families include DEX/liquidity state, holder/concentration changes, aggregate ERC-20 transfer flow and Flashblocks market context. Experimental research features remain zero-weight until separately validated and approved.

4. Moe Agent

Moe Agent is the controlled action layer. The intended flow is:

Moe Scanner decision → Moe risk policy → user permission check → managed operator policy → reviewed execution adapter → Base

AgentKit/CDP may provide execution plumbing. They do not become Moe’s trading brain. Current public product surfaces remain paper/shadow oriented while live-fund execution is locked behind later security gates.

5. Access & Identity

SYSTEMROLEPRE-TESTNET STATE
Base AccountPrimary account/login providerIntegrated
Holder verificationChecks eligible access NFT ownershipWorking read-only
Spend PermissionsBounded token / allowance / period authorizationLifecycle built; execution locked
Sub AccountsFuture isolated Moe Agent account boundaryRead-only prototype
Passport / MOER XPWallet-bound progression, titles and cosmeticsActive; persistence integration being finalized

MOER XP is progression only: it is non-transferable, non-withdrawable and does not promise conversion into a token.

6. Safety Architecture

  • Live-fund execution remains disabled before the execution release gates are completed.
  • Execution spender starts paused and is Base-chain locked.
  • Single-spend limits and approved routes/assets are enforced.
  • Emergency permission revocation and permanent disable paths exist.
  • Raw operator private keys are prohibited by the managed-operator design.
  • Foundry, Python invariants and Slither are part of the pre-testnet gate.
  • Radar research features cannot silently write production scores.
  • Games award progression through server-validated, wallet-bound records rather than client-only claims.
Passing compilation, simulations or backtests does not grant deployment permission. Website publication, testnet deployment and real-fund execution are separate release states.

7. Testnet Plan

The official website can be live while execution remains locked. Base Sepolia is the full-system rehearsal for the execution stack, not a requirement for publishing the project’s informational website.

  1. Finish website, API and security release checks.
  2. Establish the official BasedMoer.com project presence and prepare community/launch materials.
  3. Confirm Base Sepolia infrastructure and test assets.
  4. Deploy the testnet-only execution spender after explicit approval.
  5. Create and review a bounded test permission.
  6. Quote and simulate the approved route.
  7. Execute with test assets only.
  8. Verify output receipt and lifecycle tracking.
  9. Revoke permission and confirm the revoked state.
  10. Run failure/negative controls and document results.

No mainnet transition occurs automatically after a successful Sepolia test.

8. Release Process

STAGEGOALSTATE
Website finalizationApproved visual master, holder surfaces, docs, QA and mediaCurrent
Official domain + preparation windowBasedMoer.com live while Discord, visuals, video and X launch content are finalizedNext
Base SepoliaFull execution rehearsal with test assets onlyUpcoming gate
Holder launchActivate approved mint/holder campaign after testnet and release reviewLater gate
Mainnet AgentAny real-fund executionSeparate later security gate

9. Project Principles

  • Pixel first: technology supports the art and Moerverse rather than replacing it.
  • Moe decides: proprietary intelligence remains the decision authority.
  • Prove before weighting: research does not become production logic without evidence.
  • Permission before execution: users retain explicit, bounded authorization control.
  • Fail closed: missing providers, mismatched accounts or unsafe states stop the action.
  • Separate release states: a public website does not imply testnet completion, production trading approval or permission to use real funds.