Native-chain integration

Torvyon Exchange Integration

ₜBit is the native coin of Torvyon, an independent proof-of-work Layer 1. This page gives exchange teams the facts and public endpoints needed to evaluate deposits, withdrawals, and market support.

Mainnet launch: October 23, 2026. Torvyon is not an ERC-20, BEP-20, or other contract token; no contract address applies.
SHA-256dProof-of-work consensus
40 secondsTarget block interval
210,000,000 ₜBitMaximum supply

Network and wallet model

Native UTXO coin

ₜBit moves on Torvyon’s own chain. Addresses use the qbt1 / tqbt1 family, and transactions are signed with ML-DSA-65 (FIPS 204). There is no smart-contract token address.

Chain behavior

Nodes verify signatures, transaction rules, inputs, outputs, and replay protection before relay. The chain selects the valid branch with the greatest cumulative work; difficulty retargets every 45 blocks.

Public REST API

The current public integration surface is REST-based rather than JSON-RPC. These endpoints are available for read-only exchange monitoring.

/statusnetwork status
/api/supplysupply data
/api/blocks?limit=25recent blocks
/api/tx-confirmation/{hash}confirmation status
/tx/{hash}transaction lookup
/block/{idOrHash}block lookup
/api/address-utxos/{address}UTXOs for an address
/api/address-transactions/{address}address transactions
/api/mempoolmempool status
/api/peerspeer status

Deposit and withdrawal flow

Deposits

  • Assign a unique Torvyon address to each user.
  • Monitor the address and transaction hash through the explorer/API.
  • Credit only after the exchange’s selected confirmation threshold is reached.

Withdrawals

  • Validate a destination qbt1 address before sending.
  • Create and sign a native Torvyon transaction through the wallet/node integration.
  • Store the transaction hash and expose it to the user for verification.

Confirmation policy

Recommended starting policy

This is an operational recommendation for exchange review, not a protocol guarantee. Start with 1 confirmation pending, 6 confirmations for normal credit, and 12 confirmations for high-value withdrawals. At the 40-second target, these are approximately 40 seconds, 4 minutes, and 8 minutes respectively. Each exchange should set its own risk policy after testing reorg and node behavior.

Official resources