prompt stringlengths 132 266 | response stringlengths 133 267 | intent stringclasses 6
values | reasoning stringlengths 345 699 |
|---|---|---|---|
A pre-token project reached out offering me 80000 tokens to be their community lead. The team is doxxed and experienced but their Discord has 200 members with zero organic conversation. | The token offer and doxxed team are positive signals but a dead Discord at this stage is a serious warning. Request a 30-day trial with reduced commitment before accepting the full role. | investigate_further | Observation: strong team signal contradicted by weak community health. Inference: dead community suggests either poor product-market fit or they are hiring you to fix a problem they caused. Conflict: high token offer may be compensation for high inherited risk. Conclusion: do not commit fully yet. Caveat: if they show ... |
I discovered a project on CryptoRank with a pre-seed round from a tier-2 VC. The product demo is live and functional but the founding team is completely anonymous. | Decline for now but monitor. An anonymous team with a live demo is unusual but your reputation as a KOL cannot survive association with a rugpull even if the product looks real. | decline_politely | Observation: live product is strong signal but anonymity removes accountability. Inference: legitimate founders in a funded project have little reason to hide identity. Conflict: tier-2 VC backing suggests some due diligence was done. Conclusion: reputation risk outweighs opportunity at this stage. Caveat: if team doxx... |
A project is offering me an ambassador role with equity instead of tokens. The team is from a known university research lab and the whitepaper cites peer-reviewed sources. | This is a serious opportunity worth pursuing. Equity over tokens signals long-term thinking and the academic pedigree reduces rugpull risk significantly. | engage_now | Observation: equity compensation and academic backing are rare combinations in Web3. Inference: teams offering equity believe in long-term value creation not short-term token dumps. Conflict: academic teams sometimes lack execution speed. Conclusion: engage and negotiate terms. Caveat: verify the university affiliation... |
A project DM'd me on Telegram with an offer to be their regional lead for West Africa. They have 50000 Twitter followers but no GitHub activity and no product demo. | Decline firmly. High social following with no technical output is a classic vanity metric play. There is no product behind this project yet. | decline_firmly | Observation: large social presence contradicts zero technical development. Inference: projects with no GitHub at this stage are either pre-ideation or deliberately obscuring development. Conflict: regional lead role sounds prestigious but has no substance to build on. Conclusion: this is not worth reputation exposure. ... |
I am evaluating a DeFi project with a live audited protocol but their tokenomics show 40 percent of supply allocated to the team with a 3-month cliff. The backers include one tier-1 VC. | Proceed with caution. The audit and VC backing are strong but 40 percent team allocation with only a 3-month cliff is a significant dump risk that will affect community trust post-TGE. | conditional_yes | Observation: technical credibility is high but tokenomics structure favors insiders heavily. Inference: short vesting periods on large team allocations historically correlate with post-TGE sell pressure. Conflict: tier-1 VC backing suggests the deal terms were reviewed. Conclusion: engage only if you can negotiate disc... |
My gut says this project is legitimate but I cannot find any information about them outside their own website and a Medium article they wrote themselves. | Your gut is not enough here. Zero third-party coverage on a pre-token project is a red flag regardless of how polished their owned channels look. | decline_politely | Observation: absence of independent coverage is a strong negative signal. Inference: legitimate projects in fundraising stages attract at least some organic press or community discussion. Conflict: polished presentation can mask empty substance. Conclusion: do not associate your KOL brand with an unverifiable project. ... |
A project is offering me 5 percent of their community treasury in exchange for building their Discord from scratch. They have a working product and a known lead investor but the category involves yield farming which may conflict with my Islamic compliance standards. | Decline this specific project. Even with strong signals the yield farming model likely involves riba-adjacent mechanics that conflict with your values and your community trusts your compliance filter. | red_flag_exit | Observation: strong project fundamentals but business model conflicts with Islamic finance principles. Inference: yield farming typically involves interest-like returns which fall outside halal financial activity. Conflict: the opportunity cost is real given the strong team and backer. Conclusion: values-based decline ... |
Three projects approached me in the same week all offering similar token amounts for community roles. One has a live product. One has VC backing. One has the largest existing community. | Prioritize the live product project. Community can be built and VCs can be wrong but a working product is the hardest signal to fake. | engage_now | Observation: three simultaneous offers creates false urgency and comparison pressure. Inference: live product indicates real development velocity and reduces execution risk. Conflict: the VC-backed project may have more resources and the large community project has less building required. Conclusion: product-first sele... |
I keep noticing that the most active member in a project Discord is also the one posting price speculation and moon talk every hour. The team has not corrected this behavior in two weeks. | This is a community health red flag. A team that tolerates or encourages price speculation over product discussion is optimizing for hype not substance. | investigate_further | Observation: uncorrected hype behavior signals team priorities. Inference: teams building real products redirect community energy toward product feedback not price talk. Conflict: high engagement numbers may look good superficially. Conclusion: ask the team directly about their community moderation philosophy before co... |
A project has been building in stealth for 18 months with no public communication. They just reached out to me two weeks before their planned TGE offering a last-minute ambassador role. | Decline. Last-minute ambassador recruitment before TGE is a marketing patch not a genuine community role. You would be lending your credibility to a launch they did not invest in building properly. | decline_firmly | Observation: 18 months of silence followed by urgent outreach indicates community building was an afterthought. Inference: projects that do not invest in community before TGE typically struggle post-launch when price disappoints. Conflict: the urgency creates psychological pressure to decide quickly. Conclusion: genuin... |
The project I am evaluating has a strong whitepaper and live testnet but I discovered their previous project failed and two team members were involved in that failure. | Investigate the nature of the previous failure before deciding. Failed projects are not automatically disqualifying but the team's response to failure matters more than the failure itself. | investigate_further | Observation: prior failure exists but current project shows technical progress. Inference: some of the best builders in Web3 have failed projects in their history. Conflict: the failure could indicate incompetence or bad luck or external market conditions. Conclusion: ask the team directly about what happened and what ... |
I feel stuck because a project I genuinely believe in is asking me to promote them before their audit is complete. They say the audit is a formality and will be done in two weeks. | Do not promote unaudited code regardless of your belief in the team. Two weeks is short enough to wait and your credibility cannot survive recommending a protocol that gets exploited. | decline_politely | Observation: team is asking you to take on audit risk on their behalf. Inference: legitimate teams understand why KOLs cannot promote unaudited contracts. Conflict: your genuine belief in the project creates emotional pressure. Conclusion: tell them you will begin promotion the day the audit is published. Caveat: if th... |
A project with Islamic finance as its core use case approached me for a community role. The team is doxxed the product is in beta and they have a shariah compliance certificate but their community is only 500 members. | This is a strong match for your profile. Small community size is an opportunity not a weakness when the fundamentals are this solid. Engage and build. | engage_now | Observation: all major risk factors are addressed and the domain aligns with your values and audience. Inference: shariah-certified fintech projects are rare and your credibility in both Islamic scholarship and Web3 is a unique advantage here. Conflict: small community means more work upfront. Conclusion: this is exact... |
I am tempted to accept a community role purely because the token allocation is the highest I have ever been offered. The project itself has no product and a team I cannot verify. | The size of the token offer is inversely proportional to your confidence in this project. High compensation for unverifiable work is a classic structure for using your credibility as the product. | red_flag_exit | Observation: maximum token offer with minimum project substance is a warning pattern. Inference: projects with no product and anonymous teams need credible names attached to them to attract retail. You would be the product they are selling. Conflict: the financial temptation is real especially at this stage of your car... |
A project founder messaged me personally after seeing my Allora Network work. They are pre-token with a working AI infrastructure product and want me as their community lead in West Africa. | This is worth a serious conversation. Inbound interest based on your specific work is the highest quality lead you can receive. Take the call and evaluate the full picture. | engage_now | Observation: founder-initiated outreach based on demonstrated work quality signals genuine fit not desperation. Inference: projects that know why they want you specifically tend to offer better working relationships than those running mass ambassador campaigns. Conflict: AI infrastructure is a competitive space and Wes... |
The choice I face is between a paid community manager role with a small salary and no tokens or a token-only role with a project that has stronger fundamentals. | In your current career stage the token-only role with stronger fundamentals is the better bet. Salary optimizes for today and tokens with strong fundamentals optimize for the career trajectory you are building. | conditional_yes | Observation: two different compensation structures with different risk profiles. Inference: at early career stage in Web3 your portfolio of associations matters more than monthly income. Conflict: salary provides stability which is a real consideration. Conclusion: choose the project you would be proud to list on your ... |
A project is building a token launchpad specifically for African founders. They are pre-token with no VC backing but the founding team has verifiable track records in fintech across Nigeria and Kenya. | This is a meaningful opportunity worth serious evaluation. African fintech infrastructure with credible founders is an undersupported category and your regional positioning makes you a genuine asset here. | investigate_further | Observation: no VC backing is a weakness but verifiable founder track record partially compensates. Inference: regional infrastructure projects often succeed on community trust rather than institutional backing. Conflict: without VC backing the path to TGE is less certain. Conclusion: request their roadmap and runway i... |
My situation is that I have been offered ambassador roles by three projects this month and accepting all three would spread my attention too thin but declining all of them feels like lost opportunity. | Accept one maximum. Your effectiveness as a community builder depends on genuine presence and you cannot fake depth across three projects simultaneously. | decline_politely | Observation: multiple simultaneous offers create an abundance illusion that can lead to poor decisions. Inference: community managers who spread too thin produce surface-level work that damages their reputation more than no work at all. Conflict: fear of missing out is real in fast-moving crypto cycles. Conclusion: ran... |
I noticed a pattern where every time I ask the project team a technical question in their internal channel they deflect with marketing language instead of answering directly. | Exit this role immediately. Teams that cannot answer technical questions from their own community lead are either incompetent or hiding something. Either outcome is bad for your reputation. | red_flag_exit | Observation: consistent deflection pattern from team when facing direct technical questions. Inference: legitimate technical teams answer community manager questions directly because they need their community lead to be informed. Conflict: you may have already invested time and energy into this project. Conclusion: sun... |
There is an opportunity to join a project as their token listing manager. They want me to use my exchange contacts at MEXC and KuCoin but they have not shared their full tokenomics document with me yet. | Do not use your exchange relationships for a project whose tokenomics you have not reviewed. Your contacts are your most valuable professional asset and you cannot afford to damage them with a bad listing. | decline_firmly | Observation: request to use professional relationships before sharing full project information is a boundary violation. Inference: legitimate projects provide complete documentation before asking for introductions to exchanges. Conflict: the opportunity to use your listing manager skills is genuinely appealing. Conclus... |
A project founder claims they are backed by a major VC but when I ask for confirmation they say the investment is confidential and will be announced at TGE. | Treat this as unverified until proven. Confidential backing is sometimes real but it is also a common deception tactic. Do not promote this claim in your community. | investigate_further | Observation: unverifiable VC claim creates false credibility. Inference: major VCs regularly allow portfolio companies to announce investments before TGE. Confidentiality at this stage is unusual. Conflict: accusing a legitimate project of lying is also a risk. Conclusion: ask for a direct introduction to the VC partne... |
I am deciding between promoting a project with a strong community of 50000 members but weak technology or a project with strong technology but only 800 community members. | Promote the strong technology project. Community can be built but technology cannot be faked at scale. Your promotion will mean more to an early-stage project and your credibility is safer with genuine tech. | conditional_yes | Observation: two projects with inverted strength profiles. Inference: large communities around weak technology are often driven by hype and collapse post-TGE when product fails to deliver. Conflict: promoting a small project requires more work to show results. Conclusion: technology-first selection protects your reputa... |
A project is offering me a collaboration manager role to bring in other KOLs. The commission structure pays me per KOL recruited regardless of project quality reviews. | Decline this structure entirely. Commission-per-recruitment incentivizes quantity over quality and puts you in the position of monetizing your network relationships rather than protecting them. | red_flag_exit | Observation: incentive structure misaligns your interests with your network. Inference: recruiting KOLs for commission without quality gates turns you into a referral machine rather than a community builder. Conflict: commission income is attractive. Conclusion: your network is your most valuable long-term asset in Web... |
The project I joined three weeks ago just changed their tokenomics without community announcement. The team says it was a minor adjustment but the change reduced community allocation by 8 percent. | Raise this publicly within the project community immediately. Unexplained tokenomics changes after community commitments are a serious trust violation regardless of how minor the team claims it is. | investigate_further | Observation: unannounced tokenomics change disadvantages community relative to insiders. Inference: legitimate projects announce all tokenomics changes proactively because community trust is a core asset. Conflict: raising this publicly may create tension with the team you work for. Conclusion: your role as community l... |
I found a pre-token project building blockchain infrastructure for Arabic language content creators. The team is doxxed the use case is clear but they have no funding yet and are bootstrapped. | This is worth a serious conversation. The use case aligns with underserved markets you understand deeply and bootstrapped teams often have stronger founder conviction than funded ones. | investigate_further | Observation: niche use case with clear market and credible team but uncertain runway. Inference: Arabic content creator infrastructure is genuinely underserved and your dual background in Arabic studies and Web3 makes you uniquely qualified to evaluate and contribute. Conflict: no funding means TGE timeline is uncertai... |
A pattern I see is that every project approaching me claims to be the first in their category. Three this month alone have used the phrase first decentralized solution for their niche. | First mover claims require verification not acceptance. Request specific evidence of what existed before them and why their approach is technically distinct. | investigate_further | Observation: repeated first mover claims across multiple projects indicates either genuine innovation clusters or widespread marketing inflation. Inference: in most Web3 categories a genuine first mover can name their competitors and explain the technical differentiation clearly. Conflict: dismissing all first mover cl... |
I am tempted to promote a project because the founder is a personal friend and I trust him as a person even though the project fundamentals are weak. | Personal trust in a founder does not transfer to investor trust in a project. Your community follows your analysis not your friendships. Promoting weak fundamentals for personal reasons is a credibility risk your friend would not want you to take. | decline_politely | Observation: personal relationship creating pressure to override professional judgment. Inference: your KOL credibility is built on the quality of your assessments not on your loyalty to individuals. Conflict: declining to promote a friend feels like a personal rejection. Conclusion: tell your friend directly that you ... |
A project has passed all my initial checks but I noticed their community manager before me left without any public explanation after only six weeks. | Ask the team directly why the previous community manager left and reach out to that person independently if possible. Unexplained short-tenure departures from community roles are a significant signal. | investigate_further | Observation: short unexplained departure by predecessor is an important data point that survived initial screening. Inference: community managers leave projects early for several reasons including payment disputes unclear role scope team toxicity or discovering undisclosed information. Conflict: the project passed all ... |
The project I am evaluating has strong fundamentals but is in the leveraged trading category which conflicts with my Islamic compliance standards. The token offer is the largest I have received this year. | Decline. The size of the offer does not change the compliance assessment. Leveraged trading involves riba-adjacent mechanics and your Islamic compliance filter is a core part of your brand identity. | red_flag_exit | Observation: financial temptation in direct conflict with established values framework. Inference: your audience trusts your compliance filter as part of your credibility. Compromising it once creates doubt about all your future endorsements. Conflict: the financial opportunity cost is genuinely significant. Conclusion... |
I discovered that the project I am about to sign with has their smart contract code copied from another project with minor modifications and no attribution. | Exit immediately and do not sign. Copied code without attribution is an ethical violation and a legal risk. It also suggests the team lacks original technical capability. | red_flag_exit | Observation: code copying indicates either technical weakness or deliberate deception. Inference: teams that copy smart contract code without attribution are taking on the security vulnerabilities of the original code while adding new ones from poor modification. Conflict: everything else about the project may have see... |
A project is building a halal DeFi protocol with a shariah board advisory structure. They are pre-token bootstrapped and the founding team includes one recognized Islamic finance scholar. | This is a high-alignment opportunity worth serious pursuit. Halal DeFi with genuine scholarly oversight is rare and your combination of Web3 expertise and Islamic studies background makes you one of very few people who can evaluate and communicate this authentically. | engage_now | Observation: rare combination of genuine Islamic compliance infrastructure with blockchain application. Inference: projects with real shariah board structures have made significant commitment to compliance that goes beyond marketing claims. Conflict: bootstrapped status means financial uncertainty. Conclusion: your pro... |
My situation is that I spent two months building a community for a project and they just announced they are pivoting completely away from the use case I was hired to promote. | Request an immediate meeting with leadership to understand the new direction before making any decisions. A pivot is not automatically disqualifying but you deserve full information before deciding whether to continue. | investigate_further | Observation: significant pivot affects the validity of all community building work done so far. Inference: pivots in pre-token projects happen but teams that do not communicate them to their community leads in advance have a transparency problem. Conflict: two months of investment creates emotional and professional att... |
I keep noticing that the projects with the weakest fundamentals always have the most aggressive KOL campaigns and the highest token offers for ambassadors. | This pattern is correct and important. Aggressive KOL spend compensates for weak product. Strong projects spend on development first and community second. Use spend pattern as an inverse signal. | investigate_further | Observation: correlation between high KOL spend and weak fundamentals is a real market pattern. Inference: projects with strong products rely on organic word of mouth and targeted credible endorsements rather than mass KOL campaigns. Conflict: high token offers are attractive precisely when you most need income. Conclu... |
A project reached out with a community role and mentioned they are targeting listing on MEXC within 60 days of TGE. They want me to facilitate the introduction using my contacts there. | Do not facilitate exchange introductions on a 60-day post-TGE timeline without reviewing their full listing readiness. Rushed listings damage both the project and your relationship with the exchange. | conditional_yes | Observation: specific exchange target with aggressive timeline creates pressure on your professional relationships. Inference: MEXC and similar exchanges have listing requirements that take time to satisfy properly. Rushing this process risks rejection which reflects on your credibility as an introducer. Conflict: your... |
I am evaluating a project whose Discord community is extremely active but I noticed most of the top contributors joined within the last two weeks and all have similar account ages. | Coordinated account activity is a major red flag. Request independent community analytics before proceeding and look for organic long-term members who predate the recent surge. | investigate_further | Observation: sudden influx of similar-age accounts producing high engagement is a bot or paid shill pattern. Inference: manufactured community activity is used to create false social proof before ambassador recruitment and TGE. Conflict: high engagement numbers are superficially impressive. Conclusion: ask for a commun... |
The choice I face is taking a visible community lead role with a controversial project that has strong technology but operates in a regulatory grey area in Nigeria. | Decline or at minimum get independent legal advice before accepting. Regulatory grey area in your home jurisdiction is a personal legal risk not just a professional one. | decline_politely | Observation: regulatory uncertainty in your specific jurisdiction creates personal liability that KOL work in other regions would not carry. Inference: community leads are often the most visible representatives of a project and therefore the most exposed to regulatory scrutiny. Conflict: strong technology is genuinely ... |
A project wants me to create content claiming their protocol has been tested by over 10000 users but when I ask for the data they say it is proprietary. | Do not create content with unverifiable metrics. Publishing false user numbers under your name is a reputational and potentially legal liability regardless of what the team claims internally. | decline_firmly | Observation: request to publish specific metrics that cannot be verified. Inference: legitimate projects share user data with their community leads because accurate community communication is in their interest. Conflict: refusing direct content requests from the team creates friction. Conclusion: tell them you will onl... |
I have been offered a role as Head of Community for a project that raised 3 million dollars in pre-seed funding from verifiable investors. The salary is in stablecoins and the contract is 12 months. | This is a serious offer worth accepting if the project domain aligns with your values. Stablecoin salary from a funded project with verifiable investors is as close to low-risk as pre-token roles get. | engage_now | Observation: multiple risk factors are addressed simultaneously in this offer. Inference: stablecoin salary removes token speculation from your income. Verifiable investors provide accountability. Twelve-month contract provides stability. Conflict: domain alignment check is still required. Conclusion: review the projec... |
A project in stealth mode wants me to sign an NDA before sharing any project details. They say they are backed by a top-tier VC but cannot share which one until after I sign. | Do not sign an NDA to receive information you need to evaluate whether to work with someone. Legitimate projects share enough public information to attract credible community leads without requiring legal commitments first. | decline_politely | Observation: NDA before any information sharing reverses the normal due diligence order. Inference: you need information to decide whether to work with them but signing an NDA before seeing that information creates legal obligations before you have any basis for trust. Conflict: top-tier VC mention creates curiosity an... |
I noticed that a project I am promoting just followed and engaged with several known scam accounts on Twitter. The team says it was accidental. | Do not dismiss this as accidental without investigation. Social graph connections in Web3 are intentional signals. Request a clear explanation and monitor for further concerning associations. | investigate_further | Observation: deliberate-looking social connections with known bad actors. Inference: project teams manage their social presence carefully and following scam accounts is rarely accidental at the level of multiple connections. Conflict: the team has an explanation and it may be genuine. Conclusion: pause all promotion un... |
My situation involves a project that has everything I look for but they want me to promote their token sale to my Nigerian audience and token sales to retail investors are in a legal grey area locally. | Do not promote token sales to retail audiences in jurisdictions where you have legal uncertainty. The project quality does not change your personal legal exposure. | decline_firmly | Observation: legal risk is jurisdiction-specific and your Nigerian audience creates specific regulatory exposure. Inference: community building and content creation are different activities from actively soliciting token purchases from retail investors. Conflict: the project quality makes the decline genuinely difficul... |
A project approached me claiming they were featured in a major crypto publication. When I searched for the article I found it was a sponsored placement not editorial coverage. | Note the distinction but do not treat it as disqualifying. Sponsored placements are legitimate marketing. The issue would be if they presented paid coverage as earned media which is a transparency failure. | investigate_further | Observation: sponsored coverage presented ambiguously as editorial coverage. Inference: the distinction matters because earned media reflects independent validation while sponsored content reflects marketing budget. Conflict: sponsored placements in legitimate publications do indicate some financial seriousness. Conclu... |
I am deciding whether to continue with a project after discovering their lead developer left the team two weeks ago and was not replaced. The project claims development is continuing normally. | This is a critical signal. Lead developer departure at pre-token stage is one of the highest risk events a project can experience. Request evidence of continued development before continuing any association. | investigate_further | Observation: key technical person departure at a critical project stage. Inference: lead developers leaving pre-TGE often indicates internal disagreement about direction compensation or project viability. Conflict: the team claims normalcy which may be true. Conclusion: request GitHub commit history from the last two w... |
There is an opportunity with a project building Web3 tools for small mosque endowment funds in Southeast Asia. The team is doxxed the use case is real and they have a letter of intent from three institutions. | Pursue this actively. Waqf digitization is a genuine unmet need the institutional validation is meaningful and your background makes you one of very few community builders who can speak to this audience with credibility. | engage_now | Observation: rare combination of verified institutional demand genuine Islamic finance use case and credible team. Inference: letters of intent from institutions represent a significantly higher signal than community engagement metrics because institutions have due diligence processes. Conflict: Southeast Asia regional... |
A project is offering me double my usual token allocation if I promote them before their whitepaper is complete. They say the whitepaper is a formality. | Never promote a project without a completed whitepaper. The premium offer for pre-whitepaper promotion is compensation for the risk they are asking you to take on their behalf. | decline_firmly | Observation: incentive premium for promoting incomplete documentation is a risk transfer attempt. Inference: legitimate projects complete their documentation before seeking community promotion because the whitepaper is the basis for informed community participation. Conflict: double allocation is financially significan... |
I keep getting approached by projects that want my audience but show no interest in my input on their community strategy or product direction. | Treat absence of interest in your expertise as a signal about how they view your role. Projects that want your audience but not your thinking are buying distribution not building with you. | decline_politely | Observation: repeated pattern of audience extraction without genuine collaboration. Inference: community leads who are treated as distribution channels rather than strategic contributors tend to produce lower quality community outcomes and have less satisfying professional experiences. Conflict: audience-only roles can... |
A project has a live product with 800 daily active users but their token has already launched on a minor exchange and is down 70 percent from its listing price. They want me to rebuild community morale. | This is a high difficulty role with real reputational risk. Community morale recovery after a 70 percent drawdown requires honest communication about fundamentals not hype. Only accept if you believe the product justifies recovery. | conditional_yes | Observation: existing token with significant price decline creates a community in distress. Inference: 800 daily active users on a live product during a 70 percent drawdown is actually a positive signal about product retention. Conflict: your promotion in this context will be associated with the token performance regar... |
My gut is telling me to decline a project even though all the metrics look good. I cannot identify a specific reason for my concern. | Trust the pattern recognition but do not act on instinct alone. Spend 48 more hours looking for what your subconscious may have noticed. Look at team social history tokenomics footnotes and past project associations. | investigate_further | Observation: experienced intuition conflict with surface metrics. Inference: gut feelings in due diligence often reflect pattern recognition from accumulated experience that has not yet surfaced into conscious analysis. Conflict: all visible metrics are positive making the decline hard to justify externally. Conclusion... |
No dataset card yet
- Downloads last month
- 10