This brief FAQ aims to complement the paper describing the details of Sabir.
#1: How could we verify a person registering in the website actually belongs to the CBE she is stating?
As a basic mean of automatic verification, we can ask for an email from the recognized domain of the CBE, e.g. @creativecommons.org. In the (hopefully few) cases where this is problematic, such as informal communities or CBEs without their own domain, we may move to crowd verification (others should validate you) or manual verification (a person should check your credentials).
#2: Why would our CBE vouch for others? What would be the motivation for it?
In the start, we should probably link the fact of receiving vouches with giving vouches: that is, either you play with the rules, or you don’t play. That is, you cannot be receiving vouches (and value) without vouching anyone. If the system reaches critical mass, the rules could be more relaxed.
#3: We want our CBE’s social value to be seen! Not just by those who register…
The same way as anyone can embed a badge, a license, or a crowdfunding banner in a website sidebar, your CBE could embed their recognized social value for any visitor to your CBE website to see it.
#4: What will be the initial population of the system?
The same way Bitcoin and other cryptocurrencies pre-mine currencies before launch (that is, generating additional currencies that will generate the initial transactions, distributed among predefined actors), we should provide a set of preselected initial CBEs within the system. Those, manually selected, will be guaranteed to follow a Commons-based approach (e.g. Wikipedia, Creative Commons, Mozilla), and therefore should help to grow the community organically on the right direction.
#5: What do you mean by a wallet for each contributor?
If I earn 50 WP-tokens, those may be published in a page of Wikipedia, or in my Wikipedia profile page. However, if I earn 50 WP-tokens, 10 CC-tokens, and 2 CouchSurfing-tokens, I would need a place to keep track of all those. It may be a web service or a client software installed in my computer. And such wallet would calculate how many sabirs I have in any given moment. In order to have an updated record, the wallet should query the CBE websites for the info, using the contributor’s credentials to verify that she’s actually the one who owns that username in that CBE. Thus, the wallet keeps a record of all the identifiants used by the contributor to interact with the different communities, i.e. something akin to keybase.io.
#6: Where would the information be stored?
Again, we may think of several ways of implementing this. The sabir.cc website (or any other website) could host public wallet information and/or a collection of uploaded and customised value matrixes (see Equation 3 in full paper). The site could have a public API that may be consulted from third-parties. The actual data could be stored either on a distributed and transparent database, such as the Ethereum blockchain (the technology behind Bitcoin) or on a centralised database governed by a particular community.
#7: How will the commoner show her sabirs to the market entity?
Although there can be others, a possible manner would involve the commoner’s smartphone and her wallet. The wallet software (an app or a webapp) may generate a QR code containing the information needed, including a verification of its legitimacy. The market entity may read the QR code, consider it valid, and apply the appropriate gift/discount. It may be compared to a coupon from those deal-based websites such as Groupon.