Anova Fine-Tuning Policy

Last updated: Thursday, August 28th, 2025

This policy explains the rules and expectations for community participants who help fine-tune the Anova Large Language Model (LLM) in exchange for $BB payouts.

1. Submission Review

All submissions are subject to a formal review process for accuracy, quality, and compliance with this Fine-Tuning Policy. Reviews are conducted by our internal team and may include both automated checks and manual evaluation. The standard review period is up to 2 weeks from the date of submission; however, this timeframe is provided as an estimate only and does not create a binding obligation.

By participating in the fine-tuning program, you expressly acknowledge and agree that:

• The review process may be delayed, suspended, or extended at our sole discretion, including (but not limited to) delays caused by submission volume, technical issues, or the complexity of the material.
• We reserve the right to modify, shorten, or extend the review timeframe at any time without prior notice to participants.
• No payout, credit, or other form of compensation is owed to the participant solely on the basis of a submission being under review.
• Acceptance or denial of a submission is final and not subject to appeal or dispute once the review process is complete.
• We are under no legal obligation to provide justification or reasoning for denial, although such reasoning may be provided at our discretion.

The review process is an integral part of maintaining the integrity of the Anova fine-tuning program. Submissions are evaluated objectively, and we retain the exclusive right to determine whether a submission meets the quality and compliance standards required for payout eligibility.

2. Minimum Requirements

To ensure the fine-tuning process of Anova remains high-quality, fair, and beneficial for all participants, all submissions must meet the following minimum requirements:

• Length Requirement: Any question or answer under 250 characters in length is automatically denied without review.
• Effort and Clarity: Submissions must demonstrate genuine effort and provide clear, structured responses. Content that is rushed, vague, incoherent, or incomplete will not be accepted.
• Readability: Answers should be written in a way that is understandable to non-technical readers whenever possible. Overly complex, overly technical, or jargon-heavy answers that do not add value may be denied.
• Relevance: Submissions must directly address the specific question or prompt provided. Off-topic answers, generic content, or material unrelated to the question will be denied.
• Accuracy and Reliability: All submissions must be factually correct and up to date. Outdated, misleading, or incorrect information will result in denial.
• Code Quality: Any code provided must be directly relevant, functional, and executable. Code that does not run, contains obvious errors, or fails to address the problem will be denied.
• Fraud and Misuse: Submissions that are fraudulent, spam-like, plagiarized, or intended to take advantage of the payout system will be denied. Claims of fact or copied material must include proper citations where appropriate.
• Professionalism: Answers must maintain a professional and respectful tone. Submissions that include offensive, harmful, or otherwise inappropriate content will be denied.
• Originality: Submissions must be original and provide value beyond simple rephrasing or repetition of existing content. Duplicate or low-effort submissions may be denied.
• Quality Assurance: We reserve the right to deny any submission that, in our judgment, fails to meet the quality, accuracy, or integrity standards of this program—even if the specific issue is not explicitly listed above.

3. Grounds for Refusal

We reserve the right to refuse payout to any participant at our sole discretion. Submissions may be denied if they fail to meet the required standards of quality, accuracy, and integrity. Grounds for refusal include, but are not limited to:

• Repeated Low-Quality Submissions: Providing answers that are inaccurate, incomplete, vague, or otherwise lacking in quality on a consistent basis.
• Spam and Abuse: Attempting to “game the system” with meaningless, irrelevant, or mass-generated content intended to earn payouts without contributing value.
• Irrelevant or Unacceptable Content: Submissions that do not directly address the question, are off-topic, contain inappropriate material, or fail to meet the intent of the prompt.
• Plagiarism and Misrepresentation: Copying existing content without proper citation, submitting third-party work as one’s own, or fabricating sources or references.
• Fraudulent Behavior: Any attempt to manipulate results, falsify information, or exploit the payout process for unfair gain.
• Outdated or Incorrect Information: Providing information that is no longer accurate, current, or relevant to the subject matter.
• Non-Functional Code: Submitting code that does not compile, execute, or otherwise fails to solve the described problem.
• Offensive or Harmful Submissions: Content that is abusive, discriminatory, or violates community standards.

Any behavior that undermines the fairness, integrity, or educational purpose of the fine-tuning process may result in denial of payouts and, in severe cases, permanent exclusion from participation.

4. Anonymity and Data Storage

The fine-tuning platform is designed to operate as a fully anonymized system. We do not collect, track, or store any personally identifiable information (PII) from participants. The only data stored in relation to a submission includes:

• The question being answered.
• The answer text provided by the participant.
• Any code that is submitted as part of the response.
• The participant’s wallet address, strictly for payout purposes.

To improve user experience, the provided wallet address may be stored in the participant’s local browser storage for a maximum of 12 hours. This temporary storage exists solely on the user’s device and is not transmitted to, or retained by, our servers. Once expired, the wallet address is automatically removed and must be re-entered by the user.

No names, email addresses, IP logs, account registrations, or other identifying details are collected. As a result, we have no ability to determine the real-world identity of the person behind any given submission. All evaluation, acceptance, and payout decisions are made solely on the content submitted and the wallet address provided for payment.

Because of this design, it is the participant’s sole responsibility to ensure their wallet address is valid and correct. If payouts are made to an invalid, incorrect, or inaccessible wallet, we cannot recover those funds or reissue them elsewhere.

5. Payouts

Payouts are calculated based on the following factors:

• The current market price of $BB (Backyard Bandwidth, Solana-based token, contract address: E7MYzWD8GtLYNsgRyECSts2p1s2mu5JLb6wR9CiCBAGS): Loading... USD
• Question complexity (scope, required depth, difficulty, and originality).
• Answer quality (technical accuracy and completeness).
• Functional correctness (whether the solution works as intended during our internal review).
• Clarity & readability (grammar, structure, comments, and overall ease of understanding).
• Coverage (does the answer address all parts of the prompt and any sub-requirements?).
• Security & robustness (safe handling of inputs, error handling, and reasonable performance where relevant).
• Originality (no plagiarism; cite external sources or licenses when applicable).
• Policy compliance (adheres to program rules and content guidelines).

Bonuses & deductions. We may apply discretionary bonuses for exemplary solutions (e.g., superb documentation, thoughtful edge-case handling, or performance improvements) and deductions for issues (e.g., inaccuracies, incomplete coverage, unclear writing, runtime errors, missing required artifacts, or policy violations).

Who handles validation. We perform all validation and execution on our side. You are not required to perform or provide automated testing.

How conversion works. Payout decisions are made in USD terms for clarity. The on-chain amount of $BB is calculated from the real-time USD price of $BB at the moment we send the transaction. Network fees are not deducted from your payout amount but are paid separately as part of the transfer process.

Transparency. To improve trust in the process, we may publicly display acceptance/denial decisions with the submitted wallet address, decision reason, and decision date. Do not include any personal information in your submission.

Finality. We are not responsible for payouts sent to invalid or incorrectly provided wallet addresses. If you provide an incorrect wallet, we cannot reverse or reissue the payout. All on-chain transfers are final.

6. Compliance with Other Policies

All participants in the fine-tuning program are required to abide by all other Backyard Bandwidth policies located at policy-list.html.

7. Changes to This Policy

We may revise this Fine-Tuning Policy at any time. Updates will be posted on this page and become effective immediately upon publication.