OFFICIAL DOCUMENT · VERSION 1.0
GEXCORE Whitepaper
Next-generation hybrid Web3 ecosystem
TABLE OF CONTENTS
01 — LEGAL NOTICE
Legal Notice
This document is informational in nature and does not constitute an investment recommendation, a public offer, an invitation to acquire securities or financial instruments, and must not be regarded as a guarantee of returns, liquidity, or any other financial outcomes.
The use of GEXCORE services may involve market, technology, legal, and operational risks. Certain ecosystem functions may depend on completion of KYC/AML, applicable legal requirements, connection of compatible wallets, and availability of technical infrastructure.
Before using the platform, the user is required to review the current terms of use, the personal data processing policy, and the risk disclosure published on the GEXCORE website.
02 — EXECUTIVE SUMMARY
Executive Summary
GEXCORE is a hybrid Web3 ecosystem that combines gaming mechanics, on-chain NFT logic, DAO governance, listing infrastructure, an exchange model, and a planned finance hub into a unified system of participation, growth, and financial interaction.
The ecosystem is built around the following key modules:
- —GEXCORE Islands — a dedicated island platform for users and external projects
- —GEXCORE Hive — the GameFi product and strategic gaming circuit of the ecosystem
- —GEXCORE DAO — a hybrid governance model with on-chain NFT verification
- —GEXCORE NFT — a collection with DAO utility, in-game bonuses, and the ecosystem reward distribution model
- —GEXCORE Exchange — the planned market logic module and GXC listing infrastructure
- —GEXCORE Finance Hub — planned finance hub / fiat access layer for off-ramp, payment rails, and corporate mode
The primary network of the ecosystem is BSC, the primary token is GXC. The GEXCORE Islands module uses a separate settlement circuit on TON.
The key distinction of GEXCORE is not merely a set of Web3 services, but a connected ecosystem where NFTs are verified on-chain, DAO is built on token and NFT status, token release to market is constrained by a hybrid market formula, and gaming and infrastructure modules operate as a unified economy.
03 — ARCHITECTURE
Ecosystem Architecture
The GEXCORE ecosystem is built on a modular principle. Each module solves its own task while being connected to the common infrastructure through the GXC token and NFT tiers.
GEXCORE Islands
Infrastructure island platform for launching individual island-worlds and user participation through Web3 gamification.
GEXCORE Hive
Ecosystem gaming module combining strategy, GameFi mechanics, NFT utility, and in-game economy.
GEXCORE DAO
A hybrid governance model where strategic decisions are formed through DAO, while execution flows through treasury and operational infrastructure.
GEXCORE NFT
On-chain collection of four tiers granting DAO multipliers, reward shares, and in-game bonuses.
GEXCORE Exchange
Module for working with the GXC token, its listing model, and the hybrid market release logic.
GEXCORE Finance Hub
Planned Finance Hub / Fiat Access Layer for integrations with licensed financial and payment partners, off-ramp mechanics, settlements, cards, and corporate payment scenarios.
04 — INFRASTRUCTURE
Networks & Infrastructure
BSC is the primary network of the GEXCORE ecosystem and is used for the GXC token, the NFT collection, DAO logic, on-chain NFT reads, and Web3 integrations of the primary cabinet.
TON is used as a separate settlement circuit for GEXCORE Islands. This allows using the Telegram Mini App as an entry point, linking the TON wallet separately from the BSC wallet, and keeping the primary web3 circuit of the ecosystem isolated from island mechanics.
GEXCORE uses a unified account model where a user has a single internal user_id to which the following may be linked: site, Telegram Mini App, BSC wallet, TON wallet, KYC status, NFT/DAO/referral/islands state.
05 — TOKEN
GXC Token
GXC is the primary token of the GEXCORE ecosystem. It is used as a governance asset for DAO, a unit of account across several ecosystem circuits, an element of the strategic tokenomics model, and the base for forming voting power in combination with NFTs.
Classic GXC staking is not provided. GXC mining and distribution are conducted exclusively through GEXCORE Islands.
06 — LISTING
GXC Listing Mechanics
GEXCORE does not use a simple calendar-based token unlock model. The volume of GXC released to the market is constrained by actual turnover and available liquidity, which reduces price pressure and makes the model more resilient.
Formula
Parameters
After the listing price of $0.60, further token dynamics are determined by actual demand, liquidity, turnover, and the permitted release volume per the formula.
14b — TREASURY, DISTRIBUTION & EMISSION CONTROL FRAMEWORK
Treasury, Distribution & Emission Control Framework
SECTION SUMMARY
GEXCORE uses a connected architecture in which the GXC token, listing layer, emission control, utility mechanics, NFT reward distribution, and treasury execution operate as a unified system.
GEXCORE does not use a fragmented token model. The ecosystem applies a connected treasury and distribution architecture in which token emission, market mechanics, utility functions, dividend flow, and treasury execution are structurally linked on-chain.
Core Structural Layers
The primary value and utility token of the ecosystem. Fixed supply, BSC-native, used across all on-chain interactions.
Governs the conditions and mechanics of GXC market activation. Controls when and how GXC enters circulating supply via exchange.
Regulates the rate and volume of GXC release. Tied to market turnover and available liquidity via the Release Cap formula.
GXC used for access, staking, participation, governance voting weight, claim mechanics, and ecosystem product entry.
NFT-based reward distribution mechanism. Rewards flow from treasury through the Reward Claim Contract to NFT holders.
The execution and coordination hub. Not merely a storage vault — treasury is the active dispatch layer for all distribution flows.
Core On-Chain Contracts
NFT contracts (Diamond, Gold, Silver, Bronze) are also part of the on-chain framework logic and interact with the Reward Claim Contract for NFT-based reward distribution.
Treasury Layer as Execution Architecture
The treasury layer is not a passive storage vault. It functions as the primary execution and coordination layer for all distribution flows within the ecosystem. Treasury dispatches rewards, funds ecosystem utility, coordinates listing mechanics, and interfaces with governance decisions.
Execution Layer
Treasury executes distribution events — rewards, utility funding, listing support.
Coordination Hub
All distribution flows pass through or are authorized by the treasury layer.
Governance Interface
Treasury execution logic is compatible with the hybrid governance model and DAO decisions.
Transparency Layer
On-chain contracts make treasury movements transparent and verifiable by any participant.
Distribution Model Inside the Framework
- —Listing liquidity provision
- —Exchange depth support
- —Market-making framework reserves
- —GXC utility grants for product participation
- —Staking and access mechanics
- —Hive and Islands reward flows
- —On-chain via Reward Claim Contract
- —Proportional to NFT tier and holdings
- —Transparent, claimable by NFT holder
- —TON-chain GXC claim mechanics
- —Islands activity reward flows
- —Linked to core account via hybrid bridge
Emission and Market Control Linkage
The emission control layer is directly linked to market conditions. The Release Cap formula prevents excessive supply expansion during low-liquidity periods while allowing measured release as market depth grows.
RELEASE CAP FORMULA
kMarket sensitivity coefficientαLiquidity utilization cap factorMarket TurnoverObserved trading volume within the measurement windowAvailable LiquidityAccessible on-chain liquidity at time of calculationGovernance Linkage
The Treasury, Distribution & Emission Control Framework is fully compatible with the hybrid governance model. Treasury execution decisions can be proposed and ratified through the DAO governance process. Emission parameters, distribution allocations, and treasury deployment decisions are subject to governance oversight within the defined framework boundaries.
Hybrid Governance Compatible
Framework execution is aligned with the DAO + treasury hybrid decision model.
Emission Governance Oversight
Emission parameters can be reviewed and adjusted via governance proposal process.
Distribution Transparency
All distribution events are traceable on-chain, visible to DAO participants.
Treasury Execution Ratification
Major treasury deployments are subject to governance authorization within defined limits.
ARCHITECTURE STATEMENT
GEXCORE uses a Treasury, Distribution & Emission Control Framework in which the token layer, listing logic, emission control, utility mechanics, reward distribution, and treasury execution are connected into a unified digital economy architecture of the ecosystem.
— — CONTRACTS
Smart Contract Registry
All GEXCORE smart contracts are deployed on BNB Smart Chain (BSC Mainnet, chainId 56). Addresses are verified and official.
Core Contracts
GXC Token
Core ecosystem token (BEP-20)
0x292E60E86eE1281Be7A8e810fB2873A5bF676471
Reward Claim Contract
On-chain reward distribution for NFT holders
0x93B6A5AA07c64a50f8E3d4De03B41832c9EA4466
Utility Contract
Ecosystem utility infrastructure logic
0x257d140D4a7B97380B6fEC8A54f48503581e64a7
Listing Contract
GXC listing infrastructure
0xe6C2fc8A3370c489A302B00d7c5112a8240b3A03
Emission Contract
Emission control and Release Cap framework
0x6176FE8Dc77c3c4444358A45cfa994b6E4d9efEc
NFT Contracts
Diamond NFT
ERC-721 · 88 tokens · DAO ×30 · 6 dividend shares
0xfc311b6FeE695F326022CE6f7C8D6e9CcC447355
Gold NFT
ERC-721 · 88 tokens · DAO ×10 · 4 dividend shares
0xDFf3C9Dd4d381bC45278E2886738006894a90C65
Silver NFT
ERC-721 · 88 tokens · DAO ×5 · 2 dividend shares
0xcc54502B2653D5dF346529D5bCF5d0F36Bc14ab4
Bronze NFT
ERC-721 · 88 tokens · DAO ×3 · 1 dividend share
0x86e2585D03155c752588bfE738Bc163CcAE37Fcb
These contracts collectively support the token layer, NFT ownership model, reward distribution, ecosystem utility logic, listing infrastructure, and emission control framework of GEXCORE.
07 — ISLANDS
GEXCORE Islands
GEXCORE Islands is a dedicated island platform of the GEXCORE ecosystem, designed for launching individual island-worlds within a unified Web3 environment.
The platform enables:
- —users to participate in island mechanics
- —external projects to launch their own branded worlds
- —community formation
- —using Web3 gamification as a tool for growth and engagement
GEXCORE Islands is not a classic round-based token sale page. It is not a token sale by rounds — it is a dedicated participation platform where island mechanics are used as an infrastructure and gaming tool.
TON is used as a separate settlement circuit for Islands.
08 — GAMEFI
GEXCORE Hive
GEXCORE Hive is a strategic GameFi product within the GEXCORE ecosystem.
Hive combines:
- —strategic progression
- —game mechanics
- —NFT utility
- —in-game economy
- —PvE / PvP activities
- —rewards and progression system
Hive is the gaming module that strengthens user engagement, enhances NFT utility, expands the role of digital assets within the ecosystem, and forms a dedicated GameFi participation circuit.
09 — NFT
GEXCORE NFT
The GEXCORE NFT collection has been issued and distributed. The collection includes Bronze, Silver, Gold, and Diamond tiers. Each tier provides a DAO multiplier, in-game bonuses, and a share in the project's ecosystem reward distribution model.
The GEXCORE NFT collection is verified on-chain through smart contracts on the BSC network. The system determines which NFT tiers actually belong to the user and uses that to calculate the DAO multiplier, reward shares, full-set bonus, and active in-game advantages.
Utility by Tier
🎯 Full Set Bonus (Bronze + Silver + Gold + Diamond)
- —Farm bonus +300%
- —Auto-repair / auto-collect — once per month
- —Island protection — 7 days
- —Killer bee and Wool-bee — up to 4 times per day
- —Boss attack ×10
14 — CLAIM
Hybrid Claim Architecture
Two distinct claim models are used within the GEXCORE ecosystem.
💎 Claim Rewards
Ecosystem reward claim is tied to the NFT collection, on-chain ownership verification, and the reward distribution model based on NFT tiers.
⛏️ Claim GXC
GXC token claim is tied to the GEXCORE Islands mechanics and implemented as a hybrid flow through platform distribution logic and backend infrastructure, with optional use of a blockchain settlement layer.
This approach separates:
- —on-chain claims based on verified NFT ownership
- —and hybrid claims based on user participation and Islands logic
Within the GEXCORE ecosystem, claim mechanics are intentionally separated into distinct functional layers depending on the nature of the asset and the source of entitlement.
Claim Rewards is tied to the GEXCORE NFT Collection and uses contract-linked distribution logic based on verified NFT ownership and reward share allocation.
Claim GXC follows a hybrid claim flow, where eligibility and claimable balance are determined through GEXCORE Islands participation logic and processed through backend/platform infrastructure, with blockchain settlement used where applicable.
15 — ACCOUNT
User Model and Wallets
A user has a single GEXCORE account to which the following may be linked:
- —site
- —Telegram
- —BSC wallet
- —TON wallet
- —KYC
- —NFT / DAO state
Wallet Separation
At the current stage, the primary scenario remains connecting the user's existing wallets. Built-in generation of a new non-custodial wallet may be implemented later, only in a client-side-only format, without seed phrase storage on the project side.
15b — MULTI-LAYER WALLET ARCHITECTURE
Multi-Layer Wallet Architecture
SECTION SUMMARY
GEXCORE uses a multi-layer wallet architecture in which the primary Web3 wallet serves the core on-chain layer, the TON wallet supports the separate Islands layer, and future trading and terminal access is developed as a separate functional wallet context.
GEXCORE does not use a single universal wallet model for all modules simultaneously. The architecture is built on the principle of separating wallet roles and product layers. Each layer of the ecosystem has its own wallet context, clearly defined connection method, and scope of use.
Wallet Layers
The primary wallet layer of the GEXCORE ecosystem. Used for all core on-chain operations.
- —GXC token operations (transfer, approve, market)
- —NFT ownership verification (all 4 tiers)
- —DAO governance — voting power and proposal logic
- —Dividend claim from NFT collection
- —Exchange preparation and market access
- —Primary Web3 context of the GEXCORE cabinet
A separate, independent wallet layer for GEXCORE Islands. Not mixed with the BSC layer.
- —GEXCORE Islands participation logic
- —Telegram Mini App wallet context
- —Island settlement and distribution flow
- —TON Connect — separate from WalletConnect / EVM
A future functional wallet context for the Hybrid Exchange / Trading Terminal. Operates on BSC core layer with architecture designed for expansion.
- —Quick Swap context (PancakeSwap V2 Router)
- —Market transaction signing (swap, approve)
- —Order management in Hybrid Terminal
- —Expandable to additional supported networks
A separate wallet-based entitlement logic layer for claim mechanics.
- —Claim Rewards — on-chain, based on NFT ownership (BSC)
- —Claim GXC — hybrid flow via Islands distribution logic
- —Wallet signature used as proof of entitlement
- —No seed phrase exposure — read-only on-chain verification
BSC and TON: Strict Layer Separation
BSC and TON wallet objects must not be merged into a single wallet context. They serve distinct product layers and must remain operationally independent.
BSC wallet
Current core layer — GXC, NFT, DAO, Exchange, Cabinet
TON wallet
Separate Islands layer — Islands only, never mixed with BSC exchange
A single GEXCORE account links multiple wallet layers into one account model via a shared internal user_id, while keeping BSC and TON contexts operationally isolated.
Wallet UX Model
The GEXCORE wallet UX is built around three functional zones that reflect the multi-layer architecture:
Header Wallet Status
Persistent wallet state visible across the cabinet: connection status, network, address, BSC chip.
Wallet Management Screen
Dedicated wallet management screen in the cabinet: connect / disconnect, switch wallet, view address, BSC and TON separately.
Contextual Wallet Access
Context-aware wallet prompt in modules: Exchange shows BSC wallet, Islands shows TON wallet — never mixed.
Supported Connection Methods
Multi-Network Future
The current wallet architecture uses BSC as the core layer for all primary product operations. The wallet layer architecture is designed as expandable — future network support should not break the current product model but extend it.
- —BSC remains the primary core layer throughout the listing phase and early product stages
- —Each future supported network gets its own wallet context — no merged multi-chain wallets
- —TON remains the dedicated Islands layer regardless of future EVM expansion
- —The single account model links all layers via user_id without mixing wallet contexts
ARCHITECTURE STATEMENT
GEXCORE uses a multi-layer wallet architecture in which the primary Web3 wallet serves the core on-chain layer, the TON wallet supports the separate Islands layer, and future trading and terminal access is developed as a separate functional wallet context.
15c — MULTI-LAYER ACCOUNT & IDENTITY MODEL
Multi-Layer Account & Identity Model
SECTION SUMMARY
GEXCORE uses a unified account model in which site account, wallet layers, Telegram identity, compliance state, and governance status are combined into a single scalable access architecture.
GEXCORE is not structured around a single wallet as the only user identifier. The ecosystem uses a unified account entity to which different identity layers are attached. Account identity and wallet identity are not the same thing — a wallet remains a critically important element of on-chain verification but is not the sole level of identity.
Identity Layers
The base identity layer of the ecosystem. Created at registration and persists across all sessions and product modules.
- —User registration and authentication
- —Session management (secure cookie)
- —Profile and cabinet access
- —Legal consents (ToS, Privacy Policy, Risk Disclosure)
- —Internal user_id — the universal connector of all layers
On-chain identity layer linked to the core account. A wallet is a proof of on-chain ownership and participation, not a login mechanism.
- —Core Web3 wallet (BSC) — GXC, NFT, DAO, Exchange
- —TON wallet — separate Islands layer
- —Future multi-network wallet contexts (expandable architecture)
- —Wallet address verified and linked to account, not used as primary identifier
Telegram-linked state connecting the user's Telegram identity to the core GEXCORE account via the Mini App.
- —Telegram user ID linked to core account
- —GEXCORE Islands participation state
- —TON wallet linkage within Islands context
- —Islands activity synchronized with core account
A separate verification layer. KYC is a verification layer, not a replacement for the account model.
- —KYC status (when required)
- —Access restrictions based on legal context
- —AML compliance state
- —Jurisdiction-specific legal / compliance logic
On-chain ownership and governance state, updated through blockchain reads and linked to the core account.
- —GXC balance (voting power base)
- —NFT ownership and tier status
- —DAO eligibility and voting history
- —Claim entitlement — rewards and GXC
- —Reward share calculation based on NFT holdings
Identity Continuity Between Site and Telegram
The GEXCORE site and Telegram Mini App are connected through a single core account. Telegram identity is a separate layer attached to the same account — not a separate account. There are no duplicate accounts between the website and Mini App.
One Core Account
A single internal user_id links all product surfaces: site cabinet, Telegram Mini App, wallet contexts.
Telegram as a Layer
Telegram user ID is attached as an additional identity layer — not a separate account entity.
Islands State Sync
Islands activity and participation state are synchronized with the core account across both surfaces.
No Account Duplicates
The architecture prohibits account duplication between the site and Mini App — one user = one account.
Access Levels Inside the Account Model
The account model supports layered access levels. Each level is unlocked by satisfying specific conditions — registration, wallet linkage, Islands participation, NFT ownership, governance activity, compliance verification, or business context.
ARCHITECTURE STATEMENT
GEXCORE uses a multi-layer account & identity model in which the user exists as a single account entity, while site account, wallet layers, Telegram identity, compliance state, governance status, and product access are connected within a single unified ecosystem model.
15d — ECOSYSTEM ACCESS MODEL
Ecosystem Access Model
SECTION SUMMARY
GEXCORE uses a multi-layer access model where user rights depend on account state, wallet linkage, Islands context, NFT ownership, governance eligibility, verification level, and product-specific access layers.
GEXCORE does not use a single flat access model for all functions. The ecosystem applies a layered access architecture where access is determined by a combination of account state, wallet linkage, network context, product-specific linkage, on-chain ownership, governance eligibility, verification level, organization role, and future terminal access.
Access Levels
How Access Layers Overlap
A user can hold multiple access layers simultaneously within a single account entity. Access layers are additive — each new layer unlocks additional capabilities without removing or replacing previous ones.
Example: Combined Access Profile
Access Model by Ecosystem Module
Access Continuity and User Experience
The access model must be visible and understandable to the user at the interface level. Each locked feature displays a clear explanation of the required condition. Progress through access layers is incremental and non-destructive — unlocking new layers never removes previously obtained access.
Locked State Transparency
Locked modules always display the exact condition needed to unlock — no hidden gates.
Incremental Unlock
Each new verified condition opens additional layers without disrupting existing access.
Access Status Dashboard
The user cabinet displays current access level and what the next layer requires.
Cross-Surface Continuity
Access state is consistent between site cabinet and Telegram Mini App — same account, same rights.
Strategic Justification
Modular Access
Each product module defines its own entry conditions independently, keeping the architecture clean and extensible.
Product-Specific Entry
Conditions vary by module — Islands requires TON, DAO requires GXC + NFT, Bank requires verification.
Layered Role Separation
Access layers never conflict — governance participation does not interfere with trading or Islands access.
Scalability for Future Modules
New products can define their own entry layer without restructuring the existing access model.
ARCHITECTURE STATEMENT
GEXCORE uses a layered ecosystem access model in which access to features is determined by the combination of account state, wallet linkage, product-specific identity, on-chain ownership, governance eligibility, verification level, and future business or terminal contexts.
10 — DAO
DAO Governance Model
Participation in GEXCORE DAO governance is available only to wallets holding at least 1,000,000 GXC.
This threshold is introduced to ensure that voting rights are assigned to ecosystem participants with a meaningful economic stake, while reducing governance noise from insignificant balances.
1. Eligibility Threshold
A wallet becomes eligible to vote only if:
GXC Balance ≥ 1,000,000 GXC
If the wallet balance is below this threshold, voting power is equal to zero.
2. Base Voting Power
To prevent governance centralization by large token holders, GEXCORE uses a non-linear voting model based on the square root of the qualifying balance.
Base Voting Power = √(GXC Balance / 1,000,000)
3. NFT Governance Multipliers
Bronze = 3x
Silver = 5x
Gold = 10x
Diamond = 30x
4. Maximum Multiplier Cap
Maximum Effective Multiplier = 100x
5. Final Voting Power Formula
Final Voting Power = Base Voting Power × min(NFT Multiplier, 100)
Where:
— Base Voting Power = √(GXC Balance / 1,000,000)
— NFT Multiplier = governance coefficient based on NFT tier
— 100 = hard protocol cap
6. Governance Design Rationale
This model rewards meaningful GXC exposure, recognizes the strategic value of NFT holders, and limits whale dominance through non-linear token weighting and multiplier caps.
11 — GOVERNANCE
Hybrid Governance & Treasury Execution
GEXCORE uses a hybrid governance model where strategic decisions are formed through DAO, while their execution is conducted through treasury and the project's operational infrastructure.
This means:
- —on-chain influence is verified by token and NFT
- —governance direction is set by DAO
- —practical execution is provided through the project structure, treasury logic, and operational circuits of the ecosystem
This approach combines transparency of Web3 participation with manageability, legal accountability, and operational executability of decisions.
12 — EXCHANGE
GEXCORE Exchange
GEXCORE Exchange is the exchange module of the ecosystem, focused on operations with BSC, the GXC token, and the hybrid market release model.
The Exchange module provides:
- —market circulation logic for GXC
- —connection to tokenomics
- —infrastructure foundation for the further trading circuit
- —display of key market model parameters
GEXCORE Exchange is not a classic earn / staking product. The token's market model is built not on APY but on release constraints driven by actual turnover and liquidity.
12b — MULTI-NETWORK EXCHANGE ARCHITECTURE
Multi-Network Exchange Architecture
SECTION SUMMARY
GEXCORE Exchange uses BSC as the current primary on-chain layer for GXC market activation, but both the Exchange module and the future Trading Terminal are architecturally designed as expandable multi-network trading infrastructure. TON remains a separate layer for GEXCORE Islands only.
Current Core Layer
On the current stage, GEXCORE Exchange operates on BNB Smart Chain (BSC) as the primary on-chain layer. BSC hosts all core exchange-related infrastructure:
- —GXC token (BEP-20 contract)
- —GEXCORE NFT Collection (4 tiers, on-chain ownership verification)
- —Dividend logic and claim contracts
- —Utility, listing, and emission contracts
- —Primary Web3 wallet layer of the GEXCORE cabinet
Separation of Network Roles
GEXCORE maintains a clear separation between its network layers. BSC is the primary trading and settlement layer. TON is a strictly separate layer used exclusively for GEXCORE Islands — it is not used as an exchange layer and must not be mixed with BSC-based market mechanics.
- —GXC token
- —NFT collection
- —DAO governance
- —Dividend contracts
- —Cabinet Web3 layer
- —GEXCORE Islands
- —Telegram Mini App
- —Island settlement
- —Separate TON wallet
Why Multi-Network Approach Matters
While BSC provides the current stable foundation for GXC exchange operations, the GEXCORE Exchange architecture does not treat BSC as a permanent single-network constraint. The hybrid exchange model is designed to support expanding trading scenarios across compatible networks as the ecosystem scales.
- —BSC remains the primary core layer throughout the listing and initial trading phases
- —Exchange architecture is modular and can be extended to additional EVM-compatible networks
- —Trading Terminal infrastructure is designed as expandable, not BSC-only
- —Multi-network approach reduces single-chain dependency risk at scale
Hybrid Exchange Model
GEXCORE Exchange is a hybrid market infrastructure module combining on-chain DEX-routed swap mechanics with a future Hybrid Trading Terminal. It is not a classical earn or staking product. The exchange layer integrates:
- —Quick Swap via PancakeSwap V2 Router (BSC) — activates after listing
- —Release Cap formula limiting GXC market supply
- —Hybrid Trading Terminal — separate future interface with charts, order book, limit orders
- —Planned pairs GXC/USDT and GXC/BNB (not live until listing activates)
Planned Pairs vs Live Markets
Prior to listing activation, GEXCORE Exchange operates as an infrastructure module only. No live GXC trading pairs exist before listing.
Primary trading pair on BSC after listing
Native ecosystem pair on BSC after listing
Planned pairs are displayed for informational purposes only. They are not active markets and do not represent live trading, live prices, or live volumes. Trading simulation prior to listing is not performed.
Launch Stages
Exchange operates as infrastructure module. No active GXC trading. Planned pairs visible.
GXC listing activation. Quick Swap GXC/USDT, GXC/BNB via PancakeSwap V2 on BSC.
Full Trading Terminal: charts, order book, limit orders, trade history.
Architecture expansion to additional compatible networks and market layers.
Wallet Access Model
Access to the GEXCORE Exchange and future Trading Terminal is provided through the user's primary Web3 wallet. At the current stage, the primary trading layer operates on BSC — MetaMask, Rabby, Trust Wallet, and other EVM-compatible wallets via WalletConnect are supported. The TON wallet is used exclusively for GEXCORE Islands and is not part of the exchange or trading flow.
Strategic Rationale
The decision to separate BSC as the current core layer from a multi-network future architecture reflects a deliberate design principle: clarity of the current stage combined with architectural readiness for growth. The GEXCORE Exchange does not overpromise immediate multi-chain capabilities, nor does it restrict the long-term architecture to a single network.
ARCHITECTURE STATEMENT
At the current stage, the primary on-chain infrastructure of GEXCORE Exchange relies on BSC as the current core layer. However, the architecture of the Exchange module and the future Trading Terminal is designed from the outset as an expandable multi-network trading infrastructure.
13 — BANK
GEXCORE Finance Hub
GEXCORE Finance Hub is the planned finance hub / fiat access layer of the GEXCORE ecosystem.
Core directions:
- —integrations with licensed financial and payment partners
- —off-ramp
- —potential card and fiat scenarios via licensed partners
- —payment integrations via licensed partners
- —international payment routes via licensed partners
- —local payment routes via licensed partners
- —international card routes via licensed partners
- —planned stablecoin off-ramp through licensed partners
- —tax reporting
- —corporate mode
GEXCORE Finance Hub does not provide token staking. GXC mining is conducted exclusively through GEXCORE Islands.
16b — SECURITY, AUDIT READINESS & OPERATIONAL RESILIENCE FRAMEWORK
Security, Audit Readiness & Operational Resilience Framework
SECTION SUMMARY
GEXCORE uses a multi-layer infrastructure resilience model covering smart contract security, wallet safety, account integrity, distribution consistency, treasury execution, and cross-platform stability.
Security in GEXCORE is treated as a multi-layer infrastructure framework, not merely as an external contract audit. Each operational layer of the ecosystem — from smart contracts to wallet integration, account model, distribution mechanics, and cross-platform UX — carries its own security and resilience requirements.
Core Security Layers
- —On-chain contract architecture with clear role separation
- —Registry of all deployed contracts with addresses
- —Product-to-contract mapping for each ecosystem module
- —No undisclosed proxy or upgrade logic without documentation
- —Emission and distribution logic separated from token core
- —BSC wallet connection via WalletConnect (no private key exposure)
- —Cancel / reject / reconnect flows handled without state corruption
- —Mobile Safari and Android wallet flows tested for stability
- —Wallet address verified and stored securely without overreach
- —TON wallet isolated from BSC wallet context — no cross-contamination
- —Session managed via secure HMAC-SHA256 signed cookie
- —No wallet address used as sole account identifier
- —user_id internal — never exposed in client-facing URLs or responses
- —Auth state consistent across site and Telegram Mini App
- —Legal consents logged and preserved per session
- —On-chain reward distribution — no off-chain distribution without disclosure
- —Reward Claim Contract verifies NFT ownership before release
- —Claim logic separated from treasury execution context
- —No simulated or mocked distribution flows in production interfaces
- —Islands GXC claim operates on TON layer, distinct from BSC dividend claims
- —Treasury execution requires governance authorization within defined limits
- —No unilateral treasury deployment without documented decision process
- —On-chain traceability of all treasury-originated transactions
- —Treasury layer is the sole authorized execution hub — not replicated elsewhere
- —Emergency protocols documented separately from standard execution flows
Audit Readiness as a Process, Not a Formality
Audit readiness in GEXCORE is built through structural clarity — not through post-hoc documentation. The architecture is designed to be legible to an external auditor at any stage of development.
Structured Contract Architecture
Each contract has a documented role, scope, and interaction model within the ecosystem framework.
Clear Contract Registry
All deployed contracts listed with addresses, roles, and product-to-contract mapping.
Distribution Context Separation
BSC reward distribution and Islands GXC claim are separated — no shared execution paths.
Governance & Treasury Logic
Treasury execution and governance decision logic are documented and consistent with stated framework.
External Audit Path
GEXCORE will publish audit information only after the audit process has been formally completed. Until that point, no language implying "audited" or "fully audited" status is used in any official communication, interface, or documentation. Audit readiness is a structural state — audit completion is a formally confirmed event.
Operational Resilience
Operational resilience covers the stability of all user-facing flows — particularly in Web3 contexts where wallet interactions, network transitions, and mobile environments introduce failure points that standard web applications do not face.
Auth / Session Stability
Session persists across page refreshes, tab changes, and wallet reconnects without requiring re-login.
Wallet Reconnect Flows
Cancel, reject, and reconnect scenarios handled without corrupting account state or UI context.
Mobile Safari & Android
Wallet flows tested for stability on iOS Safari and Android Chrome — the primary mobile Web3 surfaces.
Module Transition Consistency
State is preserved correctly when users switch between cabinet modules or return after inactivity.
Security and UX Are Linked
Broken UX in Web3 often creates security and integrity problems — not just usability issues. An unclear wallet flow can result in double-signing. A confusing claim interface can lead to accidental or misunderstood transactions. A broken session can expose incorrect account state. In GEXCORE, UX clarity is treated as a direct component of operational security.
Key Resilience Domains
ARCHITECTURE STATEMENT
GEXCORE uses a Security, Audit Readiness & Operational Resilience Framework in which smart contract security, wallet safety, account integrity, distribution consistency, treasury execution, and cross-platform stability are unified into a single infrastructure resilience model.
16 — COMPLIANCE
Compliance / Privacy / Legal
The GEXCORE ecosystem provides for:
- —personal data processing policy
- —separate consents for registration
- —separate consents for KYC
- —separate consents for support
- —AML / KYC Notice
- —risk disclosure
- —user agreement
- —international privacy layer for other countries
For Russia, particular attention is paid to the requirements of 152-FZ and 115-FZ, compliance reviews, data localization, and legal recording of consents.
For international users, a separate privacy / compliance layer applies, taking into account applicable law and the relevant lawful bases for processing. ### Legal Entity & Operational Separation GEXCORE develops under a modular model of legal and operational separation. Individual ecosystem modules may be provided by different legal entities, technical providers, regulated structures, or licensed partners depending on jurisdiction, functional scope, and applicable requirements. A Russian IT company, if used in the project structure, performs exclusively software development, technical support, maintenance of the website, Telegram Mini App, backend/frontend, QA, and DevOps functions. Such a company does not issue tokens, does not provide digital asset exchange services, asset custody, banking, payment, investment, brokerage, deposit, credit, or asset management services. Exchange, finance hub, fiat off-ramp, card, payment, banking, and other regulated functions may only be launched in stages, through separate legal entities, licensed partners, or upon obtaining necessary authorizations in the relevant jurisdiction.
— — PARTNERS
Partners & Integrations
GEXCORE develops its partner network across six key integration verticals: Web3 infrastructure, payment solutions, KYC/AML, banking integrations, security infrastructure, and ecosystem launches.
The current partner list will be published separately after integrations and agreements are finalized. Partner logos and details will follow upon confirmation.
— — SECURITY
Security & Audit
GEXCORE smart contracts and key modules are designed from the ground up with security in mind: minimal attack surface, phased verification, and on-chain transparency.
- —Modular smart contract architecture with isolated access boundaries
- —All NFT ownership, rewards, and DAO votes confirmed on BSC Mainnet
- —Contracts open for independent on-chain verification via BSCScan
- —Security reviewed at each development phase before public module release
- —Independent external audit is planned prior to full public launch
Audit Status
Information about the independent external audit will be published after the procedure is complete. This disclosure will include the auditing firm, scope, and findings.
— — ROADMAP
Roadmap / Next Phase
GEXCORE develops as a phased Web3 ecosystem where each next module strengthens the overall infrastructure of participation, governance, digital assets, and settlement layers.
- —Expanding Islands and Hive modules
- —Refining wallet infrastructure and cross-platform UX
- —Developing DAO and governance logic
- —Publishing confirmed partner integrations
- —Preparing for external independent audit
- —Expanding banking and off-ramp layer
- —Strengthening product and legal infrastructure
Product Expansion
Expanding Islands, Hive, NFT utility, and internal ecosystem claim mechanics.
Governance Layer
Further implementation of DAO infrastructure, voting flows, and governance execution logic.
Wallet & Access
Enhancing BSC / TON wallet UX, mobile compatibility, and account-linking between the website and Telegram Mini App.
Partners & Integrations
Publishing confirmed integrations and developing the ecosystem partner infrastructure.
Security & Audit
Preparing smart contracts and key modules for external independent audit.
Planned Finance & Fiat Access Layer
Expanding off-ramp, payment rails, banking integrations, and corporate mode.
Roadmap items reflect planned development priorities. Specific timelines and release dates will be communicated separately as milestones are confirmed.
17 — RISKS
Risk Factors
Use of the GEXCORE ecosystem involves the following risks:
18 — CONCLUSION
Conclusion
GEXCORE is building not a standalone Web3 service but a holistic ecosystem where:
- —the GXC token has its own hybrid release model
- —NFTs are verified on-chain and participate in DAO and the ecosystem reward distribution model
- —Islands form a dedicated infrastructure for engagement and project world mechanics
- —Hive strengthens the ecosystem through the GameFi circuit
- —Exchange and Bank form the infrastructure financial layer
- —DAO connects on-chain participation and practical execution of decisions
It is precisely the combination of these elements that forms the hybrid architecture of GEXCORE as a next-generation Web3 ecosystem.
Download Full Version
The full GEXCORE Whitepaper is available for download as PDF. The document is intended for investors, partners, and regulators.