AllotRa FAQ
A practical guide to pool types, visibility, claims, invites, and what AllotRa enforces onchain.
AllotRa is a programmable USDC allocation platform built on Arc. Teams and communities can create onchain funding pools, assign roles and claim limits, approve payouts, revoke access, close pools, refund unused funds, and publish configurable trust pages.
Team pools are for internal contributors and controlled team spending, such as core teams, security review budgets, and operating allowances. Community pools are for public rewards, ambassadors, hackathons, bounties, and community distributions. Hybrid pools are for projects that need team access controls plus broader contributor allocation workflows.
Public pools show more pool status and trust information publicly. Partial pools show aggregate funding and payout status without contributor-level detail. Private pools restrict pool details to authorized users. Visibility is app-level disclosure control; onchain transactions may still be visible on ArcScan.
Direct claims let eligible users claim within their allowance without admin approval. Approval-required claims create a request first; an owner or admin reviews it, then approves and pays the claim.
Pool creation, funding, roles and access where supported, allowances, claim requests, payments, refunds, and close logic are enforced onchain. Display names, Discord metadata, private notes, comments, pool images, and UI visibility preferences are kept offchain for usability and privacy.
No. Discord can help identify community members, but invite links work with wallet login. Discord linking is optional unless a specific pool uses Discord-based access.
New claims stop. Refundable unused funds can be returned to the pool owner according to the pool rules and contract state. Paid history remains available according to the pool visibility settings.
A wallet signs onchain actions and receives USDC payouts. AllotRa prepares transactions, but your wallet confirms actions before they become final.
