CN110555684A - Account and system based on block chain system - Google Patents
Account and system based on block chain system Download PDFInfo
- Publication number
- CN110555684A CN110555684A CN201910795161.7A CN201910795161A CN110555684A CN 110555684 A CN110555684 A CN 110555684A CN 201910795161 A CN201910795161 A CN 201910795161A CN 110555684 A CN110555684 A CN 110555684A
- Authority
- CN
- China
- Prior art keywords
- account
- transaction
- clearing
- time
- insurance
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/04—Payment circuits
- G06Q20/06—Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme
- G06Q20/065—Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme using e-cash
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/08—Insurance
Abstract
The application discloses account based on block chain system includes: the system comprises an account module, an API (application program interface) module, a transaction module, an account data module and a transaction data module. The account based on the block chain system integrates the UTXO model and the account model, and has the advantages of bit currency and ether houses; the UTXO is used for supporting a multi-concurrent transaction mode, so that the processing efficiency is higher; the transaction can be accurately traced through the UTXO set in the account; the UTXO can be used for carrying out rapid security authentication on the transaction, and the security is good; the intelligent contract is supported based on the account mode, has good expansibility and can be widely used in various scenes and fields; supporting revocable operations of transactions; an automatic clearing function supporting transactions; the characteristics of non-tampering and decentralization of the block chain technology are ensured.
Description
Technical Field
The application relates to the field of communication, in particular to an account based on a blockchain system.
background
The continuous popularization and development of the blockchain technology, which gradually extends from single encrypted digital currency to other application fields, requires that the blockchain system can deal with a large number of complex business environments rather than a simple form of book keeping. The main morphological structure of the current block chain is also the UTXO and etherhouse account models of the bitcoin system, both of which have different defects and problems, and thus cannot be easily applied to other application fields besides the digital currency scenario.
The bitcoin system does not have a strict account model, but uses UTXO (full name Transaction Outputs, without spending Transaction Outputs), which has obvious advantages and disadvantages. The advantages are as follows: 1) first, the UTXO allows multiple transactions to be conducted in parallel because no account exists; 2) secondly, the UTXO has higher traceability, and the historical track of each transaction can be accurately traced; 3) thirdly, security, UTXO is also considered to be relatively secure and allows rapid Verification of Verification transactions via Simple Payment Verification (SPV). UTXO, however, also has significant disadvantages: 4) since UTXO is Stateless, which is very disadvantageous for developing applications thereon, Qtum, although the base is the transaction model of UTXO, still designs Account Abstraction Layer to facilitate the development of applications.
etherhouse system to 5) implement multi-scenario applications, we introduce smart contracts with full-blown figures to increase their programmability using the account model, but the resulting problems are: 6) because the Ethernet shop adopts an Account mode instead of a UTXO mode in a bitcoin, the transaction cannot be executed concurrently, the processing efficiency is greatly limited, and the transaction in the Ethernet shop is synchronously executed according to the sequence of nonces in an Account; 7) the extensibility is insufficient, and when a large number of transactions are generated in the ethernet network, the transaction confirmation time will become long.
Disclosure of Invention
The main objective of the present application is to provide an account based on a blockchain system, which improves or solves the defects of the account while ensuring the advantages of the above bitcoin and ether house system, and realizes a novel safe, efficient and extensible blockchain system integrating the advantages of the bitcoin and the ether house system.
in order to achieve the above object, the present application provides an account based on a blockchain system, including:
the account module is used for uniformly maintaining and managing user accounts, and the data change of the account module represents the change of the block chain state data;
an API interface module;
A transaction module, the transaction comprising: transaction verification and transaction pool management; the transaction verification is realized in a mode of pluggable verifiers, and the support for various characteristics of the transaction can be realized by adding or reducing corresponding verifiers; the transaction pool management is used for recording and managing unlinked transactions and providing a transaction reading interface for block-chain system block output and inquiry;
An account data module comprising an account ID, the type of account comprising: the first is common account and insurance account; and
a transaction data module comprising:
Common transaction, all operations based on the blockchain system are regarded as one transaction, operations not related to delay, clearing and withdrawal are regarded as common transaction, and the common transaction takes effect in real time;
The node incentive is used for an incentive mechanism of activities such as system accounting and voting, and the incentive mechanism is optional and can be cancelled in the authorization chain;
creating an insurance account for creating the transaction of the insurance account, wherein a receiving account number of the transaction is created as an insurance account number, if the account number exists, the account number is changed from a common account number to the insurance account number, and if the account number does not exist, an insurance account number is newly generated;
delayed transaction, wherein the delayed transaction is a transaction transferred by an insurance account number, can be withdrawn and has withdrawal time limit
and withdrawing the transaction for withdrawing the delayed transaction.
a clearing transaction for clearing an insurance account, the digital assets of the insurance account being transferred to the corresponding secure account after the clearing transaction has occurred.
and setting clearing time transaction for setting the time when the clearing transaction occurs, wherein the setting is delayed.
Optionally, the underlying data structure is responsible for organizing and maintaining all account information in the blockchain, and for efficient organization, query and storage of data;
the method comprises the following steps that (1) the down-link account management maintains the detailed state of an account on a block chain according to specific transaction/block information, wherein the detailed state comprises various specific attribute information of the account;
the on-chain account management maps the off-chain state of the account into a state which can be stored on the chain, and conversely, the detailed off-chain state represented by the off-chain state can be acquired according to the state stored on the block chain.
Optionally, creating an insurance account includes:
Creating an insurance account transaction; and
Inquiring details of the insurance account, and determining the creation condition of the insurance account;
setting a clearing time, comprising:
creating a set clearing time including a manner of taking the block height as a time unit and an actual time and a relative reference time;
setting a clearing time validation delay;
clearing an insurance account, comprising:
The clearable data prior to the clearing time will all be transferred to a secure account;
After the clearing time is reached, the current block node is used as a clearing node to automatically initiate a corresponding clearing transaction;
The clearing node verifies clearing data corresponding to the clearing transaction;
after verification, transferring the liquidable from the liquidable to a secure account;
the liquidable data is cleared after liquidation;
The secure account receives all of the data in the liquidable.
optionally, creating the insurance account transaction comprises: the insurance account transaction only has a unique input address and a unique output address, the input is the insurance account, and the output is the safety address of the insurance account; the clearing time must expire legally; the data in the clearing account is not null; the signature of the insurance account transaction must be the signature of the clearing node.
optionally, setting the clearing time comprises: the transaction only has unique input and output, and the input and the output are the insurance account; clearing time is greater than effective time; before the setting is not effective, the new clearing time cannot be set again, and the old clearing time is used; the clearing transaction and the clearing time are independently executed.
Optionally, the formalization of the insurance account is defined as:
A(k)＝<k,addr(A),type,S(k),key,L(t),I(k),data>，
Wherein:
k is the unique identification of account A (k);
addr (k) is the address of account A (k);
type is the type of account A (k), type ∈ { n, s }, n denotes a common account, s denotes an insurance account;
s (k) is the business status managed by account A (k);
key (k) is the public key of account A (k);
L (t) is the clearing time of account A (k);
i (k) an account specifying an insurance account revocation status output;
The data records a (k) initiated revocable transaction list.
Optionally, the insurance account creates a transaction TSAC, creates an insurance account A (k), the operation is to initiate a transfer transaction of type SAC from a normal account A (j),
the TIAC is an irrevocable transaction, successful execution of which transfers the amount designated by Ii +1 from A (j), the status of which is changed to insurance account A (k)change the state of A (k) to
Alternatively, the transaction TSAR may be withdrawn, initiated from insurance account A (k), and transferred to account A (j), i.e., the account may be replaced
Wherein θ isA set withdrawable time.
optionally, the transaction TR is withdrawn, initiated from the insurance account A (k), withdrawnsecured account i (k) bound to transaction initiating account a (k), namely:
the condition for proper execution of TR is that the transaction Tm is located at a block height less than θ.
Optionally, the revocable transaction TSAR and the revocable transaction TR, the designing of the revocable service comprising:
User k initiates a revocable transfer transaction TSAR through insured account a (k) at time i. The TSAR designates a transfer amount I, a destination account is an account A (j) of a user j, and the delayed effective time is theta;
after transaction is verified and chain confirmed, in addition to recording TSAR in the account book, state changes related to TSAR are also recorded in accounts A (k) and A (j), but the state changes related to TSAR are not immediately changedand
if user k finds a problem with the transaction during time I < n < theta, a one-time withdrawal transaction TR may be sent, withdrawing the TSAR transfer amount I to a (k) a designated one of the secure accounts s (k);
If a revocation transaction TR was initiated for TSAR once during time i < n < θ, and TR was verified and chain confirmed, then all revocation transactions initiated for TSAR after time n are invalid;
At time n θ, and TSAR is not withdrawn, the account status of the transfer parties changes, i.e. the transfer is posted,
at time n ≧ θ, the withdrawal transactions TR initiated by TSAR are all invalid transactions.
Compared with the prior art, the account based on the blockchain system has the following advantages:
1. Integrates the UTXO model and the account model, and has the advantages of the bitcoin and the Ethengfang
2. The UTXO is used for supporting a multi-concurrent transaction mode, so that the processing efficiency is higher;
3. the transaction can be accurately traced through the UTXO set in the account;
4. The UTXO can be used for carrying out rapid security authentication on the transaction, and the security is good;
5. The intelligent contract is supported based on the account mode, has good expansibility and can be widely used in various scenes and fields;
6. supporting revocable operations of transactions;
7. An automatic clearing function supporting transactions;
8. The characteristics of non-tampering and decentralization of the block chain technology are ensured.
drawings
the accompanying drawings, which are incorporated in and constitute a part of this application, serve to provide a further understanding of the application and to enable other features, objects, and advantages of the application to be more apparent. The drawings and their description illustrate the embodiments of the invention and do not limit it. In the drawings:
FIG. 1 is a schematic flow diagram of an account based on a blockchain system according to one embodiment of the present application;
FIG. 2 is a schematic diagram of a computer device according to one embodiment of the present application; and
FIG. 3 is a schematic diagram of a computer-readable storage medium according to one embodiment of the present application.
Detailed Description
in order to make the technical solutions better understood by those skilled in the art, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only partial embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
it should be noted that the terms "first," "second," and the like in the description and claims of this application and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It should be understood that the data so used may be interchanged under appropriate circumstances such that embodiments of the application described herein may be used. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
The application provides an account and a system based on a block chain system, which are used for solving the problem of data loss caused by key loss in the block chain system; the characteristics of extremely difficult tampering and decentralization of the block chain transaction system are ensured to be unchanged; the clearing efficiency of the block chain system is improved; the risk of human operation is avoided by automatic clearing.
it should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict. The present application will be described in detail below with reference to the embodiments with reference to the attached drawings.
In the formulas enclosed in this application, a plurality of variables or constants are provided, and the basic definitions of these variables or constants are as follows:
traffic State (State): the traffic state usually represents the state s e R by a rational number. The traffic state at time (block height) n is denoted sn.
account (Account): an account is a collection of business states. Given a traffic state space S, an account space a, an account a with k traffic states (x) e a is formally denoted as a (k) { S1]. The state of account A (x) at time n is represented assi∈S,i＝[1,k]。
Transaction (Transaction): one change in traffic state is called a transaction, i.e., the sequence is identified as Ti ═ F (Si, Ii +1) → Si +1, i ∈ N for the i +1 th transaction.
state Machine (State Machine): the state machine represents the change of the account business state with time. Defining a state transfer function F (S, I): S ∈ S → S, where I, S ∈ S are respectively referred to as the input and the starting state of the state transfer function, the state machine is formally represented as a set of state transfer functions, M ═ F (Si, Ii) → Si +1}, whereis the business status of all accounts at the time of the ith transaction,Is the entry of the account at the ith transaction.
Ledger (Ledger) the collection of transactions forms the Ledger L. The ledger at time n is denoted by l (n) ═ Ti }, and i ═ 1, n.
service State withdrawable (State retrievable) that a change to the account State can be partially or completely withdrawn under strict permission from the service level point of view. For a given transaction sequence i and j, i<partial revocation refers to achieving a certain state of account A (x)All retraction means that Sj ═ Si is achieved.
revocable Ledger (retrievable leader) if the Ledger is implemented with a blockchain that supports business state revocable, the Ledger is called revocable.
in an embodiment of the application, an account based on a blockchain system mainly includes five parts, namely an account model, an interface design, a transaction module design, an account data structure and a transaction data design.
The account module is in charge of unified maintenance and management of the user accounts, changes of the block chain state data are reflected in the changes of the account data finally. The bottom layer data structure is responsible for organizing and maintaining all account information in the block chain, does not understand the meaning of specific data, but is responsible for effective organization, query and storage of the data.
The down-chain account management maintains the detailed status of the account on the blockchain according to specific transaction/blockchain information, including various specific attribute information of the account.
The on-chain account management maps the off-chain state of the account into a state which can be stored on the chain, and conversely, the detailed off-chain state represented by the off-chain state can be acquired according to the state stored on the block chain.
interface design: the account module exists as a library and is not operated independently, but is called and managed by the node module. Therefore, the externally issued interface is an API interface.
the design of a transaction module, wherein the transaction comprises transaction verification and transaction pool management:
the verification of the transaction is realized by the pluggable verifier, and the support of various characteristics of the transaction can be realized by adding or reducing the corresponding verifier, for example, the related verification of the revocable transaction is realized by a specific verifier.
The management of the transaction pool is responsible for recording and managing unlinked transactions, and provides a transaction reading interface for block-chain system block-out and inquiry.
transaction data design account data structures include account type, UTXO set, clearing time, and security address.
account ID is an account unique identification
The account types are divided into two categories: one is a common account and the other is an insurance account.
the UTXO set represents the number of UTXOs owned by the account, i.e., the account balance.
The clearing time represents the time after which the account will effect the account clearing.
The secure address is the corresponding target address when the account clearing and revocable operations are performed.
the relevant definitions are as follows:
Common account: and the user establishes an account for the normal service. The transaction initiated by the common account is validated and then immediately takes effect, and cannot be cancelled.
an insurance account: the user establishes an account for the revocable service. The insurance account only supports delayed transactions. When the insurance account is created, the security account of the insurance account is bound, and the clearing time is calculated.
a security account: ordinary account bound with insurance account
And (4) delayed trading. The delayed transaction is a transaction rolled out by the insured account number and may be withdrawn. And has a withdrawal time limit.
the transaction is withdrawn. For revoking delayed transactions.
Clearing the transaction. A transaction for clearing an insurance account, digital assets of the insurance account being transferred to a corresponding secure account after the clearing transaction has occurred.
Transaction data design
in the common transaction, all operations based on the blockchain system are considered to be one transaction, operations without delay, clearing and withdrawing are considered to be common transactions, and the common transactions take effect in real time.
and (6) exciting the node. And (4) an incentive mechanism used for the participation of each node in activities such as system accounting, voting and the like, wherein the incentive mechanism is optional and can be cancelled in the authorization chain.
The insurance account creates a transaction. A transaction for creating an insurance account whose receiving account number is to be created as an insurance account number. If the account exists, the account is changed from a common account into an insurance account, and if the account does not exist, an insurance account is newly generated.
And (4) delayed trading. The delayed transaction is a transaction rolled out by the insured account number and may be withdrawn. And has a withdrawal time limit
The transaction is withdrawn. For revoking delayed transactions.
Clearing the transaction. A transaction for clearing an insurance account, digital assets of the insurance account being transferred to a corresponding secure account after the clearing transaction has occurred.
A clearing time transaction is set. For setting the time at which the clearing transaction takes place, the setting is time-delayed.
the signature of the transaction is used for verifying the transaction, so that the validity of the transaction is ensured.
the data of the transaction holds additional data of the transaction such as clearing information in the revocable related transaction, secure address, etc.
referring to fig. 1, an embodiment of the present application provides an account based on a blockchain system, including:
S2: creating an insurance account, comprising:
s21: creating an insurance account transaction; and
s22: inquiring details of the insurance account, and determining the creation condition of the insurance account;
S4: setting a clearing time, comprising:
s41: creating a set clearing time including a manner of taking the block height as a time unit and an actual time and a relative reference time;
s42: setting a clearing time validation delay;
S6: clearing an insurance account, comprising:
s61: the clearable data prior to the clearing time will all be transferred to a secure account;
S62: after the clearing time is reached, the current block node is used as a clearing node to automatically initiate a corresponding clearing transaction;
S63: the clearing node verifies clearing data corresponding to the clearing transaction;
s64: after verification, transferring the liquidable from the liquidable to a secure account;
s66: the liquidable data is cleared after liquidation;
S66: the secure account receives all of the data in the liquidable.
In one embodiment of the present application, creating an insurance account transaction includes: the insurance account transaction only has a unique input address and a unique output address, the input is the insurance account, and the output is the safety address of the insurance account; the clearing time must expire legally; the data in the clearing account is not null; the signature of the insurance account transaction must be the signature of the clearing node.
In an embodiment of the present application, setting the clearing time includes: the transaction only has unique input and output, and the input and the output are the insurance account; clearing time is greater than effective time; before the setting is not effective, the new clearing time cannot be set again, and the old clearing time is used; the clearing transaction and the clearing time are independently executed.
In an embodiment of the present application, the formalization of the insurance account is defined as:
A(k)＝<k,addr(A),type,S(k),key,L(t),I(k),data>，
Wherein:
k is the unique identification of account A (k);
addr (k) is the address of account A (k);
type is the type of account A (k), type ∈ { n, s }, n denotes a common account, s denotes an insurance account;
S (k) is the business status managed by account A (k);
key (k) is the public key of account A (k);
l (t) is the clearing time (block height) for account A (k);
I (k) an account specifying an insurance account revocation status output;
the data records a (k) initiated revocable transaction list.
In one embodiment of the present application, the insurance account creation transaction tsac (secureacountcreation transaction), creation of the insurance account a (k), initiates a transfer transaction of type SAC from the normal account a (j),
the TIAC is an irrevocable transaction, successful execution of which transfers the amount designated by Ii +1 from A (j), the status of which is changed to insurance account A (k)Change the state of A (k) to
In one embodiment of the present application, the transaction TSAR (SecureAccountRectractable transaction) may be withdrawn, initiated from insurance account A (k), and transferred to account A (j), i.e., account A (j)
wherein θ isA set withdrawable time.
in one embodiment of the present application, the transaction TR (Recall transaction) is withdrawn, initiated from the insurance account A (k), and withdrawnSecured account i (k) bound to transaction initiating account a (k), namely:
the condition for proper execution of TR is that the transaction Tm is located at a block height less than θ.
in an embodiment of the present application, where the revocable transaction TSAR and the revocable transaction TR are designed, the revocable service comprises:
user k initiates a revocable transfer transaction TSAR through insured account a (k) at time i. The TSAR designates a transfer amount I, a destination account is an account A (j) of a user j, and the delayed effective time is theta;
after transaction is verified and chain confirmed, in addition to recording TSAR in the account book, state changes related to TSAR are also recorded in accounts A (k) and A (j), but the state changes related to TSAR are not immediately changedAnd
if user k finds a problem with the transaction during time I < n < theta, a one-time withdrawal transaction TR may be sent, withdrawing the TSAR transfer amount I to a (k) a designated one of the secure accounts s (k);
if a revocation transaction TR was initiated for TSAR once during time i < n < θ, and TR was verified and chain confirmed, then all revocation transactions initiated for TSAR after time n are invalid;
At time n θ, and TSAR is not withdrawn, the account status of the transfer parties changes, i.e. the transfer is posted,
at time n ≧ θ, the withdrawal transactions TR initiated by TSAR are all invalid transactions.
The present application also provides a blockchain account revocation system, comprising:
the insurance account client is used for initiating a transfer transaction request and/or a withdrawal request to the server;
and the server end is used for delaying the theta time to execute or change the transfer transaction request.
In an embodiment of the application, a specific verification implementation is performed based on a withdrawable model, namely, an insurance account is introduced as an insurance account, and a set security account is used as an output of the withdrawal of the insurance account; secondly, transaction withdrawing logic is realized, and the method is suitable for scenes that a user has an account key but generates unexpected transfer transactions, such as hacking, misoperation, financial fraud and the like; thirdly, introducing revocable transaction and revocable transaction types to support transaction revocable logic.
the insurance account supports revocable transactions:
transactions transferred from this type of account have a set delayed lifetime
the transaction itself is recorded in the blockchain system,
But the account status will not change immediately but will actually take effect after waiting for the delay period
During the delay period, the insurance account may initiate a transaction-revocation operation to revoke the corresponding roll-out transaction-to-account status.
The target account that the insurance account withdraws is called a secure account.
The revocation output of the insurance account is not returned to the originating insurance account itself, but is output to the secure account. The secure account improves the security of revocation.
Through the division of the account types, the user can clearly distinguish whether the current account is an insurance account, whether the assets transferred from the account can be withdrawn or not and whether the withdrawable transaction is effective or not, so that the user can conveniently select different account types according to actual needs
The withdrawal logic of the transaction is suitable for a scenario that the user withdraws the insurance account to transfer out the transaction under the condition that the user has the secret key, and the implementation process comprises the following steps:
The insurance account A initiates a transfer transaction to transfer assets to the account B, and is set as a withdrawable transaction, after the transaction is successfully executed, the transaction and the effective time are respectively recorded in the accounts A and B,
but transfer assets are not available in a and B.
in the event that the transaction expiry date has passed, the transfer transaction is formally effected and the asset is formally available in B.
within the transaction period of validity, the insurance account a itself may initiate a withdrawal transaction,
The asset withdraws a and is immediately available and the transfer is cancelled in B.
the transaction itself is recorded in the blockchain system and the non-validated transactions maintained in the account are cleared.
as shown in fig. 2, the present application further provides a computer device comprising a memory, a processor and a computer program stored in the memory and executable by the processor, wherein the processor implements the method of any one of the above when executing the computer program.
as shown in fig. 3, a computer-readable storage medium, a non-volatile readable storage medium, having stored therein a computer program which, when executed by a processor, implements the method of any of the above.
A computer program product comprising computer readable code which, when executed by a computer device, causes the computer device to perform the method of any of the above.
the account based on the blockchain system defines accounts and action names with different functions:
common account/address: and the user establishes an account for the normal service. The transaction initiated by the common account is validated and then immediately takes effect, and cannot be cancelled.
insurance account/address: the user establishes an account for the revocable service. The insurance account only supports delayed transactions. When creating an insurance account, the insurance account is bound and a clearing time is required to be set.
Secure account/address: refers to the ordinary account to which the insurance account is bound.
And (3) creating a insurance account transaction, namely initiating a insurance account creating transaction when a user needs to create an insurance account, and simultaneously designating an insurance account address, a safety account address, clearing time and an initial safety account and clearing time in the transaction.
Clearing and trading: the transaction of clearing the insurance account and transferring the sum into the security account is realized. After the clearing transaction is completed, all data in the original insurance account is transferred into the security account bound with the original insurance account
Clearing time: a time length value set by the user for the insurance account. Once the data in the insurance account cannot be extracted due to the loss of the private key of the user, the data can be automatically transferred into the security account after the clearing time is expired. The clearing time takes the block height as an operation.
Clearing time delay validation time: the time from the time when the user initiates to set the clearing time of the insurance account to the time when the clearing time actually takes effect is referred to. That is, the clearing time is set not to take effect immediately, but to take effect after the clearing time is delayed by the effective time.
setting clearing time trade: the user modifies the transaction initiated by the insurance account clearing time.
The following structure is mainly added in the transaction account data structure:
clearing time (see item e) in 1) above) represents that the account will automatically implement account clearing after a specified time.
And the safe address represents that the account transfers the corresponding data into the address when the clearing action is implemented.
the data are organized in a form of a down-link account tree, an account tree root is finally formed and stored in a block, and the data structure form of the account tree is MPT.
Compared with the prior art, the account based on the blockchain system has the following advantages:
1. integrates the UTXO model and the account model, and has the advantages of the bitcoin and the Ethengfang
2. the UTXO is used for supporting a multi-concurrent transaction mode, so that the processing efficiency is higher;
3. The transaction can be accurately traced through the UTXO set in the account;
4. the UTXO can be used for carrying out rapid security authentication on the transaction, and the security is good;
5. The intelligent contract is supported based on the account mode, has good expansibility and can be widely used in various scenes and fields;
6. supporting revocable operations of transactions;
7. An automatic clearing function supporting transactions;
8. The characteristics of non-tampering and decentralization of the block chain technology are ensured.
It will be apparent to those skilled in the art that the modules or steps of the present invention described above may be implemented by a general purpose computing device, they may be centralized on a single computing device or distributed across a network of multiple computing devices, and they may alternatively be implemented by program code executable by a computing device, such that they may be stored in a storage device and executed by a computing device, or fabricated separately as individual integrated circuit modules, or fabricated as a single integrated circuit module from multiple modules or steps. Thus, the present invention is not limited to any specific combination of hardware and software.
The above description is only a preferred embodiment of the present application and is not intended to limit the present application, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, improvement and the like made within the spirit and principle of the present application shall be included in the protection scope of the present application.
Claims (10)
1. An account based on a blockchain system, comprising:
The account module is used for uniformly maintaining and managing user accounts, and the data change of the account module represents the change of the block chain state data;
an API interface module;
a transaction module, the transaction comprising: transaction verification and transaction pool management; the transaction verification is realized in a mode of pluggable verifiers, and the support for various characteristics of the transaction can be realized by adding or reducing corresponding verifiers; the transaction pool management is used for recording and managing unlinked transactions and providing a transaction reading interface for block-chain system block output and inquiry;
An account data module, comprising: account type, UTXO set, clearing time and security address, the account type comprising: a general account and an insurance account; and
A transaction data module comprising:
Common transaction, all operations based on the blockchain system are regarded as one transaction, operations not related to delay, clearing and withdrawal are regarded as common transaction, and the common transaction takes effect in real time;
the node incentive is used for an incentive mechanism of activities such as system accounting and voting, and the incentive mechanism is optional and can be cancelled in the authorization chain;
Creating an insurance account for creating the transaction of the insurance account, wherein a receiving account number of the transaction is created as an insurance account number, if the account number exists, the account number is changed from a common account number to the insurance account number, and if the account number does not exist, an insurance account number is newly generated;
delayed transaction, wherein the delayed transaction is a transaction transferred by an insurance account number, can be withdrawn and has withdrawal time limit
and withdrawing the transaction for withdrawing the delayed transaction.
a clearing transaction for clearing an insurance account, the digital assets of the insurance account being transferred to the corresponding secure account after the clearing transaction has occurred.
and setting clearing time transaction for setting the time when the clearing transaction occurs, wherein the setting is delayed.
2. The blockchain system based account of claim 1, wherein the underlying data structure is responsible for organizing and maintaining all account information in the blockchain, for efficient organization, querying and storage of data;
the method comprises the following steps that (1) the down-link account management maintains the detailed state of an account on a block chain according to specific transaction/block information, wherein the detailed state comprises various specific attribute information of the account;
The on-chain account management maps the off-chain state of the account into a state which can be stored on the chain, and conversely, the detailed off-chain state represented by the off-chain state can be acquired according to the state stored on the block chain.
3. the blockchain system based account of claim 2, wherein creating an insurance account comprises:
Creating an insurance account transaction; and
inquiring details of the insurance account, and determining the creation condition of the insurance account;
Setting a clearing time, comprising:
Creating a set clearing time including a manner of taking the block height as a time unit and an actual time and a relative reference time;
setting a clearing time validation delay;
Clearing an insurance account, comprising:
The clearable data prior to the clearing time will all be transferred to a secure account;
after the clearing time is reached, the current block node is used as a clearing node to automatically initiate a corresponding clearing transaction;
the clearing node verifies clearing data corresponding to the clearing transaction;
After verification, transferring the liquidable from the liquidable to a secure account;
The liquidable data is cleared after liquidation;
The secure account receives all of the data in the liquidable.
4. the blockchain system based account of claim 3, wherein creating an insurance account transaction includes:
the insurance account transaction only has a unique input address and a unique output address, the input is the insurance account, and the output is the safety address of the insurance account; the clearing time must expire legally; the data in the clearing account is not null; the signature of the insurance account transaction must be the signature of the clearing node.
5. The blockchain system based account of claim 4, wherein setting a clearing time includes:
The transaction only has unique input and output, and the input and the output are the insurance account; clearing time is greater than effective time; before the setting is not effective, the new clearing time cannot be set again, and the old clearing time is used; the clearing transaction and the clearing time are independently executed.
6. the blockchain system based account of claim 5, wherein the formalization definition of the insurance account is:
A(k)＝<k,addr(A),type,S(k),key,L(t),I(k),data>，
wherein:
k is the unique identification of account A (k);
addr (k) is the address of account A (k);
type is the type of account A (k), type ∈ { n, s }, n denotes a common account, s denotes an insurance account;
S (k) is the business status managed by account A (k);
key (k) is the public key of account A (k);
l (t) is the clearing time of account A (k);
I (k) an account specifying an insurance account revocation status output;
The data records a (k) initiated revocable transaction list.
7. The blockchain system based account of claim 6 wherein the insured account creates a transaction TSAC, creates an insured account A (k), the operation is to initiate a transfer transaction of type SAC from a normal account A (j),
the TIAC is an irrevocable transaction, successful execution of which transfers the amount designated by Ii +1 from A (j), the status of which is changed to insurance account A (k)change the state of A (k) to
8. the blockchain system based account of claim 7, wherein the transaction TSAR may be withdrawn, initiated from insurance account a (k), transferred to account a (j), i.e., the account is
wherein θ isA set withdrawable time.
9. the blockchain system based account of claim 8 wherein the transaction TR is withdrawn, initiated from the insurance account a (k), withdrawnsecured account i (k) bound to transaction initiating account a (k), namely:
The condition for proper execution of TR is that the transaction Tm is located at a block height less than θ.
10. the blockchain system based account of claim 9, wherein the revocable transaction TSAR and the revocable transaction TR design the revocable service includes:
user k initiates a revocable transfer transaction TSAR through insured account a (k) at time i. The TSAR designates a transfer amount I, a destination account is an account A (j) of a user j, and the delayed effective time is theta;
after transaction is verified and chain confirmed, TSAR is recorded in the account book, and state change related to TSAR is also recorded in accounts A (k) and A (j), but TSARHas not been changed immediatelyAnd
if user k finds a problem with the transaction during time I < n < theta, a one-time withdrawal transaction TR may be sent, withdrawing the TSAR transfer amount I to a (k) a designated one of the secure accounts s (k);
if a revocation transaction TR was initiated for TSAR once during time i < n < θ, and TR was verified and chain confirmed, then all revocation transactions initiated for TSAR after time n are invalid;
At time n θ, and TSAR is not withdrawn, the account status of the transfer parties changes, i.e. the transfer is posted,
at time n ≧ θ, the withdrawal transactions TR initiated by TSAR are all invalid transactions.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910795161.7A CN110555684A (en) | 2019-08-26 | 2019-08-26 | Account and system based on block chain system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910795161.7A CN110555684A (en) | 2019-08-26 | 2019-08-26 | Account and system based on block chain system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110555684A true CN110555684A (en) | 2019-12-10 |
Family
ID=68738349
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910795161.7A Pending CN110555684A (en) | 2019-08-26 | 2019-08-26 | Account and system based on block chain system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110555684A (en) |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111275414A (en) * | 2019-12-31 | 2020-06-12 | 深圳市网心科技有限公司 | Block chain-based digital currency exchange method, device and system |
| CN111445333A (en) * | 2020-03-26 | 2020-07-24 | 腾讯科技（深圳）有限公司 | Block generation method and device, computer equipment and storage medium |
| CN111461721A (en) * | 2020-04-16 | 2020-07-28 | 北京俩撇科技有限公司 | Block chain-based method and device for protecting account and verifying transaction |
| CN112700240A (en) * | 2021-03-24 | 2021-04-23 | 南京金宁汇科技有限公司 | UTXO architecture-based transaction commission fee promotion method and system in block chain |
| CN113610643A (en) * | 2021-08-13 | 2021-11-05 | 郑杰骞 | Chain structure processing method, transaction data processing device, data verification method, data verification device and medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105469510A (en) * | 2014-10-12 | 2016-04-06 | 吴思进 | Encryption currency wallet capable of noticing in advance delayed payment or finding |
| CN109102297A (en) * | 2018-09-04 | 2018-12-28 | 深圳市百宝廊珠宝首饰有限公司 | A kind of voidable method of payment and device |
| CN109347943A (en) * | 2018-10-10 | 2019-02-15 | 百洲集团 | A kind of method and apparatus based on one key cochain of block chain |
| WO2019035573A1 (en) * | 2017-08-16 | 2019-02-21 | 김용태 | Blockchain-based trading system and method therefor |
-
2019
- 2019-08-26 CN CN201910795161.7A patent/CN110555684A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105469510A (en) * | 2014-10-12 | 2016-04-06 | 吴思进 | Encryption currency wallet capable of noticing in advance delayed payment or finding |
| WO2019035573A1 (en) * | 2017-08-16 | 2019-02-21 | 김용태 | Blockchain-based trading system and method therefor |
| CN109102297A (en) * | 2018-09-04 | 2018-12-28 | 深圳市百宝廊珠宝首饰有限公司 | A kind of voidable method of payment and device |
| CN109347943A (en) * | 2018-10-10 | 2019-02-15 | 百洲集团 | A kind of method and apparatus based on one key cochain of block chain |
Non-Patent Citations (2)
| Title |
|---|
| 叶良 等: "《大数据支撑下的区块链技术研究》", 31 May 2019 * |
| 王志鹏等: "一种清算结算区块链设计", 《密码学报》 * |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111275414A (en) * | 2019-12-31 | 2020-06-12 | 深圳市网心科技有限公司 | Block chain-based digital currency exchange method, device and system |
| CN111445333A (en) * | 2020-03-26 | 2020-07-24 | 腾讯科技（深圳）有限公司 | Block generation method and device, computer equipment and storage medium |
| CN111445333B (en) * | 2020-03-26 | 2023-12-08 | 腾讯科技（深圳）有限公司 | Block generation method, device, computer equipment and storage medium |
| CN111461721A (en) * | 2020-04-16 | 2020-07-28 | 北京俩撇科技有限公司 | Block chain-based method and device for protecting account and verifying transaction |
| CN112700240A (en) * | 2021-03-24 | 2021-04-23 | 南京金宁汇科技有限公司 | UTXO architecture-based transaction commission fee promotion method and system in block chain |
| CN112700240B (en) * | 2021-03-24 | 2021-06-25 | 南京金宁汇科技有限公司 | UTXO architecture-based transaction commission fee promotion method and system in block chain |
| CN113610643A (en) * | 2021-08-13 | 2021-11-05 | 郑杰骞 | Chain structure processing method, transaction data processing device, data verification method, data verification device and medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11893626B2 (en) | Method for creating commodity assets from unrefined commodity reserves utilizing blockchain and distributed ledger technology | |
| US11829997B2 (en) | Self-enforcing security token implementing smart-contract-based compliance rules consulting smart-contract-based global registry of investors | |
| AU2020200682B2 (en) | Systems and methods of secure provenance for distributed transaction databases | |
| CN110555684A (en) | Account and system based on block chain system | |
| CN109886677B (en) | Commodity purchasing method and device based on block chain | |
| CN108805707A (en) | Works copyright revenue distribution method and device based on block chain | |
| US11216802B2 (en) | Self-enforcing security token implementing smart-contract-based compliance rules consulting smart-contract-based global registry of investors | |
| CN111164629A (en) | Methods, apparatus, and computer-readable media for compliance-aware tokenization and control of asset value | |
| CN109598147B (en) | Data processing method and device based on block chain and electronic equipment | |
| KR102313675B1 (en) | Block chain-based crytography donation server and donation method without limitation to donation target | |
| CN110020936B (en) | Asset management method and device based on block chain and electronic equipment | |
| CN110020948B (en) | Asset tracing method and device based on block chain and electronic equipment | |
| US11107076B1 (en) | Automatic transaction-based verification of account ownership | |
| CN111402033A (en) | Asset information management method and device based on block chain | |
| WO2018192931A1 (en) | Delivery versus payment mechanism | |
| EP3736760A1 (en) | Automated transaction protocol linking renewable energy generation assets to energy power consumers applying distributed digital ledger technology and iot energy meters | |
| CN109859031A (en) | A kind of information processing method, node and the storage medium of block chain network | |
| Hrga et al. | Technical analysis of an initial coin offering | |
| CN116961876A (en) | Virtual resource management method, device, equipment and storage medium for blockchain | |
| US20230053969A1 (en) | Tokenization of digital media files and associated derivatives | |
| KR20230031983A (en) | Methods and systems for creating, tracking and changing the state of non-divisible tokens | |
| TW201933245A (en) | Management method and system for credit line | |
| US20210374843A1 (en) | Debt Resource Management in a Distributed Ledger System | |
| CN111161074A (en) | Block chain account balance model construction method supporting sum locking | |
| US20230360029A1 (en) | Non-fungible tokens for stadium seats and tickets |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20191210 |
|
| RJ01 | Rejection of invention patent application after publication |