Finance Without IntermediariesSelf-submitted3rd place (self-declared)

Decentralized Ad-Space Auctions (DASA)

ad::team · ttarnawski/hackyeah-solana

Council score

Median of 3 models, weighted by the task's official criteria
68.5 / 100

A carefully engineered, genuinely non-custodial on-chain auction escrow with real tests and honest permission documentation, held back by the absence of any confirmed public-chain transaction and by an ad-display promise that stays off-chain.

Criteria · line = median, dots = each member
Relevance30%
7.0

The financial transaction is genuinely intermediary-free: bids move into a vault PDA, displaced bidders are refunded in the same transaction, and any wallet can trigger the supplier payout. Residual trust points, the admin KYB gate and ad display that is not enforced on-chain, support the median of 7 over A's 9.

Members disagree here: scores range by 2.0 points.
Completeness & functionality25%
6.0

The full flow is implemented in the Rust program, exercised by 15 integration tests and wired into a React client, but the pack contains no confirmed devnet transaction or program account to back the form's claim of a working devnet contract, and an Anchor.toml cluster setting is not deployment proof. The demo video link does load publicly with the file page visible, so the login-wall claims of A and B are not supported by the check, though the video's content still cannot be confirmed from the pack.

Members disagree here: scores range by 4.0 points.
Idea & problem20%
8.0

The deck and form quantify the ad-tech problem (intermediary tax, Net-30 and Net-90 terms, single point of failure), name two user groups, and answer where the intermediary goes. The one gap is that only the money leg is trustless, since whether the winning ad is shown is not verified on-chain.

Implementation potential15%
7.0

The program shows careful design: stored PDA bumps, a separate realloc-able metadata account, custom errors for every failure mode, buyout overage refunds, and clock-based lazy settlement. C's 5 is too low; the permanent admin and the missing timeout refund are real deployability concerns, but they sit on top of a sound core.

Members disagree here: scores range by 2.0 points.
Originality10%
6.0

Escrowed auctions are a canonical Solana pattern, so the core is familiar, but recurring lazy-settled cycles, atomic outbid refunds, buyout closure, and a documented permission map lift it above tutorial level.

Members disagree here: scores range by 2.0 points.
Source lines4,572
Tests15 cases
Claims built7.0 / 10
Task fitYes

Strengths

  • Bid funds sit in a vault PDA, outbid bidders are refunded in the same transaction by CPI, and any wallet can trigger the supplier payout, so no party can trap the money.
  • Edge cases are handled in code: cycles settle lazily from clock timestamps with no background service, and a vanished supplier can still be paid through a permissionless claim.
  • Fifteen integration tests match the trust claims, and the README documents an actor-by-actor permission table including what the admin cannot do.
  • The backend is deliberately reduced to health and RPC-status endpoints and holds no keys or funds, keeping the trust boundary clean.

Weaknesses

  • No confirmed devnet transaction signature, explorer link, or program-account evidence appears anywhere in the pack despite the form claiming a functioning devnet contract; the README defaults to Localnet and Surfpool, so proof of a deployed public-chain contract is missing.
  • Ad display is not enforced on-chain and there is no timeout refund for bidders if the supplier never delivers, so only the money leg is trustless.
  • The admin can revoke KYB after bids are escrowed, there is no admin-transfer instruction, and the upgrade authority can replace the program after deploy, softening the claim that nothing can change.
  • The pack contains no screenshots or captured app text, so the working demo rests on the video alone.

Red flags

  • The form asserts a functioning smart contract on Solana devnet, but the only devnet artifact in the pack is the public RPC endpoint status page, with no transaction or program evidence behind the claim.
Built during the event: yes: 9 commits by 1 author, 2026-10-03 16:46 to 2026-10-04 08:58 UTC
Live demo: https://api.devnet.solana.com (HTTP 200); https://drive.google.com/file/d/1IcOIKGImrwPpmfrLaAP68jXLXfz2DtFe/view?usp=drive_link (HTTP 200)
Council v9
Aclaude:glm-5.3-flash75.080% agree
Bdots-studio/dots-3-note-preview:free62.070% agree
Cinclusionai/ling-3.0-flash-sante:free64.580% agree
Jclaude:glm-5.3–judge
Self-submitted and unverified: the result shown is the team's own claim. The council read an evidence pack built from the repo, its decks and docs; it didn't run the code or see the pitch.
The site is open source

The council, the evidence pack, the prompts and the queue are all on GitHub. If a review helped you, a star helps other teams find it.

Star on GitHub