Code review · SecurityThe on-chain `policy_hash` comparison against `Campaign.policy_hash` was deleted, so payouts no longer verify the report was produced under the campaign's policy; enforcement is now purely off-chain and the still-stored `Campaign.policy_hash` becomes dead state, weakening defense-in-depth even thougsolana/programs/contrib-oracle/src/instructions/on_report.rs:58-62
Code review · Code qualityA bare `solana program deploy ...` command is appended to the very end of the root README with no heading or surrounding context, adding unrelated churn (and dropping the file's trailing newline) to a doc that is otherwise untouched by this change.README.md:2541-2543
Code review · Code quality`PolicyMismatch` is retained as dead code; keeping the code stable is reasonable, but leaving an unused variant without any test or reference adds maintenance noise now that no code path can raise it.solana/programs/contrib-oracle/src/errors.rs:18
Code review · CorrectnessThe PR declares `fixes #31`, but issue 31 is an unrelated placeholder ('test issue'), so the linkage between the change and the referenced issue cannot be validated.
Issue fit · ScopeAn unrelated solana program deploy command is appended to the top-level README with no newline or surrounding context, which is a stray change unrelated to the report-size fix.README.md:2542-2543
Issue fit · ValueDropping the on-chain policy_hash check removes a security invariant while Campaign.policy_hash is still stored, so a report produced under a different policy is no longer rejected on-chain and policy enforcement now relies entirely on evaluation_hash being honest off-chain.solana/programs/contrib-oracle/src/instructions/on_report.rs:60-63
Issue fit · ValueRemoving score and policy_hash from the Payout struct changes its serialized layout (and account size), so previously created Payout accounts and any decoders can no longer be read without a redeploy/migration.solana/programs/contrib-oracle/src/state.rs:55-63
Issue fit · Issue relevanceThe linked issue (#31) contains only the placeholder text 'test issue', so there is no concrete acceptance criteria to confirm the change actually resolves the reported problem.