Hooks on a mint, transfer, burn, or setting change can launch a token, swap in a pool, mint from another collection, pay a treasury, or block the action, all in the same transaction. If a side effect fails, the whole action rolls back.
docs.abx.io/docs/using-abx/guides/custom-mechanics
ABX FS puts whole folders onchain, with version history and locks you control. Publish a site, a dapp, or an archive whose files live onchain.
docs.abx.io/docs/using-abx/guides/utilities
Store a program onchain. Every token runs it with its own seed and live settings. It can pair with a physical device too, like a handheld toy whose clicks grow its onchain creature.
docs.abx.io/docs/protocol/code-projects
Give tokens values that holders can change, then decide who changes what: a level that only goes up, or a pass that can’t be sold.
docs.abx.io/docs/protocol/params
Read a pool, a treasury, or a community token, and act on them too.
docs.abx.io/docs/using-abx/guides/ecosystem-integrations
Store, compute, or hash-commit fields, then lock them. Every change leaves a public trail anyone can replay.
docs.abx.io/docs/protocol/metadata
1/1s, series, editions, and code-based work, onchain or off.
docs.abx.io/docs/using-abx/guides/deploy-a-digital-asset
Not listed? Whatever a contract can do onchain, a hook can do. The docs page has patterns, prompts to steal, and the limits to plan around.
docs.abx.io/docs/using-abx/what-you-can-build#prompts-to-steal