About Custom solution verify

[apool-io]

From a development perspective, directly porting XMR’s verification algorithm into the Core and validating it via core nodes would be the fastest approach. However, for the outsource computing feature, assuming diverse future business scenarios, this implementation would lack scalability and significantly impact the development velocity and stability of Qubic Core’s codebase. Thus, the following design prioritizes extensible business support:

1. Introduce a Relay Node (or Light Node)

• Primary responsibilities:
  • Monitor and Relay P2P messages on the Qubic network.
  • Provide HTTP callback interfaces for notify Task messages and Solution messages.
  • Offer a transaction (Tx) submission interface.

2. Custom Solution Verifier Modules per Outsourcing Business

• Each outsourced computing scenario designs a dedicated Solution Verifier module to:
  • Validate the correctness of submitted solutions using the corresponding algorithm.
  • Track contributions (number of valid solutions) per Computer ID for each Task.
  • Aggregate statistics every N Tasks and broadcast a Custom Solution Counter Tx to the Qubic network.

3. Verifier Node Eligibility

• PoC Phase: Allow Computers to run Verifiers to avoid introducing additional consensus/trust mechanisms.
• Long-term: Consider alternative mechanisms (e.g., staking) for Verifier qualification.

4. Frequency Control for Custom Solution Counter Tx

• Limit the number of Custom Solution Counter Tx to avoid network overload.
• To prevent fraud, adopt a design similar to Vote Counter:
  • Each Computer submits aggregated statistics once every 676 Tasks.

[J0ET0M]

i like the idea.

from a design perspective, would the "Solution Verifier" match an Oracle?
if yes, then relay/light nodes (which are already planed) would be like generic nodes which help to strengthen the network and facilitate network access.