Slack and Budget Breaking in Threshold Team Production

Abstract

A threshold system completes a public task only after κ verifiable shares are publicly committed. If the honest schedule creates \( =κ+Δ\) share opportunities by deadline t, then Δ shares are slack such that a coalition delays completion if and only if it withholds at least Δ+1 shares. The incentive problem is therefore to price the cheapest sabotage set. Agents receive a direct fee f per committed share. A delaying coalition may also obtain delay value at most L, and may earn additional fee revenue during recovery after the deadline. Let R1+ be a pathwise upper bound on the coalition's incremental fee revenue in a recovery slot that completes the task, including any same-slot overshoot. The principal can post a nonnegative completion bounty that depends only on committed shares, uses no deposits or punishments, and expires if completion is late. The optimal rule is uniform, as if completion occurs by t, every admissible horizon share receives B/, otherwise no bounty is paid. Full participation is ex-post strongly delay proof exactly when \( (Δ+1)f+Δ+1B L+R1+ . \) Equivalently, the exact worst-case budget is \( B = Δ+1 (L+R1+-(Δ+1)f)+ . \) The bound is tight for every nonnegative completion measurable bounty, among the horizon shares, some Δ+1 receive total bounty at most (Δ+1)B/, and withholding precisely those shares delays completion. The result applies to threshold signatures, data availability certification, coded dissemination, and generic k-of-n completion tasks. We also isolate a separate limit, no transfer rule based only on completed shares can remove a final slot race in which a coalition has already observed enough pre-completion shares to act.

0

Turn this paper into a full lesson

ArcXiv compiles a staged curriculum from this paper: 8-12 lessons across beginner → advanced, synthesised section guides, visuals, flashcards, a quiz, exercises, and on-demand deep dives per section. Grounded in the abstract, never invented.

Discussion (0)

Sign in to join the discussion.

Loading comments…