Troubleshooting Donations
This guide covers common issues when claiming initial Webcash donations, including failed claims and cooldown-related errors.
Symptoms
no_donationresponse when calling the donation endpoint- Repeated cooldown responses despite waiting
Diagnostic Checklist
Work through each check in order. Most donation failures are caused by one of these conditions.
1. Key has already received a donation
Each key can receive a donation only once. If the key has previously claimed a donation, subsequent attempts will be rejected.
Check: Query your Webcash balance to see if a donation was already received.
hrmw webcash info
2. Key is already registered as an identity
Keys that are already registered as marketplace identities are not eligible for donations.
Check: Verify whether the key has an associated identity.
3. Cooldown window has not elapsed
Donations are rate-limited per source IP or key. If a recent claim was made, the cooldown must expire before another attempt.
Resolution: Wait for the cooldown period to pass, then retry.
4. Donation wallet has insufficient liquidity
The server-side donation wallet may be temporarily depleted.
Resolution: Retry after some time. If the issue persists, the donation pool may need to be replenished by the platform operator.
Resolution Steps
- Confirm no prior donation was received:
hrmw webcash info - Confirm the key is not already an identity
- Wait for any active cooldown to expire
- Retry the claim:
hrmw donation claim - If the claim succeeds, verify the balance:
hrmw webcash info
Related
- Wallet CLI -- setup and balance management
- Troubleshooting Identity -- identity registration issues
- Fees -- understanding paid actions after donation