Hukt

Transfer hook framework.
GH: HW8cwBUHhciAuZjuetEvhJ1JcrFzZDSLbhPXSj9pump

[Hukt @huktfun]

Eight gates. One path through.

A transfer that cannot clear a gate does not leave the yard.

https://t.co/xNzjIZufmH

[Hukt @huktfun]

Presets do not stack. They couple.

Six cars, one train, checked at every joint.

https://t.co/xNzjIZufmH

[Hukt @huktfun]

/3
And mints that pass the check wear the plate, which is an advertisement for the catalogue that verified them. Publisher to catalogue to integrator to mint, back to publisher.

Today the loop is small and we say so. But every coupling in it is a thing that happened on-chain, not a projection. Yards are built that way: one verified coupling at a time.

https://t.co/PM2FjhKpoB

[Hukt @huktfun]

/1
Hook infrastructure compounds from three directions at once, and none of them is ours to fake.

Publishers put preset shapes into the registry and stake behind them. Every attested shape makes the catalogue worth one more read.

[Hukt @huktfun]

/2
Integrators -- wallets, DEXs, marketplaces -- read that catalogue through one resolver call, and each one that does turns "hooked token" from a support ticket into a normal asset. Mints notice which integrations do not break, and route accordingly.

[Hukt @huktfun]

https://t.co/vZpV7vnlOn

[Hukt @huktfun]

Five surfaces now stand on the mainline: Inspector, Registry, resolver, the demonstration yard, and the plate -- the framework whole and readable, and where the rails go from here is a longer conversation we will only ever hold about what is already live.

https://t.co/s5ERAD3Ok0

[Hukt @huktfun]

"Hooked by HUKT" is live.

One self-contained SVG, served from https://t.co/teuC7sXzBX in the yard's own palette: a signal lamp, the mark, the fork glyph. The Registry page hands you the Markdown and HTML snippets with copy buttons; the plate drops into a README, a docs page, a site footer.

[Hukt @huktfun]

What it means, precisely: this mint's transfer hook resolves to a known-good listing in the Hook Registry -- the catalogue $HUKT gates, where publishing spends the token and a vouch locks it. What it links to: the check itself, so the plate is only ever as good as the chain says it is.

[Hukt @huktfun]

A builder's plate never says "trust us." It says: serial number, standard, works number. Things you can take to a ledger.

That is the bar for the plate we are about to ship, and it is the bar for everything else in the yard. The Inspector shows accounts, not adjectives. The Registry shows stakes, not stars. The presets say "validates" where lesser copy would say "enforces value transfer," because the hook checks the fee path -- the Token-2022 fee extension or an escrow moves the value.

The open tools stay open: inspecting, building, resolving, reading the registry. The plate will be open too. $HUKT meters the registry those tools feed -- publish spends it, a vouch locks it.

https://t.co/PM2FjhKpoB

[Hukt @huktfun]

Heavy machines carry a builder's plate: who made this, to what standard, bolted where anyone can read it.

Next from HUKT: a plate for mints. If a token's transfer hook resolves to a known-good, attested listing in the registry, the project gets a mark to bolt into its README and its site -- and anyone who sees it can check the claim against the chain in one call.

Not a promise of quality. A pointer to the proof.

Opening soon.

https://t.co/PM2FjhKpoB

[Hukt @huktfun]

The whole reason hooked tokens strand, removed in one call:

const ix = await resolver.buildTransfer({ source, mint, destination, owner, amount, decimals })

The resolver reads the mint, derives the validation PDA, decodes the TLV, and hands back a transfer instruction with every extra account already in place. No account-not-found, no guessing, no copying an account list from a doc that went stale last month.

https://t.co/Ph0S5RPNO5

[Hukt @huktfun]

/3
The cost of that placement is discipline: the hook can check and refuse, nothing more. It cannot reach into balances. HUKT thinks that trade -- absolute coverage for a narrow verb -- is the best deal in token design, and built the whole yard on taking it.

https://t.co/PM2FjhKpoB

[Hukt @huktfun]

/1
Every token rule lives somewhere, and where it lives decides what it is worth.

A rule in a frontend binds whoever uses that frontend. A rule in a marketplace binds whoever stays on that marketplace. A rule in a legal document binds whoever reads it. Each of those has a side exit, and value finds side exits.

[Hukt @huktfun]

/2
A transfer hook is the one placement with no side exit. The token program itself will not finish a transfer without calling Execute, so the rule holds for every wallet, every DEX, every script, every counterparty that has never heard of you. Not because they cooperate -- because the transfer cannot complete otherwise.

[Hukt @huktfun]

https://t.co/ygz6Xc8qjW

[Hukt @huktfun]

A yard you can watch is a yard you can check -- and next, the mints that pass get something to wear, a plate that says so and links to the proof.

https://t.co/xNzjIZufmH

[Hukt @huktfun]

The demonstration yard is open on the landing page.

https://t.co/xNzjIZufmH -- scroll to the yard.

One demonstration mint, three hooks composed on it, every transfer caught. Each lane shows its rule and its signal: proceeds, conditional, halts.

[Hukt @huktfun]

The mint address sits right there with a copy button, so the next stop is the Inspector, where the same hooks resolve from chain data -- not from a marketing table. Everything on the section is labeled demonstration, because honesty about what a number is beats the number.

[Hukt @huktfun]

The switchman clocks in before the light does.

Nobody watches him work. The wagons do not thank him. His whole job is a short list of questions asked of every single car that crests the hump: where are you routed, what are you carrying, are you cleared. Ask, answer, throw the lever, next.

Infrastructure is a personality type. It shows up every dawn, applies the same rule to every wagon, and goes home unphotographed. That is the job description we wrote a framework for.

https://t.co/PM2FjhJRz3

[Hukt @huktfun]

Something is being parked on the landing page.

One demonstration mint, several hooks composed on it, and a lane-by-lane view of what happens when a transfer rolls in: which rule proceeds, which one holds, which one halts. Labeled as a demonstration everywhere, because it is one -- no number on it will pretend to be live traffic.

You will not have to imagine what "every transfer gets caught" looks like. You will scroll to it.

Opening soon.

https://t.co/PM2FjhJRz3