changeset.md

Hornet Node Configuration & TLIP KRA Integration

1. Overview

The TLIP KRA node is currently pointing to a private Hornet node hosted at KRA.
This setup prevents the TLIP KRA node from resolving identities and verifying data originating from other TLIP participant nodes.

To restore proper interoperability, the TLIP KRA node must be configured to point to a public IOTA Hornet node.

---

2. Why the Hornet Node Must Point to a Public Node

TLIP uses the distributed ledger (IOTA L1) to:

• Resolve DID Documents (identities of organizations)
• Verify data fingerprints (hashes)
• Validate signatures and timestamps
• Ensure trust across node-to-node communication

A private Hornet node does not contain:

• Identities anchored by other participants
• Hashes/fingerprints submitted by other TLIP nodes
• The shared state of the global TLIP ecosystem

This results in identity resolution failure and verification failure when receiving external data.

Pointing to a public IOTA Hornet node allows TLIP KRA to synchronize:

• All DID documents
• All data anchors
• All updates from the TLIP ecosystem

Ensuring full interoperability.

---

3. How TLIP KRA Works in the Data Flow

Step 1: Receive data from ICMS

TLIP KRA listens to an incoming queue from ICMS.

Step 2: Apply Data Exchange Subscriptions

For each incoming dataset:

• If a subscription exists → TLIP KRA forwards to the subscriber node (e.g., TLIP community node).
• If no subscription exists → data stays internal and is not shared.

Step 3: Anchor identity and data fingerprint

Regardless of whether data is shared, TLIP KRA:

• Anchors identity information
• Anchors the hash/fingerprint of the dataset

Only the hash is stored on the ledger;
the actual data remains inside TLIP KRA.

---

4. Required Change

✔ Update Hornet configuration in TLIP KRA

The Hornet endpoint must be changed to a public IOTA Hornet node (or a synchronized one that mirrors the IOTA global network).

This ensures that:

• Identity resolution works for all TLIP participants
• Data verification across nodes succeeds
• The TLIP KRA node becomes fully compliant with TLIP architecture

---

5. After the Fix

Feature	Current (Private Node)	After Update (Public Node)
Identity resolution	❌ Fails	✅ Works globally
Data fingerprint verification	❌ Not possible	✅ Fully supported
Interoperability	❌ Limited	✅ Cross-node
TLIP compliance	❌ Broken	✅ Correct

---

6. Summary

The Hornet node is the source of truth for identities and data anchors in TLIP.
TLIP KRA must connect to a public IOTA Hornet node so that it can verify and trust data coming from other nodes in the TLIP ecosystem.

Without this, identity resolution and multilateral data exchange cannot function.