I’ve been mulling over how a curated decentralised library app could potentially work on the SAFE network. I have a rough architecture in mind, and it’d be great to get some feedback on the potential viability of such a structure so I thought I’d share my thoughts so far.
There are various roles that people can choose to fulfil on the app:
Lender - Someone who donates a book to the library
Borrower - Someone who borrows a book from the library
Librarian - Someone who curates the content of the library.
Builder - Someone who maintains/improves the codebase.
There would be an innate token on the app which is tied in to the rewards which the app earns through GETs when a book is borrowed. This token would be used to incentives/pay Lenders, librarians and builders.
Things to think about:
Tipping - it would seem that an innate ability to tip the author of a book you have read would be a good thing. Ascertaining the correct recipient of the tip would be fairly complicated for historical books (ie where the lender is not the author), but would be pretty simple for new books where it is assumed that the author has ‘lent’ their book to the library before it is made public elsewhere.
Lending - Could the lender/author earn funds from the GETs their book receives (incentivising uploading and overcoming the initial cost of the PUT)
Governance structure - Is there a simple way to do this by using the native token as having voting rights? Is there a pre-exiting solution which already exists which could be used?
I’m aware this is a high level design and ignores things like how librarians reach consensus in a decentralised environment and many other things. For right now though, I just wanted to see if there are there any obvious technical reasons why such an app structure may be floored, or could be improved upon, so all feedback/input welcome.