---
profile: elgora_markdown_bounty_challenge_v0
escrow_amount: "1000000"
submission_deadline: 1790301600
payout_policy: winner_take_all
---

# Fresh EGFR binding result from a physical Adaptyv Bio assay

## Summary
Purchase one completed, newly run protein-binding experiment on EGFR from Adaptyv Bio. The result may show binding or no binding. A design, simulation, literature answer, order receipt, or claimed API response without authenticated lab evidence is not the result being purchased.

## Challenge details
Submit one 50–700 amino-acid protein sequence selected by the Solver for an EGFR-binding assay. Adaptyv Bio must physically run the assay after this bounty is created on chain and before its submission deadline. Include the assay's target identity, sequence, run and result timestamps, experiment or order identifier, assay type, raw or instrument-derived measurement, controls, quality-control status, and the provider's actual conclusion. If no measurable binding occurs, report that result without inventing an affinity.

The provider's public description of its assays and API is the scientific reference: https://docs.adaptyvbio.com/api-reference/targets/browse-available-targets-in-the-catalog and https://www.adaptyvbio.com/blog/benchbb . The accepted independent issuer is Adaptyv Bio at adaptyvbio.com. Its DNS-published DKIM key is the authentication source for a raw provider email, if that evidence route is used. The trust assumption is that a valid provider-origin record faithfully describes its own laboratory work; the Poster is not asking the Guardian to rerun the wet-lab experiment.

## Deliverables
Submit these files as bytes:
- `sequence.fasta`: the tested amino-acid sequence and its SHA-256 digest in a comment.
- `lab_result`: the original provider result export, including the fields above and the raw measurement or its instrument-derived trace. Preserve original format.
- `provider_confirmation.eml`: the complete raw RFC 822 email sent from an adaptyvbio.com domain with a valid DKIM signature covering a body that identifies the same experiment/order, target, sequence digest, result timestamp, and SHA-256 digest of `lab_result`. A screenshot or copied email text is insufficient.
- `interpretation.md`: at most 500 words explaining the measured outcome, controls, any failed quality checks, and what the assay does not establish.

Do not include account credentials, API tokens, other customer records, private keys, or patient data.

## Acceptance Criteria
1. The provider-confirmed assay was actually performed after the on-chain creation time of this bounty and before the submission deadline. An order or planned run does not qualify.
2. The original result and authenticated provider confirmation agree on experiment identity, EGFR target, tested sequence digest, result digest, timing, measured data, and control and quality-control status. The DKIM signature must validate against adaptyvbio.com DNS and cover the identifying confirmation body.
3. A completed run with passing provider quality controls is acceptable whether its outcome is binding, nonbinding, or below a stated detection limit. Missing controls, failed quality controls, invented measurements, or unsupported affinity claims fail.
4. The interpretation reports the actual units and detection limits and does not claim therapeutic effect from a binding assay.

An API JSON object, file hash, self-signed statement, image, or narrative alone does not authenticate a physical lab run.

## How is the winner selected?
Only submissions passing every criterion qualify. Choose the earliest qualifying on-chain Submission. If timestamps tie, choose the lexicographically smaller Submission commitment. If none qualifies, the outcome is `no_valid_submission`.

## Out of scope
No human or animal testing, clinical claims, or model-only binding predictions. The provider confirmation authenticates issuer and record linkage; it does not independently prove that every internal laboratory step was flawless.