System and method for providing a decentralized exchange for credit lending
A system and method for performing a financial transaction are disclosed. An application running on a first server requests a financial transaction secured by collateral of a first party in the form of digital currency. The application generates a semantic ASK message encoded with parameters defining the requested financial transaction. The semantic ASK message is sent to one or more second parties via a decentralized web node thereof. A BID message is received from at least one of the one or more second parties defining proposed terms for the requested financial transaction. Credentials for the first party are forwarded from a decentralized web node of the first party, the credentials defined in the BID message. Access is provided to the collateral of the first party to the second party upon receipt of confirmation of the financial transaction from the second party.
1 . A method of performing a financial transaction, comprising:
requesting, via a first application running on a first server, a financial transaction secured by collateral of a first party in a form of digital currency;
generating, by the first application running on the first server, a semantic loan request (“semantic ASK”) message encoded with parameters defining the requested financial transaction and an identification of personally identifiable information available for the first party;
identifying, by the first application running on the first server, a second party via a decentralized identifier associated with the second party, wherein the decentralized identifier associated with the second party is obtained via a decentralized identifier resolver application programming interface running on an associated processor of a decentralized identifier resolver server;
sending, by the first application running on the first server, the semantic ASK message to a decentralized web node of the second party, wherein the decentralized web node of the second party is identified via the decentralized identifier associated with the second party;
receiving, by the first application running on the first server, a BID message from the second party defining proposed terms for the requested financial transaction and specifying information required from the first party for responding to the BID message;
providing, by the first application running on the first server, a second application running on a separate remote server with access to personally identifiable information of the first party including income, assets, and/or payment history stored in encrypted form on a decentralized web node of the first party, wherein the decentralized web node of the first party is identified by a decentralized identifier associated with the first party;
generating, by the second application running on the separate remote server, a trust score based on the personally identifiable information of the first party, the trust score formatted as a verifiable credential of the first party;
transmitting, by the second application running on the separate remote server, the generated trust score to the decentralized web node of the first party;
forwarding to the second party, by the first application running on the first server, credentials for the first party from the decentralized web node of the first party, wherein the credentials comprise the information required from the first party for responding to defined in the BID message and the trust score; and
providing, by the first application running on the first server, access to the collateral of the first party to the second party upon receipt of confirmation of the financial transaction from the second party.
2 . The method of claim 1 , wherein the financial transaction is a loan of fiat money.
3 . The method of claim 1 , wherein the decentralized web node of the first party is provided via a decentralized web node application programming interface running on a processor at a server associated with the first party.
4 . The method of claim 1 , wherein the decentralized identifier associated with the first party is obtained via the decentralized identifier resolver application programming interface running on the associated processor of the decentralized identifier resolver server.
5 . The method of claim 1 , wherein the decentralized web node of the second party is provided via a decentralized web node application programming interface running on a processor at a server associated with the second party.
6 . The method of claim 1 , wherein the first party is a consumer.
7 . The method of claim 1 , wherein the second party is a participating financial institution.
8 . A system for performing a financial transaction, comprising:
a remote server having an associated processor and an associated non-transitory computer-readable storage medium, the associated non-transitory computer-readable storage medium having executable instructions for an associated application, which when executed, cause the associated processor to perform the following operations:
receiving access to personally identifiable information of a first party including income, assets, and/or payment history stored in encrypted form on a decentralized web node of the first party, wherein the decentralized web node of the first party is identified by a decentralized identifier associated with the first party;
generating a trust score based on the personally identifiable information of the first party, the trust score formatted as a verifiable credential of the first party; and
transmitting the generated trust score to the decentralized web node of the first party;
a first server having an associated processor and an associated non-transitory computer-readable storage medium, the associated non-transitory computer-readable storage medium having executable instructions for an associated application, which when executed, cause the associated processor to perform the following operations:
requesting a financial transaction secured by collateral of the first party in a form of digital currency;
generating a semantic loan request (“semantic ASK”) message encoded with parameters defining the requested financial transaction and an identification of personally identifiable information available for the first party;
identifying a second party via a decentralized identifier associated with the second party, wherein the decentralized identifier associated with the second party is obtained via a decentralized identifier resolver application programming interface running on an associated processor of a decentralized identifier resolver server;
sending the semantic ASK message to a decentralized web node of the second party, wherein the decentralized web node of the second party is identified via the decentralized identifier associated with the second party;
receiving a BID message from the second party defining proposed terms for the requested financial transaction and specifying information required from the first party for responding to the BID message;
forwarding, to the second party, credentials for the first party from the decentralized web node of the first party, the credentials defined in the BID message, wherein the credentials comprise the information required from the first party for responding to the BID message and the trust score; and
providing access to the collateral of the first party to the second party upon receipt of confirmation of the financial transaction from the second party.
9 . The system of claim 8 , wherein the financial transaction is a loan of fiat money.
10 . The system of claim 8 , wherein the decentralized web node of the first party is provided via a decentralized web node application programming interface running on a processor at a server associated with the first party.
11 . The system of claim 8 , wherein the decentralized identifier associated with the first party is obtained via the decentralized identifier resolver application programming interface running on the associated processor of the decentralized identifier resolver server.
12 . The system of claim 8 , wherein the decentralized web node of the second party is provided via a decentralized web node application programming interface running on a processor at a server associated with the second party.
13 . The system of claim 8 , wherein the first party is a consumer.
14 . The system of claim 8 , wherein the second party is a participating financial institution.