<aside> 📜

TABLE OF CONTENTS

• Quick Start

• Introduction

• Technology Stack

• Integrations

• Comparison

• Meet the Team </aside>

<aside> 💎

OUR COMMUNITY

• X (Twitter)
• Telegram
• Discord </aside>

Wallet Infrastructure - MPC via Sui Multi-Signature Wallet SDK (Planned for V2)

• Wallet Derivation:

  Wallets will be generated using Sui’s derive_multisig_address_quiet method, which creates native multisig wallet addresses based on user-defined weights and thresholds.

• Distributed Signing:

  Multiple signers will generate partial signatures that are aggregated into a valid transaction signature off-chain — ensuring no single entity controls the key.

• Automatic MPC Conversion:

  In V2, all wallets imported into the bot will be automatically migrated into this MPC structure without user intervention, eliminating seed phrase exposure and improving operational security.

• On-chain Compatibility:

  The architecture is fully compatible with Sui’s Move contract framework and optimized for gas efficiency and composability.

  Current Phase (V1):

  Centron Bot currently uses standard seed phrase-based wallets, and the seed phrases are temporarily stored securely on encrypted servers to enable streamlined transaction execution via Telegram.

  ⚠️ Advisory to Users:

  During this phase, we strongly advise that users only import wallets meant for active trading and avoid storing large or long-term balances within the Centron Bot. Until the full MPC infrastructure is rolled out, Centron Bot is not intended to act as a cold wallet or long-term vault.

  This approach balances usability and performance while we finalize the decentralized MPC system. Export functionality will be available and users retain the ability to withdraw assets at any time.

  Transparency Commitment:

  We uphold a strong commitment to radical transparency, especially in matters involving security and custody. We believe in telling users the truth about current risks, trade-offs and limitations. In the crypto space, user trust is paramount—and it must be earned through honesty and clarity.

  Future Delegation Strategy:

  The MPC infrastructure is modular. We may delegate part of the key signing process to trusted co-signers like Turnkey or Portal (if they expand support for Sui).

  This decision will not be user-configurable — Centron Bot will only implement it if it results in objectively better security or performance.

  These third parties will act as co-signers only, not custodians.

Execution Engine – Aftermath SDK

Centron routes all trades using the Aftermath SDK, a robust TypeScript-based framework for interacting with Sui liquidity pools.

Core Functions:

• Dynamic trade routing

• Multi-hop execution

• Pre-trade simulation

• Route fallback logic

  Advanced Order Support:

• DCA (Dollar-Cost Averaging):

  Users allocate funds and choose intervals. A scheduled Move contract uses Sui’s clock object to execute swap_exact_amount at regular intervals.

• Limit Orders:

  Backend monitors Nexa price feeds and executes once target price is hit and the trade route is viable.

📚 Aftermath SDK Reference:

• Docs: https://docs.aftermath.finance
• GitHub: https://github.com/AftermathFinance

Token Intelligence Layer – Nexa API

Centron integrates Nexa’s powerful metadata engine to protect users from risky or malicious tokens.

Data Pulled from Nexa:

• Token creation block
• Proxy contract detection
• Ownership distribution
• Liquidity and volume metrics
• Volatility scoring and safety ratings

📚 Nexa API Reference:

• Website: https://nexa.xyz
• Docs: https://docs.insidex.trade/docs/insidex-api/introduction

Transaction Safety Controls: Slippage & Gas

Users can configure:

• Slippage Tolerance: 0.1%, 0.5%, 1%, or custom
• Max Gas Units / SUI Budget

Before signing, the bot checks:

• Whether expected output is within slippage limits
• Whether gas fits within budget

If conditions fail, the trade is automatically aborted to prevent loss.

Telegram UX Layer

Centron uses the Telegram UI and it is not a static bot — it’s a reactive execution interface with full trade context per session:

• Session Persistence:

  Each trade maintains session state — token pair, slippage, route, gas config — allowing single-tap re-entry.

• Context-Aware UI:

  UI adapts to current wallet state (e.g., insufficient balance triggers top-up suggestion).

• Ephemeral Notifications:

  Alerts are automatically cleared after viewing for user privacy.

• Live Token Info:

  Real-time price and token metadata is displayed inline using formatted bot messages, minimizing taps while maximizing transparency.

AI UX Layer (Research Phase)

Planned for V2. Features under consideration include:

• Slippage & Gas Estimation Engine: Based on historical data, liquidity depth and Sui block time.
• Strategy Suggestions: Advises user when a DCA or Limit Order strategy may offer better value than a market order.
• Chart image analysis: Users can upload screenshots of price charts; the AI will parse support/resistance zones, RSI/MA patterns, and suggest entry/exit logic.
• Token risk scoring: Predictive models based on Nexa’s token metrics, whale activity, and market behavior

AI UX functions will run in passive (notification only) or active (interactive assistant) mode, configurable per user.

🔒Note: While this outline plans for an AI-powered trading assistant capable of analyzing uploaded chart screenshots and adapting to a user’s trading style, this feature is currently in the conceptual and research phase. Development has not yet commenced and no implementation timeline is being committed at this stage. This technology stack item is intended to signal long-term intent and innovation direction. Users and stakeholders should be aware that AI functionality is not part of the initial release and will only be introduced after foundational infrastructure components are fully deployed and stable.