Project profile and team
A project profile explains who is launching, what the token is for, and how the raise will be used. The profile and the launch terms should tell the same story.
Project information
Include a clear project name, short summary, full description, logo, website, and official social and repository links. Describe the product, current stage, intended users, roadmap, and concrete use of raised capital.
Avoid presenting a future milestone as a completed result. Link to working products, code, or published material when those support a claim.
Team
Describe each public team member's name or handle, role, relevant experience, and official profile links. Explain who controls the token admin, distribution wallet, project proceeds, and team allocation.
The current curve sends team claims to a single owner address. A list of team members on a profile does not create separate onchain vesting recipients.
Token and tokenomics
Show the token identity, supply, allocation table, quote asset, and vesting terms. On Base that identity is the ERC-20 address. On Stellar it is the asset code, issuer, and SAC address.
Explain any supply held outside the vault and any remaining admin powers.
The tokenomics guide explains how to keep the supply allocation internally consistent. A tokenomics narrative does not create additional contract-enforced allocation buckets.
Launch terms
Publish the selected format, pricing mechanism, opening date, fees, access rules, and claim schedule. Auctions and presales also need their close and settlement terms.
Participants should be able to distinguish a submitted commitment, an accepted allocation, a claimable amount, and a token already received.
Stored metadata today
The current Stellar contract stores only these display fields:
| Field | Limit |
|---|---|
name | Nonempty, at most 64 bytes |
description | At most 512 bytes |
logo | URL string, at most 256 bytes |
symbol | Nonempty, at most 12 bytes and matching the asset SAC |
Byte limits are not character counts for all languages. Stellar asset-code validity is also determined during asset issuance; the contract's string-length check does not issue an asset.
Rich descriptions, team biographies, documents, and extended tokenomics belong to the project-profile data layer. The current logo field stores a string; it does not upload or pin media.