Consensus Mechanism

To ensure the legitimacy of the submitted PoG scores, Oracles employ asymmetric cryptography (ECDSA or Ed25519, depending on the network implementation). This process involves:

• Private Key Signing: Each PoG score is signed using the Oracle's private key.

• Public Key Verification: Other Oracles, or the consensus contract, use the public key associated with the Oracle to verify the authenticity of the submission.

Aptos on-chain Consensus

• The PoG network leverages the Aptos blockchain’s Byzantine Fault Tolerant (BFT) consensus mechanism to reach agreement on submitted scores:

• Consensus Threshold: The smart contract deployed on Aptos will wait until at least 67% of the Oracles submit their PoG scores before reaching consensus.

• Finality: Once the threshold is met, the network calculates the median or weighted average of the submitted scores to finalize the PoG scores.

• Error Handling: Submissions that are deemed invalid (due to signature issues or incorrect calculations) are excluded from the consensus process, and malicious actors may face penalties such as stake slashing.