Terms of Use

1. Scope and eligibility

Bounties is a wallet-authenticated, permissionless marketplace interface where a requester may publish work and select a service provider. You must have legal capacity to enter a binding agreement, control the wallet you use, and comply with laws that apply to you. We do not provide email, password, custodial-wallet, or guest accounts. Bounties is owned and managed by Bittrees and authored by Bittrees Technology. “Bounties,” “we,” and “us” refer to Bittrees as the owner and service manager.

2. Marketplace role

Bounties provides software and information. We are not a party to a work agreement, employer, staffing agency, fiduciary, broker, payment processor, escrow agent, arbitrator, or guarantor. Requesters and providers independently decide whether to transact and are responsible for scope, quality, permissions, licenses, delivery, payment, taxes, and legal compliance. Nothing creates employment, agency, partnership, or exclusivity.

3. Tokens and smart contracts

The escrow accepts ERC20 token contracts selected by users. Curated labels and inspection results are informational, may become stale, and are not endorsements. Anyone may inspect and use another ERC20, subject to contract behavior and network support. You must verify the chain, token contract address, metadata, source code, proxy or upgradeability status, transfer behavior, approvals, and risks before signing. Native ETH is not accepted by the escrow; WETH is a separate ERC20 contract representing wrapped ether.

Fee-on-transfer, sender-taxed, and rebasing tokens are intentionally rejected or fail closed because escrow amounts must reconcile exactly. Token value, liquidity, redemption, issuer conduct, and legal status are not guaranteed.

Smart contracts may contain defects. Transactions may fail, be irreversible, or be affected by fees, congestion, forks, wallet software, token mechanics, or third-party infrastructure. Bounties never asks for a seed phrase or private key.

4. Escrow lifecycle

The requester selects a provider and funds an ERC20 escrow record with one or more deliverables, each with a positive delivery deadline. Consecutive milestone deadlines must be more than 21 days apart so an earlier milestone’s review and revision periods cannot consume the next delivery window. The provider accepts the committed terms and submits a delivery commitment before the active deadline. During the seven-day review period, the requester may approve the delivery or request one revision for that deliverable by recording a nonzero reason commitment. A revision gives the provider seven days to submit a different evidence commitment and cannot be requested a second time for the same deliverable. After a missed delivery or revision deadline, anyone may trigger the deterministic refund, but unreleased principal is returned only to the requester.

After an original or revised submission, full payment for the active deliverable becomes permissionlessly releasable when its seven-day review period expires. The requester may cancel before provider acceptance. The website’s database is descriptive and may lag the chain; the deployed contract and canonical chain state control token movement.

5. Bilateral settlement; no dispute authority

Before final release, either participant may propose an exact provider payout between zero and the unreleased escrow principal. Only the other participant may accept that exact proposal; acceptance atomically pays the provider amount and returns the remainder to the requester. A newer proposal replaces the prior proposal. Rejected or replaced proposals do not pause or extend delivery, revision, or review deadlines. Participants should preserve evidence, communicate through verifiable channels, and may settle by mutual consent before the contract’s deterministic outcome becomes available.

Bounties has no escrow administrator, arbiter, pause key, token allowlist, unilateral clawback, or authority to decide a dispute or move escrow funds. If participants cannot agree, the contract continues under its existing deadlines and state, including the one-revision limit and release after review.

6. Profiles, content, evidence, and reviews

Wallet profiles are public and may include an optional display name, biography, link, marketplace activity, and role-specific reputation. You retain ownership of content you submit and grant us a worldwide, non-exclusive, royalty-free license to host, reproduce, format, and display it as needed to operate, moderate, and secure the service. You represent that you have the rights to submit it. Evidence URIs and commitments may be public, permanent, or independently retained.

After a Released or Settled escrow is re-verified onchain, each participant may leave one rating and review: the requester reviews service received, and the provider reviews payment received. Reviews must reflect genuine experience and may not be manipulated, retaliatory, unlawful, or misleading. We may label or hide review content under the Acceptable Use Policy without changing the underlying transaction record.

7. Hosted-interface moderation

Users may report content. Authorized moderators may hide or restore listings, reviews, and profile content in the Bounties frontend to address apparently illegal, unsafe, abusive, or prohibited content. Moderation does not edit chain history, escrow state, token balances, deadlines, or participant rights under the contract. We may limit access to the hosted interface but cannot prevent direct interaction with public contracts.

8. Prohibited use

You must follow the Acceptable Use Policy. We may preserve evidence, restrict the hosted interface, and respond to valid legal process. You remain responsible for sanctions, export-control, anti-money-laundering, consumer, labor, tax, licensing, and professional-services obligations applicable to your activity.

9. Fees, taxes, and third parties

You are responsible for network fees, wallet and RPC fees, taxes, reporting, and third-party charges. Any application fee will be disclosed before a transaction is signed. Wallets, RPC providers, block explorers, Supabase, Vercel, token issuers, storage providers, and linked sites are independent services governed by their own terms.

10. Availability, suspension, and changes

The hosted service may change, suspend, or end, including to address security, legal, operational, or integrity risks. We may update these Terms prospectively and will identify a new effective date and provide notice where required. Continued use after an update constitutes acceptance where permitted by law. Contract changes require a separate deployment and do not rewrite an existing deployed contract.

11. Disclaimers and liability

To the maximum extent permitted by law, the service is provided “as is” and “as available,” without warranties of title, merchantability, fitness, non-infringement, uninterrupted availability, token value, provider quality, requester solvency, or outcome. You use wallets, tokens, contracts, content, and counterparties at your own risk.

12. Indemnity

To the extent permitted by law, you will defend and indemnify Bittrees and the service’s authors and contributors against third-party claims, losses, and reasonable costs arising from your content, work agreement, token selection, violation of law or another person’s rights, taxes, or misuse of the service. This section does not require indemnification where prohibited by law.

13. Governing framework: the Open Metaverse

The parties voluntarily choose the Open Metaverse as the governing framework for their use of Bounties. In this agreement, that framework means self-sovereignty and informed consent; respect for property and freely made contract commitments; transparent rules and code-backed evidence; interoperability and decentralization; portable, experience-based reputation; and nonaggression against people, property, systems, and lawful autonomy.

This choice asks participants to understand and consent to the wallet signatures, token approvals, deadlines, evidence commitments, and deterministic contract outcomes they use. It favors direct resolution by the requester and provider, verifiable performance, and enforcement no broader than the authority actually expressed in code or a voluntary agreement.

The Open Metaverse is a contractual framework and set of principles. It is not a nation, sovereign, court, territorial jurisdiction, or claim of immunity from law. Nothing in these Terms waives consumer protections, privacy rights, remedies, forum rights, or other mandatory rights that cannot lawfully be waived. Any applicable nonwaivable law prevails to the extent of a conflict. If a provision is unenforceable, it will be limited to the minimum extent necessary and the remainder continues. These Terms, the Acceptable Use Policy, and the Privacy Notice form the agreement for the hosted interface. Questions or legal notices may be submitted through the official Bittrees contact channel published at bittrees.org.