Tri-Pillar Consensus
PoHH, PoCS, and CeR โ A Unified Framework for Merit-Based, Economically-Integrated Blockchain Consensus
Author
Jordan Pobienski
TRITO Foundation, Sofia
Version
v2.0 โ June 17, 2026
First disclosure: June 12, 2026
Contents
Abstract
This paper introduces three novel blockchain consensus protocols โ Proof of Hidden History (PoHH), Proof of Commitment & Streak (PoCS), and Community Engagement Rank (CeR) โ collectively forming the Tri-Pillar Consensus framework implemented in the TRITO blockchain ecosystem.
PoHH is the first consensus mechanism to incorporate real-time token burn events as cryptographic entropy for block sealing, creating a dual-layer history verification that is simultaneously computationally and economically resistant to manipulation. PoCS is the first consensus eligibility protocol to use streak continuity as a primary weight metric, fundamentally separating stake size from consensus influence. CeR is the first consensus weight system to employ dual-activity merit scoring โ simultaneously measuring staking consistency and trading activity as co-equal determinants of validator influence.
Together, these three protocols create a consensus architecture where validator influence is determined by behavioral commitment and community engagement rather than wealth accumulation, representing a fundamental departure from all existing Proof of Stake variants. To the authors' knowledge, none of these three mechanisms have prior art in existing blockchain literature as of the date of this publication.
1. Introduction
The dominant consensus paradigm in modern blockchain systems โ Proof of Stake (PoS) and its variants โ shares a common structural weakness: validator influence scales proportionally with token holdings. This creates plutocratic feedback loops where wealthy validators accumulate disproportionate block rewards.
This paper presents three protocols that together solve this problem:
PoHH
Addresses the entropy source problem โ where does the randomness for committee selection come from, and how can it be made simultaneously unpredictable and economically costly to manipulate?
PoCS
Addresses the eligibility and weight problem โ how can we gate validator participation on behavioral commitment rather than wealth?
CeR
Addresses the merit quantification problem โ how can we measure multi-dimensional community engagement and translate it into a fair, manipulation-resistant consensus weight?
1.1 Limitations of Existing Systems
Entropy manipulation
Most VRF-based systems derive randomness from block hashes or validator keys. These are computationally secure but economically decoupled โ the cost of manipulating entropy is unrelated to network activity.
Wealth proportionality
Even time-locked systems remain fundamentally wealth-proportional. A validator with 1,000,000 tokens locked for 1 day has more influence than one with 1,000 tokens locked for 210 days.
Single-dimension merit
No existing system measures validator merit across multiple independent activity dimensions simultaneously. CeR is the first to combine staking consistency AND trading activity into a unified weight.
2. Protocol 1: Proof of Hidden History (PoHH)
PoHH = PoH + BHH
Proof of History (deterministic hash chain) + Burning Hidden History (VRF-selected burn event entropy)
2.1 BurnEvent Structure
BurnEvent {
burner: address, // wallet that triggered the burn
amount: uint256, // tokens burned (18 decimals)
timestamp: uint256, // block timestamp
slotId: uint256 // slot identifier
}2.2 BHH Entropy Computation
targetSlot = previousSlot if |burnPool[previousSlot]| >= 3
else lastValidSlotId
selectedIndex = randomWord % |burnPool[targetSlot]|
selected = burnPool[targetSlot][selectedIndex]
BHH_entropy(N) = keccak256(
selected.burner,
selected.amount,
selected.timestamp,
selected.slotId
)2.3 PoHH Seal
PoHH_seal(N) = keccak256(PoH_hash(N), BHH_entropy(N), slot_id(N)) drawRand = keccak256(VRF_randomWord, PoHH_seal) member[0] = weightedSelect(candidates, effectiveTickets, drawRand) # effectiveTickets is the COMMITTED weight vector: a node in cooldown or # excluded by conduct carries zero, so it is skipped arithmetically rather # than by a per-candidate lookup. The vector is fixed at request time, # before the VRF word exists. # # member[0] is the primary draw, NOT a leader. All three members carry # identical duty and identical reward; the address is published singly # only because an external consumer must be able to name one party.
2.4 Security Scaling
| Daily Transactions | Burn Events/Block | Manipulation Difficulty |
|---|---|---|
| 100 | ~5 | Low (bootstrap) |
| 1,000 | ~50 | Medium |
| 10,000 | ~500 | High |
| 100,000 | ~5,000 | Very High |
| 1,000,000+ | ~50,000+ | Computationally Infeasible |
Game-Theoretic Property: Involuntary Security Contribution
Every trader who executes a swap generates a burn event for their own economic reasons. This burn event enters the BHH pool and strengthens consensus entropy โ automatically, without the trader needing to know about PoHH.
3. Protocol 2: Proof of Commitment & Streak (PoCS)
Core Innovation: Stake as eligibility gate only โ not influence
A validator with 1,000 tokens and 121 staking days has 150x more influence than one with 10,000,000 tokens staked for 1 day.
3.1 The 21-Tier Commitment Ladder
| Tier | Lock Duration | APR |
|---|---|---|
| 1 | 10 days | 5% |
| 2 | 20 days | 7% |
| 3 | 30 days | 10% |
| ... | ... | ... |
| 18 | 180 days | 100% |
| 19 | 190 days | 110% |
| 20 | 200 days | 120% |
| 21 | 210 days | 130% |
3.2 Commitment Accrual (v2)
Earlier versions used a consecutive-day streak that reset on any gap. It was replaced because it measured the wrong thing: it counted the days a participant sent a transaction, not the days their capital was actually committed โ and it punished a flat battery exactly as hard as abandonment.
WINDOW = 242 days (constant, not governable)
Time accrues continuously while the stake floor is met:
accruedStakeSecs += elapsed (no daily action required)
Days sit inside a rolling 242-day window โ twice the 121
the top rank needs, so up to half of it may be missed.
A missed day costs A DAY, NOT A STREAK. Nothing resets.
rank = min(rankByDays, rankByStake)
โ both gates must be met; the lower one binds.3.3 Early Unstake Mechanism (v2.0)
Sliding Scale Penalty โ Full principal always returned
earlyReward = principal ร (tierAPR ร 50%) ร (daysHeld / 365)
unstakeEarly(stakeIndex):
daysHeld = (block.timestamp - startTime) / 86400
earlyAprBps = originalAprBps / 2
reward = principal ร (earlyAprBps / 10000) ร (daysHeld / 365)
return principal + reward
Example โ Tier 18 (100% APR, 180-day lock):
Unstake at day 90: reward = 1,000 ร 50% ร (90/365) = 123.3 TRITO
Normal at day 180: reward = 1,000 ร 100% ร (180/365) = 493.2 TRITO3.4 Four-State Economy Integration
Normal state: Full APR (5%-130% per tier) Warning state: APR reduced by rebalancer SOS state: 5% flat all tiers HardCap state: 0% (no minting โ network under stress)
4. Protocol 3: Community Engagement Rank (CeR)
CeR Total Tickets = Staking Pillar + Trading Pillar + Behavior Pillar
Maximum: SS staking (1,024) + SS trading (1,024) + behavior = 2,048+ tickets
Tickets are derived, not awarded
Each pillar computes tickets as a fixed division of the resource committed โ TRITO held for staking, TRITO burned for trading. Weight is therefore linear in that resource, which is what makes splitting a holding across many wallets pointless: a hundred wallets earn exactly what one wallet with the same total earns.
Both gates must clear. Capital without time earns nothing above the lowest rank, and time without capital is capped by what is held. Days accrue inside a rolling 242-day window โ twice the 121 the top rank requires โ and halve at each window close, so rank measures current participation rather than a threshold crossed once.
4.1 Staking Pillar Ranks (max 1,024 tickets)
| Rank | Name | Days in window | TRITO held | Tickets |
|---|---|---|---|---|
| SS | Immortal | 121 days | 358,400 | 1,024 |
| S | Legend | 90 days | 179,200 | 512 |
| A+ | Elite | 75 days | 89,600 | 256 |
| A | Champion | 60 days | 44,800 | 128 |
| B+ | Veteran | 45 days | 22,400 | 64 |
| B | Contributor | 30 days | 11,200 | 32 |
| C+ | Rising | 20 days | 5,600 | 16 |
| C | Active | 15 days | 2,800 | 8 |
| D | Entry | 5 days | 1,400 | 4 |
| E | Novice | 2 days | 700 | 2 |
| F | New | 0 days | 350 | 1 |
4.1b Trading Pillar Ranks (max 1,024 tickets)
No stake requirement โ a trader who never locks capital can still climb. A burn qualifies when it exceeds a minimum tied to the rank being claimed and goes to an address other than the sender; only the amount destroyed counts, since a transfer between two wallets one controls costs nothing but the burn.
| Rank | Name | Qualifying burns | TRITO burned | Tickets |
|---|---|---|---|---|
| SS | MarketMaker | 766 | 15,360 | 1,024 |
| S | Whale | 444 | 7,680 | 512 |
| A+ | Shark | 255 | 3,840 | 256 |
| A | Trader | 146 | 1,920 | 128 |
| B+ | Dealer | 84 | 960 | 64 |
| B | Exchanger | 48 | 480 | 32 |
| C+ | Swapper | 28 | 240 | 16 |
| C | Buyer | 16 | 120 | 8 |
| D | Beginner | 9 | 60 | 4 |
| E | Newcomer | 5 | 30 | 2 |
| F | Fresh | 3 | 15 | 1 |
4.2 Behavior Pillar Adjustments
| Event | Adjustment | Enforcement |
|---|---|---|
| Consistent uptime (99%+ over 100 selections) | +5 tickets | Measured on-chain |
| Governance vote participation | +2 tickets | Recorded manually |
| Node dormancy (repeated missed selections) | -3 tickets | Automatic |
| Quarantine (repeated committee disagreement) | -5 tickets | Automatic |
| Double-sign, proven | -20 tickets | Slash is automatic |
| Double-sign, proven โ stake penalty | 50% slashed | Automatic, burned |
How these are enforced โ precisely
This distinction matters more than the numbers, so it is stated rather than implied. The evidence for every row above is produced on-chain and is permanently checkable. The execution splits in two:
The stake slash is fully autonomous. A proven double-sign report burns 50% of every active stake belonging to that operator, in the same transaction, with no further approval. The 50% figure is a hard ceiling in the staking contract itself โ no governance action can raise it.
Ticket adjustments are executed by governance against that on-chain record. The conduct contract computes and stores what is owed and emits it publicly; the Admin Safe applies it to the rank oracle. This is weaker than full autonomy, and it is a deliberate trade: granting a policy contract โ one expected to be retuned against real behaviour โ direct write access to the rank oracle would have meant handing it every other governance power at the same time.
Uptime is denominated in selections, not epochs or days. Slots open in response to network activity, so their timing varies; an epoch would be a unit the protocol cannot actually measure. Each window of 100 is assessed on its own โ a poor window is neither carried forward nor redeemable later by a recovering average.
4.3 Attack Resistance
Capital gets you through the door. Nothing more.
Half your rank must be burned for. Every power must be sealed for. Neither is for sale.
TIME CANNOT BE PURCHASED Attacker buys 10,000,000 TRITO, stakes today: 0 days accrued โ F-New โ 1 staking ticket The capital is present; the time is not. Rank requires both gates, and the lower one binds. SPLITTING CANNOT DILUTE 358,400 TRITO in one wallet, 121 days: SS-Immortal โ 1,024 tickets 358,400 TRITO split across 1,024 wallets, 121 days: 1,024 x F-New โ 1,024 tickets Identical. Tickets are a fixed division of the resource committed, so weight is linear in it โ and any linear weighting is indifferent to how it is divided. A sub-linear curve would REWARD splitting; that is the failure this replaces. WHAT IS NOT CLAIMED Capital now matters. A participant holding 1,000 TRITO cannot reach SS however long they wait โ the stake gate caps them at E-Novice. The protection is that influence cannot be acquired QUICKLY, and cannot be MULTIPLIED by fragmenting a holding. It is not a claim that small holders outweigh large ones.
4.4 Merit Credentials โ ARETE and MUNERA
Two non-transferable credentials sit alongside the ticket system. Neither can be bought, sold or moved: there is no transfer function, no approval, and no market. They exist to make certain powers reachable only by participation, in a protocol where capital already buys the entry ticket.
| Credential | Earned by | Spent on | Accrual |
|---|---|---|---|
| ARETE | Sealing blocks | Staking APR multiplier (up to ร3), and penalty-free early exit | 9.2% of seal reward |
| MUNERA | Staking interest | Shorter operator cooldown and a seal reward bonus | 3.1% of interest paid |
Each is earned by one activity and spent on the other, and that cross-link is the part that makes the system stable rather than a flourish. If sealing earned the credential that improved sealing, the most-selected operators would compound into permanent dominance and the cooldown between selections would stop doing its job. Crossing the two means winning selections never buys more selections โ it buys better staking terms, which is a different axis entirely.
Why non-transferability is a consensus property, not a policy
Spending a credential burns it, and those burns feed the entropy pool that selects sealers. An attacker with unlimited capital can flood that pool with ordinary trade burns โ but cannot spam credential burns at any price, because credentials accrue only through sustained participation over time. A portion of the entropy supply is therefore sybil-resistant by construction rather than by assumption.
Base staking APR was reduced to one third when ARETE was introduced, and ARETE restores it. This was not a yield cut dressed up as a feature: staking previously minted far more TRITO than node rewards did, and node rewards are burn-backed while staking was minted against nothing. Yield above the base is now earned through consensus work rather than bought with capital, and total issuance roughly halves.
5. Tri-Pillar Integration
PoHH
Entropy source
What randomness seals this block?
PoCS
Eligibility gate
Who is allowed to participate?
CeR
Selection weight
Who gets chosen from eligible participants?
Block Sealing Flow
Step 1: ACTIVITY GATE โ a slot may open only once the closing one
cleared BOTH bars: burn VOLUME and a distinct burn EVENT count.
Neither implies the other: one whale transfer clears any volume
bar while producing exactly one event. Slots therefore track real
activity rather than a clock.
Step 2: requestSlot()
โ PoH hash: keccak256(blockhash, currentSlot)
โ The CANDIDATE SET is resolved and committed HERE โ eligible
nodes, their cooldown-adjusted weights, and the weights root.
Doing this before randomness exists means no party who learns
the VRF word can influence who was a candidate for it.
โ VRF request fired to Chainlink
Step 3: Chainlink VRF returns randomWord
โ fulfillRandomWords() triggered
Step 4: Inside fulfillRandomWords():
โ BHH: the VRF word selects one burn event from the valid slot
โ PoHH seal: keccak256(PoH_hash, BHH_entropy, slotId)
โ THREE EQUAL SEALERS drawn from the committed weight vector.
There is no leader. The address published externally carries
the primary draw only because an outside consumer must be able
to name one party; it holds no extra duty and no extra reward.
โ NOTHING IS MINTED HERE.
Step 5: Seal window
โ Each member independently derives the slot's result and submits
it with submitAttestation(). A member that merely shows up earns
nothing โ the work is agreeing.
Step 6: finalizeSlot()
โ Two of three must have submitted the SAME value for the slot to
seal. Matching members are paid a FLAT, IDENTICAL share to their
owner wallet; a member that disagreed or never attested is not.
โ Issuance is burn-backed: the reward is computed from TRITO
actually destroyed in the previous slot, so a quiet market mints
nothing at all.
Step 7: Next slot
โ The seal and the committee become entropy leaves for a FUTURE
slot's BHH selection. Every component is fixed at fulfilment, so
the leaves cannot be ground by choosing to seal or not.5.1 Presence โ absence is not misconduct
A participant running from a phone can only prove it is online while the application is open; mobile operating systems do not permit background signing. Under a naive rule such a node is selected while asleep, fails to attest, and is penalised for the failure โ three consecutive misses send it dormant. Worse, a committee containing two absent members can never reach the agreement threshold, so the slot does not seal and the one honest member goes unpaid.
TRITO therefore separates being offline from misbehaving. A node proves liveness by signing a short-lived message committing to a recent block hash. A node whose proof has expired is simply not selected, and rejoins the moment it signs again โ no misses accrue, no penalty applies, and no committee is poisoned.
The commitment to a recent block hash is what prevents pre-signing: a signature cannot be produced before the block it references exists, so a node cannot prepare a supply of proofs and go offline.
This does not make phones continuously available, and the protocol does not claim it does. It makes their absence accurate and costless, which is a different and achievable goal.
Comparison to Major Consensus Systems
| Property | Bitcoin PoW | Ethereum PoS | Solana PoH+PoS | TRITO PoHH+PoCS+CeR |
|---|---|---|---|---|
| Energy efficient | โ | โ | โ | โ |
| Wealth independent | โ | โ | โ | โ |
| Streak/consistency metric | โ | โ | โ | โ |
| Trading as consensus input | โ | โ | โ | โ |
| Burn events as entropy | โ | โ | โ | โ |
| Dual verification sources | โ | โ | โ | โ |
| Security scales with volume | โ | โ | โ | โ |
| Economic self-healing | โ | โ | โ | โ |
| Flexible early exit | โ | โ | โ | โ |
6. Novelty Claims
To the authors' knowledge, the following claims represent genuine novel contributions to blockchain consensus research as of June 12, 2026:
PoHH Novelty Claims
- 1.First use of real-time token burn events as cryptographic entropy for block sealing
- 2.First dual verification of block entropy from two independent on-chain sources
- 3.First consensus mechanism where trading activity directly and automatically strengthens consensus security
- 4.First consensus entropy mechanism whose security scales proportionally with trading volume
- 5.Combination of deterministic hash-chain ordering (PoH) with economic burn entropy (BHH) into a single compound consensus pillar
PoCS Novelty Claims
- 1.First consensus protocol to use streak continuity as a primary consensus weight metric
- 2.First implementation of stake as eligibility gate only โ completely separating stake size from consensus influence
- 3.First 21-tier commitment ladder where lock duration determines reward tier rather than proportional stake weight
- 4.First consensus protocol with sliding-scale early exit โ proportional penalty preserving capital safety
- 5.Integration of consensus eligibility with a four-state economic self-healing mechanism
CeR Novelty Claims
- 1.First consensus mechanism to use dual-activity merit scoring โ combining staking AND trading consistency as co-equal consensus weight determinants
- 2.First implementation of 12-tier symmetric rank ladders for both staking and trading pillars (144 possible rank combinations)
- 3.First system where trading activity feeds both consensus weight (tickets) AND consensus entropy (burn events) simultaneously
- 4.First consensus weight system achieving complete wealth independence
7. Implementation
7.1 Smart Contract Architecture
| Contract | Role | Protocol |
|---|---|---|
| TRITOToken.sol | BurnEvent collection, slot tracking, four-state economy | PoHH |
| TRITOSequencer.sol | PoHH seal computation, BHH entropy, VRF integration | PoHH |
| TRITOStaking.sol | 21-tier ladder, early unstake, slashing | PoCS |
| CEROracle.sol | Dual-activity rank computation, ticket management | CeR |
| TRITORebalancer.sol | Dynamic APR adjustment, halving schedule | PoCS |
| TRITOReleaseCalendar.sol | Governance-gated token release schedule | Governance |
| RegistrationGift.sol | ECDSA-signed 500 TRITO welcome gift | Community |
| TRITOVestingVault.sol | Universal vesting for team, investors, DAO | Tokenomics |
| TRITOAirdropDistributor.sol | Merkle proof airdrop, badge vesting 20/40/40% | Community |
7.2 Deployed Addresses (Arbitrum Sepolia, CeR v2)
TRITOToken: 0xE5625CE0308054EEcBCC9444beA7cbbF9E009ee9 TRITOStaking: 0x1635FBC162Eae19b8EAC74fD828411e6d4a3Abb4 CEROracleV2: 0x207178a1679267A32C33d81baC4575933c9186e0 TRITOSequencer: 0x9De332379dF06aF8DF6f71376dcfDfbE62Aae57e TritoIssuancePolicy: 0x88C76fA268Fcb4739c79ACE356B2302a3F552871 TritoSequencerLens: 0xf59F07675C835655f6d6D9Fc81ac77AF6712b55a TRITOBurnForwarder: 0x206E548e9a3193377ca15bb1Ddea575De00ca64d TritoSequencerSelector: 0xfCC878d7Ce207fD5444F37EB5592a5A10690fc33 TRITONodeConductV2: 0x800DA86dbEd73507B9F165f47C47f591b4051C28 ARETECredential: 0x8E0Bc6aB59A83F476495b89FC49580735F2bc2D6 MUNERACredential: 0xbe7E2907938Da3A373AeD2FCaCe055003C191e30 TritoNotary: 0xbAb74285E0D795F1583b9F10b25d9d7C1A577685 TritoNotaryLens: 0xc5F4792c3edE72367f869148925dF72F04C778Ec PresenceAnchor (ArbSys): 0x1E53732A2196923396FA6f863B6915753efd6493 TRITORebalancer: 0x72c5C48E45D126184F109Fde09707806F505faf6 TRITOReleaseCalendar: 0x9046F40751C0603a5222854f156D37EE3b321b0e RegistrationGift: 0x3F5D7A12238d29F136a30405D6EfC2eB5e14D2dB TRITOVestingVault: 0x88fc55128BbBB86F69D3ae103EBf60a127c7b7e9 TRITOAirdropDistributor: 0x2469Aa07d87a19F927B50433eb4e96fDb439F3B3 Multi-tenancy (2026-08-30): TritoTenantRegistry: 0xc0915D2271A14897398C33657a8080D69713Eac4 TritoElection: 0xcfd26c35feE886078c6AD4a61D997ea56a48F037 TritoTenantPerformance: 0x77f5c09F678E788D3267f4918986EF652B218f55 TritoRewardPool: 0xDA58f6E88a79edD8404Bb342b1e54D6026c2Bab2 TritoFloorPayer: 0xd13aFeeA97686f99b6A968EDD7aB53F2737a2068 TRITOToken is never redeployed โ it holds every balance. Everything else above was replaced at the CeR v2 rebuild because each held an immutable reference to the oracle. Sequencer + Selector replaced 2026-08-08: the VRF callback exceeded Chainlink's 2,500,000 gas ceiling once the network had enough nodes to seal continuously, stranding three slots. The candidate set is now resolved when a slot is requested rather than inside the callback โ 2,642,585 gas before, 832,537 after. Conduct replaced 2026-08-17 to add presence heartbeats, so a node that is offline is simply not selected rather than accruing misses toward dormancy. Sequencer replaced again 2026-08-29 for issuance v4: rewards now scale with burn volume instead of clamping to a flat 210. The contract had reached EIP-170's 24,576-byte limit, so the economic parameters moved to TritoIssuancePolicy and the read-only audit surface to TritoSequencerLens โ both replaceable without touching consensus.
7.3 Tokenomics
Total Supply
2,000,000,000 TRITO
Transfer Tax
0.6% (0.3% charity + 0.3% dev) โ capped at 2%
Staking Tiers
21 tiers, 1.67% to 43.3% base APR โ up to ร3 with ARETE
Airdrop Pool
150M TRITO (7.5% of supply)
Registration Gift
500 TRITO (first 10,000 members)
Test Coverage
418 contract tests passing
7.4 Notary โ corroboration as a service
Summarised here as a deployed component; see ยง8 for how it sits alongside the other services offered to external chains.
The committee that seals a slot is, at no additional cost, a set of independently-operated machines selected by verifiable randomness and weighted by reputation earned over months. That is an unusual object, and it is useful to parties who have nothing to do with TRITO's consensus.
An external organisation registers, posts a refundable bond, and files a 32-byte checkpoint โ typically a commitment to its own state over some period. The checkpoint is stamped with the open slot and frozen when that slot closes; the committee attesting the following slot folds it into the value they independently compute. Two of three must agree.
What this produces is narrow and precise: this value was filed by this party, in this slot, and was independently recorded by a committee nobody chose.
It is not validation. TRITO's nodes have not executed the filer's chain, do not hold its state, and could not detect a fraudulent root. This is timestamping and corroboration; a party filing nonsense about itself receives nonsense faithfully recorded. Verifying correctness would require running the filer's chain โ a different service with different economics and a different operator class.
We state the limit explicitly because a corroboration service that oversells its guarantee is worse than none, and because overstating it would imply liability for state that was never checked.
Economics
Each checkpoint carries a fee. Sixty percent goes to the committee that corroborated it โ split only among members whose attestation matched the canonical value, since being elected is not the work. The contract enforces a floor: the operator share cannot be set below forty percent. Revenue that does not reach the machines producing the service is extraction, and it is the parameter most likely to drift downward one governance decision at a time unless something refuses.
This is the protocol's first revenue that is not issuance. Sealing rewards are minted against destroyed supply; notary fees are paid by a customer. The distinction matters for a network that intends to outlast its emission schedule.
โ The treasury share is a transfer, not a burn. The token records burns only through its taxed-transfer path, so protocol revenue does not currently contribute to burn accounting or to BHH entropy. Correcting this requires a token-level function and the token is never redeployed โ it is therefore a mainnet-launch decision rather than a later fix.
8. Services for External Chains
Electing a committee produces something reusable: a set of independently-operated machines, chosen by verifiable randomness, weighted by reputation earned over months, and required to agree before anything is recorded. That object is useful to parties who have no interest in TRITO's own consensus. What follows is what TRITO offers them, what it charges, and โ as importantly โ what each service does not claim.
| Service | Status | Price | What it gives you |
|---|---|---|---|
| Notary โ checkpoint corroboration | Live | Bond + per checkpoint | Proof a value existed at a time, recorded independently |
| Committee election | Deployed (testnet) | Prepaid escrow | Verifiable, reputation-weighted selection among YOUR operators |
| Entropy beacon | Live | Free | Randomness whose manipulation costs destroyed value |
8.1 Notary โ corroboration (live, paid)
An organisation files a 32-byte checkpoint โ typically a commitment to its own state over some period. It is stamped with the open slot and frozen when that slot closes; the committee attesting the following slot folds it into the value they independently compute, and two of three must agree.
The result: this value was filed by this party, in this slot, and independently recorded by a committee nobody chose.
Not validation. The nodes have not executed the filer's chain and could not detect a fraudulent root. A party filing nonsense about itself receives nonsense faithfully recorded.
Cost: a refundable bond, returned in full, plus a fee per checkpoint. Sixty percent of each fee goes to the committee that corroborated it โ split only among members whose attestation matched โ and the contract refuses to set that share below forty percent.
8.2 Committee election (deployed on testnet, paid)
Every rollup with a centralised sequencer faces the same question: who sequences next, and can anyone verify the choice was fair? Most answers stop at stake-weighted randomness and ask you to trust the output.
TRITO's selection can be recomputed. The weight vector is committed before the randomness exists, so an observer holding the published leaf set can re-run the draw and arrive at the same committee. Selection being reproducible proves the right parties were chosen; agreement proves they reached the same result independently.
What it elects: your own operators, not TRITO's. They register, stake, and accrue reputation on the same two-pillar ladder described in ยง4 โ which is what makes the weighting sybil-resistant rather than a proxy for wealth.
Scope, stated honestly: this is epoch-level election, not block-level scheduling. Verifiable randomness takes seconds and a rollup produces blocks in milliseconds; anyone claiming otherwise is describing something else. TRITO elects who is authorised for a window, and publishes an intra-epoch rotation so a member going dark costs a grace period rather than the whole window.
Not yet available: it requires multi-tenancy โ the ability to elect from a consumer's operator set rather than TRITO's own โ which is a change to the reputation oracle and is scheduled with the mainnet architecture work.
8.3 Entropy beacon (live, free)
Every sealed slot publishes a PoHH seal binding a proof-of-history hash, the burn-derived BHH component, and the VRF word. Any contract may read it, andverifySealconfirms the published seal genuinely binds its published components.
What is unusual about it: most randomness can be biased by a party willing to forgo a reward. Influencing BHH requires destroying TRITO. The cost of manipulation is denominated in burned value rather than opportunity cost.
What it is not: TRITO does not generate randomness โ it consumes Chainlink VRF and mixes it with burn-derived entropy. This is defence in depth, not a superior primitive, and a consumer who trusts Chainlink completely gains little. It is also slot-paced, so it suits a weekly draw or a jury selection, not randomness on demand.
Free, permanently. It is published on-chain and could not be metered without withholding data that is already public. Charging for it would mean pretending to restrict something we cannot.
A note on what is being sold
Published on-chain state cannot be paywalled: anyone may read the selection, the seals and the weights, and TRITO could not tell who did. What can be charged for is work โ a committee corroborating a checkpoint, operators servicing a consumer's chain. Where a service is only data, it is free, and described as such. A protocol that claims to gate what it cannot gate invites the first person who checks to disprove it.
9. Conclusion
This paper has introduced three novel blockchain consensus protocols โ PoHH, PoCS, and CeR โ that together form the TRITO Tri-Pillar Consensus framework. Each protocol addresses a distinct limitation of existing consensus mechanisms:
PoHH
Creates consensus entropy that is simultaneously cryptographically secure and economically costly to manipulate, scaling in security with network trading volume.
PoCS
Eliminates wealth proportionality from consensus by separating eligibility (stake presence) from influence (commitment duration + streak consistency), with a flexible early exit mechanism that preserves capital efficiency.
CeR
Introduces multi-dimensional merit scoring that rewards genuine ecosystem engagement across two independent activity dimensions.
The combination creates, to the authors' knowledge, the first consensus system where validator influence cannot be purchased with wealth alone but must be earned through sustained behavioral commitment to the network.
10. Intellectual Property Declaration
The protocols described in this paper โ PoHH, BHH, PoCS, and CeR โ were conceived and designed entirely by Jordan Pobienski.
This paper constitutes a public disclosure establishing prior art for all protocols described herein. Any implementation of PoHH, PoCS, or CeR after June 12, 2026 post-dates this disclosure.
ยฉ 2026 Jordan Pobienski / TRITO Foundation. All rights reserved.
First disclosure: June 12, 2026. Version 2.0: June 17, 2026.