The Tri-Pillar Consensus
Three independently novel blockchain consensus protocols — invented by Jordan Pobienski, first disclosed June 12 2026, permanently published with a citable DOI on Zenodo.
PoHH
Proof of Hidden History
Entropy Source"What randomness seals this block?"
PoCS
Proof of Commitment & Streak
Eligibility Gate"Who is allowed to participate?"
CeR
Community Engagement Rank
Selection Weight"Who gets chosen from eligible participants?"
Pillar 1 — Entropy Source
PoHH — Proof of Hidden History
PoHH is a compound entropy protocol — the first consensus mechanism to use real-time token burn events as cryptographic randomness for block sealing. It combines two sub-protocols:
PoH — Proof of History
SHA-256 recursive hash chain. Creates a deterministic cryptographic clock. Every slot references the previous block hash — tamper-evident and verifiable.
PoH = keccak256(blockhash, slotId)BHH — Burning Hidden History
VRF randomly selects one burn event from the previous block's trading activity as additional entropy. The selected event is hidden until VRF fires — yet permanently recorded.
BHH = keccak256(burner, amount, timestamp, slotId)// Final PoHH seal
PoHH_seal = keccak256(PoH_hash, BHH_entropy, slotId)
🎲 The Hidden Property
The burn event selected as entropy is unknown until VRF fires — yet permanently recorded in two places: block history AND contract event log. Dual verification.
📈 Scales with Volume
More trading = more burn events = larger entropy pool = harder to manipulate. Security scales directly with network economic activity — a first in blockchain.
🔄 Involuntary Security
Traders unknowingly contribute to consensus security through normal trading. No extra action required — every swap automatically strengthens block sealing entropy.
Minimum 3 burn events required
A slot must have at least 3 burn events to be valid for BHH selection. This prevents single-transaction entropy manipulation. Empty or low-activity slots fall back to the last valid slot.
Pillar 2 — Eligibility Gate
PoCS — Proof of Commitment & Streak
PoCS fundamentally separates two questions that classical Proof of Stake conflates:
Eligibility question
"Should this node be allowed to participate?"
Answer: Yes, if they have staked any amount. Stake SIZE is irrelevant — only presence matters.
Influence question
"How much consensus weight do they have?"
Answer: Proportional to lock duration tier and streak consistency. Stake size is completely irrelevant here.
21-Tier Commitment Ladder
5%
10d
T1
10%
30d
T3
17%
50d
T5
26%
70d
T7
50%
110d
T11
100%
180d
T18
130%
210d
T21
Full 21 tiers from 10 days/5% APR to 210 days/130% APR. APR is fixed — not proportional to stake size.
⏱ Streak Mechanics
Staking streak increments by 1 for each consecutive daily epoch with an active stake. Missing a day resets to 1.
Key: unstaking does NOT reset the streak. Only missing a consecutive epoch resets it.
💡 Wealth Attack Resistance
An attacker staking 10,000,000 TRITO today has 1 CeR staking ticket. A regular participant with 1,000 TRITO staking for 121 days has 250 tickets.
Time cannot be purchased.
Pillar 3 — Selection Weight
CeR — Community Engagement Rank
CeR is the first consensus weight system to use dual-activity merit scoring — measuring both staking consistency AND trading activity simultaneously as co-equal determinants of validator influence.
250
max staking tickets
12 tiers — F-New to SS-Immortal
250
max trading tickets
12 tiers — F-Fresh to SS-MarketMaker
±50
behavior adjustment
bounded per call — manipulation resistant
🔗 Cross-Pillar Integration
Trading activity simultaneously feeds CeR trading rank (more tickets) AND PoHH BHH entropy (burn events). The same economic action contributes to both consensus weight and consensus security.
How the Three Pillars Interact
Trading activity feeds:
Staking activity feeds:
Block sealing flow
5-second slot timeout → all burn events collected for BHH entropy pool
requestSlot() called → PoH hash computed → VRF request fired to Chainlink
Chainlink VRF returns (~30 seconds) → fulfillRandomWords() triggered
BHH: VRF selects one burn event from valid slot → combined with PoH = PoHH seal
CeR: PoHH seal used as additional entropy → weighted selection from ticket pool
Leader + 2 co-signers selected → rewards distributed (70% / 25% / 5%)
Intellectual Property Notice
The protocols described on this page — PoHH (Proof of Hidden History), BHH (Burning Hidden History), PoCS (Proof of Commitment & Streak), and CeR (Community Engagement Rank) — were conceived and designed entirely by Jordan Pobienski, TRITO Foundation, Sofia, Bulgaria.
First disclosure
June 12, 2026
GitHub commit 8f6870c
Published record
Zenodo DOI
10.5281/zenodo.20767816
Implementation
Live on Sepolia
100/100 tests passing