# \[Proposal\] Provers: Bonded Prover Auction

**URL:** <https://forum.aztec.network/t/proposal-provers-bonded-prover-auction/2401>\
**Category:** Aztec\
**Tags:** rfp, provers\
**Created:** [October 12, 2023, 8:29pm UTC](https://forum.aztec.network/t/proposal-provers-bonded-prover-auction/2401 "2023-10-12T20:29:19Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Anon](https://avatars.discourse-cdn.com/v4/letter/a/47e85d/32.png) [@Anon](https://forum.aztec.network/u/Anon)\
**Post date:** [October 12, 2023, 8:29pm UTC](https://forum.aztec.network/t/proposal-provers-bonded-prover-auction/2401/1 "2023-10-12T20:29:19Z")

</div>

# Summary

Use proposers to run an auction for proof production. This proposal is compatible with both [PBS](http://forum.aztec.network/t/proposal-pbs-proposer-builder-separation/2283) and [Fernet](http://forum.aztec.network/t/proposal-sequencer-selection-fernet/533).

# Context

Monero has a [decentralized mining pool](https://p2pool.io/), which uses a second blockchain to coordinate work. This proposal defines a fair structure under which such work pools may be created. Highly-available decentralized networks are expected to have the cheapest access to capital and compute, assuring liveness without adding complexity to the core protocol.

# Details

1. (init) **provers** deposite bond collateral
2. **builder** broadcasts bond requirements and proof data to **provers**
  - a bond consists of a proposal portion, and an MEV portion

3. **provers** with sufficient bond broadcast bids
4. **builder** signs and broadcasts the winning bid
5. **proposers** attest to timely availability of the winning bid
6. **prover** submits proof to L1

If a prover fails to submit a proof in time, the **builder** avoids slashing by submitting the signed winning bid.  
The provers proposal bond portion is burnt, and the MEV portion transfered to the **builder**.

---

<div class="post-metadata">

**Author:** ![cooper-aztecLabs](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.aztec.network/cooper-azteclabs/32/130_2.png) [@cooper-aztecLabs](https://forum.aztec.network/u/cooper-aztecLabs)\
**Post date:** [October 17, 2023, 4:20pm UTC](https://forum.aztec.network/t/proposal-provers-bonded-prover-auction/2401/2 "2023-10-17T16:20:28Z")

</div>

Hey @Anon! Thank you for taking the time to post.

I’d kindly ask you to please adhere to the submission format for it to be considered a valid proposal.

* * *

**Title:** A concise, descriptive title for your proposal

**Summary:** A brief, easy to understand summary of your proposal (about 300 words)

**Comparisons:** Explain what makes this solution unique and different from alternative solutions

**Details:** Explain the prover coordionation protocol, its components (including parameters), and its functionality

**Questions:** Any outstanding questions

* * *

Additionally some type of diagram (&/or visual) would likely be an efficient way to get on the same page, prior to diving into some of the specific details and questions. If you could update when you get a chance, that’d be great!

---

<div class="post-metadata">

**Author:** ![Anon](https://avatars.discourse-cdn.com/v4/letter/a/47e85d/32.png) [@Anon](https://forum.aztec.network/u/Anon)\
**Post date:** [October 17, 2023, 11:43pm UTC](https://forum.aztec.network/t/proposal-provers-bonded-prover-auction/2401/3 "2023-10-17T23:43:35Z")

</div>

Hey @cooper-aztecLabs!  
Your feedback is noted, and I have added section headers.

> [@cooper-aztecLabs](#):
>
> considered a valid proposal

I am here to have fun. I communicate succinctly and in good faith. I believe my ideas are rational and well thought out. This is enough. Let us focus instead on designing a robust privacy network.

---

<div class="post-metadata">

**Author:** ![Anon](https://avatars.discourse-cdn.com/v4/letter/a/47e85d/32.png) [@Anon](https://forum.aztec.network/u/Anon)\
**Post date:** [October 21, 2023, 4:20pm UTC](https://forum.aztec.network/t/proposal-provers-bonded-prover-auction/2401/4 "2023-10-21T16:20:20Z")

</div>

To better facilitate 3rd party prover network support, **prover** deposits may optionally be any quantities of any assets. If a **builder** accepts these bids, their bond remains at stake, and they receive the **provers** deposit if they are slashed.

---

<div class="post-metadata">

**Author:** ![JoakimEQ](https://avatars.discourse-cdn.com/v4/letter/j/97f17d/32.png) [@JoakimEQ](https://forum.aztec.network/u/JoakimEQ)\
**Post date:** [October 24, 2023, 9:39am UTC](https://forum.aztec.network/t/proposal-provers-bonded-prover-auction/2401/5 "2023-10-24T09:39:08Z")

</div>

Have you thought about the common occurance (“Winner’s Curse”) where in bidding markets like this, winners tend to overbid and thus create value loss over time? How would you counteract this?

---

<div class="post-metadata">

**Author:** ![Anon](https://avatars.discourse-cdn.com/v4/letter/a/47e85d/32.png) [@Anon](https://forum.aztec.network/u/Anon)\
**Post date:** [October 24, 2023, 11:15am UTC](https://forum.aztec.network/t/proposal-provers-bonded-prover-auction/2401/6 "2023-10-24T11:15:04Z")

</div>

Winner’s curse applies in common value auctions (the value of the item is the same but imprecisely known to all bidders). This is a private value auction, where bidders have different values because their compute overhead is different (and known ahead of time).

An English auction (open first-price ascending, this proposal) is pareto-optimal (and equivalent to a Vickrey auction (sealed second-price)), incentivising bidders to bid their true value (less the information value of bids).

Edit: There does appear to be some uncertainty regarding L1 fees.  
I propose a gas rebate (funded by base-fee), which refunds L1 fees for submitting proofs.
