DOMI Digital Rental Passport Architecture & Data Workshop
DOMI: Digital Rental Passport, Architecture & Data Brainstorming Workshop
Convener: Katrie Lowe, Pavel Metelitsyn, Juan Caballero
Notes-taker(s): Katrie Lowe
Tags for the session - technology discussed/ideas considered:
Discussion notes, key understandings, outstanding questions, observations, and, if appropriate to this discussion: action items, next steps:
Link to notes which includes diagram/images – provided by Katrie:
Intro to Domi:
Domi is a digital rental passport and a decentralised data management platform that empowers renters and applicants to fully control their personal data through the entire application and renting process. Domi enables tenants to “passport” their rental data wherever they relocate, and landlords handle rental applications in a more GDPR compliant way.
The Domi team is part of the SSI incubator program (ssiincubator.com) and is focused on building a proof of concept over the 12 weeks of the program.
Get feedback on how to approach delivering some of the features of Domi in the context of SSI data flow / architecture.
Suggestion that Domi was building a “reputation system”.
Team stated that we are definitely not intending to build a subjective/scoring reputation system.
The principle behind Domi is to improve fairness in the way renting happens so what is recorded in a tenant’s passport will be just pure fact based events so that landlords assess tenants just on this, like a CV.
Discussion was had what “reputation system” means. The concept of a “subjective” based
reputation versus one that is “fact-based”.
The problem with credit scores being used to judge people in rental application is that credit
scores are designed with not sufficiently narrowing context that they aren’t suitable to be used in the context of renting.
Measure theory concept introduced - the question of what ration / interval scale in which things are assessed. E.g. Uber lift rating is really not 1 to 5, because if you drop below 4 you are out of the system. It is actually are 1 or 2 rating system (yes/no).
Subjective ratings are gamed and corruptable.
Suggestion: Map Domi against existing rental management tools and see how we fit
Native or hosted wallet
Suggestion: Tenants will prefer to use Domi’s cloud service / hosted wallet. Landlords (big
corporate landlords) might want to manage their own wallet
How to address linking multiple issued VCs together if they below to a single contract (e.g. in when there is a rent price increase)
Domi idea: Issue new VC with old contract embedded within and revoke the last VC.
Question was asked why we need to revoke the last VC - it was explained that there are two
ways to think about ‘revocation’:
- 1) Change in (definition???)
- 2) Credential that has a definitive time of validity
So... revocation is immaterial in Domi’s situation. May not need to revoke old VCs.
Other points suggested for consideration:
- 1) Landlords will want a complete history (so perhaps tenant’s are not able to selectively disclose what they share of their tenant history)
- 2) Need a dispute process - Domi explained that VCs can only be issued with consensus from both parties. If sign off from one party is not achieved, we would use existing 3rd party arbitration if consensus from both parties is not possible to provide the 2nd signature needed.
Brainstorm of other items people might want to see in their passports
- - Providing rental payments
- - Maintenance being done (repairs to be recorded)
- - Approving renovations
Domi idea: 4 options identified 1) VCs issued by banks confirming payment; 2) Landlords issue
VCs - a commitment to be done as part of using Domi; 3) Tenants self attest; 4) Payments are
processed through Domi.
Re: 2) Incentive for landlords to participate? Need to see what landlords would actively
Re: 4) Domi could also be an escrow agent. Also support the management / return of security
deposit. Extra risk Domi would need to take on board as an escrow agent, but it is another
revenue stream opportunity.