What caught my attention in Newton Protocol's documentation is how smart contracts verify BLS Attestations before executing. It's a specific instruction: a decentralized operator network returns an attestation, and smart contracts check it.
This means the smart contract's execution depends entirely on an external, cryptographically signed approval. The contract isn't evaluating complex policies itself. It just checks the attestation. This setup places policy validation outside the contract's direct logic, making the attestation a mandatory, pre-execution gate for onchain transactions.
Technical Question: What might be the exact gas cost implications for smart contracts to verify BLS Attestations on-chain, given varying attestation sizes?#newt $NEWT @NewtonProtocol
This means the smart contract's execution depends entirely on an external, cryptographically signed approval. The contract isn't evaluating complex policies itself. It just checks the attestation. This setup places policy validation outside the contract's direct logic, making the attestation a mandatory, pre-execution gate for onchain transactions.
Technical Question: What might be the exact gas cost implications for smart contracts to verify BLS Attestations on-chain, given varying attestation sizes?#newt $NEWT @NewtonProtocol