Bounties on NEAR testnet
Bounties
Each row is one repair bounty, read from the contract. Open ones accept attempts until they close. Finished ones show how the money moved. Look at the status to see whether a payment was backed by a proof or paid by timeout.
How was it paid?
The contract checked a proof for the paid attempt.
No proof arrived in the window. The contract paid by rule. This is not a proof.
Nothing was paid out. The vendor got the reward back.
Open until Nov 15, 21:43 UTC. 1 attempt so far.
2 revealed attempts waiting for a verdict. Commits accepted until Nov 5, 14:11 UTC.
A team-run test of the confidential proving spike: Proof 0 on a rented GPU; the attempt's prove step ran inside an attested Phala Cloud confidential VM (Intel TDX), then the shrink on a rented GPU and the Groth16 proof the contract checked. The researcher account is the project's own test account. docs/evidence/tee_spike/README.md
A PASS proof was accepted by the contract.
Created. It opens when its Proof 0 is accepted.
Created. It opens when its Proof 0 is accepted.
Created. It opens when its Proof 0 is accepted.
Created. It opens when its Proof 0 is accepted.
A PASS proof was accepted by the contract.
No proof arrived in the window. Paid by the timeout rule.
A throwaway bounty for the live test of the per-account cap: one account's second commit was refused.
An AI agent's fix of a private bug it could not see, proven PASS and paid by the contract. Proved and shrunk on a rented GPU, wrapped to Groth16 on a separate Docker machine; the secret never left the vendor's control.
Refunded to the vendor.
Created. It opens when its Proof 0 is accepted.
Created. It opens when its Proof 0 is accepted.
Created. It opens when its Proof 0 is accepted.
Created. It opens when its Proof 0 is accepted.
1 revealed attempt waiting for a verdict. Commits accepted until Dec 4, 09:39 UTC.
The vendor's proof finished after the 4 hour window, so the contract paid by timeout. Not a proof.
The agent's fix on the public demo module was proven PASS and paid. It shows the path, not a model's skill: the demo bug is named in the module's comments.
No proof arrived in the window. Paid by the timeout rule.
No proof arrived in the window. Paid by the timeout rule.
One attempt allowed. No proof arrived in the window.
Paid by timeout, not by a proof: its one attempt came from a team-run account (the owner's account, external agent software), and the vendor's watch does not cover bounty 12.
The bounty was split equally between two revealed attempts.
Refunded to the vendor.
One attempt was rejected by a valid FAIL proof. Another was paid by timeout.
The contract shows this bounty as Paid, but the payout went to an account that does not exist: the transfer failed and the NEAR stayed in the contract (review finding 8, a known limit).
Open until Nov 23, 19:19 UTC. No attempts yet.
Refunded to the vendor. Junk commit fees went to the protocol pool.
Refunded to the vendor after a self block test.
A silent vendor test. No proof arrived in the window.
No proof arrived in the window. Paid by the timeout rule.
Refunded to the vendor.
Attempt 0 passed and was paid. Attempt 1 was a valid proof of FAIL, which spent that attempt.
Refunded to the vendor.
Every bounty on this contract is listed, read live from testnet. Test, demo and judge bounties are labelled. Titles are short descriptions; every status, amount and count comes from the chain.
On private bounties, researchers and the public never see the secret input. Demo bounties use a public input so anyone can check them.