DAO Maker calculates launchpad allocations after users commit their contributions
DAO Maker participation requires checking the selected offering, completing its eligibility requirements and confirming the contribution before interpreting an allocation. Public and private offerings use different allocation mechanisms. A successful deposit establishes what entered the offering; settlement determines what the contribution buys. Any unused balance and subsequent token claim need their own confirmation.
Last updated
Begin with the offering you intend to enter and keep its participation record alongside your wallet activity. Registration, spending permission, contribution and token delivery describe different states. Each state needs evidence of the corresponding action before you continue.
A confirmed deposit establishes a contribution, while the offering’s settlement determines the allocation and any amount available to return.
Public and Private Participation Paths
Public offerings allocate through deposits, while private offerings use DAO Power and contributions to determine allocations. DAO Power measures participation power obtained through eligible DAO staking or retained DAO Boost deposits. Select the participation path before preparing funds, because the same wallet balance does not satisfy every path’s requirements.
The public system offers a classic USDT deposit and DAO Boost. Boost converts the contribution into DAO and changes its allocation weighting, creating exposure to the DAO token. DAO Power does not determine public allocations. These differences affect both the commitment and the asset returned from unused contributions.
For private participation, distinguish the guaranteed-allocation option from the lottery option when the offering provides them. The former calculates a share using registered DAO Power; the latter applies its lottery rules. Record the selected option with the contribution instead of treating both as interchangeable registrations.
Eligibility Before Funding
Eligibility checks belong before a purchase commitment, including identity verification and the offering’s participation restrictions. Know Your Customer, usually shortened to KYC, involves personal information and verification procedures. A connected wallet does not establish completion of those procedures.
Check whether your account has completed the requirements applicable to the selected sale. Submitted documents and accepted verification are different states. Wait for verification to be accepted before committing funds, even if the interface lets you inspect an offering. The platform’s terms require KYC checks before participants pay the purchase price and allow token delivery to be refused when required verification information is missing or invalid.
Wallet and Offering Requirements
The participating wallet must support the offering’s contribution network and the tokens it will receive. Compare the account address shown by the application with the account selected in your wallet. Then check the contribution asset, supported network and funding requirements together.
Keep the contribution balance separate from the balance needed for network charges. A wallet holding enough of the sale’s payment token may still lack the native asset required to submit its transaction. Use the network and asset the selected offering identifies; a matching token name on another network does not establish compatibility.
Also record the registration or contribution deadline and the token release conditions. A funding action becomes useful only while the relevant participation window remains open. For private offerings, confirm the required staking state before assuming a visible DAO balance supplies participation power.
Approval and Contribution Permissions
A spending approval and a contribution authorize different operations, so inspect what each wallet request permits. Where the contribution uses an ERC-20 allowance, approval gives a specified contract permission to spend tokens. The contribution action then uses the applicable permission to fund the offering.
Token Spending Permission
The Authorized Contract
The spender is the contract receiving permission to move the approved token. Compare that contract with the spender identified for the selected offering. An approval involving another contract does not establish readiness for this contribution.
The Spending Amount
An ERC-20 allowance limits how many tokens an authorized spender may withdraw from an account. Compare the requested allowance with the intended contribution. A permission extending beyond that amount gives the spender broader access than this purchase requires.
The Contribution Transaction
The contribution request must correspond to the intended offering and amount. If the wallet groups several operations, inspect the included actions rather than counting confirmation prompts. One prompt can contain several actions, while separate prompts can represent permission followed by payment.
The Deposit Commitment
The final wallet request is the point to compare the intended contribution with the action awaiting authorization. Check the account, network, spending contract, token amount and estimated network charge. Where DAO Boost applies, include the conversion into DAO in that review. Reject a request whose meaning remains unclear before signing; closing the application after broadcast does not reverse an executed transaction.
Contribution Receipts and Participation Records
A transaction hash identifies a submission, while its receipt establishes whether that transaction executed successfully. Pending transactions do not yet have an execution receipt. For a completed transaction, inspect the sending address, destination and relevant token movements rather than relying on the wallet’s activity label alone.
The offering’s participation record answers a separate question: which contribution has the application associated with your account? Compare its asset and amount with the completed deposit. A successful approval cannot fill that role, and a successful unrelated transfer cannot establish entry into the selected offering.
Keep the transaction identifier with the offering name and participating address. These details let you distinguish a contribution from an approval, return or later claim without reconstructing the entire session.
Final Allocation After Settlement
Settlement determines how much of the contribution becomes an allocation under the selected offering’s rules. A contribution receipt alone cannot establish that amount while allocation inputs remain unsettled.
Private guaranteed allocations depend on your registered DAO Power relative to the offering’s registered total and its allocation parameters. Contributions above the guaranteed portion compete for the remaining allocation. A lottery entry instead needs the lottery result before it establishes a winning allocation. Confirm the final result for the option you selected.
For public participation, allocation reflects the contribution pools and their share calculations. Record the finalized allocation separately from the deposited amount. This distinction prevents an accepted deposit from appearing to promise an equal purchase allocation.
Unused Contributions and Token Delivery
Unused contribution funds and purchased project tokens are separate balances with different delivery rules. The private offering system also returns excess deposits automatically at the end of the offering. In the public system, excess classic USDT deposits return automatically after the offering. Excess DAO from the Boost option requires a manual claim. A returned DAO amount also retains exposure to changes in DAO’s value.
Reconcile the contribution against its allocated portion and unused balance in the relevant asset units. Keep any conversion separate from that comparison. A difference between starting and ending market value does not, by itself, identify missing tokens.
Project tokens may follow a release schedule rather than arrive with settlement. Record what is allocated, what is available to claim and what remains scheduled for later release. A future release should not appear in the same category as an overdue contribution return.
Why Is My Contribution Missing?
Your contribution may be missing because only an approval completed, the deposit is pending or failed, or the offering view does not reflect the successful deposit. Check the original operation before submitting another contribution. For a contribution to a selected DAO Maker offering, the normal confirmation consists of successful deposit execution and a matching participation record. The allocation may remain unsettled at this point.
If the wallet reports completion while the contribution remains absent, inspect which operation actually completed. The receipt’s success status describes that transaction; understanding its effect also requires checking the operation and relevant token movements.
- If only an approval completed, the deposit still needs its own execution evidence.
- If the deposit remains pending, resolve that submission before authorizing another contribution.
- If execution failed, identify the failure and recheck eligibility, funds and the participation window before retrying.
- If the deposit succeeded but the record is missing, confirm the participating account and network, then refresh the offering view.
- If the same mismatch persists, retain the transaction details and request clarification before sending more funds.
A retry belongs after the original submission’s outcome becomes clear and the offering still permits participation. Refreshing the display can reveal an existing record; it cannot repair an incorrect transfer or reopen a closed contribution window.
The contribution is confirmed when the successful deposit and participation record agree, even if allocation remains unsettled. If they still disagree, pause further contributions and seek support; the mismatch remains unresolved. Compared with repeating the payment, reconciling the existing transaction avoids adding a second commitment to an unexplained first one.
The Claim Decision and Later Releases
The claim decision should use the settled allocation and the release currently available to your account. Read any applicable claim deduction and purchase-refund conditions before authorizing delivery. Returned excess contributions do not establish a right to reverse the purchased allocation.
When the allocation includes vesting, distinguish the available release from the total award. For private offerings subject to the Strong Holder Offering rules, maintain the DAO Power used to participate. If it falls below that level, the documented grace period is 3 days to restore it; otherwise, you lose all future unlocks for that project. Check this requirement before unstaking DAO or withdrawing Boost tokens that supply the required power. Keep the completed claim transaction alongside the amount still awaiting release.
Claiming requests delivery of an available release under the current claim conditions. Later scheduled releases remain pending until their unlock dates, whether or not you claim the available portion. Follow the offering’s release terms rather than treating the entire settled allocation as immediately spendable.
DAO maker - your questions answered
-
Can I Revoke Token Approval After Making a DAO Maker Contribution?
- Yes. You can revoke any remaining ERC-20 allowance after contributing. Revocation changes future spending permission; it does not withdraw a completed contribution. Funds already transferred into an offering follow that offering’s allocation and return rules. Keep the approval record separate from the deposit record when checking the result. A later contribution may require fresh permission if the remaining allowance no longer covers it.
-
Does Closing My Browser Cancel a Submitted Contribution?
- Closing the browser does not cancel a transaction already submitted to the network. The submission can remain pending or execute without the application staying open. Its transaction record remains the relevant place to establish the outcome. Reopening the offering is a way to inspect participation, not evidence that an earlier payment was canceled.
-
Where Should I Submit Identity Documents for Launchpad Participation?
- Submit identity documents through the designated verification process associated with your account. Keep those documents separate from public transaction details when discussing a deposit problem. A transaction identifier can help identify a contribution, while identity verification requires its own document handling. The platform’s terms provide for verification through a service provider and possible requests for additional information.
-
Is a Purchase Refund the Same as Returning an Unused Deposit?
- A purchase refund reverses an eligible purchase, while an unused-deposit return releases funds the allocation did not consume. The two operations can have different conditions and deadlines. Before relying on a purchase refund, establish the terms attached to that specific offering. An automatic return of excess funds does not establish an unrestricted cancellation right.
-
What Information Helps Resolve an Unmatched Contribution?
- The transaction identifier, participating address, selected network and offering name help identify an unmatched contribution. Include the action you authorized and the discrepancy between the transaction and participation record. A screenshot can show the displayed state, but it does not replace the transaction identifier. Exclude private keys, recovery phrases and unrelated identity documents from the explanation.