Skip to content

Instantly share code, notes, and snippets.

View koeppelmann's full-sized avatar

Martin Köppelmann koeppelmann

168 followers · 5 following
View GitHub Profile
@koeppelmann
koeppelmann / .gitignore
Last active June 8, 2026 14:52
Fully collateralized symmetric options reference contract
cache/
out/
@koeppelmann
koeppelmann / whitelist-wrappers.json
Last active June 11, 2026 06:11
Whitelist CoW leverage wrappers on Gnosis staging (Safe Transaction Builder batch)
{
"version": "1.0",
"chainId": "100",
"createdAt": 1781196000000,
"meta": {
"name": "Whitelist CoW leverage wrappers + solver EOA (staging) via proxy-admin",
"description": "setManager(self) -> addSolver(CoWSafeWrapper) -> addSolver(CowFlashLoanWrapper v6) -> addSolver(solver EOA) -> setManager(restore original 4/12 manager). Run from the proxy-admin Safe (2/6).",
"txBuilderVersion": "1.18.0",
"createdFromSafeAddress": "0x68185584ccb166806f7ed69996380f50ac06035b",
"createdFromOwnerAddress": "",
@koeppelmann
koeppelmann / concise.md
Last active June 11, 2026 06:01
Safe Tx Builder JSON: whitelist CoW leverage wrappers (Gnosis staging) from 2/n admin

Safe Tx Builder JSON — whitelist CoW leverage wrappers + solver EOA (Gnosis staging)

Update 2026-06-11: added a third addSolver for the fresh solver EOA 0xFa5d3f85da8395D4562D18422cB27e032a676Af1 — the address that will actually call wrappedSettle. Wrappers alone aren't enough: the authenticator must also allow the caller. (JSON uses data: null so the Tx Builder decodes each call into readable setManager/addSolver entries instead of "Custom hex data".)

JSON for the Safe Transaction Builder to whitelist everything needed on Gnosis staging (authenticator 0x02073540567FA1EABcBf74C2F7E6F9029ca7d800) from the 2/n proxy-admin Safe

@koeppelmann
koeppelmann / index.html
Created June 22, 2026 12:23
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>Swarm File Upload</title>
<script src="https://unpkg.com/@ethersphere/bee-js/dist/index.browser.min.js"></script>
<!-- Helia for IPFS in browser -->
<script type="module">
import { createHelia } from 'https://esm.sh/helia@4';
@koeppelmann
koeppelmann / deployment_report.md
Last active July 1, 2026 19:27
EEZ two-composer deployment on 147.135.221.107 — issue report (2026-07-01)

Two-composer EEZ deployment on 147.135.221.107 — issue report

Chain: Chiado L1 (10200) + EEZ Rollup0 L2 (10201) • Registry 0xd3a59fc7…99317 • Composers C1 / C2 Date: 2026-07-01 • Updated: 2026-07-01 after live diagnosis with Edu

Correction to the original diagnosis of #1

The initial version of this report attributed the failing L1→L2 deposits to the two-composer bundle race described in eez-rollup0#20. That was wrong. After Edu identified the real cause on-chain and I re-tested, the actual behavior is described in the corrected #1 below. The two-composer race may still exist as a separate issue, but it is not what I was reproducing.