> For the complete documentation index, see [llms.txt](https://kkone.gitbook.io/kkone-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kkone.gitbook.io/kkone-docs/automation-and-records/records-and-account.md). # Records and Account ## Records Records is the signed-in activity history for task, launch, transfer, claim, and Auto Sell events. Each onchain record identifies available details such as: * action type; * network; * Wallet Group or wallet source; * token contract when relevant; * current status and timestamps; * transaction hash and explorer link when available; * a plain-language failure or delay reason when known. Base and Robinhood Chain records remain separate even if the same Wallet Group EVM address is used on both. ### Submitted is not confirmed A submitted transaction has been broadcast or accepted by an upstream service, but it may still be pending, replaced, reverted, dropped, or delayed. Treat an action as final only after the interface and the relevant network show a confirmed result. ### Partial success A multi-network launch group can contain both successful and unsuccessful deployments. Records preserves each network result, and a retry targets the failed network without recreating a token already confirmed on another network. ### Before retrying an unknown transaction 1. Reopen the record. 2. Check the transaction hash if one is available. 3. Open the correct network explorer. 4. Wait for the product's retry action or a final failure state. Do not create a duplicate action merely because an indexer or page is slow. ## Account Account contains profile, notification, and login-method settings. Available fields can depend on the authentication method and release configuration. Narrative analysis is currently free during beta. ## Notifications Notifications can include operational events such as task status, funding issues, transaction updates, claims, Auto Sell execution, and security or service notices. Notification delivery can be delayed and is not a substitute for reviewing the live product and network explorer. ## Help and security * General support: * Legal: * Privacy: * Security: * Official X account: [@kkdotone](https://x.com/kkdotone) KK.one will not ask for your private key, seed phrase, login verification code, or session token. Be suspicious of unsolicited direct messages, lookalike domains, and requests to install unknown wallet software. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://kkone.gitbook.io/kkone-docs/automation-and-records/records-and-account.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.