PepeX
  • ⚙️ PepeX
    • DEX: PepeX 🚀
    • PepeX Listing Process
  • WOJAK - PEPE - CHAD
    • Introduction
      • Token Overview
    • Wojak.farm (WOJAK)
    • Pepe (PEPE)
      • Understanding the Pepe Smart Contract
      • How are Pepe minted? Staking and Rewards System Staking:
      • Tax Mechanism and Oracle Integration
      • Contract Governance
      • Inflation: Long-Term Sustainability
      • The PEPE getReward Function: A Key Mechanism
    • Chad (CHAD)
      • Tokenomics
      • burnChadforEth
      • Fixed Supply + Ownership Renounced
  • Official links and information
    • Links
    • Contract Addresses (ETH)
  • Guides
    • Developer Contribution Guide
    • How to bridge Pepe: ETHEREUM -> BASE
Powered by GitBook
On this page

Was this helpful?

  1. Guides

Developer Contribution Guide

To ensure a smooth and transparent process for design improvements, the following steps outline the procedure from proposal to payment:

  1. Proposal Submission:

    • Developers interested in contributing should first submit a proposal outlining the specific changes or improvements they intend to make.

    • The proposal should include a clear description of the changes and a price quote for the work.

    • Submit the proposal via a pull request (PR) or through a designated communication channel as specified by the maintainers.

  2. Budget Approval:

    • The proposal will be reviewed by the project maintainers.

    • If the maintainers approve the proposed changes and budget, they will confirm the agreement.

    • If the proposal is denied, maintainers will provide feedback or request modifications to the proposal.

  3. Payment Process:

    • A designated wallet will be used to handle payments.

    • Upon budget approval, the wallet address for the project will be provided to the developer.

    • The developer can then begin coding the approved changes.

  4. Development & Submission:

    • The developer implements the changes as per the approved proposal.

    • Once the changes are ready, the developer submits a pull request (PR) with the updated code for review.

  5. Code Review:

    • The maintainers will review the submitted code to ensure it meets the agreed-upon requirements and quality standards.

    • Any necessary revisions or feedback

PreviousContract Addresses (ETH)NextHow to bridge Pepe: ETHEREUM -> BASE

Last updated 9 months ago

Was this helpful?