BlackHartBlackHart
Scores/Kinetiq/Provenance/Cross-Chain Messaging
D10

Cross-Chain Messaging

Conditional: bridge trust model, sequencer risk, fraud proof maturity, cross-chain replay risk.

Weight conditional75% confidence
42
Concerning
info

How This Score Is Built

Conditional: bridge trust model, sequencer risk, fraud proof maturity, cross-chain replay risk.

+23Strong positive
+12Positive
+5Slight positive
−15Strong negative
−8Negative
−3Slight negative

Scoring Tree

BRI Formula
300 + 700 × ∏(Dᵢ/100)^wᵢ
688
Current BRI
D10Cross-Chain Messaging
Weight 7%
42
(42/100)^0.07 = 0.9411
Sub-Scores
Message Verification
30
Ack Reconciliation
25
Endpoint Trust
55
Contributing Factors
+10ACTIVATED in this pass. Kinetiq has a genuine EVM<->HyperCore (Hyperliquid L1) read/write bridge: L1Write precompile at 0x3333...3333 (delegate/undelegate/spot-transfer writes) and L1Read precompiles (0x2222/0x1111 endpoints) for reading L1 staking/spot state. This is a real cross-chain-style messaging surface, weight ~0.07.
+10Burn-before-L1-ack (#2248, passing PoC): confirmWithdrawal burns kHYPE and pays from a shared address(this).balance pool with no per-request L1 settlement proof — cross-user drain / undercollateralization risk during L1 desync
+10L1Write silent-drop (#37, passing PoC): HyperCore's per-address pending-op queue limit silently drops ops beyond the limit while the EVM updates accounting as if successful — EVM<->L1 state desync
+10Trusted L1 precompile endpoints (#2249); no independent verification layer between EVM accounting and L1 truth
-29L1Write is FIRE-AND-FORGET: emits events, never reverts, returns nothing — the EVM contract cannot verify the L1 op actually executed (no read-after-write reconciliation). This is the core cross-chain weakness.
-29Scored 42 (weak): a real, exploitable, no-acknowledgement bridge surface with multiple passing-PoC desync findings. Activating D10 LOWERS the composite vs leaving it out — the honest direction.
Evidence Sources
blackhart_analysisMay 30sha256:4a1db3dd045a....

Sub-Score Breakdown

Message Verification
30
Ack Reconciliation
25
Endpoint Trust
55

Score Composition

-29

L1Write is FIRE-AND-FORGET: emits events, never reverts, returns nothing — the EVM contract cannot verify the L1 op actually executed (no read-after-write reconciliation). This is the core cross-chain weakness.

Negative
-29

Scored 42 (weak): a real, exploitable, no-acknowledgement bridge surface with multiple passing-PoC desync findings. Activating D10 LOWERS the composite vs leaving it out — the honest direction.

Negative
+10

ACTIVATED in this pass. Kinetiq has a genuine EVM<->HyperCore (Hyperliquid L1) read/write bridge: L1Write precompile at 0x3333...3333 (delegate/undelegate/spot-transfer writes) and L1Read precompiles (0x2222/0x1111 endpoints) for reading L1 staking/spot state. This is a real cross-chain-style messaging surface, weight ~0.07.

Positive
+10

Burn-before-L1-ack (#2248, passing PoC): confirmWithdrawal burns kHYPE and pays from a shared address(this).balance pool with no per-request L1 settlement proof — cross-user drain / undercollateralization risk during L1 desync

Positive
+10

L1Write silent-drop (#37, passing PoC): HyperCore's per-address pending-op queue limit silently drops ops beyond the limit while the EVM updates accounting as if successful — EVM<->L1 state desync

Positive
+10

Trusted L1 precompile endpoints (#2249); no independent verification layer between EVM accounting and L1 truth

Positive

Evidence Chain (1 files)

BlackHart AnalysisMay 30, 2026, 12:00 AM
sha256:4a1db3dd045a...

Score History

No dimension-level score changes recorded yet.

Methodology: 2.1Formula: 1.1Weights: 1.1
How is Cross-Chain Messaging scored?← Back to Provenance Ledger