Siegfried Bozza

An open, verifiable rating for life-science papers. The evidence lives on the OriginTrail DKG, the score on a Base Sepolia contract, and the off-chain pipeline between them is built to survive lost webhooks, retried mints and stuck transactions. Under construction: the machine score runs on testnets, and human review with Chainlink VRF is next.

• Every write converges: stores, mints, fulfils and cancels read state first, and the LLM's score is computed once and read back from the minted asset, so retries and restarts never write twice.
• At-least-once ingestion with recovery: HMAC-verified Alchemy Notify webhooks, request-derived Inngest event ids, and a cron reconciler that reads the contract's pending set instead of scanning logs.
• Decisions on record: 36 ADRs, 1,841 Vitest tests and 74 Foundry tests (fuzz and invariants), with staging and production isolated down to contracts, graphs and oracle keys.

A custody backend slice: HD wallets, an append-only ETH ledger and signed EIP-1559 withdrawals, with an HTTP layer that never receives the mnemonic.

• Receipt-driven settlement: a broadcast is stored as pending, and the poller writes one outflow from the receipt (amount + real fee), never from a balance diff.
• Consistent, exact reads: every balance in one Multicall3 eth_call pinned to its block, bigint wei end to end, and a worst-case fee check before signing.
• Signing behind one module: only signer.ts signs and no key is stored or logged; 156 offline tests, CI green on main.

A case study in treating scientific peer review as a coordination game: authors stake ETH, an AI agent screens for plagiarism, Chainlink VRF picks reviewers who sign their reviews, Gemini or a senior reviewer sets the verdict, and an agent settles it on-chain, with research artifacts pinned to IPFS.

• Getter-light contract, projected reads: BioVerifyV3 emits events instead of exposing most view getters; Alchemy Notify delivers logs to an HMAC-SHA256-verified webhook that projects into Neon Postgres with optimistic concurrency, and the frontend reads product state from that projection.
• Dual-agent pipeline: a Submission Agent fetches the IPFS manifest and runs a neural search via Exa AI for plagiarism screening; a Review Agent manages multi-day human-in-the-loop peer review, with LangGraph checkpointers carrying the pause across serverless cold starts and Inngest retrying the agent runs that chain events start.
• VRF reviewer selection: after screening passes, Chainlink VRF draws peer reviewers from the staked pool, so the draw can be checked on-chain, as long as the coordinator is Chainlink's. The agent key settles every outcome and also owns the contract, so it could swap the coordinator (listed under limitations).

A proof-of-concept prediction market on Ethereum Sepolia: Chainlink Automation triggers resolution, Chainlink Price Feeds supply the price, and VRF picks ERC-1155 reward ids. The deployed contract has a known payout bug and an oracle-timing weakness, both documented under Known limitations.

• Automation-driven resolution: Chainlink Automation calls performUpkeep so eligible rounds move without a human operator clicking resolve.
• Oracle inputs: Chainlink Price Feeds for settlement prices and Chainlink VRF v2.5 for unpredictable ERC-1155 reward ids.

An experiment in ERC-1155 crafting rules: the ledger (FToken) handles balances while the rules contract (Forge) encodes recipes, cooldowns, and burn-then-mint in one call, with 38 Foundry tests.

• Atomic forging: Composite tokens (IDs 3–6) are created by burning their inputs and minting the result in a single transaction (burnBatch + mint), one wallet confirmation.
• Factory-owned ledger: Forge deploys FToken (ERC-1155) in its constructor and is its immutable owner, so users cannot mint or burn outside the recipes and ownership can never change.
• Foundry tests: 38 unit tests through the real deploy script, asserting exact custom errors and events; contracts verified on Etherscan.

A learning build for full-stack auction flows: Postgres triggers that track the highest bid and write notifications sent over private Supabase Realtime channels, RLS, scheduled closure via an Edge Function, and Stripe payments in test mode through a signature-verified webhook. Bid and payment rules are not all enforced on the server yet, as listed under Known limitations.

• Stripe payments: a signature-verified Stripe webhook records payment through a server-only Supabase service role; the payment notification fires once.
• Postgres-native workflow: triggers track the highest bid and write notifications, pushed to each user over Supabase Realtime; a scheduled close-auctions Edge Function closes due auctions.
• i18n + layering: French, English, and German via Lingui; services behind repository interfaces with Jest unit tests in CI.