Verax Attestation Registry
  • 👋Introduction
  • ⚒️Getting Started
  • Core Concepts
    • High-Level Overview
    • Attestations
    • Schemas
    • Linked Data
    • Modules
    • Portals
    • Ecosystem
  • Developer Guides
    • ♒For Attestation Issuers
      • Create and register a Schema
      • Create a Module
      • Register a Module
      • Create a Portal
      • Register a Portal
      • Create an Attestation
      • Encoding Attestation Data
      • Revoke an Attestation
      • Replace an Attestation
      • Link Attestations
      • Bulk Create Attestations
      • EAS compatibility
    • 🧑‍🏫Tutorials
      • From a Schema to an Attestation
      • Using Ceramic to store the Attestation Payload
    • 🚀Examples
    • 🌐Using the Subgraph
    • 🛠️Using the SDK
  • Discover
    • 📚Modules Standard Library
      • ECDSAModule
      • ERC1271Module
      • FeeModule
      • IndexerModule
      • IssuersModule
      • SchemaModule
      • SenderModule
    • 🤝Integrations
  • Get Involved
    • Get in Touch
    • Contribute
    • Governance
      • Governance Charter
      • Governance Parameters
      • Overview of Governance
      • Proposal Templates
Powered by GitBook
On this page
  • 🛠️ Product Contributions
  • 🚀 First-Time Contributors
  • 🎨 Design, UX, and UI
  • 📚 Documentation Contributions
  • 🐛 Bug Reports
  • 🔧 Bug Fixes
  • 🔒 Vulnerability Reporting
  • 📦 Dependencies Upgrades
  • 💬 Still Have Questions?
  1. Get Involved

Contribute

PreviousGet in TouchNextGovernance

Last updated 5 months ago

Verax is an open-source, community-driven project. It thrives on contributions from the ecosystem at all levels—whether it’s brainstorming ideas, implementing features, or maintaining the codebase.

And guess what? Yes, you! You can shape the roadmap, propose new features, and contribute to any component of the Verax stack. Here’s a guide to the many ways you can get involved and make a difference.

🛠️ Product Contributions

Verax already offers a robust set of features and supports a variety of use cases. But maybe you’ve spotted something missing? Or thought of a new feature that could unlock exciting possibilities?

  • Submit ideas and suggestions: Share your thoughts as .

  • Discuss with the community: Not sure what to propose? Start a debate on our . Once the discussion is mature, summarize it into a GitHub issue.

🚀 First-Time Contributors

Feeling overwhelmed? Don’t worry—we’ve got you!

  • Explore “”: These are handpicked tasks that are simple, well-documented, and perfect for beginners.

  • Need help?: Ping us anytime on . We’re here to guide you.

🎨 Design, UX, and UI

Great design enhances usability, and we welcome your creativity!

  • Submit your ideas: Have concepts for improving how Attestations are displayed?

  • Share designs: Send us Figmas, mockups, or any design feedback.

  • Explore visual upgrades: Help us enhance the Explorer or make our website shine.

📚 Documentation Contributions

Our documentation is shaped by community feedback, but it’s always evolving.

  • Prefer a simpler approach?: Draft your ideas in Notion, Google Docs, or your favorite tool and share the link. We’ll handle the Markdown and integration!

🐛 Bug Reports

Found a bug? Uh-oh! Don’t worry—here’s how to help us fix it:

🔧 Bug Fixes

If you’ve found a solution to an issue listed in our repository:

  • Submit a Pull Request (PR): Fix the bug and let the community celebrate your contribution!

🔒 Vulnerability Reporting

We prioritize security, but if you’ve discovered a vulnerability, we need to know.

📦 Dependencies Upgrades

Keeping our dependencies up-to-date ensures Verax remains modern and reliable.

  • Use pnpm workflows: Upgrade or fix dependency versions to avoid deprecated libraries in the stack.

💬 Still Have Questions?

Not sure how to contribute or have an idea that doesn’t fit into these categories? Let’s talk!

  • Share your thoughts, and together, we’ll make the Attestation world better!

Contributing to Verax isn’t just about code—it’s about building a better ecosystem together. So, jump in, share your ideas, and leave your mark. We can’t wait to collaborate with you!

Need something new?: to request a specific topic or tutorial.

Ready to write?: in the documentation repository.

Report it: describing the bug. Our team will take it from there!

Contact us privately: Reach out via to ensure a secure and timely resolution.

Reach out on , , or .

GitHub issues
Community Forum
Good First Issues
Discord
Open a GitHub issue
Open a PR
Open a GitHub issue
email
Discord
Twitter
Lens