Skip to content
Sprint projectOct 25, 2026Hong Kong Hub

FeeGuard: Financial Agent Collusion Carriers and Private Execution

Gu Xinfeng · Team FeeGuard

Submitted to AI Collusion Research Sprint. Sprint projects are early-stage work by participants, not Apart Research publications.

Read the report

Report: FeeGuard: Financial Agent Collusion Carriers and Private Execution

Presentation

Presentation: FeeGuard: Financial Agent Collusion Carriers and Private Execution

Code (opens in new tab)
Share

FeeGuard investigates how AI agent collusion can cause financial harm and how an independent execution boundary can constrain harmful actions while preserving legitimate cooperation. We address all four Track 3 questions: action-based communication, trusted recruitment probes, peer replacement, and adaptation to monitoring.

Across three fixed treasury cases, we collected 141 live model calls and coupled agent decisions to genuine Groth16 proofs and mandatory Solidity execution. An instructed tool-order channel achieved 48/48 hidden-route matches; sorting reduced this to 24/48. Direct recruitment offers produced no unsafe joint approvals in six decisions. Blind peer observers correctly identified 3/9 cases in both raw-text and canonical views. Monitoring experiments continued for two rounds after actual execution feedback.

In deterministic controls, dual-agent approval executed 3/3 planted violations. The ZK boundary executed 0/3 while completing 3/3 honest actions. The archives contain 37 genuine proofs. External treasury verification requires zero of sixteen private witness openings, while retaining eight public inputs. Complete plaintext rules enforce the same finite policy more cheaply; ZK adds private verification.

These are bounded descriptive pilots using synthetic funds. They do not establish spontaneous collusion or universal prevention. Protection depends on complete authenticated sources, correct rules, and mandatory execution.

Reviews

Judging this Sprint?

Review “FeeGuard: Financial Agent Collusion Carriers and Private Execution”

Your public critique appears on the project page without your name. Reviews of strong projects are shared with funders, as you choose below.

Not shown on the project page.

Shown on the project page, without your name.

Only the Apart team reads this, and funders if you agree below.

Decline to score

Only when the quality of the writing makes the work impossible to follow. Say why in your private critique; the project page shows only that a judge declined, not why.

How much would this matter for the field if it worked? How innovative is it? For scores of 4-5: is this actually new to the field, or replicating recent work?

Scoring guide
  1. 1Negligible. No clear problem addressed, or no meaningful novelty.
  2. 2Limited. Addresses a real problem but with a generic or well-trodden approach. Incremental at best.
  3. 3Moderate. Clear problem with a reasonable approach; some novelty in framing or method beyond routine application of existing tools.
  4. 4Significant. Important problem with an original approach, or identifies a neglected problem area. A valuable contribution others could build on.
  5. 5Exceptional. Tackles a critical problem with a genuinely novel approach, or opens a new research direction. Clear theory of change. You'd be excited to share this with researchers in the area.

How sound are methodology, implementation, and findings?

Scoring guide
  1. 1Seriously flawed. Methodology broken, results uninterpretable, or implementation doesn't work.
  2. 2Weak. Approach has significant gaps: missing validation, flawed experimental design, or incomplete implementation.
  3. 3Competent. Technically solid given the short duration. Methodology makes sense, results are interpretable, limitations acknowledged, work builds toward clear conclusions.
  4. 4Strong. Thorough methodology with convincing validation. Results clearly support conclusions. Immediately useful for future work.
  5. 5Exceptional. Ambitious scope executed rigorously. Surprising findings, novel methods, or unusually robust validation.

How clearly are work, findings, and impact potential communicated?

Scoring guide
  1. 1Incomprehensible. Cannot determine what the project is actually claiming or doing.
  2. 2Hard to follow. Key information buried, missing, or diluted by excessive length. Significant effort to extract main points.
  3. 3Clear enough. Can understand the problem, approach, and results without undue effort. Core content clearly present: problem, method, findings, limitations.
  4. 4Well presented. Easy to follow, well-structured, appropriate level of detail. Target audience would get it quickly.
  5. 5Exceptionally clear. A pleasure to read. Complex ideas made accessible. Could serve as a model for how to present this type of work.
Sharing your name *

When we share a strong project with funders, your name, scores and public critique go with it, confidentially; this choice is only about whether your name is public. If you think this project deserves funding, please also endorse it: that carries the most weight.

Share my private critique with funders *

See our Privacy Policy.

No public critique yet.

Cite this project

@misc{xinfeng2026feeguard,
  title = {{FeeGuard: Financial Agent Collusion Carriers and Private Execution}},
  author = {Gu Xinfeng},
  year = {2026},
  month = oct,
  note = {Submitted to AI Collusion Research Sprint, an Apart Research Sprint},
  howpublished = {\url{https://apartresearch.com/sprints/projects/feeguard-financial-agent-collusion-carriers-and-private-execution-yv18}},
  url = {https://apartresearch.com/sprints/projects/feeguard-financial-agent-collusion-carriers-and-private-execution-yv18}
}