API – Transaction statuses (Update)

Oct-2-2023

BusyDAO is built on our Hyperledger Fabric framework, so transaction statuses are tethered with the core functions. These statuses are handled on the Explorer to show the status of the particular transaction.

There are a total of three statuses so far:

• Success – The transaction is successful and properly confirmed.
• Failed: MVCC – The transaction is refused. The full name of the error is “MVCC_READ_CONFLICT”. In simple words, it means that there was a collision between two transactions. Some transactions are protected so that only one of a type can be in the same block. That is because of the extended logic related to the BusyDAO staking as with every staking action, the BusyDAO state can be changed (e.g., change the phase of the blockchain). In this case, the transaction has to be done again.
• Failed: PRC – The transaction is refused. The full name of the error is “PHANTOM_READ_CONFLICT”. In simple words, it means that there was a collision between transactions and blockchain execution. In this case, the transaction has to be done again.