0x0.su Blockchain Platform Documentation Version 2.3 | Last Updated: 2025-12-22

1. Introduction

0x0.su is a private decentralized blockchain focused on secure data exchange, asset tokenization, and dApp creation. The platform combines privacy, scalability, and flexibility, supporting both public and corporate scenarios.

Key Advantages: - Privacy: Anonymity of participants and ability to hide data. - Security: Cryptographic algorithms (SHA-256, ECDSA). - Scalability: Sharding and adaptive block formation speed (1–60 sec). - Flexibility: Support for text, images, videos, and smart contracts. - Decentralized Governance: Decisions made through PoA consensus with trusted validators.

2. Basic Concepts

  • Blockchain: Distributed ledger with immutable data blocks.
  • Smart Contract: Autonomous code on Solidity (EVM-compatible).
  • Transaction: Operation of transferring data/assets (up to 30,000 tr/sec).
  • Nodes: Participants with validator role (PoA consensus).
  • 0x0 Token: Native token for transaction fees and network interaction.

3. Architecture and Technical Parameters

3.1 Blockchain Layers: - Network Layer: P2P network with Ethereum, BSC bridges. - Consensus Layer: Proof of Authority (PoA) for trusted nodes. - Application Layer: Support for dApps, IPFS integration, and Metamask.

3.2 Technical Characteristics:

Parameter Value
Block Speed 1 sec (under load) / 60 sec (idle)
Block Size 700,000,000 GAS (~30,000 transactions)
Throughput Up to 30,000 tr/sec (theoretical)
Data Storage Decentralized (IPFS + local nodes)

4. Platform Usage

4.1 Application Scenarios: - Corporate Solutions: Supply chain management, document handling. - Loyalty: Bonus systems and NFT coupons. - Gamification: Tokenization of gaming assets.

4.2 Getting Started: 1. Wallet: - Connect Metamask through metamask.0x0.su. - Save your mnemonic phrase. 2. Transactions:

javascript // Example of secure Web3.js interaction // WARNING: This is example code. Always verify addresses and transaction data const tx = { to: '0x...', value: web3.utils.toWei('1', 'ether'), gas: 21000 }; web3.eth.sendTransaction(tx); 3. Management: Network development decisions are made through voting by PoA validators.

4.3 ERC20 Token Deployment and Loyalty Systems Thanks to EVM-compatibility, the 0x0.su platform supports token creation according to the ERC20 standard, which defines rules for token interaction in the blockchain. This opens opportunities for implementing flexible loyalty and coalition models.

ERC20 Token Application in Loyalty Systems

  1. Activity Bonuses:
  2. Users receive tokens for purchases, registration, or task completion. For example, 1% of the purchase amount is awarded as tokens.

  3. Accumulated points can be exchanged for discounts, exclusive services, or goods, similar to airline loyalty programs.

  4. Personalization:

  5. Smart contracts automate bonus accrual based on individual conditions (e.g., increased bonuses for VIP users).

  6. DApp Integration:

  7. Tokens are displayed in Metamask and other wallets, and their balance can be checked through the block explorer.

Coalition Loyalty Systems

In such models, several organizations combine their programs, creating a unified ecosystem: - Multilateral Exchange: Tokens are used by different partners (cafes, shops, services), increasing their value for users. - Flexible Rules: Bonus accrual and spending conditions are set through smart contracts, including restrictions on expiration dates or application zones. - Transparency: All operations are recorded in the blockchain, excluding fraud and errors in accruals.

ERC20 Advantages for Loyalty

  • Standardization: Compatibility with wallets (Metamask, Trust Wallet) and DApps simplifies integration.
  • Automation: Smart contracts manage processes without third-party involvement.
  • Liquidity: Tokens can be traded on exchanges, adding real value.

Implementation Example

A project can issue a LOYAL token that: - Is awarded to users for purchases from partner stores. - Is exchanged for discounts or gifts through DApp. - Is integrated into a mobile app with balance tracking through the block explorer.

Technical Implementation

  1. Contract Deployment:
  2. Use libraries like OpenZeppelin to implement functions:
    • totalSupply() — total number of tokens.
    • balanceOf(address) — user's balance.
    • transfer(address, uint256) — token transfer.

  3. Example code:

    ```solidity pragma solidity ^0.8.0;

    import "@openzeppelin/contracts/token/ERC20/ERC20.sol";

    contract LoyaltyToken is ERC20 { constructor(uint256 initialSupply) ERC20("LoyaltyToken", "LOY") { _mint(msg.sender, initialSupply * 10 ** decimals()); } } ``` 2. Deployment: - Compile and deploy the contract through Remix IDE or Hardhat, specifying the RPC node address: nodes.0x0.su. 3. Verification: - Monitor transactions through the block explorer.

4.4 Transaction Cost Calculation in Gwei

Description: Gas Price = 20 Gwei. Minimum cost of a simple transaction (token transfer, 21,000 gas): Formula: Gas Used × Gas Price = 21,000 × 20 Gwei. Result: 420,000 Gwei (equivalent to 0.00042 native token if 1 token = 10^9 Gwei).

For more complex transactions (e.g., loyalty smart contract, ~100,000 gas): Cost: ~2,000,000 Gwei.

Advantages: Compared to public networks (where often 50+ Gwei) — ultra-low fees, almost free for private network.

5. Developer Tools

5.1 Block Explorer API The platform provides Block Explorer API for programmatic access to blockchain data. API is available at: https://api.explorer.0x0.su

Main Endpoints

  • Health Checks:
  • GET / — application health status
  • GET /api/health — simple service health check

  • GET /api/health/detailed — detailed check (DB, blockchain, task queue)

  • Account Information:

  • GET /account/{account} — account details (balance, transaction count, contract type)
  • GET /balance/{address}/latest — latest address balance
  • GET /balance/{address}/by_date — balance by date

  • GET /balance/{address}/latest/{contract_address} — contract token balance

  • Block Information:

  • GET /last_block — last block number

  • GET /block/{block_number} — block details (hash, timestamp, transactions, etc.)

  • Transaction Information:

  • GET /tx/{tx_hash} — transaction details (sender, receiver, amount, gas, etc.)

  • Contract Registration:

  • POST /contract/register — register new contract (JWT authentication required)

All requests return data in JSON format. JWT authentication token is required for contract registration.

Usage Examples

# Get address balance
curl -X GET "https://api.explorer.0x0.su/balance/0x742d35Cc6.../latest"

# Get block information
curl -X GET "https://api.explorer.0x0.su/block/12345"

# Register contract (with JWT)
curl -X POST "https://api.explorer.0x0.su/contract/register" \
  -H "Authorization: Bearer YOUR_JWT_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"name": "MyContract", "address": "0x...", "abi": "[...]", "description": "Contract description"}'

6. Security and Governance

  • Anti-spam mechanisms: Dynamic fees and limits.
  • PoA Consensus: Network management is carried out by trusted nodes.

7. License and Support

  • License: Apache 2.0
  • Contacts:
  • Website: 0x0.su
  • Email: support@0x0.su

Version 2.1 Changes: - Removed mentions of DAO governance. - Emphasis on Proof of Authority (PoA) and technical improvements. - Clarified the role of the 0x0 token (transaction fees, network interaction). - Added description of ERC20 token support and their application in loyalty systems.

Version 2.2 Changes: - Added transaction cost calculation in Gwei instead of Wei for better clarity. - Integrated Block Explorer API information for developers. - Removed outdated main API section. - Improved documentation structure for better readability.