diff --git a/docs/incentivizedtestnet/01-getting_started.md b/docs/incentivizedtestnet/01-getting_started.md index 1cdef8fb..0e0d96f3 100644 --- a/docs/incentivizedtestnet/01-getting_started.md +++ b/docs/incentivizedtestnet/01-getting_started.md @@ -2,40 +2,42 @@ title: Getting started --- -Welcome, intrepid explorer, to the frontier of blockchain innovation! The zkVerify Incentivized Testnet offers you a great opportunity to shape the future of privacy and scalability with ZK tech. - -### Why zkVerify? -zkVerify provides rapid and inexpensive proof verification for any type of zero-knowledge proof. This enables dApp developers to implement the latest zk proving systems to generate their proofs, and zkVerify to verify them. Proofs are verified in seconds, enabling developers to create and deploy games, voting,identity, and interoperability systems that are either usable and economically viable. - -### What is zkVerify? -zkVerify is a dedicated modular proof verification layer that empowers blockchain applications with the power of zero-knowledge proofs. By offloading the complex proof verification process to a dedicated chain, we're paving the way for a new era of scalable, secure, and privacy-preserving digital world. - -### Your mission: build the future -The Incentivized Testnet is your chance to be a trailblazer through a series of challenges. Whether you're a seasoned developer or a passionate zero-knowledge enthusiast, the zkVerify Incentivized Testnet welcomes you with open arms. - -Your contributions will be recognized and rewarded: you can earn points for your contributions and activities, with the most complex and impactful tasks earning the highest rewards. - -Even better, the true reward lies in the lasting impact you'll have on the industry. Your work will not only earn you points but also cement your place as a pioneer in zero-knowledge and decentralized technologies. - -### Why participate? -By participating, you can: - -- Create dApps with zk features, excellent performance, and low cost -- Contribute to the robustness and advancement of the zkVerify ecosystem -- Earn points and potentially receive future rewards -- Gain hands-on experience with cutting-edge blockchain and ZK technology -- Collaborate with a passionate community of developers and enthusiasts - -Ready to embark on this exciting journey? Let's get started! - -### For existing zkApps and zkRollups -Are you an existing zkApp or zkRollup looking to offset your ZK proof verification costs? We want to hear from you too! - -Express your interest through this [form](https://forms.gle/rTLYKdskVRXxGRGz9). -Briefly describe your current project and how you plan to integrate with zkVerify. - -We'll contact you for the next phase of our incentivized testnet. - -Points and incentives are also allocated for established projects joining our ecosystem. +The original zkVerify Incentivized Testnet concluded successfully in October 2025, with the completion of the final claim event. +All reward distributions linked to the Volta Testnet and the ProofPoints program are now closed. + +We are now entering a new phase of the Incentivized Testnet — running directly on mainnet. +While we have kept the name for continuity, this phase no longer operates on a testnet environment. +Instead, participants interact directly with the zkVerify mainchain and can accrue points by contributing to the network in production. + +### What This New Phase Is About +The mainnet Incentivized Testnet focuses on supporting the growth of zkVerify by rewarding users who: +- contribute proofs to the network through integrated partners +- help strengthen decentralization by participating in ecosystem activities +- support applications and protocols building on zkVerify +- engage with governance and community-driven processes + +Rewards are issued based on on-chain activity and partner-verified contributions, depending on the task category. + +### If You Participated in the Previous Testnet +All rewards related to the Volta Testnet and ProofPoints have already been distributed. +- The final claim window opened in October 2025 and closed few months after. +- No further actions are required for past participants. +- Historical data remains available for transparency but is no longer updated. + +### How to Participate Now +Participation in this new phase happens directly on mainnet. + +You can get started by: +1. Exploring the tasks avaialable at [points.zkverify.io](https://points.zkverify.io) +2. Following the announcements on our website or Discord or X for new tasks and campaigns. + +### Why We Still Call It “Incentivized Testnet” +Although the environment is now mainnet, the program continues the mission of the original Incentivized Testnet: +- onboarding new developers +- testing and hardening the proof ecosystem +- rewarding early contributors +- growing adoption of zkVerify’s verification engine + +The name reflects the continuity of the initiative while acknowledging that zkVerify is now fully live. Remember, this is your chance to be at the forefront of zero-knowledge technology. We can't wait to see what you'll build with zkVerify! diff --git a/docs/incentivizedtestnet/02-phases.md b/docs/incentivizedtestnet/02-phases.md deleted file mode 100644 index b9f64219..00000000 --- a/docs/incentivizedtestnet/02-phases.md +++ /dev/null @@ -1,42 +0,0 @@ ---- -title: Phases ---- -## Phase 2 - Build-to-Earn...more! + Galxe campaign -Following the initial technical Phase 1, we're thrilled to announce Phase 2 of zkVerify's Incentivized Testnet! While our core technical tasks remains almost unchanged, we're now also opening doors to the wider Web3 community. - -Phase 2 operates on two parallel tracks: - -### Technical Track - -- Build a verification pallet: we are keeping the task open for Phase 2...and increasing the reward to 50'000 points! -- Integrate zkVerify: you can either build a ZK dApp from scratch or integrate in your existing project. Use zkVerify for proof verification and get rewarded. Point reward depends on complexity. -- Send proofs for verification: prove that your integration works and send proofs to zkVerify for rapid and cheap verification. More proofs sent = more points awarded. - -| Challenge | Points | Status | -|---|---|---| -| Build a verification pallet | 50'000 | Active | -| Integrate zkVerify | Depends on complexity | Active | - -Questions? Reach out to our team in the zkVerify [Discord](https://discord.com/invite/zkverify)! - -### Community Track -Not a ZK developer? [Join zkVerify's campaign on Galxe](https://app.galxe.com/quest/QzaQxuvgdzSVXmvvcY5HHy/GCRCJtV8PN) and become part of our growing community! Complete engaging quests to learn about zero-knowledge proofs, share your knowledge, and help spread the word about zkVerify. Points are awarded for successful quests completion. - -### A single source of truth -To track and measure your contributions, we have built a dedicated dApp, bringing together achievements from both technical and community tracks. Whether you're earning points through technical contributions or completing Galxe quests, all your progress syncs there – your single source of truth for the Incentivized Testnet. - -Track your standing on our comprehensive leaderboard, watch your points accumulate in real-time, and see how you stack up against other participants. Link: TBD - -## Phase 1 - Build-to-Earn -Welcome to zkVerify's Incentivized Testnet - Phase 1. In this Phase, we have two exciting challenges for developers: - -- Build a verification pallet: dive into the core of zkVerify by creating a crucial component for our Substrate-based chain. This task involves developing a pallet that efficiently handles the verification of zero-knowledge proofs. - -- Build a demo dApp: showcase the practical applications of zkVerify by developing a demo dApp from scratch. This challenge encourages you to integrate zkVerify as a proof verification and settlement layer, bringing real-world use cases to life on our platform. One way to do this is take an existing dApp on GitHub, modify it to use zkVerify for its verification, and deploy it. Another way is to upgrade the dApp to use a newer type of zk-proof that can be generated on a mobile device rapidly, and create a mobile dApp. - -| Challenge | Points | Status | -|---|---|---| -| Build a verification pallet | 5000 | Updated (Phase 2) | -| Build a demo app | Variable | Updated (Phase 2) | - -Questions? Reach out to our team in the zkVerify [Discord](https://discord.com/invite/zkverify)! diff --git a/docs/incentivizedtestnet/05-terms-and-conditions/01-IT_terms_and_conditions.md b/docs/incentivizedtestnet/02-terms-and-conditions/01-IT_terms_and_conditions.md similarity index 100% rename from docs/incentivizedtestnet/05-terms-and-conditions/01-IT_terms_and_conditions.md rename to docs/incentivizedtestnet/02-terms-and-conditions/01-IT_terms_and_conditions.md diff --git a/docs/incentivizedtestnet/05-terms-and-conditions/02-claim_terms_and_conditions.md b/docs/incentivizedtestnet/02-terms-and-conditions/02-claim_terms_and_conditions.md similarity index 100% rename from docs/incentivizedtestnet/05-terms-and-conditions/02-claim_terms_and_conditions.md rename to docs/incentivizedtestnet/02-terms-and-conditions/02-claim_terms_and_conditions.md diff --git a/docs/incentivizedtestnet/05-terms-and-conditions/_category_.json b/docs/incentivizedtestnet/02-terms-and-conditions/_category_.json similarity index 100% rename from docs/incentivizedtestnet/05-terms-and-conditions/_category_.json rename to docs/incentivizedtestnet/02-terms-and-conditions/_category_.json diff --git a/docs/incentivizedtestnet/03-challenges/02-phase1_challenges/01-build_a_verifier.md b/docs/incentivizedtestnet/03-challenges/02-phase1_challenges/01-build_a_verifier.md deleted file mode 100644 index 6bd4b397..00000000 --- a/docs/incentivizedtestnet/03-challenges/02-phase1_challenges/01-build_a_verifier.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Build a Verification Pallet ---- - -### This task has been updated - please check Phase 2 challenges \ No newline at end of file diff --git a/docs/incentivizedtestnet/03-challenges/02-phase1_challenges/02-build_a_demo_app.md b/docs/incentivizedtestnet/03-challenges/02-phase1_challenges/02-build_a_demo_app.md deleted file mode 100644 index 2c76c1ef..00000000 --- a/docs/incentivizedtestnet/03-challenges/02-phase1_challenges/02-build_a_demo_app.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Build a Demo App that integrates zkVerify ---- - -### This task has been updated - please check Phase 2 challenges \ No newline at end of file diff --git a/docs/incentivizedtestnet/03-challenges/02-phase1_challenges/_category_.json b/docs/incentivizedtestnet/03-challenges/02-phase1_challenges/_category_.json deleted file mode 100644 index f960a0ca..00000000 --- a/docs/incentivizedtestnet/03-challenges/02-phase1_challenges/_category_.json +++ /dev/null @@ -1,3 +0,0 @@ -{ - "label": "Phase 1 Challenges" -} diff --git a/docs/incentivizedtestnet/03-challenges/03-phase2_challenges/01-build_a_verifier.md b/docs/incentivizedtestnet/03-challenges/03-phase2_challenges/01-build_a_verifier.md deleted file mode 100644 index 3d315839..00000000 --- a/docs/incentivizedtestnet/03-challenges/03-phase2_challenges/01-build_a_verifier.md +++ /dev/null @@ -1,96 +0,0 @@ ---- -title: Build a Verification Pallet ---- - -### Overview -Following the initial response to our verifier-building initiative, we're proud to announce that several verifiers are already under active development! But there's still plenty of opportunity to contribute - we have an updated list of verifiers that need to be built, which you can find below. - -To get started, check out our "[Add a New Verifier tutorial](https://docs.zkverify.io/tutorials/add-new-verifier/introduction)" in the zkVerify docs, which walks you through the basics of adding a new verifier to the zkVerify blockchain. - -Also, before you begin, we recommend reviewing our [existing verifier implementations](https://github.com/zkVerify/zkVerify/tree/main/verifiers), especially if you need to incorporate advanced functionality like verification across multiple elliptic curves or runtime benchmarking for different input sizes. - -The zkVerify team is always here to help if you need guidance along the way. Find us on [Discord](https://discord.com/invite/zkverify). - -### Scope -From higher to lower priority: - -* Stwo (Starkware, Cairo) - * Objective: Support verification of Starkware zkRollup’s proofs as well as generic proofs generated via Cairo programs -* Stone - * Objective: Support verification of Starkware zkRollup’s proofs as well as generic proofs generated via Cairo programs -* Jolt -* Kimchi + Pickle - * Objective: Support verification of Mina’s succinct state proofs as well as proofs generated via O1-JS -* Supernova - * Over “pasta” cycle of elliptic curves -* Starky - -### Requirements and Best Practices - -* The programming language should be Rust, the latest stable version of the toolchain must be used (as to enable direct runtime inclusion via WASM compilation). - -* Try to leverage as much as possible already existing and possibly well audited/battle-tested solutions, in case you plan to adopt third party libraries, and make sure that such libraries have some kind of open-source license. - -* Implementations with “no-std” (thus compilable in WASM and directly includible in the runtime) are required - * The rationale behind this is that we want to keep the flexibility to upgrade the verifiers without having to fork the chain. If you can’t get away with “no-std” you can try to put only low-level libraries in the node (Rust), and keep the business logic in the runtime (WASM, no-std). - * This is the rationale we adopted, for instance, for our [Risc0](https://github.com/zkVerify/zkVerify/blob/main/native/src/risc0.rs) and [Ultraplonk-Noir](https://github.com/zkVerify/zkVerify/blob/main/native/src/ultraplonk.rs) verifiers. - * If nothing else works, another acceptable (though with more effort) solution, is rewriting the verifier from scratch and making sure it supports no-std. - -* Proper benchmarks are extremely important. If the execution time of your verifier is not fixed and dependent on some parameters (e.g. size of the circuit, proving system configuration, etc.) be sure to capture it properly in the benchmarks. See some examples of such a situation for [Risc0](https://github.com/zkVerify/zkVerify/blob/main/verifiers/risc0/src/benchmarking.rs) verifier and [Ultraplonk-Noir](https://github.com/zkVerify/zkVerify/blob/main/verifiers/ultraplonk/src/benchmarking.rs) verifier. - -* We don’t want to depend on forks of external repositories so if, for any reason, you are not able to work with a given original repository (e.g. because it doesn’t have support for no_std for the verifier), and thus you are forced to fork it, we require you to be able to open a PR to the original repo integrating the changes you’ve made. - -* Please keep in mind that we have 5MB maximum block space and 1.5s of maximum execution time per block. If you think your verifier artifacts will take more space and the verification will be higher than 1.5 seconds please reach us immediately. - -* Add tests for the Verification Library: - * Tests should cover happy/unhappy paths for proof verification and serialization/deserialization of vk/proof/public inputs. - * Include some tests with hardcoded data ideally taken from third-party on-chain/official sources, depending on the use case for which we wish the verifier to be integrated. - - -* Add tests for the Verification Pallet. Tests should include: - * Correct inclusion of the pallet in the runtime. - * Unit tests with mock runtime. - * Weight tests. - * Modifications to e2e tests which already tests the other already included verifiers. - - -* Documentation for the newly added verification pallet must be added to zkverify-docs [repository](https://github.com/zkVerify/zkVerify-docs). Please, follow the same pattern as the [ones](https://docs.zkverify.io/overview/verification_pallets/abstract/) already present. - - -* An end-to-end tutorial on how to submit proofs for the verifier you’ve just added to the zkVerify blockchain must be provided. For instance, if you are integrating the gnark verifier, make sure to document or reference how to generate gnark proofs using the gnark toolchain. - - -* Make sure to provide any tool that users might require to transform proofs, vk and public inputs from the chosen source (e.g. Gnark) to the format accepted by the zkVerify blockchain, as provided by your implementation. - - -* For the submission itself to the zkVerify blockchain, feel free to leverage either the Polkadot JS frontend for submission via copy-paste, or any kind of Javascript/Rust code to do it programmatically. - - -* As a reference, take a look at the tutorials we already [have](https://docs.zkverify.io/tutorials/submit-proofs/typescript-example) in our documentation. - -### Acceptance Criteria and Submission - -* Code must compile and CI must pass. Take a look at the [instructions](https://github.com/zkVerify/zkVerify?tab=readme-ov-file#running-github-workflows-on-local-environment) on how to run the CI locally for more information. If you require the CI to install some dependencies, feel free to modify it. Otherwise reach the team for further support. - -* Try to make sure that compilation time is not “highly impacted” by the inclusion of your verifier (e.g. if you are including heavy dependencies). The zkVerify team, upon review, might decide to reject your implementation. - * Be sure to pin the version of your dependencies as to avoid unwanted updates of the Cargo.lock - -* Branch from the “main” branch for your implementation. Give the branch a meaningful name, ideally "\-verifier". - -* Open a PR in the [zkVerify repository](https://github.com/zkVerify/zkVerify) targeted against the “main” branch. Make sure that throughout the review process your branch stays up-to-date with the “main” branch. If not, align it exclusively via git rebase. - -* All the commits must be signed. - -* Make sure the CI passes. If not, apply your fixes and contact the team that will trigger an additional CI run. - -* [Documentation & Tutorial] Open a PR in the zkVerify [documentation repository](https://github.com/zkVerify/zkVerify-docs) against the main branch. - -* PRs will be reviewed by at least 2 members of the zkVerify team. Please make sure to be responsive during the review phase. - - -### Application process -To participate in this challenge we kindly ask you to complete an [application form](https://forms.gle/idYKZ8n7T21embgLA). We're looking for developers with a strong background in cryptography, blockchain technology, and preferably experience with zero-knowledge proofs. Please provide detailed information about your relevant past projects and any specific verifier implementations you're interested in or have expertise with. - -Our team will carefully review all applications to ensure a fair and efficient distribution of tasks. This vetting process allows us to avoid duplication of work and ensures that we don't have multiple participants working on the same verifier, as we will only award one implementation per verifier type. - - diff --git a/docs/incentivizedtestnet/03-challenges/03-phase2_challenges/02-build_a_demo_app.md b/docs/incentivizedtestnet/03-challenges/03-phase2_challenges/02-build_a_demo_app.md deleted file mode 100644 index 85b3f001..00000000 --- a/docs/incentivizedtestnet/03-challenges/03-phase2_challenges/02-build_a_demo_app.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Integrate zkVerify in your dApp ---- - -### This task has concluded - thank you for participating! \ No newline at end of file diff --git a/docs/incentivizedtestnet/03-challenges/03-phase2_challenges/03-use_relayer.md b/docs/incentivizedtestnet/03-challenges/03-phase2_challenges/03-use_relayer.md deleted file mode 100644 index ffe79c86..00000000 --- a/docs/incentivizedtestnet/03-challenges/03-phase2_challenges/03-use_relayer.md +++ /dev/null @@ -1,55 +0,0 @@ ---- -title: Use the zkVerify Relayer ---- - -### Overview - -The zkVerify Relayer is a tool that makes it easy to verify zero-knowledge proofs using the zkVerify network. This challenge invites you to explore its functionality, submit real proofs, and provide valuable feedback to improve the developer experience. - -This is a technical challenge within the zkVerify Incentivized Testnet Phase 2. By completing the tasks below, you can earn zkVerify Incentivized Testnet Points and move up the leaderboard. - -**Start here**: Read the [Relayer documentation](https://docs.zkverify.io/overview/getting-started/relayer) to understand how the system works. - -### Tasks & Rewards - -#### 1. Submit Valid Proofs at Scale Using the Relayer API - -- Relayer usage is tracked via your API key. To use the Relayer API, you will need an API key. Contact a zkVerify team member or open a ticket on Discord to request a unique API key. -- Power users can reach out to us on Discord to adjust their rate limits; participants should specify their use cases and/ or apps they’re working on that uses the ZKVerify integration and we will determine the rate limit increase accordingly. - -To earn zkVerify Incentivized Testnet Points, this requires creating a new circuit, registering your verification key, and submitting unique proofs. The proof types we support are: Groth16, UltraHonk, UltraPlonk, Risc0, Plonky2, SP1, and EZKL.
- -
- -Points will be calculated based on your valid submission volume over time for qualified use cases. Points will not be rewarded for submitting the same proof examples provided in the documentations. - -
- -| # of Unique Proofs Submitted | Points | -| ---------------------------- | ------ | -| 1-100 | 5 | -| 101-500 | 10 | -| 501-1000 | 25 | -| 1000+ | 60 | - -#### 2. Provide Feedback on the Relayer - -Help improve the tool by submitting detailed feedback or reporting issues: - -- Complete the [Relayer Feedback Form](https://forms.gle/PVjhLkDt2TbgmspGA) -- Report an unknown bug (include sufficient details and screenshots): +50 points - -### How to Claim Points - -Once you’ve submitted a proof or provided feedback: - -1. Fill out the [submission form](https://forms.gle/PVjhLkDt2TbgmspGA) -2. Provide your EVM wallet address and the API key, Job ID or transaction hash for the proof you submitted via the Relayer -3. The zkVerify team will verify your submission and assign points accordingly - -Make sure to use the provided API key or your unique API key for all submissions so that your activity can be accurately tracked. - -### Resources - -- [Relayer Documentation](../../../overview/02-getting-started/05-relayer.md) -- [Leaderboard & Points Dashboard](https://points.zkverify.io/loyalty) diff --git a/docs/incentivizedtestnet/03-challenges/03-phase2_challenges/_category_.json b/docs/incentivizedtestnet/03-challenges/03-phase2_challenges/_category_.json deleted file mode 100644 index 0bb3c754..00000000 --- a/docs/incentivizedtestnet/03-challenges/03-phase2_challenges/_category_.json +++ /dev/null @@ -1,3 +0,0 @@ -{ - "label": "Phase 2 Challenges" -} \ No newline at end of file diff --git a/docs/incentivizedtestnet/03-challenges/04-phase3_challenges/01-use_relayer.md b/docs/incentivizedtestnet/03-challenges/04-phase3_challenges/01-use_relayer.md deleted file mode 100644 index 6a9224a8..00000000 --- a/docs/incentivizedtestnet/03-challenges/04-phase3_challenges/01-use_relayer.md +++ /dev/null @@ -1,55 +0,0 @@ ---- -title: Use the Relayer API - Mainnet ---- - -### Overview - -The Relayer API is a product that makes it easy to verify zero-knowledge proofs using the zkVerify network. This challenge invites you to explore its functionality, submit real proofs, and provide valuable feedback to improve the developer experience. - -By completing the tasks below, you can earn Incentivized Program Points and move up the leaderboard. - -**Start here**: Read the [Relayer documentation](https://docs.zkverify.io/overview/getting-started/relayer) to understand how the system works. - -### Tasks & Rewards - -#### 1. Submit Valid Proofs at Scale Using the Relayer API - Mainnet - -- Relayer usage is tracked via your Mainnet API key. To use the Relayer API, you will need an API key. Create your API key here: https://relayer.horizenlabs.io -- Power users can reach out to us on Discord to adjust their rate limits or fill out this [form](https://forms.gle/8GLNhADGoxkvCdTu7); participants should specify their use cases and/ or apps they’re working on that uses the Relayer integration and we will determine the rate limit increase accordingly. - -To earn zkVerify Incentivized Testnet Points, this requires creating a new circuit, registering your verification key, and submitting unique proofs. The proof types we support are: Groth16, UltraHonk, UltraPlonk, Risc0, Plonky2, SP1, Fflonk.
- -
- -Points will be calculated based on your valid submission volume over time for qualified use cases. Points will not be rewarded for submitting the same proof examples provided in the documentations. **To qualify, you must also provide a link to your zk-app that is integrated with the Relayer** - -
- -| # of Unique Proofs Submitted | Points | -| ---------------------------- | ------ | -| 1-100 | 15 | -| 101-500 | 30 | -| 501-1000 | 60 | -| 1000+ | 100 | - -#### 2. Provide Feedback on the Relayer - -Help improve the tool by submitting detailed feedback or reporting issues: - -- Complete the [Relayer Feedback Form](https://forms.gle/79nLKD4gDd2ndtar7) -- Report an unknown bug (include sufficient details and screenshots can be sent to relayer-support@horizenlabs.io if relevant): +50 points - -### How to Claim Points - -Once you’ve submitted a proof or provided feedback: - -1. Fill out the [submission form](https://forms.gle/hVutiC2Syb16bDg37) -2. Provide your EVM wallet address and the email address, app link for the proofs you submitted via the Relayer -3. The zkVerify team will verify your submission and assign points accordingly - -Make sure to use the provided API key or your unique API key for all submissions so that your activity can be accurately tracked. - -### Resources - -- [Relayer Documentation](../../../overview/02-getting-started/05-relayer.md) -- [Leaderboard & Points Dashboard](https://points.zkverify.io/loyalty) diff --git a/docs/incentivizedtestnet/03-challenges/04-phase3_challenges/_category_.json b/docs/incentivizedtestnet/03-challenges/04-phase3_challenges/_category_.json deleted file mode 100644 index 9d7ae525..00000000 --- a/docs/incentivizedtestnet/03-challenges/04-phase3_challenges/_category_.json +++ /dev/null @@ -1,3 +0,0 @@ -{ - "label": "Phase 3 Challenges" -} \ No newline at end of file diff --git a/docs/incentivizedtestnet/03-challenges/_category_.json b/docs/incentivizedtestnet/03-challenges/_category_.json deleted file mode 100644 index d3f7d9b6..00000000 --- a/docs/incentivizedtestnet/03-challenges/_category_.json +++ /dev/null @@ -1,3 +0,0 @@ -{ - "label": "Challenges" -} diff --git a/docs/incentivizedtestnet/06-redeem-your-tokens/01-claim_substrate.md b/docs/incentivizedtestnet/03-redeem-your-tokens/01-claim_substrate.md similarity index 100% rename from docs/incentivizedtestnet/06-redeem-your-tokens/01-claim_substrate.md rename to docs/incentivizedtestnet/03-redeem-your-tokens/01-claim_substrate.md diff --git a/docs/incentivizedtestnet/06-redeem-your-tokens/02-claim_ethereum.md b/docs/incentivizedtestnet/03-redeem-your-tokens/02-claim_ethereum.md similarity index 100% rename from docs/incentivizedtestnet/06-redeem-your-tokens/02-claim_ethereum.md rename to docs/incentivizedtestnet/03-redeem-your-tokens/02-claim_ethereum.md diff --git a/docs/incentivizedtestnet/06-redeem-your-tokens/_category_.json b/docs/incentivizedtestnet/03-redeem-your-tokens/_category_.json similarity index 100% rename from docs/incentivizedtestnet/06-redeem-your-tokens/_category_.json rename to docs/incentivizedtestnet/03-redeem-your-tokens/_category_.json diff --git a/docs/incentivizedtestnet/06-redeem-your-tokens/img/check-claim-active.png b/docs/incentivizedtestnet/03-redeem-your-tokens/img/check-claim-active.png similarity index 100% rename from docs/incentivizedtestnet/06-redeem-your-tokens/img/check-claim-active.png rename to docs/incentivizedtestnet/03-redeem-your-tokens/img/check-claim-active.png diff --git a/docs/incentivizedtestnet/06-redeem-your-tokens/img/check-eligibility-ethereum.png b/docs/incentivizedtestnet/03-redeem-your-tokens/img/check-eligibility-ethereum.png similarity index 100% rename from docs/incentivizedtestnet/06-redeem-your-tokens/img/check-eligibility-ethereum.png rename to docs/incentivizedtestnet/03-redeem-your-tokens/img/check-eligibility-ethereum.png diff --git a/docs/incentivizedtestnet/06-redeem-your-tokens/img/check-eligibility-substrate.png b/docs/incentivizedtestnet/03-redeem-your-tokens/img/check-eligibility-substrate.png similarity index 100% rename from docs/incentivizedtestnet/06-redeem-your-tokens/img/check-eligibility-substrate.png rename to docs/incentivizedtestnet/03-redeem-your-tokens/img/check-eligibility-substrate.png diff --git a/docs/incentivizedtestnet/06-redeem-your-tokens/img/claim-extrinsic-substrate.png b/docs/incentivizedtestnet/03-redeem-your-tokens/img/claim-extrinsic-substrate.png similarity index 100% rename from docs/incentivizedtestnet/06-redeem-your-tokens/img/claim-extrinsic-substrate.png rename to docs/incentivizedtestnet/03-redeem-your-tokens/img/claim-extrinsic-substrate.png diff --git a/docs/incentivizedtestnet/06-redeem-your-tokens/img/claim_ethereum_extrinsic.png b/docs/incentivizedtestnet/03-redeem-your-tokens/img/claim_ethereum_extrinsic.png similarity index 100% rename from docs/incentivizedtestnet/06-redeem-your-tokens/img/claim_ethereum_extrinsic.png rename to docs/incentivizedtestnet/03-redeem-your-tokens/img/claim_ethereum_extrinsic.png diff --git a/docs/incentivizedtestnet/06-redeem-your-tokens/img/get-claim-message.png b/docs/incentivizedtestnet/03-redeem-your-tokens/img/get-claim-message.png similarity index 100% rename from docs/incentivizedtestnet/06-redeem-your-tokens/img/get-claim-message.png rename to docs/incentivizedtestnet/03-redeem-your-tokens/img/get-claim-message.png diff --git a/docs/incentivizedtestnet/06-redeem-your-tokens/img/polkadotjs-sign-and-verify.png b/docs/incentivizedtestnet/03-redeem-your-tokens/img/polkadotjs-sign-and-verify.png similarity index 100% rename from docs/incentivizedtestnet/06-redeem-your-tokens/img/polkadotjs-sign-and-verify.png rename to docs/incentivizedtestnet/03-redeem-your-tokens/img/polkadotjs-sign-and-verify.png diff --git a/docs/incentivizedtestnet/06-redeem-your-tokens/img/post_sign_etherscan.png b/docs/incentivizedtestnet/03-redeem-your-tokens/img/post_sign_etherscan.png similarity index 100% rename from docs/incentivizedtestnet/06-redeem-your-tokens/img/post_sign_etherscan.png rename to docs/incentivizedtestnet/03-redeem-your-tokens/img/post_sign_etherscan.png diff --git a/docs/incentivizedtestnet/06-redeem-your-tokens/img/sign_message_etherscan.png b/docs/incentivizedtestnet/03-redeem-your-tokens/img/sign_message_etherscan.png similarity index 100% rename from docs/incentivizedtestnet/06-redeem-your-tokens/img/sign_message_etherscan.png rename to docs/incentivizedtestnet/03-redeem-your-tokens/img/sign_message_etherscan.png diff --git a/docs/incentivizedtestnet/06-redeem-your-tokens/img/verified_signature_tool.png b/docs/incentivizedtestnet/03-redeem-your-tokens/img/verified_signature_tool.png similarity index 100% rename from docs/incentivizedtestnet/06-redeem-your-tokens/img/verified_signature_tool.png rename to docs/incentivizedtestnet/03-redeem-your-tokens/img/verified_signature_tool.png diff --git a/docs/incentivizedtestnet/04-rules_and_guidelines.md b/docs/incentivizedtestnet/04-rules_and_guidelines.md deleted file mode 100644 index 748a4681..00000000 --- a/docs/incentivizedtestnet/04-rules_and_guidelines.md +++ /dev/null @@ -1,38 +0,0 @@ ---- -title: Rules and Guidelines ---- - -### 1. Terms and Conditions -Participation in zkVerify's Incentivized Testnet requires strict adherence to the Terms and Conditions. Please review the full Terms and Conditions document before participating. - -### 2. Challenges -The zkVerify Incentivized Testnet is structured around a series of challenges designed to engage a diverse set of participants, including developers, node operators, zero-knowledge projects, and passionate community members. - -Phase 1 will commence on September 4, 2024, with an initial set of challenges. As the testnet progresses over time, new challenges will be introduced, encouraging active involvement and showcasing the creativity and technical expertise of the zkVerify community and beyond. - -The challenges will vary in duration, with some spanning just a few days and others lasting the entirety of the testnet, to ensure ongoing engagement and appropriate time for challenges completion. - -### 3. Testnet Phases -The testnet will be conducted in multiple phases: -Phase 1 focuses on two key challenges: - -- Building a verification pallet -- Creating a demo application that leverages zkVerify for zero-knowledge proofs verification - -Subsequent Phases will be introduced in the next weeks, with new tasks and challenges. More details on Incentivized Testnet duration and detailed point rewards will be unveiled soon. - -### 4. Rewards and Incentives -Successful completion of the challenges will be rewarded with points, with the more complex tasks earning higher point values. This fair, points-based system aims to recognize and incentivize meaningful community engagement and participation throughout the testnet. - -A dedicated dApp will soon be available where participants can connect their wallets and track their accumulated points and contributions across multiple platforms. - -### 5. Submission Process -Each challenge will have its own dedicated submission process, which will be clearly outlined on the corresponding challenge page. Participants will be provided with detailed instructions on how to submit their work for evaluation. This may involve filling out forms, uploading project files, or linking to external repositories, depending on the nature of the challenge. - -### 6. Updates and Communication -Participants should regularly check for updates on the Incentivized Testnet on zkVerify’s [Discord](https://discord.com/invite/zkverify) and [X](https://x.com/ZKVProtocol) profile, including new challenges, phases, or changes to existing ones. - -Information about future phases, mainnet duration, and point systems will be communicated as it becomes available. - -Remember, your participation contributes to the development and robustness of zkVerify. We encourage engagement, innovation, and community collaboration throughout all phases of this Incentivized Testnet. Stay tuned for more information about upcoming Phases and opportunities to contribute. - diff --git a/docs/incentivizedtestnet/07-FAQs.md b/docs/incentivizedtestnet/07-FAQs.md index 03d44ce0..c7d0ac77 100644 --- a/docs/incentivizedtestnet/07-FAQs.md +++ b/docs/incentivizedtestnet/07-FAQs.md @@ -25,11 +25,11 @@ The zkVerify Incentivized Testnet is structured around a series of Phases, each ### What are the different Phases of the zkVerify Incentivized Testnet? -The testnet will be conducted in multiple phases. Phase 1 will commence on September 4, 2024, with an initial set of challenges, and new challenges will be introduced as the testnet progresses. +The testnet will be conducted in multiple phases. Phase 1 commenced on September 4, 2024, with an initial set of challenges, and new challenges are being introduced as the testnet progresses. ### How will Rewards and Incentives work in the zkVerify Incentivized Testnet? -Successful challenge completion will be rewarded with points. More complex tasks will earn a higher point amount. A dedicated dApp will allow participants to connect their wallets and track their points and contributions. +Successful challenge completion will be rewarded with points. More complex tasks will earn a higher point amount. A dedicated dApp allows participants to connect their wallets and track their points and contributions. ### What is the Submission Process for the zkVerify Incentivized Testnet? diff --git a/src/css/custom.css b/src/css/custom.css index f4c22845..f70f46e7 100644 --- a/src/css/custom.css +++ b/src/css/custom.css @@ -6,26 +6,26 @@ /* You can override the default Infima variables here. */ :root { - --ifm-color-primary: #2e8555; - --ifm-color-primary-dark: #29784c; - --ifm-color-primary-darker: #277148; - --ifm-color-primary-darkest: #205d3b; - --ifm-color-primary-light: #33925d; - --ifm-color-primary-lighter: #359962; - --ifm-color-primary-lightest: #3cad6e; + --ifm-color-primary: #5C72FF; + --ifm-color-primary-dark: #4e63e5; + --ifm-color-primary-darker: #4458d1; + --ifm-color-primary-darkest: #3444aa; + --ifm-color-primary-light: #7386ff; + --ifm-color-primary-lighter: #8c9aff; + --ifm-color-primary-lightest: #b7c0ff; --ifm-code-font-size: 95%; --docusaurus-highlighted-code-line-bg: rgba(0, 0, 0, 0.1); } /* For readability concerns, you should choose a lighter palette in dark mode. */ [data-theme='dark'] { - --ifm-color-primary: #25c2a0; - --ifm-color-primary-dark: #21af90; - --ifm-color-primary-darker: #1fa588; - --ifm-color-primary-darkest: #1a8870; - --ifm-color-primary-light: #29d5b0; - --ifm-color-primary-lighter: #32d8b4; - --ifm-color-primary-lightest: #4fddbf; + --ifm-color-primary: #5C72FF; + --ifm-color-primary-dark: #7485f0; + --ifm-color-primary-darker: #6374db; + --ifm-color-primary-darkest: #4c59b3; + --ifm-color-primary-light: #9baaff; + --ifm-color-primary-lighter: #b0bdff; + --ifm-color-primary-lightest: #d6dcff; --docusaurus-highlighted-code-line-bg: rgba(0, 0, 0, 0.3); } diff --git a/static/img/meta-image.png b/static/img/meta-image.png index f25649f3..77b1df69 100644 Binary files a/static/img/meta-image.png and b/static/img/meta-image.png differ