惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

WordPress大学
WordPress大学
小众软件
小众软件
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
博客园 - Franky
Jina AI
Jina AI
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
Y
Y Combinator Blog
V
Visual Studio Blog
C
Check Point Blog
阮一峰的网络日志
阮一峰的网络日志
U
Unit 42
量子位
人人都是产品经理
人人都是产品经理
博客园 - 聂微东
M
MIT News - Artificial intelligence
爱范儿
爱范儿
B
Blog RSS Feed
MyScale Blog
MyScale Blog
H
Help Net Security
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
美团技术团队
L
LangChain Blog
D
Docker

Hacker News - Newest: "AI"

AI can't read an investor deck AI as an attorney? Student uses ChatGPT, Gemini to sue UW over alleged racial discrimination Hacking MCP Servers in AI Systems – The Rug Pull: Tool Changes After Approval GitHub - MeepCastana/KubeezCut: Free Web based video editor Can AI judge journalism? A Thiel-backed startup says yes, even if it risks chilling whistleblowers Coming soon: 10 Things That Matter in AI Right Now DARPA built an AI to fact-check enemy weapons claims What explains heterogeneity in AI adoption? When AI Meets Muscle: Context-Aware Electrical Stimulation Promises a New Way to Guide Human Movements - Department of Computer Science AI Changed How We Build. It Did Not Change What Matters. Linux rules on using AI-generated code - Copilot is OK, but humans must take 'full responsibility for the… Meta spins up AI version of Mark Zuckerberg to engage with employees Code Mode: Let Your AI Write Programs, Not Just Call Tools | TanStack Blog GitHub - Delavalom/graft: Go framework for building AI agents. Type-safe tools, multi-provider (OpenAI, Anthropic, Gemini, Bedrock), zero vendor SDKs. India's TCS tops estimates, says new AI models did not dent services demand Gen Z's fading AI hype Strong feeling: we are in a folded AI reality GitHub - machinarii/total-recall-catalog: A reference catalog of latest knowledge retrieval, memory & RAG systems GitHub - mensfeld/code-on-incus: Give each AI agent its own isolated machine with root, Docker, and systemd. Active defense detects and stops threats automatically.. Quantization, LoRA, and the 8% Problem: Benchmarking Local LLMs for Production AI Iran war: We spoke to the man making Lego-style AI videos that experts say are powerful propaganda Powell, Bessent discussed Anthropic's Mythos AI cyber threat with major U.S. banks GitHub - immartian/bellamem: Persistent belief-graph memory for AI agents. Retrieves decisive context by importance — not recency, not RAG, not /compact. recursive-mode: The Repo-Native Operating System for AI Engineering After the attack on Sam Altman's home, will AI CEO's go on the offensive? The biggest advance in AI since the LLM Opus 4.6 vs GPT 5.4 One Prompt Unity World Generation Test “AI polls” are fake polls Client Challenge Can AI be a 'child of God'? Inside Anthropic's meeting with Christian leaders
Solymus_Architecture.md
kevinkibeom · 2026-04-25 · via Hacker News - Newest: "AI"

Sub-Tangle Offline Merges, $O(1)$ Hardware-Anchored Finality, and Dafny-Verified State Transitions on an ETH-Restaked Cosmos AppChain

Author: Solymus Protocol Research Status: Architecture proposal (v0.1) Audience: EigenLayer researchers, ZK engineers, formal-verification practitioners

0. Abstract

We describe the protocol-level architecture of Solymus, an ETH-restaked Cosmos AppChain targeting consumer payment finality. Three results:

  1. A deterministic state-diff canonicalization protocol that reduces HSM signing from $O(N)$ telemetry operations to exactly one $O(1)$ temporal anchoring operation per micro-epoch, without weakening FIPS 140-3 compliance.
  2. A Merkle-merge DAG (the Sub-Tangle) that resolves peer-to-peer offline payment forks with commutative, idempotent, balance-conserving semantics.
  3. Machine-checked proofs in Microsoft Dafny, discharged by Z3: 5 modules, 43 theorems, 112 verification conditions, no unsolved obligations.

The execution-layer primitive at the center of the rail is patent-protected and out of scope here.


1. Architecture Context

Solymus is not a Layer 1, and it is not a rollup. It is a Cosmos SDK v0.50 AppChain with CometBFT v0.38 BFT consensus, restaked against Ethereum via an EigenLayer AVS. Economic security is borrowed from Ethereum; execution and micro-epoch sealing stay sovereign; validator admission is gated by hardware-root attestation (TPM 2.0 + AWS Nitro Enclave NSM).

Layer Primitive
Settlement anchor SolymusAVSRegistry.sol on Ethereum L1
Economic security EigenLayer AVS, operator $\leftrightarrow$ validator pubkey map
Execution Cosmos SDK modules (x/microepoch, x/feeburn, x/signer, x/attestation)
Consensus CometBFT, 1-second block time
Validator admission TPM 2.0 quote + Nitro NSM attestation document
Signing FIPS 204 ML-DSA-65 (PQC) with ECDSA-SHA256 fallback seam

The AVS contract receives one Merkle root commitment per micro-epoch via a Go relayer. The only property we rely on here is that the on-chain anchor is strictly monotone in epoch id.


2. The Hardware Signing Bottleneck

2.1 The $O(N)$ trap

A naive edge telemetry rail exposes a FIPS 140-3 HSM to per-event signing. For a 1-second-finality consumer rail, $N$ can reach $10^3$ to $10^4$ events per second per edge node. No certified HSM sustains this without queueing. The structural wall is per-signature certified entropy: each sign consumes audited entropy budget, and that budget is not negotiable.

2.2 The $O(1)$ reduction

Our reduction hinges on deterministic state-diff canonicalization via RFC 8785 JSON Canonicalization Scheme (JCS). The insight: if $N$ edge events collapse into a single canonical pre-image with byte-identical serialization across every honest observer, the HSM signs the canonical pre-image exactly once per temporal anchor.

Let $\Delta_i$ be the $i$-th edge event in a micro-epoch $e$. Define

$$ C(e) ;=; \text{JCS}!\left(\sigma!\left({\Delta_i}_{i=1}^{N_e}\right)\right) $$

where $\sigma$ is a deterministic ordering (lexicographic over $\text{SHA-256}(\Delta_i)$) and JCS is RFC 8785. By JCS determinism, any two honest nodes observing the same ${\Delta_i}$ produce byte-identical $C(e)$. The HSM signing cost per micro-epoch collapses:

$$ \text{HSM_ops}(e) ;=; 1 ;=; O(1) $$

regardless of $N_e$. Micro-epoch length is fixed at 1 s, so the amortized per-event signing cost is $O(1/N)$ and the per-event wallet fee inherits the same bound.

This is what makes hardware-rooted sub-second finality tractable under FIPS 140-3. Marginal certified-entropy cost per user tends to zero as $N_e$ grows, which drives the fee bound downward by construction.


3. The Sub-Tangle: Merkle-Merge DAG for Offline Forks

3.1 Problem statement

Two devices $A$ and $B$ enter airplane mode, each signs a sequence of payments, and later meet again. Without a central authority, they must reconcile two divergent histories into one ledger-consistent state. Structurally, this is the asynchronous CRDT problem restricted to monetary payloads with slashing on conflict.

3.2 Construction

Define a Sub-Tangle $T$ as an append-only set of nodes, where each node $n$ carries a signed payload and a content hash. The merge operator is set union:

$$ \text{merge}(T_A, T_B) ;=; T_A \cup T_B $$

The Merkle root $R(T)$ is the root of a binary Merkle tree over leaves sorted by content hash, with Bitcoin-style odd-leaf duplication and empty sentinel $0^{256}$.

3.3 Required properties

For safety, the merge must satisfy four invariants:

$$ \begin{aligned} \textbf{I1 Commutativity:} \quad & \text{merge}(A, B) = \text{merge}(B, A) \\ \textbf{I2 Idempotence:} \quad & \text{merge}(A, A) = A \\ \textbf{I3 Determinism:} \quad & \text{detect}(\text{merge}(A, B)) \text{ is a pure function of the merged set} \\ \textbf{I4 Conservation:} \quad & \forall s.; \textstyle\sum_{\text{applied}} \text{debit}_s ;\leq; \text{bal}(s) \end{aligned} $$

I1 and I2 fall out of set-union algebra. I3 (double-spend detection is order-independent) and I4 (no balance underflow under any merge order) are the load-bearing claims.

3.4 Double-spend surface

A conflicting spend manifests as two signed payloads from the same sender over overlapping nonces. A canonical walk over the merged set yields a partition $(\text{applied}, \text{slashed})$. By I3, devices that merged in different orders produce byte-identical partitions, so slashing evidence is a pure function of the anchored Merkle root, not of local history.


4. Machine-Checked Proofs

4.1 Why Dafny + Z3

Unit tests cover instances; proofs cover universals. We wanted merge-order independence over all input permutations, not over a Hypothesis-sampled subset. Microsoft Dafny + Z3 gives us uninterpreted function support (opaque over the hash model), first-class proof-carrying code, and the same toolchain used inside AWS, Microsoft, and Intel verification pipelines.

4.2 Metrics

Module Theorems VCs Scope
feeburn.dfy 7 23 Burn monotonicity, pool conservation
microepoch.dfy 7 23 Chain-hash continuity, no forks at height
subtangle.dfy 10 28 I1..I4 + composite
passkey.dfy 7 22 Address derivation determinism, domain separation
zk-merkle.dfy 6 16 SNARK $\leftrightarrow$ Merkle public-signal anchoring
Total 43 112 5 modules, Z3-discharged

All 112 VCs discharge on Dafny 4.11.0 + Z3 under --allow-warnings=false. {:axiom} is restricted to opaque deterministic hash models and is never used over ledger logic. The ledger proofs therefore survive any concrete hash instantiation that satisfies determinism.

4.3 Sub-Tangle commutativity, in Dafny

ghost function {:axiom} LeafHash(n: Node): bytes32
ghost function {:axiom} MerkleOver(leaves: set<bytes32>): bytes32

function Merge(A: SubTangle, B: SubTangle): SubTangle {
  SubTangle(A.nodes + B.nodes)
}

lemma MergeCommutes(A: SubTangle, B: SubTangle)
  ensures Merge(A, B) == Merge(B, A)
{
  // set union is commutative by extensionality
}

lemma MerkleRootCommutes(A: SubTangle, B: SubTangle)
  ensures MerkleOver(Leaves(Merge(A, B)))
       == MerkleOver(Leaves(Merge(B, A)))
{
  MergeCommutes(A, B);
  // LeafHash is deterministic under {:axiom};
  // set equality of leaves implies MerkleOver equality.
}

lemma DetectMergeOrderIndependent(A: SubTangle, B: SubTangle)
  ensures Detect(Merge(A, B)) == Detect(Merge(B, A))

lemma Conservation(T: SubTangle, s: Account)
  requires ValidBalances(T)
  ensures  AppliedDebits(T, s) <= Balance(T, s)

{:axiom} on LeafHash and MerkleOver models the hash as an uninterpreted deterministic function. Equal inputs yield equal outputs by Dafny semantics, which is enough for I1, I2, and I3 with no commitment to a specific collision-resistance assumption. I4 is proved by induction over the canonical walk, with ValidBalances as the loop invariant.


5. What This Buys

  • HSM compliance survives scale. The $O(1)$ reduction lets a FIPS 140-3 HSM anchor a sub-second consumer rail without queueing.
  • Offline forks are provably safe. I1..I4 hold over every merge order; no adversary forces a double-apply by re-ordering payload arrival.
  • Restaking gets a clean slashing surface. Slashing evidence is a pure function of the anchored Merkle root, not of local history.
  • The proof boundary is honest. Axioms are confined to the hash oracle; ledger logic is fully mechanized.

6. Open Questions

  1. Slashing wiring under Pectra-era EigenLayer AllocationManager: currently an event-only hook pending API stabilization.
  2. Trusted-setup ceremony for the Groth16 prover anchored to the public-signal binding already proved in zk-merkle.dfy. Structural binding is shipped; crypto strength of the underlying prover is the remaining swap.
  3. Formalizing relayer invariants (strict monotonicity, crash-safe checkpoint, gap-free catch-up, poison-pill stop) into a Dafny module parallel to subtangle.dfy, closing the last non-Dafny safety surface between the AppChain and the L1 anchor.

Feedback on the merge algebra and on the JCS-based HSM reduction is specifically requested.