Public ledger authentication system
Systems and methods for public ledger authentication includes receiving a first previous authentication public ledger address and a first current authentication public ledger address from a user. A verified static user key is identified in a public ledger using the first previous authentication public ledger address. A second current authentication public ledger address is then provided to the user for use in the current authentication attempt. Authentication attempt information is determined that includes a number of authentication attempts by the user, and used in a hash operation with the verified static user key to generate a first user authentication key. A second user authentication key is retrieved from the public ledger that was sent from the first current authentication public ledger address to the second current authentication public ledger address in a transaction, and the user is authenticated if the second user authentication key matches the first user authentication key.
1. An anonymous donation system, comprising:
a non-transitory memory; and
one or more hardware processors coupled to the non-transitory memory and configured to read instructions from the non-transitory memory to cause the system to perform operations comprising:
identifying, through a network, a multi-signature crypto-currency transaction that is provided by a donor device of a donor and that identifies a donee;
accessing, using a donor public ledger address that is included in the multi-signature crypto-currency transaction, a verified donor static key that is stored in a public ledger;
generating a first donor authentication key using the verified donor static key and authentication attempt information associated with the donor;
confirming, in response to the first donor authentication key matching a second donor authentication key that was received at an authentication public ledger address included in the public ledger, a verified donor identity of the donor;
signing, in response to confirming the verified donor identity of the donor, the multi-signature crypto-currency transaction to provide a signed multi-signature crypto-currency transaction;
broadcasting the signed multi-signature crypto-currency transaction to cause donation funds to be transferred from the donor to the donee; and
sending, through the network to a donee device of the donee, a notification of the donation funds.
2. The system of claim 1 , wherein the operations further comprise:
receiving, through the network from the donor device, donor identity information;
verifying the donor identity information to generate the verified donor static key; and
providing the verified donor static key on the public ledger.
3. The system of claim 1 , wherein the operations further comprise:
receiving, through the network from the donee device, donee identity information;
verifying the donee identity information to generate a verified donee static key; and
providing the verified donee static key on the public ledger.
4. The system of claim 1 , wherein the broadcasting the signed multi-signature crypto-currency transaction causes the donation funds to be transferred via a public ledger from the donor to the donee.
5. The system of claim 1 , wherein the donation funds are transferred from the donor to the donee separately from a public ledger that identifies the multi-signature crypto-currency transaction.
6. The system of claim 1 , wherein the operations comprise:
providing system provider identity information for verification such that a verified system provider identity is included on the public ledger, wherein the multi-signature crypto-currency transaction is used to confirm the verified system provider identity.
7. A method for anonymous donations, comprising:
identifying, by a system provider device through a network, a multi-signature crypto-currency transaction that is provided by a donor device of a donor and that identifies a donee;
accessing, by the system provider device using a donor public ledger address that is included in the multi-signature crypto-currency transaction, a verified donor static key that is stored in a public ledger;
generating, by the system provider device, a first donor authentication key using the verified donor static key and authentication attempt information associated with donor;
confirming, by the system provider device in response to the first donor authentication key matching a second donor authentication key that was received at an authentication public ledger address included in the public ledger, a verified donor identity of the donor;
signing, by the system provider device in response to confirming the verified donor identity of the donor, the multi-signature crypto-currency transaction to provide a signed multi-signature crypto-currency transaction;
broadcasting, by the system provider device, the signed multi-signature crypto-currency transaction to cause donation funds to be transferred from the donor to the donee; and
sending, by the system provider device through the network to a donee device of the donee, a notification of the donation funds.
8. The method of claim 7 , further comprising:
receiving, by the system provider device through the network from the donor device, donor identity information;
verifying, by the system provider device, the donor identity information to generate the verified donor static key; and
providing, by the system provider device, the verified donor static key on the public ledger.
9. The method of claim 7 , further comprising:
receiving, by the system provider device through the network from the donee device, donee identity information;
verifying, by the system provider device, the donee identity information to generate a verified donee static key; and
providing, by the system provider device, the verified donee a static key on the public ledger.
10. The method of claim 7 , wherein the broadcasting the signed crypto-currency transaction causes the donation funds to be transferred via a public ledger from the donor to the donee.
11. The method of claim 7 , wherein the donation funds are transferred from the donor to the donee separately from a public ledger that identifies the multi-signature crypto-currency transaction.
12. The method of claim 7 , further comprising:
providing, by the system provider device to the donee device, system provider identity information for verification.
13. The method of claim 12 , further comprising:
verifying, by the donee device, the system provider identity information to generate a verified system provider identity;
providing, by the donee device, the verified system provider identity on the public ledger; and
using, by the donee device, the multi-signature crypto-currency transaction to confirm the verified system provider identity.
14. A non-transitory machine-readable medium having stored thereon machine-readable instructions executable to cause a machine to perform operations comprising:
identifying, through a network, a multi-signature crypto-currency transaction that is provided by a donor device of a donor and that identifies a donee;
accessing, using a donor public ledger address that is included in the multi-signature crypto-currency transaction, a verified donor static key that is stored in a public ledger;
generating a first donor authentication key using the verified donor static key and authentication attempt information associated with the donor;
confirming, in response to the first donor authentication key matching a second donor authentication key that was received at an authentication public ledger address included in the public ledger, a verified donor identity of the donor;
signing, in response to confirming the verified donor identity of the donor, the multi-signature crypto-currency transaction to provide a signed multi-signature crypto-currency transaction;
broadcasting the signed multi-signature crypto-currency transaction to cause donation funds to be transferred from the donor to the donee; and
sending, through the network to a donee device of the donee, a notification of the donation funds.
15. The non-transitory machine-readable medium of claim 14 , wherein the operations further comprise:
receiving, through the network from the donor device, donor identity information;
verifying the donor identity information to generate the verified donor static key; and
providing the verified donor static key on the public ledger.
16. The non-transitory machine-readable medium of claim 14 , wherein the operations further comprise:
receiving, through the network from the donee device, donee identity information;
verifying the donee identity information to generate a verified donee static key; and
providing the verified donee static key on the public ledger.
17. The non-transitory machine-readable medium of claim 14 , wherein the broadcasting the signed multi-signature crypto-currency transaction causes the donation funds to be transferred via a public ledger from the donor to the donee.
18. The non-transitory machine-readable medium of claim 14 , wherein the donation funds are transferred from the donor to the donee separately from a public ledger that identifies the multi-signature crypto-currency transaction.
19. The non-transitory machine-readable medium of claim 14 , wherein the operations comprise:
providing, to the donee device, system provider identity information for verification.
20. The non-transitory machine-readable medium of claim 19 , wherein the operations further comprise:
verifying, by the donee device, the system provider identity information to generate a verified system provider identity;
providing, by the donee device, the verified system provider identity on the public ledger; and
using, by the donee device, the multi-signature crypto-currency transaction to confirm the verified system provider identity.