|
|
|
|
|
by nowarninglabel
2948 days ago
|
|
Congrats on getting to this point! Been following Dharma closely for a little while now as we (Kiva) have an interest in trying to increase financial inclusion and decrease lending costs for the world's poor and have been hoping Dharma may end up being one piece to the future of our work. Could you possibly speak to how you intend to enable KYC (Know Your Customer) / AML (Anti-Money Laundering) to work with Dharma? The best bet so far has seemed to be trying to incentivize it through providing automatic fees to external parties to perform these actions and holding the money in escrow until it goes through. However, it would be great if you could share if you'll have discussed this problem at all. I'd love a world where we didn't have to deal with KYC & AML, but we do, and the sooner we figure out how to make it work in an efficient and inexpensive manner for the world's poor, the sooner we can reach the UN Sustainable Development goals around financial inclusion. |
|
We've pretty deliberately opted out of baking jurisdiction-specific protections (be they KYC / AML, accreditation, etc.) into the protocol insofar as we really want this to be a universal standard that's jurisdiction-agnostic -- to give a somewhat crass analogy, most developers would agree that it does not make sense for content-protection against, say, child pornography, to sit at the level of TCP / IP. Jurisdictions vary widely in how they treat lending law, and so we've opted to be as flexible as possible on a technical level.
With that being said, we're actively working on making sure that, at layers above the protocol, developers have an easy time plugging in / restricting functionality on the basis of regulatory parameters. There are several interesting projects in the decentralized identity space that are tackling ways of natively attesting to KYC / AML screening on blockchains like Ethereum, and we're actively in conversations with them to make sure we maintain compatibility.