> For the complete documentation index, see [llms.txt](https://sybulls.gitbook.io/about/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sybulls.gitbook.io/about/overview/avoiding-detection.md). # Avoiding Detection ## Randomization At scale, randomization can cause multiple wallets to be flagged for similar activity. This presents a major architecture problem that most current airdrop solutions fail to address. Most current solutions follow a strict on-chain pattern that fails to provide the user with adequate randomization and distinct transaction paths. Using previous airdrop experience and fully randomized activity generation each users wallet will produce a completely unique footprint on-chain from funding to completion. ## Creating a footprint Undoubtedly the most tasking and difficult portion of a sybil wallet journey is securing funds without connecting with other wallets or contracts. Sybulls gives users the ability to consistently build their on-chain presence across multiple chains creating a more human action list. By constantly being able increase nonce, and add unique contracts, Sybull users have an immediate edge in the airdrop farming category. ## Repetitive Behavior As previously seen with $ARB, consistency is a major milestone in the airdrop world. By granting users the quick ability to increase their activity across chains and wallets without hassle allows for users to interact more often, more naturally, and most importantly more consistently on their target products. --- # 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://sybulls.gitbook.io/about/overview/avoiding-detection.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.