Blockchain-based relationship binding method, apparatus, and device
One or more embodiments of the specification provide a blockchain-based relationship binding method, apparatus, and device. An exemplary method may include: receiving a user binding request including a binding tag, the binding tag includes (1) a binding type of a binding relationship, and (2) role information of the second user in the binding relationship; sending a confirmation request to a second user; retrieving a relationship table of the second user; in response to the binding type in the user binding request includes a one-to-one binding relationship: determining whether the one or more binding types in the relationship table of the second user include the binding type in the user binding request, and if yes, terminating the method; and generating a record of binding relationship; writing the record of binding relationship into a blockchain; and updating the relationship table in the local database.
1. A blockchain-based user binding method, comprising:
receiving, by a blockchain node of a blockchain, a user binding request from a computing device of a first user, wherein the user binding request comprises user information of the first user, user information of a second user to be bound with the first user, and a binding tag, the binding tag comprising (1) a binding type of a binding relationship, and (2) role information of the second user in the binding relationship;
retrieving, by the blockchain node, information of a user terminal of the second user based on a mapping between the user information of the second user and the user terminal;
sending, by the blockchain node through a smart contract, a binding relationship confirmation request to the user terminal of the second user based on the information of the user terminal, the binding relationship confirmation request comprising the user information of the first user and the binding tag;
in response to receiving a confirming response from the second user, retrieving, by the blockchain node, a relationship table of the second user from a local database of the blockchain node, wherein the relationship table of the second user comprises a primary dimension comprising the user information of the second user, a secondary dimension comprising user information of one or more users that have been bounded with the second user, a tertiary dimension comprising one or more binding types of one or more historical binding relationships between the second user and the one or more users, and a quaternary dimension comprising the role information of the second user in the one or more historical binding relationships;
determining, by the blockchain node through the smart contract, attribute information of the binding type in the user binding request, wherein the smart contract stores a mapping relationship between the attribute information and the binding type;
in response to the attribute information indicating that the binding type in the user binding request comprises a one-to-one binding relationship:
determining whether the one or more binding types in the relationship table of the second user comprise the binding type in the user binding request, and
if yes, sending binding failure information to the first user and terminating the method;
in response to (1) the attribute information indicating that the binding type in the user binding request comprises a one-to-many binding relationship with a “one” aspect and a “many” aspect, and (2) the role information of the second user in the binding relationship corresponds to the “many” aspect of the one-to-many binding relationship:
determining whether the relationship table of the second user comprises a record with (1) the binding type in the user binding request in the tertiary dimension, and (2) the role information of the second user in the quaternary dimension; and
if yes, sending the binding failure information to the first user and terminating the method;
generating, by the blockchain node, a record of binding relationship between the first user and the second user by associating the user information of the first user, the user information of the second user, and the binding tag;
encrypting, by the blockchain node, the record of binding relationship into a ciphertext and storing the ciphertext on the blockchain, wherein the stored ciphertext is validated by a plurality of parties;
updating, by the blockchain node, the relationship table of the second user in the local database according to the user binding request, and
wherein one or more authorized users are allowed to query records of binding relationship stored on the blockchain.
2. The method according to claim 1 , wherein the record of binding relationship further comprises a timestamp of a current time.
3. The method according to claim 1 , further comprising:
determining whether a response from the second user to the binding relationship confirmation request is received within a preset time window; and
if not, sending the binding failure information to the first user.
4. The method according to claim 1 , wherein the updating the relationship table of the second user in the local database according to the user binding request comprises:
adding the user information of the first user to the secondary dimension of the relationship table, the binding type to the tertiary dimension.
5. The method according to claim 1 , further comprising:
updating, by the blockchain node, a relationship table of the first user in the local database according to the user binding request by adding the user information of the second user to the secondary dimension of the relationship table, the binding type to the tertiary dimension, and role information of the first user to the quaternary dimension.
6. A system comprising a processor of a blockchain node of a blockchain and a non-transitory computer-readable storage medium storing instructions executable by the processor of the blockchain node to cause the processor of the blockchain node to perform operations comprising:
receiving a user binding request from a computing device of a first user, wherein the user binding request comprises user information of the first user, user information of a second user to be bound with the first user, and a binding tag, the binding tag comprising (1) a binding type of a binding relationship, and (2) role information of the second user in the binding relationship;
retrieving information of a user terminal of the second user based on a mapping between the user information of the second user and the user terminal;
sending, through a smart contract, a binding relationship confirmation request to the user terminal of the second user based on the information of the user terminal, the binding relationship confirmation request comprising the user information of the first user and the binding tag;
in response to receiving a confirming response from the second user, retrieving a relationship table of the second user from a local database, wherein the relationship table of the second user comprises a primary dimension comprising the user information of the second user, a secondary dimension comprising user information of one or more users that have been bounded with the second user, a tertiary dimension comprising one or more binding types of one or more historical binding relationships between the second user and the one or more users, and a quaternary dimension comprising the role information of the second user in the one or more historical binding relationships;
determining, through the smart contract, attribute information of the binding type in the user binding request, wherein the smart contract stores a mapping relationship between the attribute information and the binding type;
in response to the attribute information indicating that the binding type in the user binding request comprises a one-to-one binding relationship:
determining whether the one or more binding types in the relationship table of the second user comprise the binding type in the user binding request, and
if yes, sending binding failure information to the first user and terminating the operations performed by the processor of the blockchain node;
in response to (1) the attribute information indicating that the binding type in the user binding request comprises a one-to-many binding relationship with a “one” aspect and a “many” aspect, and (2) the role information of the second user in the binding relationship corresponds to the “many” aspect of the one-to-many binding relationship:
determining whether the relationship table of the second user comprises a record with (1) the binding type in the user binding request in the tertiary dimension, and (2) the role information of the second user in the quaternary dimension; and
if yes, sending the binding failure information to the first user and terminating the operations performed by the processor of the blockchain node;
generating a record of binding relationship between the first user and the second user by associating the user information of the first user, the user information of the second user, and the binding tag;
encrypting the record of binding relationship into a ciphertext and storing the ciphertext on the blockchain, wherein the stored ciphertext is validated by a plurality of parties; and
updating the relationship table of the second user in the local database according to the user binding request, wherein one or more authorized users are allowed to query records of binding relationship stored on the blockchain.
7. The system according to claim 6 , wherein the record of binding relationship further comprises a timestamp of a current time.
8. The system according to claim 6 , wherein the operations further comprise:
determining whether a response from the second user to the binding relationship confirmation request is received within a preset time window; and
if not, sending the binding failure information to the first user.
9. The system according to claim 6 , wherein the updating the relationship table of the second user in the local database according to the user binding request comprises:
adding the user information of the first user to the secondary dimension of the relationship table, the binding type to the tertiary dimension.
10. The system according to claim 6 , wherein the operations further comprise:
updating a relationship table of the first user in the local database according to the user binding request by adding the user information of the second user to the secondary dimension of the relationship table, the binding type to the tertiary dimension, and role information of the first user to the quaternary dimension.
11. A non-transitory computer-readable storage medium configured with instructions executable by one or more processors of a blockchain node of a blockchain to cause the one or more processors of the blockchain node to perform operations comprising:
receiving a user binding request from a computing device of a first user, wherein the user binding request comprises user information of the first user, user information of a second user to be bound with the first user, and a binding tag, the binding tag comprising (1) a binding type of a binding relationship, and (2) role information of the second user in the binding relationship;
retrieving information of a user terminal of the second user based on a mapping between the user information of the second user and the user terminal;
sending, through a smart contract, a binding relationship confirmation request to the user terminal of the second user based on the information of the user terminal, the binding relationship confirmation request comprising the user information of the first user and the binding tag;
in response to receiving a confirming response from the second user, retrieving a relationship table of the second user from a local database, wherein the relationship table of the second user comprises a primary dimension comprising the user information of the second user, a secondary dimension comprising user information of one or more users that have been bounded with the second user, a tertiary dimension comprising one or more binding types of one or more historical binding relationships between the second user and the one or more users, and a quaternary dimension comprising the role information of the second user in the one or more historical binding relationships;
determining, through the smart contract, attribute information of the binding type in the user binding request, wherein the smart contract stores a mapping relationship between the attribute information and the binding type;
in response to the attribute information indicating that the binding type in the user binding request comprises a one-to-one binding relationship:
determining whether the one or more binding types in the relationship table of the second user comprise the binding type in the user binding request, and
if yes, sending binding failure information to the first user and terminating the operations performed by the one or more processors of the blockchain node;
in response to (1) the attribute information indicating that the binding type in the user binding request comprises a one-to-many binding relationship with a “one” aspect and a “many” aspect, and (2) the role information of the second user in the binding relationship corresponds to the “many” aspect of the one-to-many binding relationship:
determining whether the relationship table of the second user comprises a record with (1) the binding type in the user binding request in the tertiary dimension, and (2) the role information of the second user in the quaternary dimension; and
if yes, sending the binding failure information to the first user and terminating the operations performed by the one or more processors of the blockchain node;
generating a record of binding relationship between the first user and the second user by associating the user information of the first user, the user information of the second user, and the binding tag;
encrypting the record of binding relationship into a ciphertext and storing the ciphertext on the blockchain, wherein the stored ciphertext is validated by a plurality of parties; and
updating the relationship table of the second user in the local database according to the user binding request, wherein one or more authorized users are allowed to query records of binding relationship stored on the blockchain.
12. The storage medium according to claim 11 , wherein the record of binding relationship further comprises a timestamp of a current time.
13. The storage medium according to claim 11 , wherein the operations further comprise:
determining whether a response from the second user to the binding relationship confirmation request is received within a preset time window; and
if not, sending the binding failure information to the first user.
14. The storage medium according to claim 11 , wherein the updating the relationship table of the second user in the local database according to the user binding request comprises:
adding the user information of the first user to the secondary dimension of the relationship table, the binding type to the tertiary dimension.
15. The storage medium according to claim 11 , wherein the operations further comprise:
updating a relationship table of the first user in the local database according to the user binding request by adding the user information of the second user to the secondary dimension of the relationship table, the binding type to the tertiary dimension, and role information of the first user to the quaternary dimension.