Papers › Web3 Meets Behavioral Economics: An Example of Profitable Crypto Lottery Mechanism Design
Web3 Meets Behavioral Economics: An Example of Profitable Crypto Lottery Mechanism Design
Kentaroh Toyoda
The archive published only this paper's code-link row. Authors, date and abstract are from arXiv's metadata (CC0), read from the Kaggle arXiv metadata snapshot of 2026-09-12 where its title matched the archive's; the title is the archive's.
We are often faced with the non-trivial task of designing incentive mechanisms in the era of Web3. As history has shown, many Web3 services failed mostly due to the lack of a rigorous incentive mechanism design based on token economics. However, traditional mechanism design, where there is an assumption that the users of services strategically make decisions so that their expected profits are maximized, often does not capture their real behavior well as it ignores humans' psychological bias in making decisions under uncertainty. In this paper, we propose an incentive mechanism design for crypto-enabled services using behavioral economics. Specifically, we take an example of a crypto lottery game in this work and incorporate a seminal work of cumulative prospect theory into its lottery game mechanism (or rule) design. We designed four mechanisms and compared them in terms of utility, a metric of how appealing a mechanism is to participants, and a game operator's expected profit. Our approach is generic and will be applicable to a wide range of crypto-based services where a decision has to be made under uncertainty.
Code
Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.
Code Syntology ran Syntology
Not run by Syntology. Nothing on this page verifies that the listed code works.
Results from the paper archive 2025-07-28
No leaderboard rows for this paper in the archive.
Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections