Trusted Nodes List
EBSI requests are sent to a node, and each node operator runs its own nodes, each with its own URL. The Trusted Nodes List (TNL) is the signed list of approved nodes for each environment: pilot, preprod and prod.
Why it exists
- Trust: the list is signed, so a forged or modified list fails verification and you are never sent to a rogue node.
- Neutrality: every approved node serves the same ledger. The list gives every operator the same visibility, instead of a default node chosen for you.
- Freshness: nodes join and leave the network over time. The list is versioned and expires, so your application picks up the changes.
How it works
The list is published as two signed documents that form a chain of trust:
Europeum key-list key ← the only thing you trust up front
│ signs (trusted-keys.json.sig)
▼
trusted-keys.json → custodian public keys + threshold
│ these keys sign (tnl.json.sig)
▼
tnl.json → node URLs per environment
Each tnl.json has a version, an issue date and an expiry date, at most 90 days later. Your application verifies the chain from the top before it uses any node, then picks a healthy node from the environment it needs.
Where to find it
Trusted Nodes List tool
Browse the approved nodes of each environment and check their health.
Trusted Nodes List API
The endpoints that deliver the list and its signatures.
Verify the Trusted Nodes List
Fetch, verify and use the list in your application.