Introduction

We are excited to announce a bounty of 5,000 USDC for the integration of Spark support into the Erigon client. This addition will enable the Erigon client to sync with the Spark testnet network and function as an RPC node, furthering our network’s capabilities and robustness.

About Fuse/Spark Consensus Model

The Fuse Network Consensus Algorithm is based on the AuRa (Authority Round) consensus mechanism. AuRa allows the integration of on-chain validator set selection and block rewards logic with smart contracts.

By developing unique smart contracts for Consensus and block rewards, and making them upgradable via proxy contracts, the Fuse Consensus was established. The chosen validator set takes turns in a round-robin fashion to sign and confirm blocks. A signed block is broadcasted and propagated to all network participants. Every node participant verifies and appends the block to their state, thus confirming the block.

New blocks are produced every 5 seconds, during which a validator has a time window to publish their block and receive a reward for their actions. Although achieving transaction finality in this model may theoretically take some time, for practical purposes, a transaction on Fuse Network can be considered finalized after a single block confirmation.

For more details, check out the Fuse Consensus documentation, and Fuse Consensus contracts

Project Requirements

The successful implementation must:

• Enable the Erigon client to fully sync with the Spark testnet.
• Allow the client to serve as a fully functional RPC node.

Eligibility

This bounty is open to anyone with the skills to meet the technical requirements specified below.

Technical Requirements

• Sync the Spark testnet: The modified Erigon client must be able to sync up with the Spark testnet without any discrepancies.
• RPC Node functionality: The client must perform all standard RPC node functions effectively within the Spark testnet environment.

Submission Guidelines

Participants must:

1. Fork the Erigon Client repository.
2. Implement the necessary modifications to support the Spark testnet.
3. Provide proof of functionality:
   • Screenshots, logs, or other demonstrable proof that the client syncs and operates as an RPC node on the Spark testnet.
4. Include a detailed guide on how to set up and run the modified client.

Judging Criteria

Submissions will be evaluated based on:

• Code Quality: Clean, well-organized, and maintainable code will be prioritized.
• Documentation Clarity: Instructions must be clear and straightforward, allowing others to easily set up and use the client.
• Testing: Comprehensive testing demonstrating the functionality and stability of the client within the Spark environment.

Licensing

Submissions must adhere to the same licensing as the original Erigon client repository. Please ensure your modifications are compliant with the repository’s license terms.

Reward

The winner of this bounty will receive a reward of 5,000 USDC. The payment will be processed upon successful review and integration of the work.

How to Submit

Participants are required to submit their work by providing a link to their fork of the Erigon Client repository. Ensure that your fork repository is public and clearly documents all changes made as part of this bounty. Include a comprehensive README file detailing the setup, operation, and any important details about your implementation.

Please submit your work by commenting on this issue with the following information:

• Link to your GitHub fork.
• A brief overview of the changes made.
• Any additional comments or notes relevant to your submission.

Questions and discussions about the bounty can also be posted as comments on this issue.