DAY0 DOCUMENTATION
How the complete platform works.
This guide explains the user journey, wallet interactions, contract boundaries, launch process, and risks behind DAY0. It describes the current BSC testnet implementation—not a promise of future returns.
Platform overview
DAY0 is a self-custodial DeFi interface. It helps a user prepare and sign transactions, but it never holds private keys or takes custody of wallet assets. The first release focuses on a single BSC market: BNB / DAY0.
The interface is public, but DAY0 has not been deployed and no official liquidity exists. Transaction buttons fail safe until the verified token address is configured.
02
Quick start
- 1Install or open a Web3 wallet
Use MetaMask or a compatible mobile wallet. Never share your recovery phrase with DAY0 or any website.
- 2Connect to DAY0
Select “Connect wallet.” The wallet reveals only the selected public address.
- 3Switch to BSC Testnet
The network button asks the wallet to switch or add the supported test network.
- 4Use test assets only
Testnet tokens have no intended monetary value. Never bridge or send real BNB for testing.
- 5Review every confirmation
Check the contract, amount, network, and estimated fee in the wallet before signing.
03
Architecture
The platform separates visual presentation, wallet state, chain configuration, and contract calls. This keeps unsupported addresses from silently becoming transaction targets.
Responsive pages for trade, liquidity, earn, portfolio, token, governance, and documentation.
One shared connection state handles the address, network, and user-approved chain switching.
Only explicitly configured router, wrapped-native, and DAY0 addresses may be used.
An OpenZeppelin-based fixed-supply ERC-20 plus a compatible V2 liquidity router.
Current network configuration
0x9Ac64Cc6e4415144C455BD8E4837Fea55603e5c30xae13d989daC2f0dEbFf460aC112a837C89BAa7cd04
Trading flow
The first supported direction is BNB into DAY0. A swap becomes available only after the router can return a live quote for the configured pair.
- 1Enter BNB
The interface converts the amount to 18-decimal base units.
- 2Request quote
The router returns the expected DAY0 output for the BNB → WBNB → DAY0 path.
- 3Apply protection
DAY0 calculates a minimum output using the 0.5% slippage limit and a 20-minute deadline.
- 4Sign and settle
The wallet signs; BSC confirms; output tokens arrive directly at the wallet.
Slippage protection does not prevent a poor price caused by very low liquidity. Review the output and pool depth before signing.
05
Liquidity flow
Liquidity providers deposit BNB and DAY0 at the current pool ratio. The router returns LP tokens that represent a proportional claim on both reserves and accumulated trading fees.
Adding liquidity
- 1Choose BNB and DAY0 amounts.
The pool determines the accepted ratio when the transaction executes.
- 2Approve DAY0.
The ERC-20 approval authorizes the router to transfer only the entered token amount.
- 3Confirm the deposit.
A second transaction sends BNB and DAY0 into the pair and returns LP tokens.
- 4Track the LP position.
The portfolio will read the verified LP token after the pair address is deployed and indexed.
Removing liquidity
The holder approves the verified LP token, selects a percentage, and asks the router to return the underlying reserves. Removal stays unavailable until an official pair exists.
06
Earn programs
“Earn” is a registry of verified incentive programs, not an automatic yield promise. A program may become active only when it publishes the reward contract, funding source, reward token, start/end time, withdrawal rules, audit status, and known risks.
The interface intentionally shows zero active programs. Displaying invented APR or TVL before contracts exist would misrepresent the protocol.
07
DAY0 token
The token contract has three primary behaviors: transfer, burn, and permit. Its constructor mints exactly 21,000,000 DAY0 to a non-zero treasury address.
The maximum supply can fall when holders burn tokens, but it cannot return to 21 million because no mint function exists.
08
Governance
Governance begins with operational discipline. Before any mainnet deployment, DAY0 needs a multisig with identified signers, a signing threshold, separation of duties, documented treasury rules, and an emergency process. A timelock should protect sensitive administrative actions.
Future community proposals may address incentives, interface defaults, verified asset lists, supported chains, and treasury grants. Governance must not create a hidden mint path or obscure permissions affecting user funds.
09
Security model
Keys remain in the wallet. DAY0 receives only public addresses and signed transaction responses.
Missing or malformed addresses keep transaction flows in setup mode.
Swaps and deposits include slippage minimums and expiration deadlines.
No admin mint, upgrade proxy, blacklist, transfer tax, or pause control is included.
Before mainnet
- Independent smart-contract and frontend security audits.
- Verified deployment source and reproducible contract settings.
- Multisig, timelock, monitoring, alerts, and incident response.
- Transaction simulation, price-impact warnings, and reliable indexing.
- Legal review for jurisdictions, token distribution, and user disclosures.
10
Risk disclosure
DAY0 and paired assets can lose value or become illiquid.
Undiscovered flaws in tokens, routers, pairs, or reward contracts can cause loss.
Low reserves increase price impact; LPs face impermanent loss.
Compromised keys, malicious approvals, phishing, or signing mistakes can transfer assets.
Multisig or voting failures can misuse treasury funds or protocol permissions.
Laws and obligations vary and may change across jurisdictions.
DAY0 documentation explains software behavior. It is not financial, legal, tax, or investment advice.
11