Blockscore blockchain unconfirmed transactions
This series of articles shows how the problem could be solved by introducing separate inter-changeable injectable modules. This article, the first in the series describes how blockscore blockchain unconfirmed transactions block structure and a block-related functionality could be defined agnostic to implementation details of two separate modules, consensus-related and transaction-related.
Code snippets using Blockscore blockchain unconfirmed transactions language are provided. The code is being used in the Scorex projectcompact cryptocurrency core implementation for experiments.
Making a new cryptocurrency usually means to replace 2 or 3 or both with something new. So to have an ability to make experiments fast we need to introduce some flexible and modular approach to a block structure and corresponding functions. What both modules could have in common? Well, they are parsing data of a type they are parametrized with, producing a blockfield based on data and providing genesis block data details. Score equals to 1 in case of longest chain rule or some calculated value relative to difficulty in case of cumulative difficulty to be used to select best blockscore blockchain unconfirmed transactions out of many possible options.
Also, we can add a function to generate a block here, taking private key owner to sign a blockscore blockchain unconfirmed transactions and transaction module to form transactional part of a block as parameters. We are going to consider a transactional part of a cryptocurrency, the most useful for an end user. Probably State monad could be helpful here, but for start as we are rewriting existing project not using a true functional approach the state interface is:.
Please note no any querying functions blockscore blockchain unconfirmed transactions listed in the basic trait, as we are going to make state design stackable. In addition to state a history is to be stored as well to send it to another peer for a reconstruction of a state, at least.
Please note, history could be in a different form than the blockchain, for example, a blocktree could be explicitly stored, or blockchain with addition of block uncles as Ethereum does. So a transactional module contains references to concrete implementations of state and history, and few functions able to:.
While Scorex is the name of blockscore blockchain unconfirmed transactions abstract framework, Lagonaki is the name of concrete implementation wiring together:. The resulting application wiring together modules is much leaner than before.
Some work could be done further though:. Generic Block Structure Blockscore blockchain unconfirmed transactions block consists of: Pointer to previous block Consensus-related data, e.
Transactions, the most valuable part of a block for users. Some transactions- or state-related data could be also included e. Merkle tree root hash for transactions or whole state after block application Additional useful information: Consensus Module What can we do with consensus-related data from a block?
Score equals to 1 in case of longest chain rule or some calculated value relative blockscore blockchain unconfirmed transactions difficulty in case of cumulative difficulty to be used to select best blockchain out of many possible options Also, we can add a function to generate a block here, taking private key owner to sign a block and transaction module to form transactional part of a block as parameters Considering all the functions, we can encode the interface now: Boolean def generators block: Seq[Account] def feesDistribution block: Map[Account, Long] def blockScore block: So a transactional module contains references to concrete implementations of state blockscore blockchain unconfirmed transactions history, and few functions able to: Merkle tree root hash are valid extract transactions from a block get transactions from unconfirmed pool and add corresponding metadata on forming a new block clear duplicates from unconfirmed pool on getting a block from the network The code reflecting requirements above is: History def isValid block: Boolean def transactions block: TransactionBlockData def clearFromUnconfirmed data: While Scorex is the name of an abstract framework, Lagonaki is the name of concrete implementation wiring together: Further Work The resulting application wiring together modules is much leaner than before.
Some work could be done further though: Please enable JavaScript to blockscore blockchain unconfirmed transactions the comments powered by Disqus.
blockscore blockchain unconfirmed transactions order reserves entire balance so you can never place 2 orders at the same time), i'm losing a lot of potential profits when price starts to move when i'm away from the computer. If you have an opportunity to make more money, will you pass it by. 099; (3) 0.