stakeworld / paseo-action-submission

Paseo Tesnet - RFCs

Paseo Action Submission (PAS) Repository

Welcome to the Paseo Action Submission (PAS) Repository, the central hub for all proposals, discussions, and documentation related to the development and governance of the Paseo testnet. This repository is designed to foster collaboration and transparency within the Paseo community, enabling contributors, developers, and stakeholders to participate in shaping the future of the Paseo network.

Purpose

The Paseo Action Submission Repository serves as a structured platform for submitting, reviewing, and discussing proposals that impact the Paseo network's technical specifications, governance, features, and improvements. Our aim is to ensure that the Paseo testnet evolves in a way that meets the community's needs and adheres to high standards of quality and innovation.

PAS workflow

The individuals involved in creating a PAS are:

1. The author of the PAS
2. the Paseo Governance Team (PGT) which are the signers on the sudo multisig

When creating a PAS, please use the following statuses in the title of your PAS - this allows the community to see which proposals have been implemented and which are still in discussion. Please update the status with a PR.

• Open: Proposed and under discussion PAS
• Merged: Approved and merged PAS
• Closed: Dissaproved PAS

How to Contribute

• Submitting a PAS: To propose a new feature or change, start by creating a PAS document.
• Discussion and Review: Once submitted, the community will review and discuss the proposal. Feedback and constructive criticism are encouraged to refine and improve the proposal.
• Decision Making: Proposals will be evaluated by the Paseo governance team. Decisions will be made based on community feedback, the proposal's merit, and alignment with Paseo's objectives.
• All PAS proposals must be public domain. See in the bottom of this document for an example copyright waiver.

What belongs in a successful PAS?

Each PAS should have the following parts:

• Preamble - A header including: the PAS number, a short descriptive title (limited to a maximum of 44 characters), and the author details.
• Simple Summary - Provide a simplified and layman-accessible explanation of the PAS.
• Abstract - a short (~200 word) description of the issue or change being proposed
• Motivation - The motivation is optional but strongly suggested for all PAS proposals that propose to change the network in a significant way. For substantial network changes the motivation should clearly explain why the existing specification is inadequate to address the problem that the PAS is proposing. PAS submissions without sufficient motivation may be rejected outright.
• Specification - The technical specification should describe the syntax and semantics of any new feature.
• Copyright Waiver - All PASs must be in the public domain. See the bottom of this PAS for an example copyright waiver.

Index

Support Model

• PAS 2 - Core Support Model

PASs

• PAS 0 - Template
• PAS 1 - Onboarding Infraestructure Providers
• PAS 3 - Indexer Explorer.md
• PAS 4 - Paseo Network Support Wiki
• PAS 5 - Paseo Support Repository
• PAS 6 - Paseo Team call Schedule
• PAS 7 - Hardware Specs
• PAS 8 - Payouts
• PAS 9 - Onboard Paras Slots