Thomas Thiery
    • Create new note
    • Create a note from template
      • Sharing URL Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Customize slides
      • Note Permission
      • Read
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Write
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Engagement control Commenting, Suggest edit, Emoji Reply
      • Invitee
    • Publish Note

      Publish Note

      Everyone on the web can find and read all notes of this public team.
      Once published, notes can be searched and viewed by anyone online.
      See published notes
      Please check the box to agree to the Community Guidelines.
    • Commenting
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
      • Everyone
    • Suggest edit
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
    • Emoji Reply
    • Enable
    • Versions and GitHub Sync
    • Note settings
    • Engagement control
    • Transfer ownership
    • Delete this note
    • Save as template
    • Insert from template
    • Import from
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
    • Export to
      • Dropbox
      • Google Drive
      • Gist
    • Download
      • Markdown
      • HTML
      • Raw HTML
Menu Note settings Sharing URL Create Help
Create Create new note Create a note from template
Menu
Options
Versions and GitHub Sync Engagement control Transfer ownership Delete this note
Import from
Dropbox Google Drive Gist Clipboard
Export to
Dropbox Google Drive Gist
Download
Markdown HTML Raw HTML
Back
Sharing URL Link copied
/edit
View mode
  • Edit mode
  • View mode
  • Book mode
  • Slide mode
Edit mode View mode Book mode Slide mode
Customize slides
Note Permission
Read
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Write
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Engagement control Commenting, Suggest edit, Emoji Reply
Invitee
Publish Note

Publish Note

Everyone on the web can find and read all notes of this public team.
Once published, notes can be searched and viewed by anyone online.
See published notes
Please check the box to agree to the Community Guidelines.
Engagement control
Commenting
Permission
Disabled Forbidden Owners Signed-in users Everyone
Enable
Permission
  • Forbidden
  • Owners
  • Signed-in users
  • Everyone
Suggest edit
Permission
Disabled Forbidden Owners Signed-in users Everyone
Enable
Permission
  • Forbidden
  • Owners
  • Signed-in users
Emoji Reply
Enable
Import from Dropbox Google Drive Gist Clipboard
   owned this note    owned this note      
Published Linked with GitHub
Subscribed
  • Any changes
    Be notified of any changes
  • Mention me
    Be notified of mention me
  • Unsubscribe
Subscribe
# Leveraging lottery mechanisms to incentivize censorship resistance on Ethereum *Disclaimer: This post should be viewed as a "fun" idea I had rather than a serious proposal; the focus is on devising mechanisms to prevent economies of scale and centralization vectors from emerging.* ‘‘All you need is 0.001 ETH and a dream’’ ‘‘Buy a ticket. Contribute to Ethereum’s censorship resistance. Get a shot at winning life-changing rewards every week.’’ >💡 > >Some key facts about lotteries: > >- **Lotteries are universal**. They have existed for thousands of years (e.g., ancient China in ~205–187 BCE), and enjoy global popularity. >- Lotteries are purely chance-based, requiring no skill, giving **player equal odds per ticket**. This creates a unique situation in which social status, education, wealth, or skill provides no advantage. >- Lotteries naturally attract broad, diverse participation, particularly **rewarding unsophisticated players** rather than a few sophisticated actors with greater resources or information. >- Despite having negative expected value (EV)—meaning most players lose money over time—lotteries still attract **hundreds of millions of participants worldwide** each year. >- Lottery participation generally rises during young adulthood, peaks in middle age, then declines among seniors. Men and individuals with risk-seeking personalities tend to participate more frequently. This demographic **closely aligns with those interested in blockchain and cryptocurrencies.** In this post, I argue a lottery might be the perfect mechanism to reward participants across the world for contributing to Ethereum’s censorship resistance. ## Introduction A known challenge when designing mechanisms for trustless, decentralized settings is rewarding small, unsophisticated, or solo participants without enabling large, resource-rich actors to dominate and capture disproportionate benefits. The thesis is the following: If a mechanism offers positive EV, large, resource-rich actors always have incentives—and often the ability—to capture and dominate rewards. Regardless of the specific activity, if there's value to extract in permissionless settings, sophisticated actors will find ways to exploit economies of scale, either by leveraging operational efficiencies, spreading out fixed costs, or employing Sybil identities. One (h/t Julian) might argue we could theoretically design positive EV mechanisms that do not introduce economies of scale at all, but I had a hard time coming up with an example in practice. Consider Ethereum staking as an example, and imagine you want to design a mechanism to reward genuine small stakers who own and stake exactly `32 ETH`, rather than larger entities who own `2048 ETH`. In practice, large players can easily split their stake into 64 Sybil identities of `32 ETH` each, benefiting from smoother reward distributions and crowding out authentic small-stake participants. This dynamic undermines Ethereum’s decentralization goals, highlighting the inherent limitations of traditional positive-EV incentive structures. One potential way out of this fundamental trade-off is to apply insights from behavioral economics to move beyond the assumption of purely rational actors (*homo economicus*) who solely maximize expected value. Instead, I propose transitioning from a system that relies exclusively on altruistic behavior to one that actively incentivizes decentralization and censorship resistance—without introducing centralizing forces. - **Stage 1: Depend on altruism** or intrinsic motivation, expecting smaller participants to remain engaged and perform duties honestly despite unfavorable incentives. *(This approach currently describes Ethereum’s solo-staking environment, but it may not be sustainable long-term.)* - **Stage 2: Boost altruism** using negative-EV mechanisms like lotteries to leverage universal human biases and sustain or increase participation. While each ticket has the same expected value, larger and more sophisticated actors who commit more resources lose more in absolute terms—effectively reversing traditional advantages and dampening economies of scale. Lotteries are the most simple, well-studied, and popular negative-EV mechanism out there (state lotteries return only 50–70 cents on the dollar in prizes). By drawing on key concepts from economics and game theory, researchers have explored why millions of people willingly play a "losing game," highlighting the roles of risk preferences, probability perception, and utility beyond money. Further studies indicate that lotteries attract a broad cross-section of the public, particularly middle-aged men with risk-seeking personalities. Sounds familiar? It precisely matches the demographic most interested in blockchain and cryptocurrencies. Even more fun, numerous studies highlight key behavioral design techniques and game elements—such as gamification, near-miss effects, and carefully timed draws—that significantly enhance perceived value and sustained participant engagement. Here, I argue a lottery is particularly suited to reward includers—protocol participants in charge of upholding censorship resistance (CR) on Ethereum. Recent work has focused on mechanisms ([FOCIL EIP-7805](https://eips.ethereum.org/EIPS/eip-7805)) and proposals to unbundle includers from other protocol roles and duties (see [Attester-Includer Separation](https://ethresear.ch/t/towards-attester-includer-separation/21306)). However, existing proposals to reward includers (such as [AUCIL](https://eprint.iacr.org/2025/194)) remain complex and vulnerable to capture by larger, more sophisticated actors due to inherent economies of scale and Sybil-resistance challenges (e.g., crowd out honest includers to control the outcome of the aggregated IL). In the current version of FOCIL, the assumption is that includers will perform their duties honestly without explicit incentives—let’s see if lotteries can improve that by exploiting the asymmetry between expected value and expected utility. ## In-Protocol Lottery Design - **Ticket System:** Each slot, participants can buy tickets for the right to become an includer. A per-slot limit is enforced just so that ticket don’t DDOS the protocol, but with a theoretically infinite amount of tickets being sold at a fixed price. Each ticket costs `0.001 ETH` (~$2 at current prices), and each purchase adds to a cumulative weekly prize pool. If not enough tickets are bought, validators will fill the gaps and take on including duties as includer seats are assigned proportionally to the number of tickets bought. - **Inclusion Duties:** Holding a ticket places you in the includer set, obligating you to contribute to Ethereum’s censorship resistance by building and broadcasting an inclusion list to the network. When it's your turn, being selected as an includer (`16` per slot) automatically qualifies you for the weekly draw. Optionally, adding a validity and timeliness check for inclusion lists could ensure effective participation, though this adds a lot of complexity by requiring ILs to be recorded on-chain. - **Weekly Draw:** Each week, 100% of the accumulated prize pool from ticket sales is awarded randomly to one eligible includer. Imagine `16` tickets are bought per slot with `50,400` slots weekly, the weekly jackpot—if all tickets sell—would be `806 ETH` (`16 × 50,400 × 0.001 ETH`), over `$1.5 million` at current prices. *Fun note: The described mechanism is neutral EV but optionally, the lottery could allocate a portion, e.g., 70%, of ticket revenue to the prize pool, with the remainder burned or redistributed.) Another not so fun consideration is ensuring that large actors cannot bias the randomness (e.g., RANDAO) in their favor to increase their odds of receiving prizes.* ## Pros and Cons ### Memetics **Pros** **Cultural Resonance:** Lotteries have deep historical and cultural roots, making the mechanism immediately relatable and even fun for participants. **Cons** Leaning into lottery memetics might not be healthy for the L1, potentially reducing the focus on robust network security if the narrative becomes too superficial. Interestingly, one could argue that nation-states have used lotteries [under their own names](https://en.wikipedia.org/wiki/Lotteries_by_country), and embraced the associated memetics for centuries. On the flip side, lotteries are subject to strict regulations in many jurisdictions, and explicit on-chain lotteries could attract unwanted legal attention and impose additional compliance burdens on protocol participants. ### From rational choice theory to behavioral economics **Pros** Most blockchain economic models assume that all protocol participants are purely rational. By moving towards behavioral economics, we can overcome the limitations imposed by seemingly unavoidable trade-offs and design mechanisms that effectively leverage inherent human biases, thereby bridging the gap between theoretical models and real-world behavior. **Cons** Incorporating behavioral economics introduces additional variables and uncertainty, as human behavior is highly context-dependent compared to the clear-cut assumptions of rational choice models. Moreover, the overall system might become significantly more complex if the underlying assumptions change for each mechanism, resulting in a system that is less coherent as a whole. ### Rewarding honest participation The simplest form of an in-protocol lottery design automatically makes ticket holders eligible for the prize pool. However, this approach would likely result in low-quality inclusion lists, as there would be no incentive for participants to build and broadcast “good” ILs, or any IL at all. An alternative would be to track the ILs submitted by includers and deem them eligible only if they submit valid, timely ILs when it is their turn to participate. This, however, would require recording individual ILs on-chain, introducing significant complexity and some inefficiencies compared to current approaches like FOCIL, which don’t require on-chain storage (ILs are only broadcast over the CL p2p network). ### **Designing** against economies of scale The main thesis of this post is that any “positive EV” mechanism rewarding participants in a permissionless setting can be exploited by large, resource-rich actors, who end up crowding out smaller, less sophisticated participants. This outcome appears inevitable in practice, yet in theory, it might be possible to design mechanisms that avoid economies of scale without necessarily resorting to behavioral economics. ### In or out-of-protocol It is worth noting that lotteries designed to reward participation in improving Ethereum's censorship resistance don't *have* to be enshrined in the protocol. They could be run off-chain without requiring protocol changes, potentially mitigating the risk of negative perceptions associated with an L1-run lottery. However, out-of-protocol lotteries inevitably introduce additional trust assumptions and could lead to reduced participation, which is the very outcome these mechanisms are meant to avoid.

Import from clipboard

Paste your webpage below. It will be converted to Markdown.

Advanced permission required

Your current role can only read. Ask the system administrator to acquire write and comment permission.

This team is disabled

Sorry, this team is disabled. You can't edit this note.

This note is locked

Sorry, only owner can edit this note.

Reach the limit

Sorry, you've reached the max length this note can be.
Please reduce the content or divide it to more notes, thank you!

Import from Gist

Import from Snippet

or

Export to Snippet

Are you sure?

Do you really want to delete this note?
All users will lose their connection.

Create a note from template

Create a note from template

Oops...
This template is not available.
Upgrade
All
  • All
  • Team
No template found.

Create custom template

Upgrade

Delete template

Do you really want to delete this template?
Turn this template into a regular note and keep its content, versions, and comments.

This page need refresh

You have an incompatible client version.
Refresh to update.
New version available!
See releases notes here
Refresh to enjoy new features.
Your user state has changed.
Refresh to load new user state.

Sign in

Forgot password

or

By clicking below, you agree to our terms of service.

Sign in via Facebook Sign in via Twitter Sign in via GitHub Sign in via Dropbox Sign in with Wallet
Wallet ( )
Connect another wallet

New to HackMD? Sign up

Help

  • English
  • 中文
  • Français
  • Deutsch
  • 日本語
  • Español
  • Català
  • Ελληνικά
  • Português
  • italiano
  • Türkçe
  • Русский
  • Nederlands
  • hrvatski jezik
  • język polski
  • Українська
  • हिन्दी
  • svenska
  • Esperanto
  • dansk

Documents

Help & Tutorial

How to use Book mode

How to use Slide mode

API Docs

Edit in VSCode

Install browser extension

Get in Touch

Feedback

Discord

Send us email

Resources

Releases

Pricing

Blog

Policy

Terms

Privacy

Cheatsheet

Syntax Example Reference
# Header Header 基本排版
- Unordered List
  • Unordered List
1. Ordered List
  1. Ordered List
- [ ] Todo List
  • Todo List
> Blockquote
Blockquote
**Bold font** Bold font
*Italics font* Italics font
~~Strikethrough~~ Strikethrough
19^th^ 19th
H~2~O H2O
++Inserted text++ Inserted text
==Marked text== Marked text
[link text](https:// "title") Link
![image alt](https:// "title") Image
`Code` Code 在筆記中貼入程式碼
```javascript
var i = 0;
```
var i = 0;
:smile: :smile: Emoji list
{%youtube youtube_id %} Externals
$L^aT_eX$ LaTeX
:::info
This is a alert area.
:::

This is a alert area.

Versions and GitHub Sync
Get Full History Access

  • Edit version name
  • Delete

revision author avatar     named on  

More Less

No updates to save
Compare
    Choose a version
    No search result
    Version not found
Sign in to link this note to GitHub
Learn more
This note is not linked with GitHub
 

Feedback

Submission failed, please try again

Thanks for your support.

On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

Please give us some advice and help us improve HackMD.

 

Thanks for your feedback

Remove version name

Do you want to remove this version name and description?

Transfer ownership

Transfer to
    Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

      Link with GitHub

      Please authorize HackMD on GitHub
      • Please sign in to GitHub and install the HackMD app on your GitHub repo.
      • HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.
      Learn more  Sign in to GitHub

      Push the note to GitHub Push to GitHub Pull a file from GitHub

        Authorize again
       

      Choose which file to push to

      Select repo
      Refresh Authorize more repos
      Select branch
      Select file
      Select branch
      Choose version(s) to push
      • Save a new version and push
      • Choose from existing versions
      Include title and tags
      Available push count

      Pull from GitHub

       
      File from GitHub
      File from HackMD

      GitHub Link Settings

      File linked

      Linked by
      File path
      Last synced branch
      Available push count

      Danger Zone

      Unlink
      You will no longer receive notification when GitHub file changes after unlink.

      Syncing

      Push failed

      Push successfully