LEDGIT

Architecture

How LEDGIT connects agents, humans, Ledger, Hedera, and ENS

agent→CLI→Ledger→Hedera→HCS→ENS

🤖

Step 1

Agent Proposes

The AI agent calls ledgit propose with the action type and structured fields (amount, recipient, reason). The CLI validates against the configurable action schema.

🔒

Step 2

Human Approves on Ledger

The action details appear on the Ledger Stax screen. The human reviews and approves with one button press. The device returns an ECDSA signature.

💸

Step 3

HBAR Executes on Hedera

The CLI executes the HBAR transfer via TransferTransaction (or contract call via ContractExecuteTransaction). Sub-second finality, sub-cent fees.

📦

Step 4

Proof Recorded on HCS

The signed action, Ledger signature, risk level, and consensus timestamp are stored immutably on Hedera HCS. Sequence numbers ensure ordering.

📛

Step 5

Discoverable via ENS

The agent's ENS name has a text record (ledgit.hcs.topic) pointing to the HCS topic. Anyone resolves the name and queries the trail.

🔍

Step 6

View the Audit Trail

ledgit verify displays the ordered trail with risk badges and signature status. The web dashboard shows a calendar view with live polling.

Tech Stack

Ledger

Hardware signing

Hedera

HCS + HTS

ENS

Agent identity

@hashgraph/sdk

Hedera JS SDK

viem

ENS resolution

Commander.js

CLI framework

LEDGIT · Built at ETHGlobal New York 2026