Varun Srinivasan
@v
An interesting Farcaster idea: what if apps paid for storage, not users? - Apps buy a chunk of bytes. - Free to allocate to casts, reactions, follows in any way. - Free to assign to users in any way (fixed rate, free) - Lower cost by avoiding "unused storage" h/t to @vrypan.eth @deodad and @sds
24 replies
36 recasts
122 reactions
vrypan |--o--|
@vrypan.eth
Interesting! - How does pruning work in this model? Per app or per user? - Can a user easily move their data between apps? (yes, resigning and resubmitting, but are there any other limits they may hit in this case such as throttling?) - How could the ordering architecture be affected by this change? What if apps did not buy storage, but tipped sequencers? Many models, not auctions necessarily. For example a flat fee, but pick the sequencer.
1 reply
0 recast
1 reaction
Tony D’Addeo
@deodad
a thought on question 1 is move pruning to be an app level concern hubs don't prune but return an error if you try to submit w/o storage this works in global ordering and apps should be able to provide a good UX to users ex: app could offer a free version that provides 7 days of storage along with a paid version that provides indefinite storage
1 reply
0 recast
0 reaction
vrypan |--o--|
@vrypan.eth
This is why #2 is important. So, the app I've been using until now shuts down. I have no way to pay them. All the casts signed by them will start expiring? How can I save my old casts?
2 replies
0 recast
1 reaction
vrypan |--o--|
@vrypan.eth
Maybe a hybrid system, where a cast is stored/preserved is the app (key) or the user (fid) has paid for storage?
1 reply
0 recast
0 reaction
vrypan |--o--|
@vrypan.eth
Or maybe: - When submitting a cast, hubs check the app storage. This guarantees 1 year of storage for example. - When pruning a cast, hubs check user storage. Users can buy as much storage as they like. There is nothing stoping apps to pay for additional storage per user if they like (even today, I can buy storage for you).
1 reply
0 recast
0 reaction
vrypan |--o--|
@vrypan.eth
BTW, this model aligns with the snap chain design (still not my favorite :-), where we have "sequencers" and an archival service. Paid user storage could be collected by the archival service.
0 reply
0 recast
0 reaction
