Node Mesh
Business grade Cardano transaction submission service.
Features
faster delivery to next block producer, proven
chained transaction support
guarantee of submission, including microfork resilience
very high availability, with multiple layers of redundance
easy integration, as regular cardano-submit-api entrypoint
transaction tracking, that includes mempool global propagation and transactions invalidated after submission
API
Submit a transaction
POST https://subapi.nodemesh.cc/submit/tx/<license-id>
Submit an already serialized transaction to the network.
Headers
Content-Type*
application/cbor
Request Body
Transaction CBOR*
Binary
The transaction CBOR to submit.
FAQ
What are the layers of the infrastructure?
DNS level load balancing, with health checks, taking the transaction to the nearest healthy dispatcher;
Transaction dispatcher (Europe, US East, US West) - dispatches the transaction to multiple nodes, depending on subscription;
Nodes - Cardano full nodes, with custom topology and various optimizations;
Submission guarantors - checks that submitted transactions are confirmed on chain, and do retries if they are ever needed.
Every layer uses multiple hosting providers, for extra reliability.
What factors contribute to the accelerated delivery of transactions?
The accelerated delivery of transactions is attributed to a multitude of factors, including the utilization of a robust network of full nodes, the implementation of topology optimizations, and the strategic deployment of nodes at critical points of interest to facilitate efficiency.
Could you elaborate on the concept of microfork resilience within your service?
From time to time forks in the chain are created, which are solved by the chain selection rule (of the longest chain). Our transaction delivery service greatly reduces the number of microforks your transactions take part of, and also rescues your transactions in resubmits them in a timely manner if a microfork does still happen.
What are the features of transaction tracking?
In addition to standard monitoring such as submission errors, block inclusion, and confirmation, our system also tracks global mempools to better assess transaction statuses during peak chain loads. Moreover, we monitor for transaction invalidations after submission, such as when an UTXO is deliberately spent to invalidate a transaction after it has reached the mempool.
Last updated