BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//cfp.protocol.berlin//protocol-berg-v2//talk//S9JXTZ
BEGIN:VTIMEZONE
TZID:CET
BEGIN:STANDARD
DTSTART:20001029T040000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
TZNAME:CET
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20000326T030000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3
TZNAME:CEST
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:pretalx-protocol-berg-v2-S9JXTZ@cfp.protocol.berlin
DTSTART;TZID=CET:20250613T120000
DTEND;TZID=CET:20250613T122000
DESCRIPTION:Most data storage systems have a way to automatically decide th
 e physical location that data will be stored. (That's why\, for example\, 
 you don't have to calculate something about sectors and tracks when you sa
 ve a file on your computer.)\n\nIf you do automatic allocation in decentra
 lised storage\, then you also need to automate the system that distributes
  payments to the service providers — Filecoin-style manual peer to peer 
 negotiation is not possible. What is needed is a *mechanism* in the sense 
 of microeconomic theory. This mechanism needs to have good properties if i
 t is to foster a healthy service provider population and deliver good serv
 ice and efficient prices to users.\n\nI'll give an introduction to this su
 bject in the context of the EthSwarm Protocol. In EthSwarm\, as well as pr
 oviding a fixed amount of capacity\, service providers must buy revenue sh
 ares from a contract at a fixed price in a kind of Tullock contest. Perhap
 s surprisingly\, even though this allocation system has nothing to do with
  the amount or quality of service provided\, under good conditions it resu
 lts in revenue share flowing to more efficient operators\, resulting in mo
 re competitive pricing.\n\nTarget Audience: people researching and buildin
 g decentralised services
DTSTAMP:20260414T220841Z
LOCATION:Cinema 6
SUMMARY:Reward and resource sharing mechanisms in decentralised storage - A
 ndrew Macpherson
URL:https://cfp.protocol.berlin/protocol-berg-v2/talk/S9JXTZ/
END:VEVENT
END:VCALENDAR