Smart Contract and Gas Oracle Integration
The implementation relies on the EVM’s metering of gas usage.
The PoG contract may integrate a Gas Oracle mechanism to index gas prices and ensure accurate accounting of value expended.
One approach is to use the base fee (introduced by EIP-1559) as an on-chain reference for cost, combined with actual gas used.
Because EIP-1559 burns the base fee, PoG participation inherently destroys some ETH, echoing a proof-of-burn dynamic.
A probabilistic Gas Oracle could also be employed – for instance, sampling gas prices over blocks to adjust difficulty or introduce randomness in high-congestion scenarios (preventing purely deterministic sniping by bots).
Each participant’s gas expenditure can be logged in a mapping (address -> gas_used).
The contract might incorporate a commit-reveal scheme to prevent last-block manipulation: participants first commit to an intended gas spend (by calling a function that logs a hash of their address and some nonce), then reveal their identity and exact gas spent in a second phase, which the contract verifies against actual usage.
This two-phase design would add a layer of unpredictability (a form of transaction entropy) to discourage late entrants from simply outbidding everyone at the final moment.
After the participation window closes, the total token supply allocated for the PoG event is distributed.
Instead of directly transferring potentially thousands of token grants (which would be costly on-chain), the contract can emit an event with a Merkle root of allocations – a modular Merkle-proof airdrop approach.
Participants then claim their tokens by providing a Merkle proof that their address is entitled to a certain amount, ensuring scalability of distribution.
This architecture separates the costly competitive phase from the efficient settlement phase: the gas competition is intentionally costly (to ensure skin-in-the-game), while the reward claim is optimized via batched proofs.

Last updated
