> For the complete documentation index, see [llms.txt](https://polykopy.gitbook.io/polykopy-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://polykopy.gitbook.io/polykopy-docs/ecosystem/referrals.md). # Referrals ### Share the Edge. Get Rewarded. PolyKopy grows strongest when smart users bring in other smart users. That is what the referral program is built for. If PolyKopy helps you discover stronger wallets, run cleaner copy setups, and trade smarter, sharing it with others should be worth something too. The idea is simple: * you share your referral link * new users join through you * the ecosystem grows * you may earn rewards tied to participation or future referral incentives A strong product should reward real growth. *** ### Why Referrals Matter The best users often know other users who would benefit from PolyKopy: * Polymarket traders * users manually tracking wallets all day * people tired of guessing who to follow * users using weaker copy bots * Telegram-native traders * users who want more structure and better signal That makes referrals natural. You are not forcing something random. You are sharing a tool with people who actually need it. *** ### What Makes a Good Referral The best referrals are not spam. They are people who already fit the product. Great fits usually include users who: * already trade Polymarket * understand wallet following * want automation with control * value speed and Telegram workflow * care about better decision-making * are serious enough to actually use the product Quality referrals beat random volume every time. *** ### Why Some Users Win Big With Referrals Users who do well with referrals usually do one thing right: they explain the real value clearly. Instead of saying: “Join this bot.” They say: * AI finds better wallets to follow * Copy trading with limits and protection * Telegram-native workflow * Smarter than blind copying * Easier than manually hunting wallets all day That message converts because it is real. *** ### Smart Ways to Share PolyKopy #### Direct Friends in Polymarket People already active in prediction markets are obvious fits. #### Trading Communities If allowed and relevant, share in places where users already discuss wallets, edge, or Polymarket. #### Social Content Post real insights about copy trading, wallet discovery, and why blind copying is broken. #### Private Network Some of the best referrals come quietly through trusted circles. *** ### What Not to Do Do not spam random groups.\ Do not mislead people.\ Do not promise guaranteed profits.\ Do not oversell what the product is.\ Do not fake urgency. That hurts trust and attracts low-quality users. *** ### Long-Term Referral Value Strong ecosystems reward early believers. As PolyKopy grows, referral incentives may evolve through: * direct rewards * discounts * loyalty perks * access benefits * ecosystem advantages * future campaign incentives Always follow official announcements for current details. *** ### Best Referral Mindset Share PolyKopy with people who should genuinely be using it. That keeps the community sharper, the product stronger, and the ecosystem healthier. > **Good users bring good users. Everyone wins.** --- # 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: ``` GET https://polykopy.gitbook.io/polykopy-docs/ecosystem/referrals.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.