01 · About this document
This paper describes the confirmed website and allocation workflow. Project-specific product utility, economics, operators, dates and contract details will be added when approved. Read the final sale terms before making any financial decision.
02 · Project overview
Levunto is being prepared as a token project with a public information website and a separate member portal at app.levunto.com. The portal brings accounts, payment review, internal allocations, withdrawal requests and support into one place.
The underlying product, intended audience and detailed token utility have not yet been published. This draft does not present a functioning exchange, lending product, payment card, automated trading strategy or staking protocol.
03 · Token information
| Item | Current information |
|---|---|
| Project | Levunto |
| Proposed ticker | LVT |
| Distribution standard | ERC-20 |
| Network and chain ID | To be published |
| Contract address and decimals | To be published |
| Supply and allocation | To be published |
| Sale price, opening and closing | To be published |
| Vesting and distribution conditions | To be published |
An ERC-20 receiving address alone does not identify the correct token network. The final network and contract must be specified before distribution.
04 · Account experience
Register with your name, email and password. Registration signs you in immediately; there is no activation-email step. Use an email you control and a unique password with at least twelve characters.
Your dashboard shows available allocation, amounts reserved for a withdrawal and recorded distributions. The order history and private support inbox provide the context behind those balances. Preview and live balances are stored separately.
05 · Supported payment assets
The planned payment configuration supports eight assets. Network identity is part of every order, even when two assets use the same address.
| Asset | Network |
|---|---|
| BTC | Bitcoin mainnet |
| ETH | Ethereum mainnet |
| USDC / USDT | Ethereum mainnet, ERC-20 |
| BNB | BNB Smart Chain |
| SOL | Solana mainnet |
| XRP | XRP Ledger, no destination tag |
| DOGE | Dogecoin mainnet |
For live orders, the quoted amount, payment asset, network, recipient, QR code, quote expiry and wallet profile version are saved together. A subsequent receiving-wallet update applies to new quotes. It does not rewrite instructions on existing orders.
06 · From payment to allocation
- Choose an amount and a supported payment asset.
- Read the order-specific recipient, network and quoted amount.
- Send from your own compatible wallet only when the sale is live.
- Submit the transaction hash for manual review.
- Staff verify the recipient, network, genuine asset, net amount received and successful confirmations.
- Approval credits the internal allocation once.
A transaction hash is a reference, not proof of payment. Duplicate same-network payment references cannot be used for separate orders. A late or underpaid transfer requires manual reconciliation. A rejected order status is not itself an on-chain refund.
07 · Withdrawal and distribution
A withdrawal request identifies an amount and an eligible ERC-20 destination. The requested allocation moves from available to reserved so it cannot be requested twice. Staff may approve or reject the request.
Approval is an internal decision. It does not execute a transfer. Staff send tokens externally, verify the transfer and record its transaction hash before marking the request sent. Rejection releases the reservation back to the available allocation.
Distribution dates, minimums, fees, vesting conditions and eligibility will be stated in the final terms. No immediate withdrawal availability is promised by this preview.
08 · Records and safeguards
Account access, ownership checks, request validation and administrator permissions protect private records. Payment reviews, changes in allocation and withdrawal decisions are recorded in an audit trail. Orders snapshot their original receiving instructions.
No wallet private key or seed phrase is required by the portal. Outgoing transfers remain outside the website. Do not submit secrets in a form or support ticket. These implementation measures do not constitute an independent security audit.
09 · Governance and token rights
Governance arrangements, voting rights and proposal processes have not been announced. A portal allocation does not by itself establish equity, revenue participation, voting rights, redemption rights or a promised return. Any rights must be explicitly established in the applicable final project documents.
10 · Development milestones
- Build and verify the website, member portal and administrative workflows.
- Publish the actual product proposition, token economics, operator details and contract information.
- Confirm sale terms and complete readiness checks before opening live payments.
- Open distribution only when the token and transfer procedure are ready.
These are preparation milestones. Dates and external dependencies remain to be confirmed.
11 · Risks and disclosures
Digital tokens can lose their value. Technical faults, compromised accounts, network errors, incorrect destinations, liquidity constraints and changes in project plans can affect participation. Cryptocurrency transfers can be irreversible. Do not send funds based on a preview, an unofficial message or an unverified contract address.
There are no confirmed exchange listings, audited contracts, performance histories, fundraising totals, partners or returns in this draft. Refer to the risk disclosure and the eventual sale terms for the actual offering.
12 · Glossary and updates
Allocation: the internal number of project tokens credited after payment review. Reserved: an allocation held for a pending withdrawal. Distribution: an external token transfer. Transaction hash: a network-specific reference to a transaction. ERC-20: a token interface standard; it does not select a network on its own.
The latest project documents are available on this site. Questions about a portal record belong in private support. Check the portal for replies; support email notifications are disabled.