irene
irene
> This PR has seen no activity in 4 months. Is work on this topic still ongoing? We should either move to draft or close for now, depending on the...
Design doc for Arbitrum here https://hackmd.io/c6i6SP20Sz2ciFbapV1asQ
TODOs: - [ ] add to the doc the flow for cancel proposal - [ ] review the entire design - [ ] gas accounting ? @turinglabsorg can you link...
TODOs: - [x] add to the doc the flows - [x] review the entire design - [ ] compare with #89 ??
- [x] storage protocols (@irenegia, @lucaniz) will draft a first version of ticketing
@turinglabsorg Is this still in progress or should I move to paused/done?
what's elisea handle on github? so I can add her here!
okay, should we close this issue as "api work done" and open two new issues for the design work (one for retriev and one for onchain)? @turinglabsorg @0xjona
#### Why? To avoid the following "bad" behaviour from providers: never answering retrieval requests from clients, only answering to the referees. Question: can we use reputation only to prevent this...
> If anything, I would say that the current protocol actually incentivizes providers (with some considerations around CapEx and slash risk) to ignore requests from the clients. why this?