soilate
VERSION 1.0 · 28 AUGUST 2026

SOILATE WHITEPAPER.

A Wallet-Native Participation Passport on BOT Chain.

Not a token offering

Soilate Whitepaper v1.0

A Wallet-Native Participation Passport on BOT Chain

Version: 1.0 Date: 28 August 2026 Network: BOT Chain Status: Initial product specification; not a token offering

1. Abstract

Soilate is a wallet-native participation layer built on BOT Chain. Its first release gives a self-custodial wallet a simple, public and verifiable participation record without asking the user to deposit assets, approve tokens, trade, stake or surrender control of funds.

A user connects an external EVM wallet, switches to BOT Chain and explicitly confirms one smart-contract transaction. The standard route grants 100 non-transferable Soilate Points after the transaction receipt succeeds. A user may instead choose, or later upgrade through, an optional fixed 0.01 BOT boost that raises the wallet's total balance to 200 Soilate Points. Network gas is paid separately by the user.

Soilate Points are not an ERC-20 token, are not transferable and have no cash value. They do not guarantee an airdrop, token allocation, snapshot eligibility, governance right, financial return or any future benefit. The first release is deliberately narrow: it establishes an honest product surface, an inspectable contract and a public participation history before adding broader identity, reputation or agent-facing capabilities.

2. The Problem

Web3 onboarding often stops at a wallet connection. A connected wallet may appear active in a browser session, but the connection itself does not produce a public blockchain record. Projects frequently add points through local storage, opaque databases or unverifiable counters, leaving users unable to confirm whether their participation exists independently of the interface.

At the same time, early participation campaigns often mix product access with token speculation. Points may be presented as though they imply a future allocation, while no contract, allocation rule, snapshot date or legal commitment exists. This ambiguity creates poor user expectations and weakens product credibility.

Soilate addresses a limited version of this problem by making the initial participation rule deterministic and inspectable:

  • one wallet may create one base record;
  • the base record grants 100 Points after a successful receipt;
  • an optional exact 0.01 BOT boost raises the wallet to 200 Points;
  • a wallet may never exceed 200 Points in the first release;
  • successful records are publicly verifiable on BOT Chain;
  • the interface does not treat a wallet connection, rejected request or failed transaction as a successful claim.

This model is an address-level participation rule. It is not proof of unique personhood and does not prevent one person from controlling multiple wallets.

3. Vision

Soilate's long-term direction is to become a compact participation passport for the BOT Chain ecosystem: a public layer through which wallets can establish transparent activity records that may later be read by applications, communities and software agents.

The first release does not claim that this larger reputation network already exists. It implements only the foundation required to support it responsibly:

  1. an independent brand and public website;
  2. self-custodial wallet connection;
  3. BOT Chain network detection and switching;
  4. a fixed on-chain points registry;
  5. an optional fixed-value boost;
  6. a wallet profile and public activity surface;
  7. a complete whitepaper, privacy policy and terms;
  8. testnet verification followed by controlled mainnet deployment;
  9. production hosting on Vercel.

Soilate is guided by four principles.

Public proof before private promises. A displayed claim must be supported by a successful transaction receipt and contract state.

One clear action at a time. The interface should make the standard claim and optional boost easy to understand before a wallet request opens.

Self-custody by default. Soilate never requests a seed phrase, private key, keystore or unrestricted token approval.

Direction is not delivery. Roadmap items are labeled as future exploration and are not represented as live functionality.

4. Product Scope

4.1 Initial release

The initial release consists of a public website, wallet profile and smart-contract registry.

The standard user path is:

Visit Soilate
→ Connect an external wallet
→ Switch to BOT Chain
→ Review the standard or boosted route
→ Confirm the transaction in the wallet
→ Wait for a successful receipt
→ View 100 or 200 Soilate Points
→ Verify the transaction, block and contract on BOT Explorer

4.2 What Soilate does not do

The first release does not:

  • issue a Soilate token;
  • conduct a presale or public sale;
  • promise an airdrop;
  • publish a conversion ratio between Points and any asset;
  • offer staking, yield, APY or financial returns;
  • execute swaps, bridge transactions or trades;
  • custody deposits;
  • request token approvals;
  • mint NFTs;
  • prove unique human identity;
  • provide KYC or legal identity verification;
  • operate a live AI agent network;
  • fabricate partners, users, TVL, transaction volume or activity.

5. Why BOT Chain

BOT Chain is an EVM-compatible Layer 1 designed for AI, DePIN and Web3 applications. EVM compatibility allows Soilate to use familiar Solidity contracts, Ethereum wallet interfaces and established development tools while keeping its first interaction lightweight.

The verified network configuration used by the initial release is:

BOT Chain Mainnet
Chain ID: 677
Native token: BOT
RPC: https://rpc.botchain.ai
Explorer: https://scan.botchain.ai

BOT Chain Testnet
Chain ID: 968
Native token: tBOT / BOT test asset
RPC: https://rpc.bohr.life
Explorer: https://scan.bohr.life
Faucet: https://faucet.botchain.ai/basic

Testnet is the required first deployment environment. Mainnet deployment is permitted only after the project owner confirms the owner address, treasury address, production configuration and explicit deployment authorization.

6. Participation Flow

6.1 Wallet connection is not a claim

Connecting a wallet establishes a browser session with the user's wallet provider. It does not create an on-chain record. Soilate therefore never awards final Points merely because a connection succeeds.

After connection, the interface asks the user to choose an explicit transaction:

Standard route
Claim 100 Soilate Points
Contract value: 0 BOT
User cost: BOT Chain network gas

Boosted route
Receive a total of 200 Soilate Points
Contract value: exactly 0.01 BOT
User cost: 0.01 BOT plus BOT Chain network gas

No transaction is sent automatically. The user sees the network, contract, action, value and estimated gas before confirming in the wallet.

6.2 Standard claim

A wallet that has not claimed before may call claimStandard(). The call sends zero BOT value. After a successful receipt, the registry records 100 Points, the claim timestamp and the claim block.

6.3 Direct boosted claim

A wallet that has not claimed may call claimBoost() with exactly 0.01 BOT. A successful call creates the base record and boost in one transaction, resulting in 200 total Points.

6.4 Upgrade after a standard claim

A wallet that already holds 100 Points may call claimBoost() with exactly 0.01 BOT. A successful call adds the remaining 100 Points, resulting in 200 total Points.

6.5 Finality and display rules

The frontend may display a pending state after a transaction hash is returned, but it must not display final Points until the transaction receipt reports success and the contract profile has been read again.

Rejected, reverted, timed-out or incorrectly configured transactions do not increase the displayed or on-chain Points balance.

7. Soilate Points

Soilate Points are non-transferable participation records maintained by the Soilate registry contract.

The first-release constants are:

Base Points: 100
Boost Points: 100
Maximum Points per wallet: 200
Boost fee: exactly 0.01 BOT

Points:

  • are not an ERC-20 token;
  • cannot be transferred between wallets;
  • cannot be sold or withdrawn;
  • cannot be redeemed for cash;
  • do not represent equity, ownership or debt;
  • do not provide yield or interest;
  • do not guarantee access, allocation, governance or rewards;
  • remain associated with the wallet address that completed the transaction.

A wallet address is not equivalent to a unique person. Soilate's one-claim-per-address rule is not a Sybil-resistance or identity-verification system.

8. Smart-Contract Architecture

The initial contract is named:

SoilateGenesisRegistry.sol

The contract is intentionally narrow. It uses stable Solidity 0.8.x tooling and established OpenZeppelin components, including Ownable2Step, Pausable and ReentrancyGuard.

8.1 Core rules

  • claimStandard() is available once per wallet and accepts no payment.
  • claimBoost() is available once per wallet and requires exactly 0.01 BOT.
  • A direct boost grants both base and boost records when the base has not been claimed.
  • A later boost upgrades a 100-Point wallet to 200 Points.
  • A wallet can never exceed 200 Points.
  • The contract has no administrator function to add, remove or edit an individual wallet's Points.
  • The boost fee is forwarded to an immutable treasury address during the successful transaction.
  • A failed treasury transfer reverts the entire boost, including the Point update.
  • Direct native-token transfers and unknown calls revert.
  • The owner may pause or unpause new claims and may transfer ownership through a two-step process.
  • The owner cannot withdraw user deposits because the contract is not designed to retain them.

8.2 Public state

The registry exposes the connected wallet's Points, base status, boost status, timestamps, blocks and current eligibility. It also exposes aggregate participant, boosted-wallet, Points-issued and BOT-recorded counters.

8.3 Events

The contract emits events for standard claims, direct boosted claims and upgrades. Events enable third-party indexing and independent monitoring.

9. Public Activity and Data Integrity

Soilate's public activity surface must not depend entirely on scanning historical logs through the default BOT Chain public mainnet RPC, because the official RPC documentation states that eth_getLogs is disabled on that endpoint.

The first release therefore stores a small fixed-capacity recent-activity ring buffer inside the registry contract and exposes a bounded getRecentActivity(limit) view. The contract still emits events for external indexers, but the website can retrieve a trustworthy recent list without pretending that unavailable RPC log queries succeeded.

The interface follows these data rules:

  • aggregate values come from contract view functions;
  • recent activity comes from the contract ring buffer or a separately verified indexer;
  • RPC failure is shown as unavailable, not as zero;
  • an empty list is shown only after a successful read confirms no records;
  • transaction hashes, blocks and addresses link to the correct BOT Explorer;
  • no random hashes, mock wallets or fabricated protocol totals are displayed in production.

10. Security and User Control

Soilate is self-custodial. The website does not control the user's wallet and does not request a seed phrase, private key, keystore or token allowance.

Before a transaction request, the frontend must:

  1. confirm the connected address;
  2. confirm the selected BOT Chain network;
  3. confirm that a registry contract address is configured;
  4. read the wallet's current claim status;
  5. simulate the contract call;
  6. show the exact BOT value and explain that gas is separate;
  7. prevent duplicate or ineligible actions;
  8. open the wallet request only after the user presses the final confirmation button.

After submission, the frontend tracks the real transaction hash, waits for the receipt, handles reverts and reloads contract state. A page refresh may recover a pending transaction using only non-sensitive local fields such as hash, wallet, chain ID and submission time.

Smart contracts can contain defects and infrastructure can fail. A successful audit or test suite reduces risk but cannot eliminate it. Users must review the wallet request and contract address before signing.

11. Privacy

Wallet addresses, contract calls, transaction hashes, block numbers and timestamps are public blockchain information. Soilate may read and display this public information.

The first release does not require the collection of a legal name, government identity document, seed phrase or private key. Wallet connection providers, WalletConnect, RPC services, the block explorer, analytics services and Vercel may process data under their own policies.

Pending-transaction recovery may store only:

transaction hash
wallet address
chain ID
submission timestamp
action type

These values are not secret, but the Privacy Policy must disclose their purpose and retention behavior. Any future email, notification, profile or identity feature must publish a clear collection, retention and deletion policy before collecting additional personal data.

12. Administrative Boundaries

The contract owner is an operational security role, not a mechanism for discretionary rewards. Owner permissions are limited to emergency pause, unpause and two-step ownership transfer.

The owner cannot:

  • assign Points to a chosen wallet;
  • remove Points;
  • change an individual record;
  • exceed the fixed per-wallet maximum;
  • alter a successful historical transaction;
  • use a backend database to override contract state in the interface.

The treasury address is immutable in the initial deployment. The project owner must provide and verify it before deployment. A personal developer wallet must not be used as an undisclosed production treasury.

13. Token and Airdrop Policy

Soilate has not announced a token through this Whitepaper. Soilate Points are not a token and do not establish eligibility for a future token.

No airdrop is promised. No snapshot date, allocation formula, conversion ratio, expected token value, reward schedule, governance right or financial return is defined. A Points balance does not create a contractual right to any future benefit.

Soilate may explore future uses for public participation records. Any material change would require a separate announcement, updated terms, technical review and legal review. Users must not infer such a change from the first-release Points balance.

14. Roadmap

The roadmap describes direction rather than guaranteed delivery dates.

Foundation — Active scope

  • template-based public website;
  • original Soilate brand and SVG logo system;
  • BOT Chain wallet connection;
  • standard and boosted participation routes;
  • wallet account page;
  • public recent activity;
  • Whitepaper, Privacy and Terms;
  • testnet deployment, QA and Vercel production release.

Root Profiles — Planned exploration

  • richer public wallet participation profiles;
  • optional labels derived only from verified contract records;
  • portable read-only profile interfaces for ecosystem applications.

Reputation Adapters — Planned exploration

  • adapters for additional verified BOT Chain activity;
  • clear source, timestamp and confidence boundaries;
  • no hidden manual editing of public records.

Agent Access — Long-term exploration

  • structured read APIs for authorized applications and software agents;
  • authentication, rate limits, observability and abuse controls;
  • explicit separation between raw records and derived reputation signals.

15. Risks and Disclaimers

Blockchain transactions may be irreversible. Users must verify the network, wallet, registry contract, treasury address, transaction value and gas estimate before signing.

The optional 0.01 BOT boost is not a deposit, stake or investment. It does not earn yield or create a right to repayment. After a successful irreversible transaction, it may be non-refundable unless the project publishes a separate policy.

Wallet providers, RPC endpoints, explorers, browsers, smart contracts and hosting infrastructure may fail or become temporarily unavailable. Network congestion, a paused contract, insufficient gas balance, incorrect configuration or a failed treasury transfer may prevent a claim.

Soilate does not provide investment, brokerage, financial, legal or tax advice. Nothing in the website or Whitepaper is a promise of profit, token value, airdrop eligibility, governance power or protocol ownership.

The project should obtain independent technical and legal review before a public mainnet launch.

16. Conclusion

Soilate begins with a small, inspectable promise: a wallet can create one public participation record on BOT Chain, receive a fixed non-transferable Points balance and independently verify the result.

The standard path transfers no BOT value to the protocol and requires only network gas. The optional boost accepts exactly 0.01 BOT and raises the wallet to a fixed maximum of 200 Points. Every successful result must be supported by contract state and a real transaction receipt.

This foundation is intentionally more limited than the long-term vision. Soilate's credibility depends on keeping live functionality, future direction and speculative expectations clearly separated.