Terms of Use

Last updated: September 4, 2026

Status: Draft for project-owner and legal review

1. Acceptance

These Terms govern access to the Machine Bridge website, wallet-verification flow, Machine Profile, Public Proof, optional Boost, Activity and related materials.

The production operator's verified legal identity, contact method, governing law, dispute process and any required regional terms must be added before public production.

By using the service, a user agrees to the final Terms then in effect. A user who does not agree should not use the service or submit a transaction.

2. Product description

Machine Bridge is a wallet-native participation interface. The foundation release may allow a compatible self-custody wallet to:

• connect to the website;
• confirm ownership using a readable message;
• receive one 100-point application record;
• optionally record one zero-value Public Proof;
• optionally submit one exact 0.01 BOT Boost;
• receive an additional 100 Points only after successful receipt verification;
• view profile and public transaction records.

Machine Bridge is not represented as a live cross-chain asset bridge, exchange, lending market, yield product, token sale, investment service, bank, custodian, broker or financial adviser.

3. Wallet responsibility

The user is responsible for:

• controlling the wallet and device;
• protecting private keys and seed phrases;
• reviewing every message and transaction;
• verifying the amount and destination shown by wallet software;
• maintaining enough BOT for the optional Boost and separate network gas;
• understanding that public transactions are generally irreversible;
• complying with applicable law and wallet/provider terms.

Machine Bridge cannot recover a lost wallet, reverse a transaction, restore a seed phrase or guarantee wallet software.

Machine Bridge will never ask for a seed phrase or private key.

4. Ownership verification

Wallet ownership verification uses a readable, expiring message. It is not a transaction and should not move value. A successful verification may create one 100-point Machine Profile for the wallet.

The project may reject expired, invalid, replayed, automated, abusive or inconsistent requests. A browser wallet connection alone does not guarantee that a base record will be granted.

5. Machine Points

Machine Points are non-transferable application participation records.

They are not:

• a token;
• currency or stored value;
• a token allocation;
• an airdrop entitlement;
• equity, debt or revenue share;
• a governance right;
• a claim on Treasury assets;
• interest, yield or profit;
• redeemable for BOT;
• guaranteed eligibility for any future program.

A verified wallet may receive 100 base Points once. A verified successful Boost may add 100 once. The maximum foundation total is 200.

The operator may correct a demonstrable technical error through a documented process consistent with database integrity and law, but the foundation product should not offer arbitrary administrator rewards.

6. Public Proof

The optional Public Proof is a zero-value contract call. Network gas is paid separately. It does not add Points and does not guarantee identity, reputation, financial value or future eligibility.

The user must review and approve the transaction in the wallet. The interface may refuse a duplicate proof or an action while the contract is paused or unavailable.

7. Optional Boost

The Boost is voluntary. The contract accepts exactly 0.01 BOT and one Boost per wallet. Network gas is paid separately.

A confirmed Boost may be forwarded immediately to the configured Treasury and may be irreversible. The user should not submit it unless the user understands and accepts:

• exact value;
• destination;
• gas responsibility;
• one-time rule;
• public nature of the transaction;
• absence of a guaranteed refund;
• absence of a token, airdrop, return or future-benefit promise.

A submitted hash does not create Points. The transaction must succeed and pass receipt reconciliation.

8. Treasury

Boost value is forwarded to the configured Treasury. Final production disclosures should describe the operator and intended operational uses accurately. The user does not receive ownership of Treasury assets or control over their use merely by submitting a Boost.

9. Availability and changes

The service, contract, API, database, wallet providers, RPC providers, hosting or Activity index may be delayed, paused, changed or discontinued.

Roadmap items are directions rather than commitments. The operator may change or cancel future features, subject to applicable obligations. Existing public transactions remain subject to the underlying ledger.

10. Prohibited use

A user may not:

• violate law or sanctions;
• attempt unauthorized access;
• exploit, attack or overload the service or contract;
• automate abusive claims;
• bypass one-wallet limits;
• interfere with other users;
• submit malicious data;
• misrepresent affiliation;
• use the service to launder proceeds or facilitate fraud;
• request or distribute seed phrases/private keys;
• reverse engineer in violation of applicable law or license terms.

The operator may block application access, pause the contract or preserve evidence when needed for safety, maintenance or legal compliance.

11. Third-party services

Wallets, public networks, RPC providers, hosting, databases and external links are third-party services. Their terms, privacy practices, outages and defects are outside Machine Bridge's direct control.

A link to a transaction viewer does not constitute endorsement.

12. Risks

Risks include:

• smart-contract defects;
• wrong Treasury deployment;
• wallet compromise or user error;
• irreversible transactions;
• volatile BOT market value;
• gas changes;
• public-address correlation;
• provider outages;
• delayed reconciliation;
• database or deployment incidents;
• regulatory, tax and legal uncertainty;
• user speculation about future rewards;
• template or third-party intellectual-property issues.

Users should not submit a Boost based on expected financial gain.

13. No warranty

To the maximum extent permitted by applicable law, the service and materials are provided “as is” and “as available.” No warranty is made regarding uninterrupted operation, fitness, merchantability, accuracy, security, future features, Points utility, token issuance, airdrop or financial outcome.

14. Limitation of liability

The final production Terms must include a jurisdiction-appropriate limitation reviewed by counsel. It should address wallet loss, user error, market movement, gas, public-chain activity, provider failure, contract defects, data loss and indirect damages, without excluding liability that law does not permit excluding.

15. Indemnity

Where lawful, the final Terms may require users to indemnify the operator for claims arising from unlawful use, violation of these Terms or infringement of third-party rights. This clause requires legal review.

16. Governing law and disputes

Do not publish placeholder governing-law, court, arbitration or company details. Insert only verified provisions reviewed for the operator and target jurisdictions.

17. Contact

Display only a real, monitored and verified legal contact method before production.