Transaction Manager

transactions are at the center of all interactions on the blockchain they are responsible for defining the specific ledger state transitions between two consecutive blocks (ie utxos both consumed and created at an address) as a dapp developer, tracking individual states of a transaction is important and complex a transaction can be pending in a mempool, onchain in a block, or rolledback from a block capturing these state transitions in real time is challenging and can lead to corrupted data in your application service availability the transaction manager service is available on the following blockchains service bitcoin cardano dogecoin transaction manager coming soon api reference https //www postman com/go maestro/maestro api/documentation/v95q80t/cardano transaction manager api coming soon possible transaction states state description rejected rejected by the block producer due to an invalid transaction pending transaction successfully submitted and waiting in a mempool to be accepted on chain failed communication to the node has failed onchain transaction is part of a minted block rolledback transaction has been removed from the chain due to a network rollback or reorg transaction monitoring & webhook notification system maestro’s transaction manager is a state of the art tool that abstracts away the complexity of managing blockchain transaction states it provides a transaction monitoring dashboard and webhook notification system to track all transactions submitted with maestro this provides applications with the following benefits 1\ on submit transaction information ​ hhttps //www postman com/go maestro/maestro api/documentation/v95q80t/cardano transaction manager api automatic retries transactions that fail due to network issues are automatically resubmitted rejection error parsing transactions rejected by the node will return specific error messages, such as missing utxos or malformed transaction bodies pending transaction state successfully submitted transactions are classified as pending when entered into the mempool 2\ on chain webhook notifications ​ https //www postman com/go maestro/maestro api/documentation/v95q80t/cardano transaction manager api onchain once a pending transaction is included in a block, an onchain webhook notification is sent rolledback if an onchain transaction is dropped due to a rollback, a rollback webhook notification is sent timeouts \[coming soon] a transaction that remains in the mempool beyond its time to live will be marked as timed out and rejected transaction state machine ​ https //www postman com/go maestro/maestro api/documentation/v95q80t/cardano transaction manager api transaction state transitions can best be understood with a state machine https //en wikipedia org/wiki/finite state machine diagram note the state machine contains loops, meaning a transaction can transition through the same state multiple times before reaching an end state for example, a rolledback transaction may be included into another block, resulting in three webhook notifications onchain > rollback > onchain transaction submission ​ https //www postman com/go maestro/maestro api/documentation/v95q80t/cardano transaction manager api all transactions submitted via maestro's specialized endpoint are recorded and tracked by the transaction manager below are the possible response codes response code description state transition 200 valid submission start > pending 400 invalid submission start > rejected 500 network failure start > start (retry) > failed common use cases webhooks https //en wikipedia org/wiki/webhook are ideal for tracking continuously changing states of data, such as blockchain transactions maestro’s transaction notification system provides an efficient way for applications to react to on chain events, enhancing user experience—particularly for time sensitive applications examples of time sensitive web3 applications submitting a trade on a dex placing a bid for an nft auction transaction rollback notifications are essential for maintaining data integrity by providing a mechanism to revert in app operations as soon as a rollback happens on chain for example, reverting an onchain dex order after a block containing that transaction gets rolled back turbo transactions the turbo transaction service is designed to supercharge your transaction submission process it is a specialized system that employs various strategies to get your transaction on chain as fast as possible whether the network is under heavy load or operating under normal conditions, turbo transactions ensures your transactions are added to the blockchain with utmost reliability and speed this service is only included in subscriptions above the artist tier service availability the turbo transaction service is available on the following blockchains benefits of a transaction propagation system outcompete transactions trying to consume highly sought after utxos , particularly within intensive defi applications enhance the reliability of transaction submissions , particularly during periods of high network load accelerate transaction onchain confirmation and finality , providing an edge in time sensitive operations common use cases use cases are vast, ranging from defi applications, where transaction speed can significantly impact financial outcomes, to gaming platforms, where swift transactions can enhance user experience dramatically in essence, any application demanding fast, reliable transaction execution can substantially benefit from turbo transactions