Overview
Collect community wallet addresses through a native Discord submission panel. This is separate from Team Wallets, personal mint wallets and raffle entries. Members submit an address; they do not connect or sign with a wallet. Address format is validated, but ownership, balances and eligibility are not verified.
Requirements
Connect the workspace’s Discord server and enable Community & Discord or Everything access. Creating collections and managing submissions require active linked OWNER, ADMIN, LEAD or MANAGER membership. The bot needs View Channel, Send Messages and Embed Links in the selected text or announcement channel.
Submitting members need to belong to the Discord server and hold the optional required role. They do not need a CollabOS account. Membership and the required role are checked when opening and submitting the modal.
Create and publish in Discord
Run /wallet-collection create name:Community-Wallets chain:EVM channel:#wallets. Optionally add role:@Members to restrict submissions. Supported families are EVM, SOLANA, BITCOIN, APTOS, SUI, TON and TRON.
The command posts a panel with Submit Wallet and opens the collection after publication succeeds. Each collection uses one chain family. Choose a name of up to 80 characters. Creation errors are private; check the bot’s channel permissions before retrying a failed publication.
Submit or update a wallet
Click Submit Wallet on the original panel and enter the full address in the private Discord modal. One entry is stored per Discord user per collection. Submitting again while the collection is open replaces that member’s saved address. A successful submission is acknowledged privately; wallet addresses are not posted into the public channel.
Submission modals expire after 15 minutes. If access changes, the collection closes, or the modal expires, use the current panel again after resolving the issue.
Review, close and export
Open Community & Discord > Forms > Wallet Collections. Use the header Refresh action to reload collections or submissions. Select a collection to review Discord usernames, IDs, full addresses and submission times; load further pages as needed.
Close a collection to stop submissions, or reopen a successfully published collection to accept updates again. Closing preserves existing entries. An unpublished collection cannot be reopened from the dashboard.
Staff can correct a wallet address, including in a closed collection. Corrections validate the collection’s chain and preserve the member identity and original submission time. If the displayed address has changed, refresh before editing again.
Export CSV includes Discord Username, Discord ID, Chain, Wallet Address and Submitted At for all saved submissions, not just the visible page. Spreadsheet-sensitive values are escaped to protect formulas and Discord ID precision. Treat exported addresses and identities as member data.
Clean up departed members
Open the collection’s Cleanup view to review submissions whose members are explicitly marked as having left in the saved Discord membership data. This is based on synced membership, not a fresh live Discord lookup. Unknown members are not assumed to have left.
Select up to 100 entries and confirm deletion. Eligibility is checked again against saved membership before deletion, so entries may be skipped if membership changed or the entry was already removed. Cleanup is manual and permanent; the activity history records deletion and skip counts without retaining the removed wallet addresses.
Troubleshooting
- Cannot create or manage collections: check the selected workspace, active Discord connection, product access and staff membership.
- Required role denied: check current server membership and the collection’s selected role.
- Invalid or expired control: use the original panel and open a fresh modal.
- Panel could not publish: restore bot access; failed publication does not activate the collection.
- Cleanup list looks outdated: allow Discord membership sync to update before deleting entries.