A method for processing a service request, the method comprising: receiving, by a consensus node, a service request corresponding to a target service, wherein the service request comprises service data of the target service and a digest of the service data, wherein the digest of the service data comprises a string of characters generated based on the service data, and wherein the service request is received from a non-consensus node initiating the target service; performing, by the consensus node, a consensus verification on the service request based on the service data and the digest to determine an authenticity of the service data, wherein performing the consensus verification verifies whether the service data is consistent with the digest; instructing, by the consensus node, each non-consensus node to store the digest in a blockchain, in response to determining that the service request passes the consensus verification; and further in response to determining that the service request passes the consensus verification: sending, by the consensus node, the service data to at least one service node so that the service node stores the service data in a private database corresponding to the service node; or sending, by the consensus node, a storage instruction to at least one service node so that the service node stores the service data in a private database corresponding to the service node; or sending, by the consensus node, an acknowledgement instruction to a service node initiating the target service so that the service node stores the service data in a private database corresponding to the service node, and sending the service data to another service node so that the other service node stores the service data in a private database corresponding to the other service node, wherein the service node is a blockchain node participating in the target service; wherein the consensus node is only responsible for performing consensus verification on service requests and does not serve as a service node to participate in the target service and does not maintain a blockchain; and a non-consensus node does not participate in consensus verification, can serve only as a service node to participate in the target service, and maintains the blockchain. receiving, by a consensus node, a service request corresponding to a target service, wherein the service request comprises service data of the target service and a digest of the service data, wherein the digest of the service data comprises a string of characters generated based on the service data, and wherein the service request is received from a non-consensus node initiating the target service; performing, by the consensus node, a consensus verification on the service request based on the service data and the digest to determine an authenticity of the service data, wherein performing the consensus verification verifies whether the service data is consistent with the digest; instructing, by the consensus node, each non-consensus node to store the digest in a blockchain, in response to determining that the service request passes the consensus verification; and further in response to determining that the service request passes the consensus verification: sending, by the consensus node, the service data to at least one service node so that the service node stores the service data in a private database corresponding to the service node; or sending, by the consensus node, a storage instruction to at least one service node so that the service node stores the service data in a private database corresponding to the service node; or sending, by the consensus node, an acknowledgement instruction to a service node initiating the target service so that the service node stores the service data in a private database corresponding to the service node, and sending the service data to another service node so that the other service node stores the service data in a private database corresponding to the other service node, wherein the service node is a blockchain node participating in the target service; sending, by the consensus node, the service data to at least one service node so that the service node stores the service data in a private database corresponding to the service node; or sending, by the consensus node, a storage instruction to at least one service node so that the service node stores the service data in a private database corresponding to the service node; or sending, by the consensus node, an acknowledgement instruction to a service node initiating the target service so that the service node stores the service data in a private database corresponding to the service node, and sending the service data to another service node so that the other service node stores the service data in a private database corresponding to the other service node, wherein the service node is a blockchain node participating in the target service; wherein the consensus node is only responsible for performing consensus verification on service requests and does not serve as a service node to participate in the target service and does not maintain a blockchain; and a non-consensus node does not participate in consensus verification, can serve only as a service node to participate in the target service, and maintains the blockchain. the consensus node is only responsible for performing consensus verification on service requests and does not serve as a service node to participate in the target service and does not maintain a blockchain; and a non-consensus node does not participate in consensus verification, can serve only as a service node to participate in the target service, and maintains the blockchain.