Skip to main content

Overview

Contribution types define the different ways you can earn points in the GenLayer Testnet Program. Each type has specific requirements, point ranges, and evidence expectations.

Categories

Contribution types are organized into three main categories based on participant roles:

Validator

Node operation and network participation

Builder

Development, documentation, and technical content

Steward

Community management and support

Understanding Point Ranges

Each contribution type has:
  • Minimum Points: Lowest value for this type
  • Maximum Points: Highest value for this type
  • Actual Points: Determined by steward during review based on:
    • Quality of work
    • Impact on community
    • Complexity and effort
    • Evidence provided
Point ranges give stewards flexibility to reward contributions fairly based on their individual merit.

Global Multipliers

All point values are multiplied by the Global Multiplier to calculate your final points.
For example:
  • Contribution awarded: 50 base points
  • Current global multiplier: 2.0x
  • Your total points: 100 global points
Multipliers can change over time based on program phase, but your earned points are frozen at the time of contribution and never change retroactively.

Validator Contribution Types

Node Upgrade

Description: Upgrading your validator node to a new target version Requirements:
  • Must be a validator
  • Update node to match current target version
  • Update node version in your profile
Evidence:
  • Node version field in profile shows updated version
  • Optional: Screenshot of node status
  • Automatic verification via validator wallet linking
Point Range: Typically 10-50 points Frequency: Each time a new target version is released
When GenLayer releases a new node version:
  1. Target version is set in the system
  2. All validators see yellow warning: “Please update to version X.X.X”
  3. You upgrade your node following validator documentation
  4. Update node version field in your profile
  5. Submit “Node Upgrade” contribution
  6. Steward verifies and awards points

Daily Uptime

Description: Automated tracking of validator uptime Requirements:
  • Must be a validator
  • Must have linked validator wallets (via operator address)
  • Node must be online and participating in network
Evidence:
  • Automatic - no manual submission needed
  • System queries GenLayer blockchain daily
  • Points awarded automatically for each day your validator is active
Point Range: Fixed daily points (e.g., 10 points/day) Frequency: Daily (automatic)
Daily uptime is tracked automatically. You do NOT submit these manually. Link your validator wallets to enable automatic tracking.

Network Participation

Description: Active participation in network consensus and validation Requirements:
  • Must be a validator
  • Participate in block validation
  • Maintain high uptime percentage
Evidence:
  • Explorer links showing your validator address
  • Statistics screenshots
  • Participation metrics
Point Range: 20-100 points depending on activity level Frequency: Monthly summaries

Validator Bug Reports

Description: Reporting bugs in the GenLayer node software or network Requirements:
  • Detailed bug description
  • Reproduction steps
  • Expected vs actual behavior
  • Environment details (OS, node version, etc.)
Evidence:
  • GitHub issue link (preferred)
  • Discord bug report link
  • Detailed written report with screenshots
Point Range: 10-200 points based on severity and detail Frequency: As discovered

Builder Contribution Types

Contract Deployed

Description: Deploying a smart contract to GenLayer testnet Requirements:
  • Contract must be deployed to GenLayer testnet
  • Contract should be functional (not just “Hello World”)
  • Provide contract address or transaction hash
Evidence:
  • GenLayer Explorer transaction link
  • Contract address
  • GitHub repository with contract source code (recommended)
  • Description of contract functionality
Point Range: 25-500 points based on complexity Examples:
  • Simple token contract: 25-50 points
  • DeFi protocol: 100-300 points
  • Complex dApp: 200-500 points
Frequency: Per unique contract

GitHub Repository

Description: Creating a public repository related to GenLayer Requirements:
  • Repository must be public
  • Must contain substantial code (>100 lines)
  • README with clear description
  • Related to GenLayer ecosystem
Evidence:
  • GitHub repository URL
  • README describing the project
  • Commit history showing your work
Point Range: 50-300 points based on project scope Examples:
  • SDK/library: 100-200 points
  • Developer tool: 100-250 points
  • Example dApp: 50-150 points
  • Full application: 200-300 points
Frequency: Per unique repository
Linking your GitHub account in your profile is required for GitHub-related contribution types.

Blog Post / Article

Description: Technical writing about GenLayer Requirements:
  • Published on public platform (Medium, Dev.to, personal blog, etc.)
  • Minimum 500 words
  • Original content (not plagiarized)
  • Relevant to GenLayer ecosystem
Evidence:
  • URL to published article
  • Author profile showing it’s your content
Point Range: 30-150 points based on depth and reach Examples:
  • Tutorial: 50-100 points
  • Technical deep-dive: 75-150 points
  • Getting started guide: 30-75 points
  • Opinion/analysis piece: 40-80 points
Frequency: Per unique article

Tutorial / Documentation

Description: Educational content teaching GenLayer concepts Requirements:
  • Clear step-by-step instructions
  • Code examples (if technical)
  • Screenshots or diagrams (recommended)
  • Publicly accessible
Evidence:
  • URL to tutorial
  • Video link (if video tutorial)
  • GitHub repo with tutorial code
Point Range: 50-200 points based on completeness and production value Examples:
  • Video tutorial: 100-200 points
  • Written walkthrough: 50-100 points
  • Interactive guide: 75-150 points
Frequency: Per unique tutorial

Developer Tool

Description: Creating tools to help GenLayer developers Requirements:
  • Functional tool
  • Public availability (GitHub, npm, etc.)
  • Documentation on how to use
Evidence:
  • GitHub repository
  • Published package link (npm, PyPI, etc.)
  • Demo or screenshots
Point Range: 100-500 points based on utility and polish Examples:
  • CLI tool: 100-200 points
  • VS Code extension: 150-300 points
  • Testing framework: 200-400 points
  • IDE integration: 250-500 points
Frequency: Per unique tool

Builder Bug Reports

Description: Reporting bugs in GenLayer tooling, SDKs, or documentation Requirements:
  • Clear description
  • Reproduction steps
  • Expected vs actual behavior
Evidence:
  • GitHub issue link
  • Screenshots or error logs
  • Sample code demonstrating the bug
Point Range: 10-150 points based on impact Frequency: As discovered

Community Education

Description: Teaching others about GenLayer through workshops, AMAs, or presentations Requirements:
  • Public event or session
  • Educational focus
  • Recorded or documented
Evidence:
  • Event announcement link
  • Recording URL (YouTube, Twitter Space, etc.)
  • Presentation slides
  • Attendee count or engagement metrics
Point Range: 50-300 points based on reach and quality Frequency: Per unique event

Steward Contribution Types

Steward contribution types are typically assigned by lead stewards rather than self-submitted.

Community Support

Description: Helping community members in Discord, Telegram, or forums Requirements:
  • Active support activity
  • Helpful responses
  • Professional conduct
Evidence:
  • Message links
  • Screenshots of support provided
  • Community feedback
Point Range: 20-100 points based on volume and quality Frequency: Weekly or monthly summaries

Documentation

Description: Creating or improving official GenLayer documentation Requirements:
  • Contributions to official docs
  • Clear, well-written content
  • Accurate technical information
Evidence:
  • Pull request links
  • Published documentation URLs
  • Before/after comparisons
Point Range: 50-200 points per contribution Frequency: Per documentation update

Translation

Description: Translating GenLayer content to other languages Requirements:
  • Accurate translation
  • Native or fluent language proficiency
  • Maintains technical accuracy
Evidence:
  • Translation document or PR
  • Published translated content
  • Language and scope details
Point Range: 30-150 points based on length Frequency: Per translation project

Event Organization

Description: Organizing community events, hackathons, or meetups Requirements:
  • Public event
  • GenLayer-focused
  • Community participation
Evidence:
  • Event announcement
  • Participant count
  • Photos or recordings
  • Post-event summary
Point Range: 100-500 points based on scale Frequency: Per event

Content Moderation

Description: Moderating community channels and maintaining guidelines Requirements:
  • Active moderation
  • Fair enforcement of rules
  • Professional conduct
Evidence:
  • Typically tracked internally by lead stewards
  • Moderation logs (if available)
Point Range: 50-150 points for regular periods Frequency: Monthly

Submittable vs Non-Submittable Types

Submittable Types

Most contribution types are submittable - you can submit them yourself:
  • Appear in contribution type selector
  • You fill out submission form
  • Goes through steward review

Non-Submittable Types

Some types are not submittable - only stewards/admins can create:
  • Daily Uptime (automatic)
  • Builder Welcome (journey completion)
  • Validator Waitlist (journey completion)
  • Special recognition awards
These don’t appear in your submission form.

Viewing Type Statistics

On contribution type pages, you can see:
  • Total Contributions: How many times this type has been awarded
  • Unique Contributors: How many people have earned this type
  • Total Points Given: Sum of all points awarded for this type
  • Last Earned: Most recent contribution of this type
  • Current Multiplier: Active global multiplier

Tips for Each Category

For Validators

Stay Updated

Upgrade your node promptly when new versions release

Link Wallets

Connect your validator wallets for automatic uptime tracking

Document Issues

Keep detailed notes on any bugs you encounter

Maintain Uptime

High uptime = consistent daily points

For Builders

Start Simple

Begin with contract deployments and blog posts

Build in Public

Share your repos and documentation publicly

Focus on Quality

One great tutorial > five mediocre ones

Link GitHub

Required for code-related contributions

For Stewards

Be Consistent

Regular community support earns steady points

Track Your Work

Keep links and screenshots of your contributions

Collaborate

Work with other stewards on larger projects

Stay Professional

Your conduct represents GenLayer

Next Steps

Submit a Contribution

Ready to submit? Learn the submission process

Evidence Guidelines

Best practices for providing proof of your work

Build docs developers (and LLMs) love