A data processing method based on an intelligent contract, performed by an electronic device as a contract node, the method comprising: receiving (S101, 201) a firmware update request corresponding to a first server node transmitted by an execution node, the firmware update request comprising at least an updated version parameter of the first server node, wherein the updated version parameter comprises new firmware version information planned to perform a firmware update on the first server node and a hash value of the new firmware version information; invoking (S102, S202) an intelligent contract according to the firmware update request, and obtaining (S102, S202), from a blockchain based on the intelligent contract, a firmware version update record and a firmware version release record that are associated with the first server node, wherein the firmware version release record comprises version release parameters, and the firmware version release record is determined by a release node on the blockchain based on a consensus mechanism, the firmware version update record comprises a first version parameter and a second version parameter, and the second version parameter is a version parameter obtained after firmware update is performed on the first version parameter; and determining validity of the firmware update request according to the firmware version update record, the firmware version release record, and the updated version parameter, which comprises: performing rollback detection on the updated version parameter based on the first version parameter in the firmware version update record; determining, in response to detecting that the first version parameter is the same as the updated version parameter, that version rollback occurs, and determining that the firmware update request is an invalid update request, the invalid update request being used for indicating that the execution node does not have permission to perform firmware update on version information of the first server node; and determining, in response to detecting that the first version parameter is different from the updated version parameter, that the version rollback does not occur, and determining the validity of the firmware update request based on the updated version parameter and the firmware version release record. receiving (S101, 201) a firmware update request corresponding to a first server node transmitted by an execution node, the firmware update request comprising at least an updated version parameter of the first server node, wherein the updated version parameter comprises new firmware version information planned to perform a firmware update on the first server node and a hash value of the new firmware version information; invoking (S102, S202) an intelligent contract according to the firmware update request, and obtaining (S102, S202), from a blockchain based on the intelligent contract, a firmware version update record and a firmware version release record that are associated with the first server node, wherein the firmware version release record comprises version release parameters, and the firmware version release record is determined by a release node on the blockchain based on a consensus mechanism, the firmware version update record comprises a first version parameter and a second version parameter, and the second version parameter is a version parameter obtained after firmware update is performed on the first version parameter; and determining validity of the firmware update request according to the firmware version update record, the firmware version release record, and the updated version parameter, which comprises: performing rollback detection on the updated version parameter based on the first version parameter in the firmware version update record; determining, in response to detecting that the first version parameter is the same as the updated version parameter, that version rollback occurs, and determining that the firmware update request is an invalid update request, the invalid update request being used for indicating that the execution node does not have permission to perform firmware update on version information of the first server node; and determining, in response to detecting that the first version parameter is different from the updated version parameter, that the version rollback does not occur, and determining the validity of the firmware update request based on the updated version parameter and the firmware version release record. performing rollback detection on the updated version parameter based on the first version parameter in the firmware version update record; determining, in response to detecting that the first version parameter is the same as the updated version parameter, that version rollback occurs, and determining that the firmware update request is an invalid update request, the invalid update request being used for indicating that the execution node does not have permission to perform firmware update on version information of the first server node; and determining, in response to detecting that the first version parameter is different from the updated version parameter, that the version rollback does not occur, and determining the validity of the firmware update request based on the updated version parameter and the firmware version release record.