Builder submission

Submit project evidence

Choose a campaign, provide live evidence, and sign the submission from your builder wallet.

Builder signsEvidence remains untrustedAppend-only submission

The connected wallet becomes the builder address. ProofPilot validates basic evidence shape, then the contract stores the submission for later review.

Wallet

Connect an EIP-1193 browser wallet to sign transactions.

Network unknownNo private keys required

Choose submission template

The current v6 contract supports the Web3 Project evidence shape. Other templates need flexible evidence support.

v6 evidence schema

Web3 Project evidence

Active on v6. The connected wallet becomes the builder address. Submitted URLs remain untrusted until reviewed by the contract.

Target campaign

This is the campaign that will receive the submission.

This is the campaign that will receive the submission.

Project identity

Give reviewers enough context to understand the project before reading evidence.

Public evidence

Evidence fetched by ProofPilot is bounded, treated as untrusted, and scored conservatively on failures.

On-chain proof

The v6 contract requires Web3 deployment proof fields. Do not enter placeholders.

Reviewer context

Optional context helps explain what changed or what should be checked.

Transaction settings

Editable signing configuration, separate from project evidence.

Advanced transaction settings

Method

submit_project

Network

Bradbury

Default chosen from previous successful Bradbury submit_project writes. Change only if a transaction fails.

Complete the required Web3 evidence fields before preparing a wallet-signed transaction.