Manage Kaia account keys and decouple private keys from addresses.
npx skills add https://github.com/Pieverse-Eng/purrfect-skills --skill accounts
Please help me install this Agent Skill. Skill: accounts Source: https://github.com/Pieverse-Eng/purrfect-skills/tree/main/kaia-skills/vendor/accounts Command: npx skills add https://github.com/Pieverse-Eng/purrfect-skills --skill accounts
Kaia separates private keys from addresses, creating complexity for developers and wallet operators who need to perform key rotation, role-based access, and protocol-level multi-signature management without losing address continuity. This Skill explains the account model and how to safely create, update, and freeze keys so teams can reduce compromise risk and implement delegated fee payments.
Create and send a TxTypeAccountUpdate transaction specifying the new AccountKeyPublic value and the target address to rotate the account's signing key.
High-intent search queries and answers about installing and using this skill.
Kaia key rotation uses TxTypeAccountUpdate transactions to decouple private keys from addresses. You can update the AccountKeyPublic value for your target address, allowing you to rotate compromised signing keys while maintaining address continuity.
Kaia supports six AccountKey types: AccountKeyNil, AccountKeyLegacy, AccountKeyPublic, AccountKeyFail, AccountKeyWeightedMultiSig, and AccountKeyRoleBased. Each type serves specific security requirements, from single-key management to complex multi-signature setups.
Kaia role-based keys assign separate permissions for RoleTransaction, RoleAccountUpdate, and RoleFeePayer activities. This allows you to delegate fee payments and restrict sensitive account updates while letting a single key handle daily transactions.
Yes, you can use AccountKeyRoleBased to apply a weighted multi-sig requirement for RoleAccountUpdate while retaining a single AccountKeyPublic for RoleTransaction. This secures sensitive operations without complicating daily transaction signing.
Yes, you need wallets or libraries that support Kaia-specific transaction fields to construct TxTypeAccountUpdate transactions. Standard blockchain wallets lack the required fields to handle Kaia's decoupled account key model.
You should use AccountKeyFail when you need to freeze a Kaia account and prevent all future transactions. Applying it via an account update effectively disables the account's signing capabilities without destroying the address.
blueskies1818Query EVM blockchain data across 8 chains using Python standard libraries.
aviral10xBroadcast pre-signed on-chain transactions and estimate gas across multiple networks.
Pieverse-EngCreate two-signature Kaia transactions with full or partial fee delegation.
Pieverse-EngClassify Kaia transactions and explain validation and fee delegation requirements.
