Structure lesson (licence does not allow quoting code)

BidTrace

Program for Colosseum Hackathon

Original: Ujjwal1396/BidTrace
SuperStack fork: Blockchains/BidTrace @ f6c03ff
Stars: 1
Last push (original): 2026-10-14
Languages: Python, HTML, TypeScript, Rust, JavaScript, Dockerfile
Detected stack: Anchorweb3.js
Categories: Other
Licence: none detected: code not quoted on Sol.College
Homepage: https://bit-trace-one.vercel.app

Architecture

60 source files. By extension: .py ×31, .rs ×20, .js ×6, .ts ×3.

Top-level directory	Source files
`programs`	20
`tests`	15
`bidtrace_py`	9
`(root)`	5
`public`	4
`verifier`	3
`bidtrace`	2
`scripts`	2

On-chain programs: programs/bidtrace

How it works: instructions and accounts

Each instruction handler and the accounts struct it validates, found by reading the Rust source. Links go to the exact line at the pinned commit.

Instruction	Accounts	Source
`advance_tender_phase`	`AdvanceTenderPhase`	`programs/bidtrace/src/lib.rs:84`
`refund_disqualified_bond`	`RefundDisqualifiedBond`	`programs/bidtrace/src/lib.rs:158`
`handle_advance_tender_phase`	`AdvanceTenderPhase`	`programs/bidtrace/src/instructions/advance_tender_phase.rs:13`
`handle_refund_disqualified_bond`	`RefundDisqualifiedBond`	`programs/bidtrace/src/instructions/refund_disqualified_bond.rs:34`
`handle_lock_tender`	`LockTender`	`programs/bidtrace/src/instructions/lock_tender.rs:17`

Where the Solana code lives

Source files that import a Solana SDK, ranked by how many Solana APIs they use, with the APIs each one calls. Read them in this order to see how the app talks to the chain.

File	Solana APIs used
`tests/bidtrace.ts`	`PublicKey`, `findProgramAddressSync`, `SystemProgram`, `Keypair`, `requestAirdrop`, `getBalance`
`programs/bidtrace/src/instructions/commit_dual_bid.rs`	`Pubkey`, `seeds`, `Transaction`, `Program`, `transfer`, `CpiContext`
`programs/bidtrace/src/state.rs`	`Pubkey`
`programs/bidtrace/src/instructions/commit_evaluator_grade.rs`	`seeds`, `AccountInfo`, `Program`
`programs/bidtrace/src/instructions/commit_bid.rs`	`seeds`, `Transaction`, `Program`, `transfer`, `CpiContext`
`programs/bidtrace/src/instructions/finalize_technical_scores.rs`	`seeds`, `Pubkey`, `has_one`
`programs/bidtrace/src/instructions/record_award_qcbs.rs`	`Pubkey`, `has_one`, `seeds`
`programs/bidtrace/src/instructions/initialize_committee.rs`	`has_one`, `seeds`, `Program`, `Pubkey`
`programs/bidtrace/src/instructions/reveal_evaluator_grade.rs`	`seeds`, `AccountInfo`
`programs/bidtrace/src/instructions/reveal_bid.rs`	`seeds`, `AccountInfo`
`programs/bidtrace/src/instructions/initialize_tender.rs`	`seeds`, `Program`
`programs/bidtrace/src/instructions/review_administrative_compliance.rs`	`has_one`, `seeds`

Dapp: devnet deploy pending

⏳ Devnet deploy pending — goes live when the devnet wallet is topped up. This fork's own dapp is not deployed yet, so there is no program address or transaction to show. It is queued in dapp-queue.txt; once devnet SOL is available it is deployed, exercised with real devnet transactions, and this section switches to the live dapp at /dapps/bidtrace/. Until then, the lesson and step-by-step guide below are complete, and you can run it locally with the commands below.

How to run, build and test

These commands come from the repo's own manifests (package.json scripts, Anchor.toml, Cargo, go.mod, Makefile). Check the README for prerequisites and environment variables.

Directory	Command	Runs
`.`	`npm run start`
`.`	`npm run test`
`.`	`anchor build`
`.`	`anchor test`
`.`	`anchor run test`
`.`	`cargo build`
`.`	`cargo test`

What you could build from it

Fork the SuperStack copy and extend it within the Other gaps listed on the idea page.
Learn the pattern first: Program Derived Addresses (PDAs)
Learn the pattern first: Cross-Program Invocations (CPIs)