What Does Not Count as Contribution¶
Not all activity is considered a contribution.
Moosh distinguishes between meaningful participation and actions that do not provide useful signals for testing, system understanding, or protocol improvement. Activities that fall into the latter category may be ignored, deprioritized, or excluded from contribution records.
The following examples outline behaviors that are generally not recognized as contributions.
Repetitive or Scripted Activity¶
Actions that are highly repetitive, automated, or scripted solely to increase activity counts do not constitute meaningful contribution.
Examples include:
- repeatedly performing the same on-chain action without variation
- artificial cycling of positions or balances
- behavior that does not reflect realistic usage or testing intent
Volume alone is not a measure of contribution.
Self-Referral and Circular Behavior¶
Referral activity is expected to reflect genuine network growth.
The following behaviors are generally excluded:
- referring oneself or accounts under the same control
- circular referrals between related accounts
- referral activity that does not result in real protocol usage
Referral signals are evaluated based on downstream participation, not surface-level actions.
Low-Quality or Non-Actionable Feedback¶
Feedback that lacks context, reproducibility, or actionable detail may not be recognized as a contribution.
Examples include:
- vague reports without clear observations
- issues already documented or explained elsewhere
- feedback that does not meaningfully improve system understanding
Quality and clarity are essential for feedback to be considered useful.
Expected Testnet Behavior¶
Certain conditions are inherent to operating a testnet and are not considered contributions.
These include:
- effects caused by testnet resets, redeployments, or configuration changes
- temporary instability or downtime
- known limitations explicitly stated in the documentation
Experiencing these conditions does not, by itself, constitute a contribution.
Behavior That Degrades the System¶
Actions that intentionally degrade system quality, distort signals, or negatively impact other participants are not recognized as contributions.
Examples include behavior intended to:
- manipulate contribution tracking
- interfere with testing objectives
- reduce clarity or reliability of system data
Such actions may result in exclusion from contribution consideration entirely.
Final Note¶
This list is not exhaustive.
Moosh reserves the right to interpret contribution signals based on context and intent, and to adjust exclusion criteria as testing goals evolve. The purpose of defining what does not count is to preserve the integrity of contribution tracking, not to restrict good-faith participation.