> For the complete documentation index, see [llms.txt](https://node-mesh.gitbook.io/description/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://node-mesh.gitbook.io/description/node-mesh.md).

# Node Mesh

## 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

<mark style="color:green;">`POST`</mark> `https://subapi.nodemesh.cc/submit/tx/<license-id>`

Submit an already serialized transaction to the network.

#### Headers

| Name                                           | Type             | Description |
| ---------------------------------------------- | ---------------- | ----------- |
| Content-Type<mark style="color:red;">\*</mark> | application/cbor |             |

#### Request Body

| Name                                               | Type   | Description                     |
| -------------------------------------------------- | ------ | ------------------------------- |
| Transaction CBOR<mark style="color:red;">\*</mark> | Binary | The transaction CBOR to submit. |

{% tabs %}
{% tab title="200: OK " %}

{% endtab %}

{% tab title="400: Bad Request " %}

{% endtab %}
{% endtabs %}

## 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.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://node-mesh.gitbook.io/description/node-mesh.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.