A computer-implemented method for deleting a node in a blockchain network, comprising: obtaining, by a first consensus node of the blockchain network, a transaction comprising a request for deleting a second consensus node of the blockchain network, wherein the first consensus node is configured to store a node list comprising sequential numbering of all consensus nodes of the blockchain network including the first consensus node, with one of the consensus nodes being a primary node and the other consensus nodes being backup nodes; in response to that consensus verification of the transaction succeeds, executing the transaction and sequentially re-numbering the consensus nodes of the blockchain network excluding the second consensus node in the node list; and performing view change based on the re-numbered plurality of remaining consensus nodes to change the primary node for the re-numbered consensus nodes excluding the second consensus node to participate in future consensus verification based on the changed primary node, wherein the performing view change comprises initiating the view change in response to detecting any of the following conditions: a number of consensus nodes in the node list is inconsistent with a number of consensus nodes in a current view; consensus node identifiers in the node list are inconsistent with consensus node identifiers in the current view; a number of activated consensus nodes in the node list is inconsistent with a number of consensus nodes in a current view; and identifiers of activated consensus nodes in the node list are inconsistent with identifiers of the consensus nodes in the current view. obtaining, by a first consensus node of the blockchain network, a transaction comprising a request for deleting a second consensus node of the blockchain network, wherein the first consensus node is configured to store a node list comprising sequential numbering of all consensus nodes of the blockchain network including the first consensus node, with one of the consensus nodes being a primary node and the other consensus nodes being backup nodes; in response to that consensus verification of the transaction succeeds, executing the transaction and sequentially re-numbering the consensus nodes of the blockchain network excluding the second consensus node in the node list; and performing view change based on the re-numbered plurality of remaining consensus nodes to change the primary node for the re-numbered consensus nodes excluding the second consensus node to participate in future consensus verification based on the changed primary node, wherein the performing view change comprises initiating the view change in response to detecting any of the following conditions: a number of consensus nodes in the node list is inconsistent with a number of consensus nodes in a current view; consensus node identifiers in the node list are inconsistent with consensus node identifiers in the current view; a number of activated consensus nodes in the node list is inconsistent with a number of consensus nodes in a current view; and identifiers of activated consensus nodes in the node list are inconsistent with identifiers of the consensus nodes in the current view. a number of consensus nodes in the node list is inconsistent with a number of consensus nodes in a current view; consensus node identifiers in the node list are inconsistent with consensus node identifiers in the current view; a number of activated consensus nodes in the node list is inconsistent with a number of consensus nodes in a current view; and identifiers of activated consensus nodes in the node list are inconsistent with identifiers of the consensus nodes in the current view.