Funded before issue
Each accepted lock reserves its credits against a funded service budget.
The Lighthouse
token.
Two proposed uses: lock tokens for service credits, or spend tokens on memory and storage.
Two ways to use the token.
The proposed model separates locked tokens from tokens spent on a service. Fiat and supported stablecoin payments remain available.
Tokens are locked
Lock for service credits.
Commit tokens for a defined term and receive a reserved service-credit balance. Your tokens stay locked while you use the credits.
- 01
Review the terms
See the token amount, release date, credits and expiry.
- 02
Use the credits
Spend on eligible services at the published rates.
- 03
At maturity
Withdraw the committed token amount, or renew.
Using credits does not reduce your locked token balance. Holding tokens alone does not generate credits.
A balance for your services.
Credits measure usage in USD. They are separate from your tokens and from access to your data.
1service credit
=$1of eligible services
At the published rate card. Storage capacity and operation counts depend on the service selected.
Separate balances
Locked tokens and service credits are tracked separately. Using credits does not spend locked tokens.
Agent budgets
Assign credits to authorised agents. Spending permission does not grant access to memory.
Eligible uses
- Memory plans
- Storage renewals
- Additional usage
- Agent budgets
Lock-earned credits cannot be transferred or redeemed for cash.
Token allocation.
Explore the allocation categories. Supply, shares and release terms remain TBD.
- Total supply
- TBD
- Network
- TBD
- Launch date
- TBD
- Lock terms
- TBD
Team
Share and release schedule TBD
CategoryShare
Supply, release and contract details
- Maximum supply
- TBD
- Initial circulating supply
- TBD
- Token standard
- TBD
- Contract address
- TBD
- Vesting and cliffs
- TBD
- Unlock schedule
- TBD
- Emission schedule
- TBD
- Lock terms and credit rates
- TBD
- Trading venues
- TBD
- Buyback or burn policy
- TBD