HOME / WHITEPAPER · DRAFT 0.1

Diethyllence:
a technical overview.

Network architecture, asset roles, ecosystem applications, and the limits of the current deployment.

Project overview18 November 2026Diethyllence network · Chain 9428
Read this first. This document describes an experimental network. It is not a promise of production availability, token value, reserves, governance rights, or future features.
01

Executive summary

Diethyllence is an EVM-compatible Layer 1 ecosystem built on Hyperledger Besu. Its public network uses QBFT proof-of-authority consensus, chain ID 9428, and a configured one-second block period. The project combines a lightweight explorer, a V2-style decentralized exchange, token contracts, and planned app destinations for launches and games.

The network has five validators across four VPS hosts. Validators 1 and 2 share one host, so losing that host removes two validators and stops QBFT finality. This setup is not production-ready. THYL is the native gas asset and is intended to become a stable-value unit. The project targets full 1:1 reserve backing and a published redemption process within the first 30 days of ecosystem rollout; this remains a target until reserve evidence and terms are published. DPT is a fixed-supply ERC-20 intended for protocol and ecosystem governance. Voting and delegation are planned but not active in the current deployment.

02

Network architecture

Besu provides Ethereum-compatible execution. QBFT validators propose and finalize blocks under proof-of-authority rules. The genesis configuration sets a one-second block period, zero block reward, chain ID 9428 (0x24d4), and an initial native THYL balance for the configured genesis account.

Execution clientHyperledger Besu
ConsensusQBFT · Proof of Authority
Chain ID9428 / 0x24d4
Configured block period1 second
Validator count2 · shared VPS
Block rewardZero

The public RPC is served over HTTPS at scan.diethyllence.com/rpc/. The explorer at scan.diethyllence.com reads blocks, transactions, token details, and transfer events. A rate-limited Nginx proxy forwards RPC requests to a loopback-only Besu listener.

QBFT’s fault tolerance depends on validator count and independence. The current validators share a host and network failure domain; loss of that VPS stops both validators. A two-validator setup does not provide production fault tolerance. Additional independently operated validators, operational monitoring, and tested recovery procedures are needed before production use.

03

THYL: native coin and intended stable-value unit

THYL is Diethyllence’s native currency. It is used for gas and can be transferred without wrapping. The planned stable-value model is full 1:1 reserve backing paired with a published redemption process.

Rollout target: the project targets reserve and redemption readiness within the first 30 days of ecosystem rollout. This is a forward-looking goal, not a statement that reserves or an enforceable redemption right are already active. Reserve evidence, custody arrangements, and redemption terms should be published before THYL is represented as fully backed or redeemable.

Wrapped THYL (WTHYL) is a separate ERC-20 representation used by the V2 pool. The wrapper mints one WTHYL for each THYL deposited and returns the same amount of native THYL when withdrawn, subject to the deployed contract’s behavior and chain availability.

04

DPT: fixed-supply protocol token

The Diethyllence Protocol Token (DPT) is an ERC-20 with a capped supply of 1.1 billion tokens. Its constructor mints the full supply across seven allocation addresses:

AllocationAmountShare
Operations10,000,0000.91%
Founder / core190,000,00017.27%
Treasury200,000,00018.18%
Airdrop100,000,0009.09%
Ecosystem400,000,00036.36%
Staking100,000,0009.09%
Liquidity100,000,0009.09%
Total1,100,000,000100%

The allocation labels describe the constructor’s recipient wallets. They do not establish current circulating supply, vesting schedules, distribution timing, or a future market value. The addresses and balances should be verified on the explorer before relying on them.

05

Applications and ecosystem

The ecosystem’s web entry points are separate applications intended to connect with the same chain. Explorer and Swap are the current interfaces in this project workspace; Pump and Play are linked as ecosystem destinations, with their service implementations maintained separately.

The DEX includes a DPT/WTHYL V2 pool and token routes that may include bonding-curve legs. The V2 swap fee is 0.30%. Some routes are multi-step and are not atomic; if a later transaction fails, an intermediate asset can remain in a wallet. A qualifying SPIN purchase can create a pending roulette spin that pauses its curve until resolved.

The explorer is a lightweight onchain reader rather than a full historical indexing service. Token-transfer history is read from RPC in bounded block windows and is subject to public RPC limits.

06

Governance and fee routing

Governance status

DPT is designed to be the protocol’s governance asset. The deployed DPT contract is currently a fixed-supply ERC-20 and has no voting, delegation, proposal, or execution functions. The governance portal and onchain voting process are planned rollout items; governance rights should be described as active only after the voting design, contracts, rules, and operational controls are published and deployed.

Fees and buyback allocation

The FeeRouter contract splits native coin held by the contract when routeFees() is called: 50% to founder, 20% to employee, 20% to capital reserve, and 10% to buyback reserve. It does not automatically intercept each transaction’s gas fees. Besu’s block-beneficiary credit does not execute the FeeRouter, so automatic gas-fee routing would require a coordinated protocol change on every validator.

The 10% allocation is a transfer to a reserve wallet, not an executed DPT buyback or burn. Automated purchasing and burning are not implemented.

07

Onboarding and cross-chain payments

Compatible EVM wallets can connect by adding Diethyllence with chain ID 9428, symbol THYL, and RPC https://scan.diethyllence.com/rpc/. Wallets sign and submit transactions; the dApp does not custody a user’s wallet keys.

The current Buy THYL flow watches approved USDT or USDC transfers to a configured treasury on BNB Smart Chain, Base, or Polygon PoS and, after chain-specific confirmations, sends THYL from an operator-controlled wallet to the same address. It is an operator-run payment service, not a trustless cross-chain bridge. It relies on the watcher, treasury configuration, source-chain RPCs, payout key, and available THYL balance. The displayed 1:1 amount is operator-set and does not establish a dollar peg.

08

Security, limitations, and user risks

  • Validator concentration: both validators currently run on one VPS. A host failure can stop block finality.
  • Not production-ready: the network and applications have not received independent production security audits. Validators 1 and 2 share a host, so losing that VPS stops finality.
  • THYL backing: reserve backing, enforceable redemption, and peg controls need public evidence, operating terms, and ongoing verification.
  • Randomness: SPIN uses blockhash-derived randomness, which is unsuitable for secure high-value outcomes on a permissioned chain.
  • Multi-step swaps: some swaps require multiple wallet-confirmed transactions and may leave an intermediate asset if a later step fails.
  • Indexer scope: the explorer reads data from RPC and is not a complete or independently indexed historical record.

Users should use test funds only, inspect the transaction details shown by their wallet, and independently verify contracts and balances through the explorer.

09

Network parameters and contracts

ItemAddress / value
NetworkDiethyllence · chain ID 9428 (0x24d4)
Public RPChttps://scan.diethyllence.com/rpc/
DPT0x97A4d78011Ec937C4BFF69E039a2697d7C015818
V2 Router0x68426a87800ec06C05e9aeFB53422d0C03D6eC8B
V2 Factory0x0a443dE3a1421116F10511893ED70597B0bB6320
Wrapped THYL0x30f0111501808E29cFFfe8332d282F671DB8Fc82
DPT / WTHYL pair0x9Dec642CD3BBC13dc8e129d53bf2Dc6061A96EcC
FeeRouter0xda1DC7F370Cbdc552dA4aE8f311049976128CfD8

Deployment records are maintained in the project repository under deployments/9428/. Addresses should be checked against the live network before use.

10

Development priorities

The project’s next steps are engineering priorities, not release commitments:

  1. Separate validators into independent hosts and failure domains; define reliable peer, backup, and recovery procedures.
  2. Publish network monitoring, RPC limits, service status, and operational documentation.
  3. Establish THYL reserve custody, independent reserve reporting, redemption terms, compliance procedures, and risk controls against the 30-day rollout target.
  4. Deploy and publish DPT voting, delegation, treasury safeguards, governance rules, and operational controls.
  5. Review the bridge and token contracts independently; replace unsafe randomness before any real-value game use.
  6. Build and maintain dedicated status, WebSocket, indexing, governance, staking, and developer services as their designs are ready.

In closing

A foundation to test.
A network to earn trust.

Diethyllence’s current value is in making the chain and its applications testable. Production readiness depends on stronger validator independence, transparent THYL backing and redemption, active governance design, and independent security review.

Back to Diethyllence →

Draft project overview compiled from the current Diethyllence repository and project notes. It is informational, not a financial offer, investment advice, reserve attestation, audit report, or guarantee of future development.