Skip to content

dYdX Improvement Proposals

License

AGPL-3.0, MIT licenses found

Licenses found

AGPL-3.0
LICENSE
MIT
Gatsbyjs-LICENSE
Notifications You must be signed in to change notification settings

dydxfoundation/dip

Repository files navigation

Contributing

  1. Fork this repository by clicking 'Fork' in the top right.
  2. Add your DIP to your fork of the repository in the content/dips/ directory. Use the DIP template.
  3. Submit a Pull Request (PR) to the Pending DIPs branch.

Your first PR should be a draft of the final DIP. It must follow the formatting criteria enforced by the build, as detailed in the DIP template. Make sure you include a discussions-to header with the URL to a discussion forum or open GitHub issue where people can discuss the DIP as a whole.

If your DIP requires images, the image files should be included in a subdirectory of the assets folder for that DIP as follow: assets/DIP-X (for DIP X). When linking to an image in the DIP, use relative links such as ../assets/DIP-X/image.png.

When you believe your DIP is mature and ready to progress past the WIP phase, you should ask to have your issue added to the governance discord where it can be discussed for inclusion in a future platform upgrade. If the community agrees to include it, the DIP editors will update the state of your DIP to 'Approved'.

DIP Statuses

  • WIP - a DIP that is still being developed.
  • Proposed - a DIP that is ready to be proposed on-chain.
  • Approved - a DIP that has been accepted for implementation by the dYdX community.
  • Implemented - a DIP that has been released to mainnet.
  • Rejected - a DIP that has been rejected.

About

dYdX Improvement Proposals

Resources

License

AGPL-3.0, MIT licenses found

Licenses found

AGPL-3.0
LICENSE
MIT
Gatsbyjs-LICENSE

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published