Real compute revenue buys LYK and burns it. Supply only goes down.

Resource buy-back transparency

Machines online
2,000
Compute fleet earning USDT
Total earned
$0
Cumulative USDT revenue to date
LYK burned
0
Permanently removed from supply

Supply reduced 0.00% · 1B of 1B LYK remaining

Tracking since July 1, 2026.

The engine

Each month, 100% of resource earnings buy LYK, which is burned in a single monthly burn event.

Machines
Compute fleet
Revenue
100% in USDT
Buy-back
USDT buys LYK
Burn
One monthly burn
Supply down
Scarcity rises

More machines means a bigger engine, and every monthly cycle scales with the fleet.

Live

Compute online now

2,000 machines, live and earning today.

CPU cores
8,000
Memory
24.0 TB
Storage
512.0 TB
Power draw
12.0 kW
Simulator: what if the fleet grows?

Hypothetical projection. Today's real fleet is 2,000 machines.

2,000 machines
2,00038,000

8,000 cores · 24.0 TB RAM · 512.0 TB storage

Monthly revenue
$100,000
LYK bought / month
989.12K
LYK burned / year
11.87M
≈ 1.19% of total supply / year

Assumes $50 / machine / month. LYK monthly average price: $0.1011 / USDT (reference average, not live spot).

At larger fleet sizes, actual buy-backs depend on available market liquidity.

Resource earnings

Total to date · Monthly
$0
Jul 2026 – Apr 2027

USDT earned by the fleet each month. 100% funds the monthly LYK buy-back.

Tracking since July 1, 2026.

Earnings are reported figures. The on-chain anchor is the monthly burn below.

Each monthly buy-back is executed at prevailing market prices, so cumulative USDT earned and total LYK burned will not divide to the reference price.

Live burn proof

The one number you don't have to take our word for. Read it straight from the burn wallet.

Burn wallet
0x000000000000000000000000000000000000dEaD
Explorer
Supply remaining1B / 1B LYK
1B remaining · 0 burned (0.00%)

Recent burns

No burns yet. The first monthly burn posts after the first full month.

Figures marked illustrative are placeholders pending real data. Earnings are reported by LayerK; the burn total and recent burns are independently verifiable on-chain via the burn wallet linked above.