OPID

Optimism ID is the result of a Mission Request from the optimism community. The goal of this mission is to provide applications on Optimism with a toolkit that enables trusted, secure relationships between apps and users, emphasizing self-sovereign identity and privacy. While Privado ID is technically chain-agnostic, it was primarily designed for Polygon and required some adjustments to function on Optimism. Optimism ID is a fork of Privado ID, specifically tailored to simplify the implementation of the ZK identity toolkit on the Optimism network.

Privado ID

Privado ID Documentation is the documentation hub providing extensive documentation, community resources, and guides for enthusiasts and developers interested in learning about or building solutions using Privado ID.

Disclaimer

OPID is a fork from Privado Id with the aim to make identities available in the Optimism blockchain. In this repo we took Privado Id documentation and adapted it for use in Optimism with OPID. So feel free to jump back and forth with Privado Id resources.

Contribute to OpId Documentation

After running the docs locally on your machine, use a code editor to apply your changes before submitting your PR. Note that you must have a GitHub account and an understanding of Markdown syntax.

1. Create a new branch for your changes.

   git checkout -b [new_branch_name]
   

2. Commit your changes. In the commit message, please reference the issue it resolves. For help, see GitHub Docs: Linking a pull request to an issue using a keyword.

   git commit -m "brief description of changes"
   

3. Push to your forked repository.

   git push
   

4. Submit a PR against the main branch of the wakeup-labs/opid-docs repo.

5. Add a title to your PR with appropriate labels.

   For example, if you want to suggest edits to the "Develop" page, name your PR: update: develop.md.

6. Add a description to your PR. Please reference the issue it resolves.

   For help, see GitHub Docs: Linking a pull request to an issue using a keyword.

7. Write a brief description of the changes you have made. If possible, include screenshots and references.

Submit an Issue

• Create a new issue to report a bug, request a feature, or suggest changes.

• Comment on the issue if you want to be assigned to it so our team can assign the issue to you.

• If you do not have a specific contribution in mind, you can also browse current issues.

• Issues that additionally have the good first issue label are considered ideal for first-timers.