2.5k
GitHub Stars
2
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill openclaw/skills --skill hedera- _meta.json269 B
- SKILL.md4.2 KB
Overview
This skill helps developers and operators interact with Hedera: create and fund accounts, send HBAR transactions, manage HTS tokens, and use consensus/file services. It emphasizes Hedera-specific constraints like pre-created accounts, token associations, and memo usage. The guidance is practical for both testnet development and mainnet operations.
How this skill works
The skill inspects account status, required fees, token associations, and key configurations before constructing transactions. It validates account existence, estimates and attaches appropriate HBAR fees, enforces memo limits, and prepares HTS token operations (create, associate, transfer). It can also prepare consensus messages and file service payloads for ordered logging or storage.
When to use it
- Create or fund a new Hedera account for a user or service
- Prepare and send HBAR transfers with correct fees and memo format
- Create, associate, or manage HTS tokens (fungible and NFT)
- Deploy or interact with Solidity contracts that use HTS tokens
- Publish ordered messages via Hedera Consensus Service or store files via Hedera File Service
Best practices
- Always create accounts before sending funds; verify account ID (0.0.xxxxx) exists
- Estimate and include fee buffer; network sets fees and scheduled transactions cost extra
- Require explicit token association before transferring HTS tokens to an account
- Keep memos public and under 100 bytes; never include secrets
- Use multi-key accounts or threshold signatures and rotate keys if compromised
- Test flows on Hedera testnet before mainnet deployment
Example use cases
- Onboard a new user: create account, fund initial HBAR, and return numeric account ID
- Exchange withdraw flow: verify memo format and account existence before transferring HBAR
- Token launch: create an HTS token, require associations, set admin keys for supply control
- Consensus logging: publish ordered application events via HCS for auditability
- Contract + HTS integration: deploy a Solidity contract that mints NFTs and interacts with native tokens
FAQ
No. Hedera accounts must be created on network before they can receive funds. Create and fund the account first or use a wallet/exchange that sponsors creation.
Why did my token transfer fail with TOKEN_NOT_ASSOCIATED?
Recipients must explicitly associate with the token ID before receiving it. Association costs a small HBAR fee to prevent spam.
How long until a Hedera transaction finalizes?
Finality is typically 3–5 seconds thanks to Hashgraph consensus. Mirror nodes provide historical data for audits and queries.