# Native transport integrity checks

Use the supplied client to handle the native connection. The public [native TCP guide](https://coordinatordb.com/docs/concepts/features/interfaces/tcp) describes authentication, session state and request limits; it does not define a checksum algorithm or a packet layout for third-party implementations.

## Compare observable results

For a deterministic result, select a fixed row order and an explicit format:

```sh
./coordinator client --database data --query "SELECT 1 AS id, 'sample' AS value FORMAT json_each_row" > result.jsonl
```

Compare the captured bytes with a fixture only when the format and query make exact bytes part of the application's contract. For typed data, decoding the result and comparing values often gives a more useful failure than comparing a file digest alone.

## Keep integrity separate from security

A digest of a downloaded executable or exported file verifies only the comparison you performed against a trusted expected value. It does not establish server identity or encrypt a connection. Native transport has no TLS; use trusted connectivity or an external secure tunnel for credentials in transit.

When reporting a damaged transfer, include the chosen [format](https://coordinatordb.com/docs/reference/formats), input size and client error. Share a minimal non-sensitive fixture that reproduces the problem, not captured credentials or private result data.