> For the complete documentation index, see [llms.txt](https://leather.gitbook.io/guides/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://leather.gitbook.io/guides/accounts/if-i-have-several-accounts-in-one-wallet-can-anyone-tell-they-are-all-connected-to-the-same-wallet.md). # If I have several accounts in one wallet, can anyone tell they are all connected to the same wallet? If I have several accounts in one wallet, can anyone tell they are all connected to the same wallet? ### Mathematically Fresh addresses are not connected to each other in any publicly known way. From the outside one can not deduce if an account was created by the same wallet (i.e. Secret Key, also know as “seed phrase”) or not. Stacks uses points on an elliptic curve for derived addresses. An interesting video about elliptic curves can be found here: ### From chain analysis Depending on how you fund the wallet or how your accounts interact with each other someone may be able to tell that they are connected. For example, if the first account is used to fund another 9 accounts, on-chain analysis will reveal that they are somehow connected via interaction, although they can’t be definitively linked to the same wallet. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://leather.gitbook.io/guides/accounts/if-i-have-several-accounts-in-one-wallet-can-anyone-tell-they-are-all-connected-to-the-same-wallet.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.