Skip to content

Latest commit

 

History

History
64 lines (41 loc) · 3.69 KB

README.md

File metadata and controls

64 lines (41 loc) · 3.69 KB
Raw

Paseo Testnet Support

Welcome to the Paseo Testnet Support repository. This repository serves as the main hub for the Paseo community to seek support, report issues, and contribute to the ongoing improvement of the Paseo Testnet.

How to Use This Repository

This repository is intended for reporting issues related to the Paseo Testnet, requesting new features, and seeking support for development and deployment challenges.

Creating an Issue

To report a bug, request a feature, or seek support:

  1. Go to the Issues tab of this repository.
  2. Click on New Issue to create a new issue.
  3. Choose the appropriate issue template (Bug Report, Feature Request, or General Support).
  4. Fill out the template with all the necessary details. Be as specific as possible to help us understand and address your concern efficiently.
  5. Submit the issue.

🧳 Migrate Parachain State and History Across Relaychains

If you need to migrate the state and history of your parachain from one relaychain to another, we provide a comprehensive guide that covers this complex process. This guide is particularly useful for parachain maintainers who need to transfer their operations without losing historical data or state continuity.

Key Steps Covered:

  • Disabling relaychain block number checks.
  • Exporting current state and moving to a new chainspec.
  • Managing node transitions and ensuring data integrity throughout the process.
  • For a detailed step-by-step process, please refer to our full migration guide:

🧳 Migrate your parachain from Rococo to Paseo

If you are the maintainer of a parachain running on Rococo, or any other relay testnet, and you are looking to keep your parachain running in Paseo, please go ahead and follow the migration guide:

It showcases two ways of doing the migration. A re-gensis or a migration keeeping state and history.

Tagging Issues

When creating an issue, please tag it appropriately using the labels provided:

  • bug: For issues that represent errors or unexpected behavior.
  • feature request: For suggestions on new features or improvements to existing ones.
  • question: For general inquiries or support requests.
  • documentation: For issues related to documentation.
  • core: For support activities assigned to the Paseo Core Team.

How to Contribute

We welcome contributions from the community. Here are ways you can contribute:

  • Report issues or suggest features: Use the Issues tab to report problems or suggest new features.
  • Improve documentation: If you have suggestions or corrections for the documentation, please open an issue or submit a pull request.
  • Resolve issues: Feel free to pick up open issues, especially those labeled as good first issue or help wanted. Before starting work on an issue, please comment that you're taking it on to avoid duplications of effort.

Support and Community

Join our community on [Element] for real-time discussions, support, and collaboration. Whether you're seeking technical support, want to share ideas, or just want to connect with other Paseo Testnet users and developers, our community is open and welcoming to everyone.

Acknowledgments

  • Thanks to all the contributors who have helped shape the Paseo Testnet Support repository.
  • Special thanks to the Paseo Network team and the broader Polkadot community for their ongoing support and collaboration.