Unlike public blockchain platforms, TrxSys does not need to disclose the details of every transaction to prove the inetgrity and immutability of the ledger. Rather, TrxSys discloses just enough information to allow one to prove that the ledger has not been manipulated.

The following data elements can be found within their associated transactions. Once a transaction is written it cannot be changed without altering the ledger. It is also not possible for a transaction to be retroactively inserted.

Data elements defined:

• xnode_sequential_transaction_id - Each transaction is sequentially numbered.
  
• xnode_prior_record_block_hash - The hash of the prior record recorded in the current transaction.
  
• blocksigning_hash_of_all_objects - The hash of the current record. The prior hash is included to serially bind transactions together.
  

Frequently Asked Questions

Each new transaction written to the TrxSys ledger is serially hash bound to the prior transaction. This is a common feature of blockchain. If TrxSys were to regenerate a manipulated ledger then the hash record would break. From the point that a manipulated transaction was inserted in to the ledger every subsequent transaction would require that their respective hashes be regenerated. Therefore, the ledger shown here would change. Among many reasons why this is not a practical attack, the primary reason why this attack is not realistic is that any person with a valid transaction would be able to easily prove that a manipulation took place. The result of TrxSys ledger design is that every transaction contains information to prove the integrity of the historical ledger. TrxSys, nor anyone else, can manipulate, alter, change or effectively attack the ledger without the compromise becoming immediately apparent.