Create crypto-funded social bounties.
Earn crypto for community engagement.

Community Engagement Centre (CEC) connects creators who fund social and community tasks with bounty hunters who earn supported cryptocurrencies for approved claims. Projects and communities can also use its reward tools. Start with the creator guide or the hunter guide.

Open the CEC Telegram bot, start it, and follow the account and balance setup shown there. Link a social account when a task requires it. Discord flows are available in communities where CEC is enabled. Creators can also use the web order form without starting in a bot.

Follow the current bot prompts for any account, identity, or eligibility requirements that apply to you.

X/Twitter and Bluesky campaigns cover follows, likes, retweets/reposts, quotes, replies, and original posts. The web form supports X/Twitter and Bluesky. Telegram group-join and LinkedIn connection bounties use the Telegram bot. Task availability and verification depend on the platform and current configuration.

Telegram and Discord also offer community reward tools such as tips, rain, and flood where enabled. These are separate from externally verified social tasks.

Browse live crypto bounties here or the bounty lists in the CEC Telegram bot. Review the action, target, reward per approved claim, and remaining slots before acting. A website listing does not reserve a slot; availability can change before you claim.

No. Hunter rewards depend on task availability, eligibility, remaining slots, and claim approval. Campaigns fund specified tasks; they do not guarantee followers, conversions, price changes, or future engagement. A supported asset can change in value.

Contact CEC support, the CEC Telegram group, or the CEC Discord server. Include the bounty/order reference and the error you saw, while keeping private account and wallet information out of public chats.

Check the CEC announcement channel for updates and About CEC for dated project history.

Linking helps CEC verify that the hunter claiming a bounty completed its task. Use the same account you linked, the exact target post or profile, and the action specified in the bounty. Link only the accounts required for the tasks you choose.

Read the bounty instructions, complete the action on the specified target, then use its claim action in the bot. Completing an action alone does not submit a claim. Simple actions can be verified automatically; replies, quotes, and original posts require the URL of the content you created.

Follow the bounty's content guidance, including any required tags or context. Submit your own relevant content and its URL when requested. Generic, spammy, hostile, or off-topic submissions may fail the content checks or review.

Check the linked account, original target, required action, content instructions, and whether you already claimed that task. A recent action may take time to appear through the social platform's API. Wait and retry as directed by the bot; repeated clicking does not speed up verification.

If manual review is offered, provide clear evidence showing the account, action, target, and relevant time/context. Contact support if the problem continues.

CEC credits rewards to your bot balance after a claim is approved. Simple tasks may verify quickly. Creative or inconclusive tasks can require evidence and manual review, so approval is not always immediate. No fixed review time is promised here; follow the status and instructions in the bot.

A shared message can group several tasks for one post. Each task has its own slots, reward, verification, and payout. A shared claim action can process automatically verifiable likes and retweets/reposts; replies still require your created-reply URL. A displayed total for completing all tasks is not one combined automatic payment, and the same task cannot be paid twice to the same hunter.

Referral rewards may be available where the program is enabled. Check the bot for current eligibility, qualifying activity, and reward settings before inviting others. Historical announcements do not establish today's percentages or entitlement to a payout.

Use the web order form for guided X/Twitter or Bluesky setup, or the CEC Telegram bot for wider self-service options. Discord supports configured campaign flows. Select a task and target, reward coin and amount, and participant count, then review the overview before submitting and funding.

Reserved rewards = reward per participant × participant count. For example, 100 slots at 2 units each reserve 200 units of the selected reward coin, plus the displayed creation fee. The reward coin pays hunters; a separate fee coin may be needed for creation fees. Review both balances before launch.

The creation flow shows an overview before confirmation. Fees can depend on the task, participant count, selected reward/fee coins, and applicable discounts. Use the amount displayed for your actual campaign; there is no universal fee or discount percentage promised here.

No. A submitted web order can be awaiting payment. Funding must be confirmed before the bounty becomes available. Follow the payment instructions and track status through the bot or email updates for your launch path. Contact support with your order reference if payment or status needs investigation.

A campaign can be cancelled before completion. CEC completes pending payouts first, then credits remaining campaign funds to the creator's bot balance. It does not automatically return them to the original funding address, and pending or completed payouts are not reversed.

Bot-account refunds are automated. Creators with only an email-linked account, including most web-form orders, will likely need CEC support for assisted processing.

Where enabled, configure automation through Telegram for an X/Twitter or Bluesky account. Choose posts, replies, or both; an optional activation keyword; separate participant counts for likes, retweets/reposts, and replies; a reward amount and coin; and a fee coin. A zero participant count disables that task.

Matching posts create supported tasks only while there are sufficient reward and fee balances. Keep those balances funded and check any insufficient-funds notifications. Discord may display and claim generated bounties; this does not imply the same automation setup is available there.

CEC can validate targets, check linked-account actions, prevent duplicate claims, and review content where supported. Creative or inconclusive claims may go to manual review before rewards are credited. These checks reduce invalid claims; they do not guarantee fraud-free participation or campaign outcomes.

Check the supported currencies list for currently configured assets and networks. CEC can support Bitcoin-like chains, EVM-compatible coins/tokens, Omni/XEP-style assets, and Solana/SPL-style assets, but historical integration announcements do not establish current availability. Confirm the selected asset's deposit and withdrawal instructions in the bot.

No. CEC tracks campaign funds and approved rewards in a platform balance for each coin/token. An approved claim credits that balance; it does not send an on-chain transaction to your personal wallet. Use the bot's withdrawal flow to transfer available funds to an external wallet.

Use the deposit instructions for the exact coin and network selected in the bot. Confirm the address, any required wallet binding, and current asset availability before sending. Assets with similar names or tickers can use different networks; do not assume they are interchangeable. Ask support if the instructions are unclear.

EVM deposit flows can require you to bind a wallet you control. Open the bot's /bind help, sign the displayed user-specific message with your wallet using the approved signing flow, and submit /bind <address> <signature> as instructed. Binding proves wallet control; it does not transfer funds and has no transaction fee.

Bind only an address whose keys you control, never an exchange or another bot's deposit address. You can bind multiple addresses. Other network families follow their own deposit instructions. Never enter or share a seed phrase or private key.

Use the bot to withdraw an available balance to a wallet on the correct network. Check the minimum amount, destination, fee, fee currency, and any safety limits before confirming. Network conditions and current asset configuration can affect availability and fees.

Fees are not universally fixed: they can be network-estimated or subject to a configured minimum. A token withdrawal can require its network's native coin or another supported fee currency. The fee currency can differ from the coin you are withdrawing.

Never share seed phrases, private keys, login codes, or API secrets. Check the official destination and message before signing. Wallet binding proves control of an address and should not ask you to disclose its keys. For a deposit, withdrawal, or account issue, contact CEC support privately with the relevant reference rather than posting sensitive information in a group.

A configured coin/token can be used in CEC's supported reward and campaign flows, helping its community discover the project through funded tasks. Listing enables community participation and active-user rewards, with project-specific requirements discussed with the CEC team. It does not guarantee exposure, adoption, or asset value.

Use the project listing form or contact CEC support. Prepare the name, ticker, network, contract details if applicable, decimals, RPC and explorer links, deposit/withdrawal fees and minimums, website, and community links. The asset must be supported and configured before use; do not send private keys or credentials.

No. Asset support means availability for configured platform functions. Basic project screening discussed in the 2024 AMA is not certification of a project's legitimacy, security, investment value, or future performance. Make your own assessment before funding or accepting an asset.

Approved partners can discuss authenticated campaign creation and verification flows, community use cases, and customized bot options with CEC support. The August 2024 AMA discussed white-label Telegram bots, but current availability and commercial terms need confirmation with the team. Do not assume API access or a dedicated bot is included automatically.

An empty result can mean no matching entries; clear any filters and check again. An unavailable/error message means the website could not retrieve the data, so it does not prove there are no bounties or supported coins. Try again later or check the bot for current availability. Website data does not reserve claim slots.

The bounty activity section shows created bounties (including those awaiting funding), campaign runners, claimed tasks, and rewarded participants. Breakdowns count bounties by status and task type; paid-out currencies show reward amounts and claim counts. Reward totals in different currencies should not be added into a single monetary value. Historical activity does not guarantee future earnings or campaign results.

The homepage describes Tuesday distributions of 75% of the week's collected bounty creation fees among users who complete more than 50% of that week's eligible tasks. Audience size does not determine eligibility.

The revenue-share report shows distributed totals by coin from the start of revenue sharing in 2026 through today. Eligible user shares count participation across weekly distributions, not unique people; someone who qualifies in two weeks is counted twice.

Historical totals do not guarantee your eligibility, future amounts, or future distribution frequency. Check current program rules in the bot or with support.

The available archive contains one CEC creator AMA recording, dated 2 August 2024, and CEC's recap published 31 August 2024. They cover project origins, rewards, automation, currencies, partnerships, and possible future directions.

Watch the full August 2024 AMA or read CEC's August 2024 AMA recap. The recording is creator testimony with a community moderator; the recap is first-party material. Neither is an independent audit or endorsement.

The August 2024 AMA recap describes an initial Twitter-like bounty prototype going live on 1 April 2021 to reduce manual engagement tracking and cryptocurrency reward distribution. Explore CEC's project history for dated milestones and announcement sources, including later platform integrations.

No. Figures such as approximately 4,000 registered users, 600 bounty-notification recipients, around 250 daily task participants, and a peak of 4,500 claims in one day were creator-reported in August 2024. They are dated, unaudited figures with different meanings, not current active-user counts or throughput guarantees.

The recap's impression-growth example is anecdotal, not proof of causation or a promised campaign outcome. Use current website reports for the specific metrics they actually describe.

The August 2024 discussion considered additional social platforms, swaps, and language-model use as possibilities. CEC's recap recorded no public roadmap and no CEC-token plan at that time. These dated statements are not current delivery commitments. Later announcements, such as the August 2026 Bluesky integration, belong to the project history; check the current bot and website for usable features.

No. In the August 2024 discussion, CEC's creator described a centralized platform collecting data considered necessary to operate it at that time. That historical account does not establish today's data collection, retention, security controls, or privacy policy. Ask CEC support for current information before sharing data if you need clarification.

Explore the CEC-focused chapters from the August 2024 recording. Timestamps come from the archived chapter index and have not been independently checked against playback. The chapter topics describe the interview at that time.

• 00:00 - AMA session introduction
• 08:45 - Where and when the initial CEC bot idea emerged
• 11:33 - Why an automated engagement-reward platform was created
• 13:23 - The market gap CEC aimed to address
• 15:17 - Core CEC services
• 19:55 - Use cases for cryptocurrency projects
• 24:00 - Completion of the first working prototype
• 27:46 - Reasons for continuing CEC development
• 31:15 - Reward-system features highlighted in the interview
• 35:09 - Most-used CEC feature at that time
• 37:32 - Interview-era CEC statistics
• 43:36 - Currency integration discussion
• 44:40 - Historical campaign examples
• 47:35 - Visibility tools for new cryptocurrency projects
• 49:57 - Project screening and security discussion
• 53:18 - Partnership opportunities
• 55:02 - White-label Telegram bot conditions at that time
• 58:56 - Possible future product plans
• 1:02:48 - Possible platform evolution
• 1:05:08 - Product competitive strategy
• 1:08:03 - Public-roadmap discussion
• 1:10:40 - Possible token exchange or swap functionality
• 1:12:40 - Airdrop discussion
• 1:15:34 - Possible additional social platforms
• 1:18:22 - Advice for a first engagement campaign
• 1:19:20 - CEC content-marketing approach
• 1:20:53 - Recommendations for the CEC community
• 1:27:52 - Campaigns created and immediately cancelled
• 1:31:32 - Possible CEC token discussion
• 1:35:57 - Decentralized-technology discussion
• 1:38:48 - Industries and use cases considered for CEC
• 1:41:20 - User privacy and data-security discussion