Finality risk
Confirmed transactions cannot be rolled back by support. Review details before signing.
Use this page as a decision gate before every wallet signature. It highlights timing, local-data, and finality risks across Place Picks, Reveal Picks, and Claim Reward.
Confirmed transactions cannot be rolled back by support. Review details before signing.
Missing reveal or claim periods can permanently forfeit reward eligibility for that round.
Reveal helper data is local to your browser/device. Clearing storage can break reveal ability.
If keys are compromised, 1for49 cannot recover custody or reverse signed actions.
Use this matrix to understand trigger, consequence, and immediate response.
| Stage | Risk level | Trigger | Consequence | Immediate action |
|---|---|---|---|---|
| Place Picks | Medium | Submitting picks for wrong round/stage or signing with wrong amount assumptions. | Entry is finalized for that round and cannot be edited post-confirmation. | Check round ID + stage + amount, then submit once. Use small-value test when uncertain. |
| Reveal Picks | High | Reveal helper data unavailable or reveal submitted after period close. | Entry can be forfeited in one-entry mode, making reward path unavailable. | Reveal early in reveal period and keep local helper data backed up before device changes. |
| Claim Reward | Medium | Claim attempted before settlement, without eligibility, or after claimable period. | Transaction can fail or reward rights can expire for that round. | Check settled status + eligibility + period before claiming; claim promptly when enabled. |
Reason: Current stage does not allow the requested action.
Risk: Repeated retries can waste fees/time and increase user error.
Recovery: Wait for next stage time and act when button is enabled.
Reason: Wallet did not place picks for that round.
Risk: Attempting reveal/claim without entry always fails.
Recovery: Switch to correct round or place picks in current open round.
Reason: Winner and reward rate not finalized yet for claim.
Risk: Early claim attempts fail and create confusion around reward status.
Recovery: Track stage timeline and claim once settlement is completed.
Reason: RPC/indexer lag during congestion can delay frontend updates.
Risk: User acts on stale assumptions and submits wrong-stage actions.
Recovery: Refresh and verify with explorer signatures/account state.
Complete context speeds triage and avoids repeated back-and-forth.