AXO SERVICES · PROJECT SETUP

AXO Raid Bot
first-party setup

AXO and its community come first. Connect identities and review the fixed AXO destination; participation and publishing remain disabled until their separate proofs are ready.

← All services
STATUSNOT ACTIVATED
NETWORKROBINHOOD · 4663
AXO FIRST-PARTY LOCKOWNER EXCEPTION
AXO setup is staged, not active. The first-party service-lock exception does not exempt members from their own locks or bypass Telegram, bot, editorial, or X checks. No raid or X post is sent.
PROJECTAXO FIRST
MEMBER RULENOT ACTIVATED
TELEGRAM DELIVERYOFF
X PUBLICATIONOFF
01 / IDENTITYCONNECT

Connect AXO admin

Connect the AXO admin wallet and the Telegram account that administers the AXO supergroup. Neither step alone grants project-admin rights.

Connect a wallet to check the protected Telegram login.

If this wallet already has a verified AXO Telegram link, reuse it here without signing in to Telegram again. This is identity only, not admin or member-lock approval.

Community member connection →
Later: external-project onboarding and 2.5 million AXO lock

External projects are not onboarding yet

This worksheet is retained for later, but AXO is the only first-party tenant in scope now.

External-project service lock (later)

  • An external project owner must maintain a normal GemPad lock of at least 2,500,000 AXO V2 on Robinhood Chain (chain ID 4663).
  • The lock must remain valid and continuously meet the threshold; expiry, unlock, transfer, or a balance below threshold means it does not qualify.
  • Each participating member must separately prove a current, project-token GemPad lock at the project-set minimum. Liquid balance alone does not qualify.
  • A project admin controls Telegram destination settings. The X account owner must independently authorize any future X activity. No automatic engagement is implied.
Open GemPad (external) to create a lock ↗

GemPad is an external owner-controlled action. Review the network, token, amount, lock terms, and destination carefully there. This page does not create or verify a lock.

3 · Project destination and holder settings

Saved only in this browser on this device. Nothing is sent to AXO or a bot.

Enter a project owner wallet to preview its public GemPad normal locks on Robinhood Chain. This does not grant access.

    The protected setup flow must read the project token’s decimals on the selected chain and calculate the exact raw threshold. The owner’s AXO service lock and each member’s own GemPad project-token lock are separate checks.

    Add @AXO_RAID_bot to that group as an administrator. The future protected setup flow must verify the exact chat ID, bot membership and your current admin rights; a typed ID never activates delivery.

    4 · Authorize the project X account

    Posting to a project’s X account requires that account’s owner to grant AXO a separate, revocable X API user-context authorization. Identity-only X login does not grant posting; never paste an X password, access token or API key here.

    Future setup must verify the stable X account ID and permissions for posting and media, then apply that account’s shared publication limits and exact-content approval. Holder votes alone never publish.

    5 · Protected review before activation

    1. Owner independently creates and verifies the qualifying GemPad lock.
    2. The owner wallet and Telegram admin identity are verified; the group ID and bot rights are checked by Telegram.
    3. The project token contract, chain and community member-lock threshold are verified onchain.
    4. The project X owner authorizes a separate write-capable, revocable API connection.
    5. AXO provides a protected enrollment flow with verified APIs and explicit activation controls.

    Until then: draft only · no service access · no bot delivery · no publishing.