Papers for

blockchain developers

Papers whose findings have a practical use for this group, as judged from the abstract. Open a paper to read what it means in practice.

IntentFuzz finds vulnerabilities in cross-chain blockchain bridges

IntentFuzz: A Protocol-Aware Fuzzer for Automated Invariant Violation Detection in Intent-Based Cross-Chain Bridges

Abstract: Cross-chain bridges move value between blockchains. Intent-based bridges are a variant where a solver fulfills a user's declared outcome and an off-chain settlement layer later reconciles the fill against the deposit. Existing smart-contract fuzzers and static analyzers only flag known-bad code patterns or require protocol-specific hand-written assertions. This work formalizes a taxonomy separating invariant violations, safety properties a contract must enforce locally, from settlement exposures legitimately delegated to the off-chain settlement layer, and proposes IntentFuzz: a protocol-aware fuzzer that recovers a bridge's intent structure and deposit/fill function roles directly from unannotated Solidity source, then synthesizes multi-step fuzz sequences using an LLM-based fallback to help build call arguments. IntentFuzz recovers the correct intent structure in 9/9 benchmark protocols and classifies deposit and fill functions with 100% recall and 82% combined precision; across a corpus of 77 manually labeled contracts, it reaches 79.5% bridge-classification precision and 97.2% recall, and among confirmed bridges, struct selection reaches 88.6% precision and recall while deposit and fill classification each reach 100% recall. On 23 planted-bug mutants, IntentFuzz attains 100% recall and 100% precision, executing 273 templates (507 transactions in a median of 14ms per template). Across 24 real-world deployments, it confirms 17 genuine invariant violations under heuristic-only input generation, rising to 22 with its LLM-assisted tier enabled, spanning eight vulnerable GitHub repositories, each finding reproducible against public, deployed bytecode.

Fri 11 SeptCryptography and Security
The gist
Moving digital value between different blockchains uses special tools called cross-chain bridges. Some bridges rely on users stating their goals, and a solver makes sure these goals are met safely. Existing tools miss some risks because they either look for known problems or need experts to add specific checks. The authors made IntentFuzz, a tool that understands how these bridges are meant to work, then tests where safety rules might break. It caught many real problems in popular bridge code, showing it can help make blockchain transfers safer.
Open 2609.13004v1

Verifiable delay proofs linked to fresh public challenges limit fast cheating

Fresh-Challenge VDF Attestations for Model-Relative Response Latency

Abstract: Can a finite verifier obtain public, model-relative evidence about response latency for sequential computation? Verifiable delay functions (VDFs) make this possible in principle: evaluation requires T sequential steps, whereas verification is efficient in the security parameter and polylogarithmic in the numerical value of T for standard constructions. Thus a delay can be astronomically large to evaluate yet succinctly represented and feasibly checked. A VDF proof for a chosen message alone is insufficient because it may be precomputed. We specify and analyze Fresh-Challenge VDF Attestations (FCLA), a protocol composition that binds a VDF to an unpredictable public challenge, a message, and independently auditable release and receipt records. Under explicit assumptions about VDF sequentiality, the challenge source, witness logs, and a calibrated upper bound on an adversary's sequential evaluation rate, an accepted FCLA transcript is inconsistent with post-challenge generation by an adversary in that bounded model. The result neither identifies a named claimant nor excludes relaying, outsourcing, or a faster unmodeled machine. A benchmark of the public reference implementation confirms the expected empirical separation between evaluation and verification on one documented machine. Our contribution is a protocol/design analysis and benchmarked reference implementation layer, not a new VDF construction or cryptographic primitive.

Fri 11 SeptCryptography and Security
The gist
The paper looks at how to prove that a certain amount of time was genuinely spent computing something in a way that others can verify quickly. While Verifiable Delay Functions (VDFs) can show a delay took place, just having a proof isn't enough because someone could prepare it in advance. The authors introduce Fresh-Challenge VDF Attestations, which tie the proof to a new unpredictable challenge and records of when the messages were sent and received. This method helps ensure that no one could have created the proof after seeing the challenge, as long as certain technical assumptions hold. They also provide a tested implementation showing that checking these proofs is much faster than creating them.
Open 2609.12727v1

PoW blockchain denial-of-service attack becomes self-sustaining and profitable

PDoS: A Profitable Denial-of-Service Attack against Proof-of-Work Blockchain Liveness

Abstract: The security and liveness of Proof-of-Work (PoW) blockchains fundamentally depend on the economic rationality of miners. Existing incentive-driven denial-of-service attacks, such as BDoS, can deter rational miners from participating, but require the attacker to continuously absorb substantial economic losses and are therefore difficult to sustain in high-value networks. Meanwhile, prior infiltration-based withholding attacks are designed to extract revenue rather than to directly disrupt chain liveness. We present PDoS, a hybrid attack that combines block header signal deterrence with parasitic revenue extraction. PDoS disrupts blockchain liveness while exploiting the victim pool's share-reward mechanism to subsidize the attack cost, thereby lowering the adversarial hash-power threshold required to induce rational miners to shut down. We further show a counterintuitive result: in high-fee or high-MEV environments, higher block value can make PoW systems less secure by increasing the attacker's parasitic revenue and pushing the attack across the break-even point into a self-sustaining, or even profitable, regime. To the best of our knowledge, PDoS is the first attack to demonstrate that disrupting PoW blockchain liveness can be economically self-sustaining and even profitable.

Fri 11 SeptCryptography and SecurityComputer Science and Game Theory
The gist
Proof-of-Work blockchains depend on miners acting in their own economic interest to keep the system running smoothly. The authors discovered a new kind of attack called PDoS that not only disrupts the blockchain’s ability to add new blocks but also earns money during the attack, making it cheaper or even profitable for attackers. This is surprising because usually attackers lose money when trying to disrupt blockchain networks. Their work shows that when block rewards or transaction fees are high, these attacks become easier to sustain and more dangerous.
Open 2609.12450v1

Conditional transaction mechanisms optimize evaluation order for offline users

Opening the Strategic Pandora Box: Conditional Transaction Mechanisms

Abstract: Conditional transaction engines (CTEs) execute conditional instructions for offline users. This paper formalizes the mechanism-design problem within each engine invocation. A conditional transaction mechanism (CTM) decides which pending conditions to evaluate first because each evaluation delays the eventual write. We model this problem as Strategic Pandora, a discounted variant of the Pandora's box model with independent Bernoulli boxes. Agents report privately assessed success probabilities and, in the full model, values for the write action. We propose the reported-Weitzman mechanism (RW) and the reported-values second-price mechanism (RWSP). To compare revenue without a common prior, we introduce dynamic No-Betting Revenue. Under the stated competition and equilibrium conditions, every qualifying pure equilibrium of RW or RWSP earns a constant fraction of its corresponding dynamic NBR benchmark.

Thu 10 SeptComputer Science and Game Theory
The gist
Sometimes computer systems need to decide which tasks to handle first when not all users are online, and each decision affects how long final updates take. This paper studies how to design rules that choose the order to check conditions using each user's own estimate of success chances and value. The authors introduce new methods that aim to get payments or rewards close to a theoretical best, even without shared knowledge among users. Their work helps understand how to efficiently manage such conditional tasks when information is private and timing matters.
Open 2609.12197v1

NEAR protocol sharding performance tested on everyday computer hardware

Shards on a Shoestring: Empirical Characterization of NEAR Protocol Nightshade Sharding on Commodity Hardware

Abstract: NEAR Protocol's Nightshade architecture targets one million transactions per second (TPS) through horizontal sharding of both state and computation. Published benchmarks were produced on expensive Google Cloud Platform infrastructure costing approximately \$700 per hour, leaving a significant reproducibility gap for academic research. We present the first independent empirical characterization of NEAR Nightshade sharding on commodity hardware: a Chameleon Cloud bare-metal node with 48 hyperthreaded Intel Xeon cores, 128\,GB RAM, and HDD storage at 80--100\,MB/s. We systematically sweep shard count from $N{=}1$ to $N{=}24$, measuring aggregate TPS, per-shard TPS, block time, BFT finality, memory, and disk I/O. We identify three distinct bottleneck regimes: L3 cache pressure at low $N$, witness gossip pipeline saturation at mid $N$, and coherence collapse at high $N$. A key unexpected finding is that HDD write latency acts as implicit flow control for the witness gossip pipeline. Removing it via RAM-backed tmpfs causes complete chain stall at $N{=}16$, with a 29$\times$ spike in orphan witness rate at 47\% CPU utilization. Aggregate TPS peaks at $N{=}8$ (+40\% over $N{=}1$) then reverses, with per-shard TPS collapsing 23$\times$ by $N{=}24$. Our dataset provides the first commodity-hardware calibration baseline for the companion SimPy sharding simulator.

Thu 10 SeptDistributed, Parallel, and Cluster Computing
The gist
NEAR Protocol uses a method called sharding to handle a lot of transactions quickly, but past tests used expensive cloud computers. The authors tested the system on a more common, affordable setup and found how different parts limit speed as more shards are added. Surprisingly, slower hard drive writing helps control data flow, and removing it can cause the system to stall. They show that increasing shards only helps performance up to a point before it gets worse.
Open 2609.12091v1

Smart contracts need user conditions to resist frontrunning attacks

On Identifying Sound Conditions for Frontrunning Resistance

Abstract: Blockchains enable decentralized applications through smart contracts---interactive programs executed through consensus. However, the inherently asynchronous nature of blockchain transaction ordering introduces a class of vulnerabilities known as frontrunning attacks, which have caused millions of dollars in losses in major blockchains, such as Ethereum. Frontrunning attacks arise because users interact with smart contracts through transactions, which are added to the blockchain by designated nodes called miners. Miners can exploit their ability to reorder, delay, or insert transactions to gain an advantage over honest users, effectively frontrunning them. Yet, to date, the field lacks a rigorous definition of what it even means for a contract to resist such attacks. Worse, we show that existing dynamic detection approaches are fundamentally inadequate: in a large-scale study comprising 287 smart contract audits, 55% of the 393 reported vulnerabilities identified by leading smart contract auditors fall outside the scope of state-of-the-art detection criteria. To address this gap, we propose the first formal definition of frontrunning vulnerability for smart contracts. Our definition captures a key insight: resistance to frontrunning is not an intrinsic property of a contract alone, but depends critically on how honest users interact with it. Grounded in this observation, we develop a sound algorithm for synthesizing secure interaction conditions, alongside a prototype implementation that we apply to audited real-world contracts---revealing previously undiscovered vulnerabilities in two Ethereum contracts.

Thu 10 SeptCryptography and Security
The gist
Blockchain programs called smart contracts can be cheated by miners who reorder or insert transactions to benefit themselves, known as frontrunning. The authors found that current ways to detect these vulnerabilities miss over half of real cases. They introduced a new way to define when a contract is safe from frontrunning that depends on how honest users interact with it, not just the contract itself. They created a method to find the right conditions users must follow to keep contracts secure and found new vulnerabilities in existing Ethereum contracts.
Open 2609.11535v1

DeFiFlowBench benchmarks safety of natural language DeFi workflows

DeFiFlowBench: Benchmarking and Improving Safe Executability in Natural-Language DeFi Workflow Synthesis

Abstract: A structurally valid DeFi workflow can still authorize a costly trade. We introduce DeFiFlowBench, a benchmark of 207 team-authored prompts for natural-language DeFi workflow synthesis. It measures graph coverage, configuration completeness, and declared safety predicates, then tests supported trade configurations on a local EVM. Direct, constrained, and few-shot prompting produce 14-19 unsafe held-out executions per configuration under a fixed 5% price-impact cap. A slippage bound derived from a quote does not prevent the price impact of the order itself. We propose Koan-Safe, which combines a prompt-only intent parser, a replaceable generator, and structural repair with default safety parameters. On 75 held-out workflow prompts, its hybrid variant scores 0.67 on the static safety proxy, compared with 0.33 for the best baseline. Koan-Safe records no unsafe executions on the saved benchmark outputs. A matched-candidate ablation produces 14-17 unsafe executions when enforcement is disabled. Additional tests expose the limits of default injection: permissive existing thresholds can still authorize unsafe trades. A separately evaluated policy cap addresses this failure on a 36-case diagnostic grid. These results support explicit trade protections and execution-based evaluation, while distinguishing declared safety from a general guarantee.

Thu 10 SeptMachine LearningSoftware Engineering
The gist
DeFi workflows can sometimes authorize risky trades even if they are structurally correct. The authors created DeFiFlowBench, a test set of 207 prompts, to measure how well systems generate safe DeFi transaction sequences in natural language. They found common prompting methods led to many unsafe executions despite safety limits. To improve safety, they designed Koan-Safe, which uses intent parsing and structural checks to reduce unsafe trades significantly. Their tests show that explicit trade safety checks and execution testing are important to really ensure DeFi trade safety.
Open 2609.11504v1

Sound removal of extra checks speeds zero knowledge neural proofs

Sound Debloating of Redundant Checks in Zero-Knowledge Machine-Learning Circuits

Abstract: Zero-knowledge (ZK) proof systems for neural-network inference compile the model into a system of arithmetic constraints. Many of these constraints are redundant checks: range proofs, sign lookups, and bit decompositions who are globally entailed by the rest of the circuit through chains of reasoning that span distant gadgets. Removing them shrinks the circuit and accelerates proving, but the removal must be carefully justified: an unsoundly debloated circuit becomes forgeable, accepting witnesses the original would have rejected and so allowing a prover to claim, for example, that a neural network produced an output it never actually computed. Such soundness vulnerabilities are not hypothetical: under-constrained circuits in deployed ZK systems have enabled attackers to forge transactions and bypass verification entirely. We present an automated framework that removes redundant checks while provably preserving soundness. For each candidate removal, our tool first checks whether the rest of the circuit, on its own, can still rule out every value the removed check was excluding. Using whole-circuit abstract interpretation, the analysis searches for such alternative justifications and records them in a provenance graph; a check is then removed only when an alternative path through the graph still derives the facts that it is checking. This ensures that the debloated circuit opens no new forging strategy to an adversary. We evaluate circuits spanning MLP, CNN, RNN, and transformer architectures generated by two production frameworks (ezkl and zkml), with up to 25.3 million constraints. Our tool removes up to 48.7\% of constraints and reduces prover time by up to 72.8\%, without weakening security.

Wed 9 SeptCryptography and Security
The gist
Zero-knowledge proofs let computers prove they did a task correctly without revealing details. When these proofs check neural network computations, many internal checks are repetitive and slow things down. The authors created a tool that safely removes these extra checks without weakening security, so proofs run faster and use fewer resources. They tested their tool on large neural network proofs and cut the work almost in half.
Open 2609.10149v1

Byzantine agreements tolerate reordered messages with new security limits

Scalable Composition of Byzantine Agreements under Reorder Attacks

Abstract: Byzantine agreement (BA) is a foundational building block in distributed systems, and the security analysis of BA protocols under multi-instance executions has attracted increasing attention. However, most existing adversary models focus solely on party corruption and neglect important threats posed by adversarial manipulations of communication channels in the network. Through channel attacks, messages can be reordered across multiple executions and lead to violations of the protocol's security guarantees, In this work, we present the first adversary model that combines party corruption and channel attacks. Based on this model, we establish new security thresholds for Byzantine agreement under parallel and concurrent compositions, supported by complementary impossibility and possibility results that match each other to form a tight bound. For the impossibility result, we show that even authenticated Byzantine agreement protocols cannot be secure under parallel composition when $n \leq 3t$ or $n \leq 2c + 2t + 1$, where $t$ and $c$ denote the number of corrupted parties and communication channels, respectively, and $n$ is the number of parties. For the possibility result, we prove the existence of secure protocols for unauthenticated Byzantine agreement under parallel and concurrent composition, when $n > \max\{3t, 2c+2t+1\}$. We first provide general black-box compilers that transform any single-instance secure BA protocol into one that is secure under parallel and concurrent executions without additional security assumptions. To optimize performance, we further design refined compilers using erasure-correcting codes. These refined versions significantly reduce communication overhead, particularly for long messages, where they achieve a constant multiplicative overhead compared with the original protocol, thus achieving the same asymptotic communication complexity.

Wed 9 SeptCryptography and SecurityData Structures and Algorithms
The gist
Byzantine agreement helps computers agree even if some parts act wrongly. The authors found that messing with message order in the network can break many agreements. They created a new way to think about attacks that change message order and party behavior together. They also proved exactly when agreement is possible or impossible with these combined attacks. Finally, they designed methods to safely run many agreements at once without much extra communication cost.
Open 2609.09623v1

Guppy speeds up blockchain light clients with zero-knowledge proofs

Guppy: Efficient Light Clients via Recursive Zero-Knowledge Proofs

Abstract: Traditional light clients rely on validators committing to the entire blockchain state at every block via a state commitment such as a Merkle tree, allowing clients to verify facts using short proofs. However, maintaining large and ever-growing state trees imposes a significant burden on validators and lies on the critical path of block production. As a result, many modern high-throughput chains avoid this approach altogether. This work asks whether efficient inclusion proofs can be supported without requiring validators to maintain full state commitments. We present Guppy, a protocol that achieves this by having validators commit to just the state updates. An off-chain, untrusted service, secured by recursive Zero-Knowledge Proofs (ZKPs), then maintains a verifiable Merkle tree over the full state. This design keeps validator overhead negligible and does not increase the asymptotic complexity of block construction. Our design rests on two key technical ideas. First, a hash-chain commitment moves validator signature verification out of the ZK circuit, keeping the proving circuit efficient. Second, we design a parallel recursive proving pipeline that leverages cheap recursion in modern ZKPs to ensure latency grows only logarithmically with throughput. Our Plonky2-based implementation demonstrates that Guppy can maintain a Merkle tree of size 2^30 while processing thousands of updates per second, adding only 2-4 s of latency.

Mon 7 SeptCryptography and Security
The gist
Light clients in blockchains need to verify data without storing everything, but this can be slow and hard for validators. The authors created Guppy, which lets validators just record changes instead of the whole state. An extra service uses special proofs called recursive zero-knowledge proofs to keep the full data trustworthy. This makes verifying information faster while keeping validator work minimal, supporting high transaction speeds with small delays.
Open 2609.07963v1

EventSpec finds event syncing problems in blockchain smart contracts

EventSpec: Defining and Detecting Event-Semantic Issues in Blockchain Ecosystems

Abstract: In recent years, smart contracts have become the backbone of decentralized applications (DApps), and off-chain systems such as bridges, wallets, and indexers rely heavily on event logs to track contract execution and state changes. However, the Ethereum Virtual Machine (EVM) does not validate or enforce event semantics, so logs can diverge from on-chain state, misleading off-chain systems into accepting incorrect state transitions. Existing smart contract vulnerability detection tools focus on logic bugs, with limited support for detecting event-semantic defects. To address this gap, we collect audit reports and incident cases and apply open card sorting to define five classes of event-semantic defects: event collision, state-event mismatch, unauthorized event emission, event emission mismatch, and event parameter mismatch. We propose EventSpec, which infers event specifications from a contract corpus via behavior inference and semantic-constraint extraction and applies differential checking to identify event-semantic defects in target contracts. We run EventSpec on 6,617 real-world contracts and evaluate detection effectiveness based on manually labeled results; EventSpec achieves an overall comprehensive precision of 90.17%. We further provide an off-chain evaluation harness that reproduces two off-chain attack vectors on any EVM-compatible chain: event origin confusion caused by unintended emitters and event-state desynchronization where events lack matching state updates. Using this harness, we demonstrate the feasibility of these attacks on bridge relayers, blockchain explorers, and NFT marketplaces, and report six wallet issues, four of which were confirmed (including a $600 bounty), with two remaining pending.

Mon 7 SeptCryptography and SecuritySoftware Engineering
The gist
Smart contracts on blockchains rely on event logs to inform off-chain systems like wallets and explorers about what happens on-chain. However, these event logs are not checked for accuracy by the blockchain itself, which can cause off-chain systems to be misled about the true state of contracts. The authors define five common types of event-related problems and create EventSpec, a tool that learns normal event patterns from many contracts and detects unusual event issues. They tested EventSpec on thousands of contracts, achieving high accuracy, and showed how event mismatches can lead to real-world problems in blockchain tools.
Open 2609.07865v1

Market behavior reveals complex communication beyond single transactions

Your Agent Says Yes: Interpreting Adversarial Market Behavior Beyond Individual Transactions

Abstract: Transaction-local controls answer whether one financial request may proceed, but market behavior can be distributed across messages, agents, assets, and time. We study this interpretation gap in a virtual exchange populated by ten role-conditioned language-model agents. The agents communicate, trade reference assets and futures, launch tokens, and manage concentrated-liquidity pools under prescriptive adversarial roles. We analyze eight 72-cycle trajectories across two time-blinded hourly replay paths, with a runner-side wallet policy enabled or disabled. The retained artifacts connect generated outgoing messages, policy events, balances, positions, and cycle-end market state. A focal reconstruction shows a launch--promotion--exit scenario realized across private coordination, public claims, follower positioning, repeatedly withheld exits, and a later non-blocking request aligned with a token balance change. Across policy-enabled runs, the gate withholds direct requests selectively; most policy-categorized candidates are flagged rather than blocked, while the surrounding interaction can continue. Repeated runs also show that category-level and within-trajectory relations can recur even when normalized score-change rankings do not. These findings motivate agent-behavior evaluation that links communication, authorization, and evolving state instead of treating individual transaction verdicts as complete safety judgments.

Mon 7 SeptComputational Engineering, Finance, and ScienceArtificial IntelligenceCryptography and Security
The gist
Financial transactions are often judged one by one, but this misses the bigger picture where many messages and actions interact over time. The authors studied a virtual market with AI agents that trade, communicate, and control assets in complex ways. They found that some transactions get flagged or delayed based on broader patterns, not just individual requests. This shows it’s important to look at how communication, rules, and changing market states all connect to understand market safety fully.
Open 2609.07675v1