> ## Documentation Index
> Fetch the complete documentation index at: https://docs.hashdit.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Supported Chains

> Network coverage across HashDit public APIs

Use this page as the single source for public API network coverage. Individual endpoint pages link here instead of maintaining separate chain lists.

<Note>
  HashDit-owned requests use `chain_id`. Numeric EVM IDs may be sent as integers or decimal strings unless an endpoint states otherwise.
</Note>

## API Coverage

| API | Supported networks |
| - | - |
| [Address Classification](/api-reference/endpoint/address-classify) | Listed EVM networks and TRON |
| [Address Poisoning — Single](/api-reference/endpoint/address-poisoning/single) | Listed EVM networks and TRON |
| [Address Poisoning — Batch](/api-reference/endpoint/address-poisoning/batch) | Listed EVM networks and TRON; every item carries its own `chain_id` |
| [Address Security v2](/api-reference/endpoint/address-security-v2) | Listed EVM networks, TRON, and Solana |
| [Domain Security](/api-reference/endpoint/domain-security) | Chain-independent |
| [EVM Token Security](/api-reference/endpoint/token-security) | Listed EVM networks and TRON |
| [Solana Token Security](/api-reference/endpoint/solana-token-security) | Solana only; do not send `chain_id` |
| [Token Approval Security](/api-reference/endpoint/token-approval-security) | Ethereum, BNB Smart Chain, and TRON |
| [EIP-712 Signature Security](/api-reference/endpoint/eip712-security) | EVM typed-data requests |
| [Transaction Security](/api-reference/endpoint/transaction-security) | Supported EVM simulation networks and TRON |

## Networks and APIs

| Network | Chain ID | APIs |
| - | - | - |
| Ethereum | `1` | Address Classification, Address Poisoning, Address Security v2, EVM Token Security, Token Approval Security, EIP-712, Transaction Security |
| BNB Smart Chain | `56` | Address Classification, Address Poisoning, Address Security v2, EVM Token Security, Token Approval Security, EIP-712, Transaction Security |
| Other listed EVM networks | See the table below | Address Classification, Address Poisoning, Address Security v2, EVM Token Security, EIP-712, Transaction Security |
| TRON | `728126428` or `"tron"` | Address Classification, Address Poisoning, Address Security v2, EVM Token Security, Token Approval Security, Transaction Security |
| Solana | `"sol"` or `"solana"` for Address Security v2; implicit for Solana Token Security | Address Security v2, Solana Token Security, and the navigation-hidden Solana simulation integration |

## Listed EVM Networks

These networks are explicitly supported by Address Classification, Address Poisoning, Address Security v2, and EVM Token Security.

| Chain ID | Network |
| - | - |
| `1` | Ethereum |
| `10` | Optimism |
| `56` | BNB Smart Chain |
| `137` | Polygon |
| `143` | Monad |
| `146` | Sonic |
| `204` | opBNB |
| `324` | zkSync Era |
| `1284` | Moonbeam |
| `2741` | Abstract |
| `4663` | Robinhood Chain |
| `5000` | Mantle |
| `8453` | Base |
| `42161` | Arbitrum One |
| `42170` | Arbitrum Nova |
| `43114` | Avalanche |
| `59144` | Linea |
| `80094` | Berachain |

<Info>
  Transaction Security coverage can expand beyond this explicit list as simulation support is added. Contact HashDit to confirm a network that is not listed here before relying on it in production.
</Info>

## Network-Specific Notes

### TRON

TRON addresses use case-preserved Base58 form (`T…`, 34 characters), not EVM `0x` hex. Address Security v2, EVM Token Security, Token Approval, and Transaction Security accept `"tron"` or `728126428`.

### Solana

Solana Token Security is dedicated to Solana and therefore has no `chain_id` field. Send the token mint in `address`. Address Security v2 accepts `"sol"` or `"solana"` in `chain_id`.

### Transaction Security

Set `chain_id` on each EVM transaction object, not at the top level. The established integration accepts numeric values in its documented integer, decimal-string, and hexadecimal forms.