Skip to main content
moonpacket

FAQ for Organizers — Sending Red Packets

API Demo
 
 
 
 
 
How to Send Red Packets
 
Set specific conditions:
 
     
  • • Join groups / Follow channels
    •  
  • • Correct passcode
    •  
  • • Custom API
    •  
 
Only eligible users can claim
Sent to valuable users.
 
 
 
   
 
 
 
FAQ for Organizers — Sending Red Packets
  
  
  
 
1) What is <span class="brand-mark">moonpacket</span>'s red packet sending
 
 
 
What is the red packet tool?
 
This is a tool to help group admins/community managers quickly send red packets in Telegram groups. Main uses: stimulate engagement, attract new members, run promotional activities. You can use USDT or mainstream tokens to send red packets. Through <span class="brand-mark">moonpacket</span>, group admins can 'customize distribution rules', 'set claim conditions', 'track claim status', and verify with API.
 
Tip: Red packets work great as an icebreaker. Reply under the packet post to announce the game/theme you want to run.
 
 
  
 
 
 
  
 
2) When is red packet sending suitable
 
 
When is red packet sending suitable?
 
    - New member greetings/welcome
- Live events / AMA / real-time interaction at events
- In-group marketing promotions, raffles, slogan tasks
- Referral rewards for inviting friends
- Limited-time promotions, countdown activities
- 'Cross-group red packets': Send to others' groups for promotion and community collaboration
 
 
  
 
3) Fees & Thresholds for sending red packets
 
 
What fees will be deducted?
 
Every on-chain operation you make will incur a gas fee. The gas fee is charged by the blockchain itself, not an additional platform charge.
 
What happens when I deposit tokens into the red packet pool?
 
When you deposit tokens into the red packet pool, the blockchain will immediately charge a gas fee. The actual amount that goes into the pool may be slightly less than the nominal amount you entered. This is a normal on-chain deduction.
 
How much does the platform charge when sending red packets in 'your own group'?
 
When you send red packets in your own group, the system will charge a 2% platform fee, which will be automatically deducted during distribution:
- 1% to maintain service and risk control (servers, anti-abuse, fraud prevention, etc.)
- 1% accumulates as token reserve, reaching the threshold to repurchase <span class="brand-mark">moonini</span> tokens, returning to the entire ecosystem

The remaining amount will be distributed to members in your group.
 
What's the difference when sending red packets to others' groups (cross-group red packets)?
 
    - Cross-group red packets can only use mainstream tokens and have a minimum amount threshold
- The system will reserve 3% as 'community incentive' to be distributed to the target group's management/admin
  This is equivalent to you sponsoring that community, boosting that community's engagement, while also promoting your project
- This is automatically handled by the system, no need for you to negotiate revenue sharing privately
 
Is there a minimum amount?
 
The system will set a minimum amount threshold. Below this amount, the system will not allow creating red packets. Please confirm you have sufficient funds before sending.
 
 
  
 
4) Security & Risk Control / Account Status
 
 
Security & Risk Control Information
 
We actively detect abuse behavior (scams, money laundering, bot abuse, fake engagement, etc.). If high-risk behavior is detected, related accounts or assets may enter 'under review' status: withdrawals may be delayed, accounts may be marked on blacklist and suspended. This is to protect overall user asset security and comply with regulations. This control measure complies with our user terms: the platform may pause, restrict, delay, or reject certain withdrawals/transfers based on internal risk control, compliance, and third-party investigation requirements. If you feel your account was misjudged, you can appeal via the official customer service bot (see next section).
 
 
  
 
5) Customer Service & Self-Service Queries
 
 
How to contact customer service?
 
You can directly contact the official customer service bot @moonini_helper_bot.

Please enter the command /setlang <language> (e.g., /setlang zh-TW or /setlang en-US) in the conversation to switch customer service language.

When reporting issues, please provide:
- Your Telegram account or user_id
- Time when the issue occurred
- Operation you were performing (e.g., 'withdraw', 'send red packet', 'claim red packet')
- Relevant transaction ID / transaction hash (if available)

Customer service only looks at on-chain data and transaction records. We won't ask you to send image files, won't ask you to provide wallet private keys, mnemonics, complete seed phrase, nor will we ask you to transfer funds for 'verification'. Official customer service will not proactively private message you to request assets.
 
 
Self-Service Query API
 
You can also use the self-service query API to check your status, e.g., whether your account is valid, whether you're on the blacklist, whether you're under review. Below is an example:

If the response shows you are is_blacklist: true or status: "hold", it means your account is under risk control review, withdrawals/distribution may be suspended. You can appeal to the customer service bot and provide the transaction hash, we will speed up processing based on on-chain evidence.
 
 
 
  
 
6) 活動規則與功能
 
 
以下功能可讓群主設定任務條件與領取規則
 
 
What are passcodes? Best use cases?
Players must obtain passcodes from external channels and enter them correctly to claim. Common practices:
 
     
  • YouTube long videos with 6-digit passcodes to encourage full viewing.
  • X.com (Twitter) posts or Threads hinting at passcodes to boost engagement.
  • Live streams announcing passcodes to drive attendance.
  • Private/paid groups with exclusive passcodes for core members.
    •  
 
 
 
Can I use my own API to determine eligibility?
Yes. <span class="brand-mark">moonpacket</span> calls your read-only API before users claim to verify eligibility. Configure api_url and api_key (optionally set allowed domains).
 
Condition Declaration (no user_id)
 
GET [api_url]?api_key=[api_key]
 
Response:
 
{
  "data": {
    "level": { "gt": 99 },
    "status": { "eq": "active" },
    "is_blacklist": { "eq": false }
  }
}
 
Operators: eq (any type), gt/lt/gte/lte (numeric only)
 
User Query (includes user_id)
 
GET [api_url]?api_key=[api_key]&user_id=[user_id]
 
Response:
 
{
  "data": {
    "level": 100,
    "status": "active",
    "is_blacklist": false
  }
}
 
<span class="brand-mark">moonpacket</span> uses 'condition declaration' as threshold, comparing against 'user query' actual values; eligible if matches, otherwise claim blocked.
 
Security Recommendations
Use read-only endpoints, enable api_key with allowed domain restrictions; for cross-domain, consider Cloudflare Workers as relay with rate limiting.
 
 
 
  
 
7) 功能詳情
 
 
What activity rules can I set?
• Distribution: Random, even split, or fixed amounts
• Task requirements: Follow channels, join groups, passcodes, external tasks
• Time limits: Start/end times
• Participation limits: Per-person max claims, regional restrictions
 
How to ensure campaign fairness?
Blockchain technology for transparency. All distribution records are queryable. Anti-cheat: IP detection, device fingerprinting, behavior analysis. Real-time anomaly monitoring.
 
Can I modify rules during the campaign?
 
No.

Once an activity starts and is public to members, all key rules are considered 'committed', including but not limited to:
- Total amount / reward pool amount
- Number of red packets, maximum number of people who can claim
- Claim conditions, participation threshold (e.g., 'complete 1 task to claim' cannot be changed to 'need to complete 10 tasks to qualify')
- Review / distribution standards
- When the activity ends, when it settles

These cannot be adjusted, deleted, added, delayed, or difficulty changed during the activity.

The reason is straightforward: participants act based on the rules you first announced. If you raise conditions midway, extend waiting time, reduce rewards, it will be seen as 'breaking promise' or 'maliciously delaying distribution', which not only damages group trust but may also result in complaints or being marked as high-risk organizer.

Special attention: Once an activity starts, there is no option to 'temporarily stop' or 'take down midway'. You cannot unilaterally declare the activity invalid, nor can you ask people to play by new rules before reaching the originally promised end conditions. The activity must run and settle according to the originally promised conditions.
 
What if the rules are really set wrong?
 
You cannot 'fix while running' during an ongoing activity. You must follow this process:

1. Let the current round run to its natural end according to the rules you first made public. 'Natural end' means reaching the end conditions you initially promised (e.g., all packets distributed, reached original deadline, rewards you promised are all distributed). During this period, you cannot temporarily add conditions, cannot reduce rewards, cannot delay settlement time, nor can you say 'I'll pause first, replenish later'. You must give all promised rewards in full according to the original commitment.
2. After this round is fully completed under old rules and all commitments are fulfilled, then you can start a 'next round' with corrected new rules. The next round is considered a brand new activity; please make the new rules, thresholds, end conditions public. If you're still not sure the new rules are mature, please test with small amounts/small batches/short durations first. Don't dump large amounts from the start. Especially for activities with API auto-distribution, please confirm the process will execute as you expect.

The key point is: You cannot stop an activity that's already running early, nor can you change difficulty or standards midway. Each round must complete and settle as originally promised; only then can the next round use new version rules.
 
How to monitor activity effectiveness?
Real-time dashboard provides: participation statistics, claim completion rate, user feedback analysis, community engagement metrics.
 
How to handle remaining funds?
Unclaimed red packets will automatically return to your wallet. Refund requests available within 7 days after campaign ends.
 
Can I run multiple campaigns simultaneously?
Yes, but recommended limits: maximum 3 active campaigns per group, avoid overlapping schedules, ensure sufficient funding.
 
How to optimize campaign effectiveness?
Adjust strategy based on data insights, A/B test different rule combinations, reference successful case studies, regularly collect user feedback.
 
 
How to prevent cheating and bot activity?
 
     
  • Behavior frequency and device/IP detection
  • Account and wallet unique binding
  • Withdrawal verification codes
  • AI risk control initial review; third-party biometric + face + ID verification when necessary
    •  
 
 
Where can I see my sent records and claim counts?
Visit your personal dashboard 'My Sent Packets' to view claim counts, remaining slots, and total amounts spent per campaign. Reports available if enabled.