T1Y Whitepaper

Public protocol overview for BNB Smart Chain.

Executive Summary

T1Y is a BNB Smart Chain token protocol built around a T1Y/WBNB liquidity pool, contract-defined participation, hashrate accounting, referral rewards, node-level rewards, sell-impact logic, and burn behavior. The project publishes this page to summarize the protocol for users, explorers, wallets, scanners, and reviewers.

The project is presented as an on-chain protocol rather than a custodial service. Core evidence is intentionally public: verified source code, deployment records, owner-renounce state, official contract addresses, logo files, and operation notes are published in this website and in the GitHub repository.

Design Principles

On-chain verifiability: Contract state, token transfers, burn transfers, LP pair state, and ownership status can be checked on BscScan.
Public evidence over claims: The project publishes contract addresses, deployment metadata, source verification data, and owner-check outputs for independent review.
Non-custodial interaction: Users interact through their own wallets and should independently verify every address and wallet prompt.
Explicit risk disclosure: T1Y contains non-standard BEP-20 mechanics, and those mechanics are disclosed instead of hidden.
No guaranteed outcome: The protocol does not guarantee price performance, profit, redemption value, or principal protection.

Terminology

Participation record: A contract-defined user state created through the intended T1Y participation path. It should not be confused with an ordinary token buy on an exchange interface.
Static hashrate: Participation-related accounting used by the protocol's reward calculation paths.
Dynamic hashrate: Referral and team-related accounting derived from contract state rather than off-chain spreadsheets.
Node level: A contract-readable user level used by the node reward path and displayed by the read-only user query page.
Burn transfer: A token transfer to the standard dead address, visible in BscScan token transfer records.
Owner renounce: The deployed owner-controlled contracts have their owner set to the zero address, making owner-only setters unavailable to a project owner.

Contract Architecture

T1YToken: 0x56b776483096c16a3eDD76156Eee47cdcbC05F7f - main BEP-20 token and participation logic.
T1YTokenExt: 0x0379d39190E125b530E84254a132563E4EaE37d2 - read and reward extension logic.
T1YFeeSwapper: 0x02A2060c730e009b4b2c2B9167f93e7af68D6Bbe - fee swapper/helper contract.
T1Y/WBNB Pair: 0x9d3153f4D033A54FbC8199eaA195655cecc92262 - PancakeSwap V2 pair.
PancakeSwap Router: 0x10ED43C718714eb63d5aA57B78B54704E256024E - BNB Smart Chain PancakeSwap V2 router.
WBNB: 0xbb4CdB9CBd36B01bD1cBaEBF2De08d9173bc095c - wrapped BNB token used by the pair.
Dead address: 0x000000000000000000000000000000000000dEaD - public burn receiver used for token burn evidence.

Protocol Components

Main token contract: Holds the primary token logic, participation records, pair address, extension address, fee swapper address, and owner-renounced configuration state.
Extension contract: Provides reward and read-path logic for user status, reward estimation, pricing routes, and related protocol calculations.
Fee swapper/helper contract: Supports fee conversion and helper flows tied to the main token deployment.
Liquidity pair: The T1Y/WBNB PancakeSwap V2 pair is the public AMM liquidity reference for swaps and reserve state.

Public Evidence Model

T1Y's public evidence package is designed so an explorer reviewer can verify the deployment without private files. The official website links to contract pages, deployment JSON, verification metadata, owner-check output, burn examples, logo files, and form-ready submission text.

Deployment record: Public BSC deployment JSON
Compiler evidence: BscScan standard JSON input
Owner and wiring check: Latest read-only owner check JSON
Reviewer response: BscScan reviewer response package
Mechanics appendix: Protocol mechanics appendix

Participation Lifecycle

Users should verify the official token contract before any interaction.
The intended participation path is contract-defined BNB transfer to the T1YToken contract, not direct interpretation of PancakeSwap purchases as deposits.
LP, static hashrate, dynamic hashrate, referral, and node-level records are contract-accounted on chain.
Reward claiming and LP redemption have specific contract-trigger paths described in the public operation guide.

The public operation guide exists to reduce address confusion. It does not ask users to sign approvals for this website and it does not request private wallet credentials.

User Operation Boundaries

The project separates read-only information pages from wallet actions. The official public website and documentation pages do not sign transactions, request approvals, or ask users to connect wallets. Any actual token interaction must be checked in the user's wallet and on BscScan before execution.

The official website is an information site for token review and user education.
The user query DApp is intended as a read-only status helper and should not replace direct contract verification.
Users should not treat wallet token balances, scanner labels, or third-party UI notices as the only source of truth.
Contract state, transaction receipts, token transfers, and read-contract values remain the authoritative public records.

Reward and Accounting Categories

Static hashrate: Participation-related accounting based on contract-defined records.
Dynamic hashrate: Referral and team-related accounting defined by contract state.
Node rewards: Node-level reward paths involving T1Y and WBNB accounting.
Burn behavior: Protocol transfers to the standard dead address are publicly visible on BscScan.

Scanner and Wallet Interpretation

T1Y is not a plain transfer-only BEP-20 token. Wallets and scanners may detect whitelist checks, external contract calls, sell-impact logic, balance-display differences, or fee-related behavior. These notices should be interpreted alongside verified source code and the current owner-renounced state.

Owner-controlled setters on T1YToken are no longer callable by a project owner after owner renounce.
Owner-controlled controls on T1YFeeSwapper are no longer callable by a project owner after owner renounce.
T1YTokenExt does not expose an Ownable owner control path in this deployment.
Non-standard mechanics still exist in the code and are disclosed as token-mechanism behavior, not hidden.

Burn and Pool Transparency

T1Y includes contract-defined burn behavior. Burn transfers can be reviewed by filtering the token transfer table for the standard dead address. The project maintains a public submission-prep file with recent burn transaction examples so explorers can check representative burn evidence without relying only on a written claim.

Burn address: 0x000000000000000000000000000000000000dEaD
Evidence notes: BscScan submission preparation notes

Ownership and Source Transparency

T1YToken and T1YFeeSwapper ownership have been renounced to the zero address. T1YTokenExt does not expose an Ownable owner control path in this deployment. Contract source and deployment materials are published in the project GitHub repository.

Security page: Security & Ownership Status
GitHub repository: https://github.com/chinaruichi-cell/t1y-token-info
Read-only owner check: Latest owner and wiring check JSON
Verification metadata: BscScan verification metadata

Audit and Review Status

This document, the transparency report, and the reviewer response are public verification materials. They are not a substitute for a formal third-party smart-contract audit. The current objective is to make source verification, owner status, burn evidence, and project information easier for explorers and wallets to review.

Verified source code is available on BscScan for the deployed contract set.
Owner-renounce evidence is published as both BscScan read-contract state and a reproducible read-only JSON check.
The project does not present this package as a formal security audit certificate.
If a formal audit is obtained later, it should be published separately and submitted to BscScan through the proper audit-report channel.

Sale and Allocation Disclosure

This website does not publish an ICO, IEO, public-sale, private-sale, seed-sale, presale, premine, or guaranteed-return campaign. Users should rely on verified contract state and their own risk assessment.

Public Representative and Communications

T1Y is represented publicly by the T1Y Team through the official website, GitHub repository, BscScan account used for token submissions, and official contact email. The project does not ask reviewers or users for private keys, seed phrases, RPC endpoints, or wallet credentials.

Representative page: Team & Public Representative Statement
Official contact: chinaruichi@gmail.com

Explorer Review Materials

To reduce review friction, the project maintains a dedicated explorer review page that maps BscScan's token information requirements to concrete public URLs. The page includes official website links, logo files, whitepaper, source verification evidence, owner-status evidence, burn evidence, official contact, and risk disclosure references.

Review package: Explorer Review Package
PDF edition: Download T1Y Whitepaper PDF
Reviewer response: Response to BscScan reviewer notes
Form payload: Copy-ready BscScan token update fields

Risks

T1Y is not a plain transfer-only token; it contains non-standard token and reward mechanics.
Wallet and scanner products may show warnings for whitelist, external-call, fee, sell-impact, or balance-display behavior.
Referral, node, reward, and redemption paths depend on contract state and user operation. Incorrect wallet actions may not produce the expected result.
Burn behavior and sell-impact rules may affect received amounts, displayed balances, and user expectations.
Market price, liquidity depth, slippage, user operation, wallet security, and smart-contract risks remain.
No page on this website is financial advice or a guarantee of outcome.

Official Contact

The official project contact address is chinaruichi@gmail.com. This public Gmail address is intentionally listed on the official website for BscScan and explorer verification until a project-domain mailbox is available.