Abstract: Implementations of the present specification include receiving a request to perform a private transaction associated with at least one account; in response to receiving the request, performing, by a workflow node, the private transaction; in response to performing the private transaction, generating, by the workflow node, a representation of the private transaction configured to be accessible only to entities that are authorized to access the private transaction; storing, in a private blockchain, the representation of the private transaction; generating, by the workflow node, an account record for the at least one account associated with the private transaction based at least in part on the private transaction, wherein the account record is configured to be accessible to at least one entity that is not authorized to access the representation of the private transaction in the private blockchain; and storing, in a public blockchain, the account record.

Abstract: Implementations of the present specification include receiving a request to perform a private transaction associated with at least one account; in response to receiving the request, performing, by a workflow node, the private transaction; in response to performing the private transaction, generating, by the workflow node, a representation of the private transaction configured to be accessible only to entities that are authorized to access the private transaction; storing, in a private blockchain, the representation of the private transaction; generating, by the workflow node, an account record for the at least one account associated with the private transaction based at least in part on the private transaction, wherein the account record is configured to be accessible to at least one entity that is not authorized to access the representation of the private transaction in the private blockchain; and storing, in a public blockchain, the account record.

Abstract: One or more implementations of the present specification provide a blockchain-based data processing method and device. Block data in a blockchain is synchronized by a data center to a local database of the data center. The data center is connect to the blockchain and a target application. A data usage request sent by the target application is received by the data center. In response to the data usage request, the local database is queried, by the data center, for requested data corresponding to the data usage request. The requested data is returned, by the data center, to the target application.

Abstract: Methods, systems and computer readable media for self-configuration of virtual network functions based on user intent are provided. In a network, a destination with an initial offering having a set of initial offering attributes is provided. A first virtual network function is connected to the destination that is capable of advertising the initial offering. A source having a set of need attributes defined by a user is also provided. The initial offering is advertised, and the source is connected to the first virtual network function. A second virtual network function with an added value is added and a modified offering having a set of modified attributes based on the set of initial offering attributes and the added value is created. The initial offering and the modified offering is advertised to the source.

Abstract: Discloses an earphone box and a control method thereof. The earphone box comprises a box body and a box cover, the box body is for containing an earphone and is connected to the box cover through a rotating shaft, and the box cover is rotatable relative to the box body and capable of being stabilized in a state of forming an angle with respect to the box body. The box body is provided therein with an angle detector which is capable of detecting a rotation angle of the rotating shaft and outputting a detected signal. The box body is further provided therein with an earphone box processor. The earphone box processor receives the detected signal, and when determining that a detected angle value indicated by the detected signal matches a preset angle value, outputs an operation instruction corresponding to the matched preset angle value.

Abstract: A method for processing blockchain-based transactions, comprising: acquiring a Nonce record from a Nonce list for a transaction initiated by a user account, wherein the Nonce list is maintained in a blockchain and is associated with the user account, the Nonce list comprises a plurality of Nonce records, and a Nonce record comprises a Nonce value; adding the acquired Nonce record to the transaction; and submitting the transaction to the blockchain, for a node in the blockchain to compare the Nonce record in the transaction with the plurality of Nonce records in the Nonce list, and to accept the transaction in response to the Nonce record matching any Nonce record in the Nonce list, wherein the Nonce value in the matching Nonce record in the Nonce list is monotonically increased based on a preset increment in response to that the transaction is accepted.

Abstract: Implementations of the present specification include receiving a request to perform a private transaction associated with at least one account; in response to receiving the request, performing, by a workflow node, the private transaction; in response to performing the private transaction, generating, by the workflow node, a representation of the private transaction configured to be accessible only to entities that are authorized to access the private transaction; storing, in a private blockchain, the representation of the private transaction; generating, by the workflow node, an account record for the at least one account associated with the private transaction based at least in part on the private transaction, wherein the account record is configured to be accessible to at least one entity that is not authorized to access the representation of the private transaction in the private blockchain; and storing, in a public blockchain, the account record.

Abstract: Implementations of the present specification include receiving, from a client in a blockchain network, a request to execute a workflow program, wherein the workflow program is stored in a blockchain maintained by the blockchain network; identifying an operation associated with the workflow program; assigning the identified operation to a subset of the plurality of nodes in the blockchain network, wherein each node is configured to execute the operation separately from the other nodes in the subset of nodes; identifying processing results for the executed operation associated with nodes in the subset of nodes, each processing result associated with a particular node from the subset and representing a result of the executed operation produced by the particular node; and determining a consensus result for the operation based on the identified processing results associated with a number of nodes greater than or equal to a consensus threshold matching the consensus result.

Abstract: Implementations of the present specification include receiving, from a client in a blockchain network, a request to execute a workflow program, wherein the workflow program is stored in a blockchain maintained by the blockchain network; identifying an operation associated with the workflow program; assigning the identified operation to a subset of the plurality of nodes in the blockchain network, wherein each node is configured to execute the operation separately from the other nodes in the subset of nodes; identifying processing results for the executed operation associated with nodes in the subset of nodes, each processing result associated with a particular node from the subset and representing a result of the executed operation produced by the particular node; and determining a consensus result for the operation based on the identified processing results associated with a number of nodes greater than or equal to a consensus threshold matching the consensus result.

Abstract: A method for processing blockchain-based transactions, comprising: acquiring a Nonce record from a Nonce list for a transaction initiated by a user account, wherein the Nonce list is maintained in a blockchain and is associated with the user account, the Nonce list comprises a plurality of Nonce records, and a Nonce record comprises a Nonce value; adding the acquired Nonce record to the transaction; and submitting the transaction to the blockchain, for a node in the blockchain to compare the Nonce record in the transaction with the plurality of Nonce records in the Nonce list, and to accept the transaction in response to the Nonce record matching any Nonce record in the Nonce list, wherein the Nonce value in the matching Nonce record in the Nonce list is monotonically increased based on a preset increment in response to that the transaction is accepted.

Abstract: Implementations of the present specification include receiving a request to perform a private transaction associated with at least one account; in response to receiving the request, performing, by a workflow node, the private transaction; in response to performing the private transaction, generating, by the workflow node, a representation of the private transaction configured to be accessible only to entities that are authorized to access the private transaction; storing, in a private blockchain, the representation of the private transaction; generating, by the workflow node, an account record for the at least one account associated with the private transaction based at least in part on the private transaction, wherein the account record is configured to be accessible to at least one entity that is not authorized to access the representation of the private transaction in the private blockchain; and storing, in a public blockchain, the account record.

Abstract: Implementations of the present specification include receiving a request to perform a private transaction associated with at least one account; in response to receiving the request, performing, by a workflow node, the private transaction; in response to performing the private transaction, generating, by the workflow node, a representation of the private transaction configured to be accessible only to entities that are authorized to access the private transaction; storing, in a private blockchain, the representation of the private transaction; generating, by the workflow node, an account record for the at least one account associated with the private transaction based at least in part on the private transaction, wherein the account record is configured to be accessible to at least one entity that is not authorized to access the representation of the private transaction in the private blockchain; and storing, in a public blockchain, the account record.

Abstract: A target transaction initiated by a member node device in a blockchain is received, where the target transaction include a reference time parameter, and where the target transaction indicates a transfer of an asset and associated data released by the member node device to the blockchain for transfer to a candidate block. Based on the reference time parameter, a determination is performed as to whether the target transaction is a valid transaction within a transaction validity period. In response to determining that the target transaction is a valid transaction within the transaction validity period, the target transaction is recorded to the candidate block.

Abstract: Implementations of the present specification include receiving, from a client in a blockchain network, a request to execute a workflow program, wherein the workflow program is stored in a blockchain maintained by the blockchain network; identifying an operation associated with the workflow program; assigning the identified operation to a subset of the plurality of nodes in the blockchain network, wherein each node is configured to execute the operation separately from the other nodes in the subset of nodes; identifying processing results for the executed operation associated with nodes in the subset of nodes, each processing result associated with a particular node from the subset and representing a result of the executed operation produced by the particular node; and determining a consensus result for the operation based on the identified processing results associated with a number of nodes greater than or equal to a consensus threshold matching the consensus result.

Abstract: This specification describes techniques for blockchain-based smart contract call. One example method includes receiving a target transaction initiated by a client device of a blockchain, wherein the target transaction is preconfigured for a call rule used to initiate a call for a smart contract; obtaining the call rule preconfigured for the target transaction; executing the call rule to initiate a call for a target smart contract; and providing a call result to the client device when the call for the target smart contract is completed.

Abstract: A target transaction initiated by a member node device in a blockchain is received, where the target transaction include a reference time parameter, and where the reference time parameter is used to determine whether the target transaction is a valid transaction within a transaction validity period. Based on the reference time parameter, a determination is performed as to whether the target transaction is a valid transaction within a transaction validity period. In response to determining that the target transaction is a valid transaction within the transaction validity period, the target transaction is recorded to a generated candidate block.

Abstract: A computer-implemented method for processing blockchain-based transactions, the computer-implemented method including: receiving a target transaction initiated by a member node device in a blockchain, wherein the target transaction comprises a unique identifier of the target transaction; querying a transaction idempotent table on the block chain to determine whether the transaction idempotent table has stored a transaction idempotent record corresponding to the unique identifier of the target transaction; and in response to determining that the transaction idempotent table has not stored the transaction idempotent record corresponding to the unique identifier of the target transaction, recording the target transaction in a candidate block on the blockchain.

Abstract: A target transaction initiated by a member node device in a blockchain is received, where the target transaction include a reference time parameter, and where the target transaction indicates a transfer of an asset and associated data released by the member node device to the blockchain for transfer to a candidate block. Based on the reference time parameter, a determination is performed as to whether the target transaction is a valid transaction within a transaction validity period. In response to determining that the target transaction is a valid transaction within the transaction validity period, the target transaction is recorded to the candidate block.

Abstract: Implementations of the present specification include receiving, from a client in a blockchain network, a request to execute a workflow program, wherein the workflow program is stored in a blockchain maintained by the blockchain network; identifying an operation associated with the workflow program; assigning the identified operation to a subset of the plurality of nodes in the blockchain network, wherein each node is configured to execute the operation separately from the other nodes in the subset of nodes; identifying processing results for the executed operation associated with nodes in the subset of nodes, each processing result associated with a particular node from the subset and representing a result of the executed operation produced by the particular node; and determining a consensus result for the operation based on the identified processing results associated with a number of nodes greater than or equal to a consensus threshold matching the consensus result.

Abstract: Implementations of the present specification include receiving a request to perform a private transaction associated with at least one account; in response to receiving the request, performing, by a workflow node, the private transaction; in response to performing the private transaction, generating, by the workflow node, a representation of the private transaction configured to be accessible only to entities that are authorized to access the private transaction; storing, in a private blockchain, the representation of the private transaction; generating, by the workflow node, an account record for the at least one account associated with the private transaction based at least in part on the private transaction, wherein the account record is configured to be accessible to at least one entity that is not authorized to access the representation of the private transaction in the private blockchain; and storing, in a public blockchain, the account record.