Terms of Service
Last updated: July 4, 2026
1. Acceptance of Terms
By accessing or using Zoetra (the "Service"), including the website, dashboard, smart contracts, and any associated tools, you agree to be bound by these Terms of Service ("Terms"). If you do not agree, do not use the Service.
2. What Zoetra Is
Zoetra is a permissionless, on-chain heartbeat SLA (Service Level Agreement) registry for DePIN (Decentralized Physical Infrastructure Network) devices, deployed on BOT Chain. It consists of:
- A smart contract ("the Registry") deployed at a public address on BOT Chain, which anyone can read, call, or verify independently.
- A web dashboard that reads from and writes to the Registry.
- An optional heartbeat client ("the daemon") that any device operator may run to send heartbeat transactions.
- One optional, stateless webhook relay endpoint for breach notifications.
Zoetra does not operate, own, or control any physical device. Zoetra does not custody funds beyond what the Registry contract itself holds as stake, and does so entirely via public, auditable smart contract logic, not through any centralized account or admin key.
3. No Account, No Registration
There is no user account system. Your identity on Zoetra is your wallet address. We do not verify identity, collect KYC information, or restrict access based on jurisdiction, though you remain responsible for complying with the laws applicable to you.
4. Eligibility
You must be legally capable of entering into a binding agreement in your jurisdiction and must not be barred from using blockchain-based services under applicable law. You are solely responsible for determining whether your use of Zoetra is lawful where you are located.
5. Mainnet Notice
Zoetra's primary deployment operates on BOT Chain mainnet (chain ID 677). Registering a device, staking, sending heartbeats, and slashing use real BOT with real economic value. Users who need BOT should bridge funds at bridge.botchain.ai and swap for BOT at dex.botchain.ai. All risks described in Section 8 apply with full force to mainnet use.
6. How the Service Works, What You're Agreeing To
By registering a device on the Registry, you acknowledge and agree that:
- You are staking real value (native BOT) against a self-declared uptime promise (the "SLA"). You choose your own heartbeat interval and SLA threshold at registration; no one else sets these for you.
- Your stake is at risk automatically and permissionlessly. If your device's on-chain uptime score falls below your declared SLA threshold, any third party, not Zoetra, not an administrator, may call the slash() function against your device. This is by design: there is no admin key, no appeal process, and no human review built into the contract. The slash executes purely based on the on-chain score at the time the transaction is processed.
- A successful slash is irreversible. Once executed, a portion of your stake is transferred to the caller as a bounty and the remainder is permanently burned. There is no refund, chargeback, or dispute mechanism.
- You are solely responsible for keeping your device's heartbeat client running. Zoetra provides a reference heartbeat client (daemon/heartbeat.mjs) as an example implementation, but you are responsible for its uptime, its private key security, and its gas funding. Zoetra is not responsible for a slash that results from your own device, key, wallet, RPC provider, or infrastructure failing.
- Withdrawing your stake requires deregistering first, followed by a cooldown period defined in the contract, after which you may withdraw remaining funds. Attempting to withdraw before deregistering or before the cooldown elapses will fail.
7. Permissionless Slashing, Acting as a Verifier
You may also call slash() against devices you do not own, if their on-chain score has fallen below their declared SLA. Doing so:
- Requires you to pay the gas cost of the transaction yourself.
- Will fail (revert) if the target device's score is not actually below its threshold at the time your transaction is processed, meaning you can lose gas fees on an unsuccessful attempt if conditions change between when you observe the breach and when your transaction executes.
- Entitles you, if successful, to a bounty (a percentage of the slashed stake), paid automatically by the smart contract, not by Zoetra.
8. Risks You Accept
Use of Zoetra involves risks inherent to blockchain technology and DeFi-adjacent mechanisms, including but not limited to:
- Smart contract risk. Although the Registry contract has been tested, no smart contract is guaranteed to be free of bugs, exploits, or unintended behavior. Funds staked in the contract may be lost due to a vulnerability, regardless of intent.
- Irreversibility. Blockchain transactions, including registrations, heartbeats, slashes, and withdrawals, cannot be reversed, cancelled, or refunded by Zoetra once confirmed.
- Network and RPC risk. Zoetra depends on BOT Chain's network, public RPC endpoints, and block explorers operated by third parties. Outages, forks, reorganizations, or changes to these services are outside Zoetra's control and may affect scoring, transaction delivery, or dashboard accuracy.
- Score-timing risk. The uptime score is computed live from block.timestamp and your device's heartbeat history. Network congestion, RPC latency, or delayed transaction confirmation may cause your device to appear to have missed a heartbeat even if your daemon attempted to send one on time.
- No insurance, no recourse. There is no insurance fund, no customer support line that can reverse a transaction, and no guarantee of any kind regarding uptime, availability, or fitness for purpose.
- Third-party wallet risk. You are responsible for the security of your own wallet and private keys. Zoetra never has access to, requests, or stores your private key.
9. No Warranty
The service is provided "as is" and "as available," without warranties of any kind, express or implied, including but not limited to warranties of merchantability, fitness for a particular purpose, non-infringement, or that the service will be uninterrupted, error-free, or secure.
10. Limitation of Liability
To the maximum extent permitted by law, Zoetra, its contributors, and its operators shall not be liable for any indirect, incidental, special, consequential, or punitive damages, or any loss of funds, stake, data, or profits, arising out of or related to your use of the service, including but not limited to losses resulting from slashing, smart contract bugs, or network failures.
11. Open Source
The Zoetra codebase, including the smart contract, dashboard, and heartbeat client, is released under the MIT License. You may inspect, fork, modify, and redeploy it subject to that license's terms.
12. Third-Party Services
Zoetra integrates with or links to third-party services it does not control, including but not limited to: BOT Chain RPC providers, the BOTScan block explorer, wallet browser extensions (MetaMask, Rabby, Coinbase Wallet, etc.), and, if you configure it, a third-party webhook destination (e.g., Discord or Slack) of your own choosing. Zoetra is not responsible for the availability, accuracy, or conduct of these third parties.
13. Changes to the Service and Terms
Zoetra may be modified, paused, or discontinued at any time. These Terms may be updated periodically; continued use of the Service after changes constitutes acceptance of the revised Terms.
14. Governing Interpretation
These Terms are intended to be interpreted in good faith, consistent with the permissionless, non-custodial nature of the Service described herein. Nothing in these Terms creates an employment, agency, partnership, or fiduciary relationship between you and Zoetra.
15. Contact
Questions regarding these Terms may be directed via the contact information listed in the project repository.