# Post 1 / Meet HENCH

Your treasury. Your crew.

HENCH brings three specialized agents into a working Solana treasury desk: Ledger, Lookout and Runner.

Open an existing Squads v4 multisig or create one with the member wallets, approval threshold and timelock you choose. Read the treasury's SOL balance, token holdings, members, pending proposals and recent vault transactions directly from public Solana data.

Ledger turns the observation into an account of the treasury and its pending SOL obligations. Lookout examines member permissions, configuration authority, approval requirements and proposal state. Runner helps turn explicit recipient addresses and SOL amounts into a payment draft.

The next steps happen through a real multisig workflow. Review a proposal, simulate the transaction, sign with your wallet, collect member approvals and execute when the on-chain conditions allow it. HENCH supports individual and batched SOL payments from vault 0, with up to five recipients per proposal.

Each agent run keeps its report and evidence. Each transaction keeps its reviewed message and signature. A pending submission stays pending until its actual chain result is resolved. Your browser can export those records for independent review.

Agents analyze. Members sign. The treasury stays on Solana.

Image: post-01-crew.png

# Post 2 / Three operators

Meet the crew behind the desk.

LEDGER checks what the treasury holds and compares pending SOL payments with the observed balance. Amounts, assets and obligations belong in the same conversation.

LOOKOUT examines how the treasury is controlled: members, permissions, approval threshold, configuration authority and timelock. It follows proposal state and recent transaction evidence, with observation times attached.

RUNNER helps organize payments. Give it exact wallet addresses and SOL amounts. It validates an unsigned draft that you can open in the payment review. A draft is the beginning of an approval workflow, not a completed transfer.

Select an operator, assign a task and inspect its report. HENCH records each run separately, including the evidence returned by its tools. Network analysis is available before you select a treasury; account analysis uses the treasury you open.

Three roles. One treasury. Your decisions.

Image: post-02-operators.png

# Post 3 / The payment path

A payment has more than one state.

In HENCH, a member prepares a SOL payment proposal with explicit recipients and amounts. The interface presents the treasury, signing wallet, network fee and estimated signer balance change before requesting approval.

The signed transaction must match the reviewed message. HENCH checks it again against mainnet before submission. Squads records the proposal, eligible members vote and an executor submits the approved payment when the treasury's timelock permits it.

Creating a proposal does not send the payment. Voting does not mean execution has happened. A returned signature does not mean finalization.

HENCH keeps these stages visible. It records a signature before broadcasting and retains an uncertain submission for status checks instead of automatically creating another payment. Confirmed records require a successful finalized transaction that matches the reviewed message.

Inspect the recipients. Review the amount. Follow the signature.

Image: post-03-payment.png

# Post 4 / Evidence belongs at the desk

A treasury is more than its headline balance.

Who can propose? Who can vote? Who can execute? How many signatures are required? Is there a configuration authority? Which proposals are approved, rejected, stale or waiting?

HENCH puts those questions beside the public on-chain evidence. Open a Squads v4 multisig, inspect vault 0, review its token accounts and follow the explorer links to the underlying records.

The desk refreshes public observations while it is open and updates are enabled. You can pause updates, refresh manually, save treasuries to your wallet-authenticated workspace and export a snapshot or run receipt.

Token addresses identify assets. Source availability and timestamps matter. A permission report is an observation, not a guarantee about a token or its future behavior.

Your crew can inspect the evidence. Your members control the treasury.

Image: post-04-evidence.png
