En esta secciónGetting Started

Platform Architecture

En esta página

This page describes the high-level architecture of Inkryptus across three layers: mobile application, backend services, and blockchain infrastructure.

Three-layer architecture

  1. 1

    Layer 1: mobile application

    Everything a user does happens in the app, on iOS or Android. It talks to layer 2 over HTTPS, and to nothing else.

  2. 2

    Layer 2: backend services

    Authentication, KYC, balances and the coordination of on-chain transactions. It reaches layer 3 over Web3.

  3. 3

    Layer 3: BNB Smart Chain

    The INKY token, the staking pools and the liquidity. Nothing here depends on the two layers above it to be verifiable.

Layer 1: Mobile application

The Inkryptus app runs on iOS and Android. Users interact with all platform products through the app: wallet, staking, and swap. The app communicates exclusively with the backend via HTTPS.

Layer 2: Backend services

The backend handles business logic including user authentication, KYC compliance, balance management, and coordination of on-chain transactions. It serves as the bridge between the user interface and the blockchain.

Layer 3: Blockchain (BNB Smart Chain)

All token mechanics and staking logic are recorded on BNB Smart Chain and publicly verifiable.

Key on-chain components:

  • INKY Token: BEP-20 contract with a hard cap of 200,000,000 tokens.
  • Staking pools: Contracts managing deposits, reward accrual, and claims for INKY, USDT, and CAKE.
  • TokenMinter: Emits INKY rewards according to the programmed emission schedule.
  • PancakeSwap liquidity: INKY/USDT pair for open-market trading.

See Contracts for all contract addresses.

Custodial wallet model

When a user creates an account, the platform generates an individual address on BNB Smart Chain, and the wallet behind it lives inside the Inkryptus smart contract. The address is the user's and is readable on BscScan; the contract is what executes on it, under multiple validation layers for transaction authorization. This is where Inkryptus departs from the common web3 model, in which custody means somebody is holding a key on your behalf.

This means:

  • The keys are held in the platform's multisig, so there is no seed phrase for the user to keep or lose.
  • Deposits go directly to the user's assigned address.
  • Withdrawals are authorized by that multisig on the account's behalf.
  • Inkryptus operates the wallet contracts, and the user trusts it to. What that trust does not cover is our account of what moved: the address and its history are public on BscScan.

See Wallet for deposit and withdrawal flows.

Security overview

MeasureDescription
Managed custodyAll on-chain transactions require multiple validation layers
Two-factor authenticationEmail-based 2FA for sensitive operations
KYC and AML complianceIdentity verification and transaction monitoring
On-chain transparencyAll contracts and transactions are public on BscScan

Security & Verification

Security measures, audit status, and verification steps.

Contracts

Contract addresses and BscScan verification links.

Token Security

Token-level security: mint controls, ownership, and permissions.

Última actualización