Mirrored from filpgf.io — ProPGF Batch 3 (Karma program 1479, application 6a2d3cdd31f8bfa184d49900, status: pending). Contact details redacted; canonical application lives on filpgf.io. 1.1 Project Name Plumbline : CalibrationNet Stability Project 1.2 Project Github https://github.com/Reiers/plumbline 1.3 Project Website https://faucet.reiers.io 1.4 Team Lead/Point of Contact Nicklas Reiersen (TSE Reiersen) 1.5 Category [ "Core Infrastructure" ] 1.6 Open Source Status Fully Open Source 2.1 Project Summary ## 2.1 Project Summary **Plumbline** ([github.com/Reiers/plumbline](https://github.com/Reiers/plumbline)) is the operational stability layer for the Filecoin CalibrationNet, run by TSE Reiersen (Org. 929 074 912). This proposal funds **6 months of operational ownership** of that surface, plus the new builder on-ramp + API roadmap. It is the **successor to the Curio/Blueshift calibration side letter**, which winds down Sept 1, 2026. ### What's covered | Component | What it is | Status | |---|---|---| | **2 stable SP test targets** | `t0143103` (raw 104.15 TiB / QAP 935.53 TiB) + `t0144416` (raw 14.12 TiB / QAP 14.12 TiB) - maintained as *repeatable* test targets across nv boundaries, not experimental SPs that reset between campaigns | 🟢 online & steady | | **Public faucet** | [faucet.reiers.io](https://faucet.reiers.io) - independent **tFIL + USDFC** drips, 24h per-asset cooldown, Cloudflare Turnstile gate, on-chain verification of every drip, live `/status` | 🟢 live since Apr 2026 | | **Calix nv-validation** | [calix.reiers.io](https://calix.reiers.io) - every network-version upgrade exercised end-to-end (manifest match, migration audit, state integrity) *before* mainnet adoption | 🟢 shipped clean through nv28 "Fire Horse" | | **Daily monitoring** | every CalibrationNet node + participating miner | 🟢 ongoing | | **Builder on-ramps + API** | one-flow self-onboarding to calibration funding + a public read-only builder API | 🔨 funded by this grant (`plumbline-monitor` / `plumbline-cli`) | ### Who this supports Every Filecoin developer who uses calibration as their integration target - application builders testing against `synapse-sdk` and `FilecoinPay`, storage providers rehearsing PDP flows before mainnet, contract developers staging FoC upgrades, and auditors who need repeatable conditions. **When calibration is hard to fund, hard to monitor, or its SP targets are unstable, FoC development velocity slows for the whole ecosystem.** This proposal removes that drag. ### The Filecoin-specific gap The surface above is funded today only by a residual Curio/Blueshift side letter (TSE Reiersen, Org 929 074 912) scoped to "maintain calibration infra" at **$3,500/mo**, which **winds down Sept 1, 2026**. The *delivered* surface — two stable SP targets, the public dual-asset faucet, daily monitoring, full nv-upgrade validation — is broader than that line funds, and there is **no successor funding after August**. A bounded ProPGF commitment formalises the surface with public SLOs + reporting, funds the builder on-ramp + API roadmap, and carries the surface past the side-letter wind-down **without a gap in service**. ### End-of-grant outcome > Calibration stays funded, monitored, and **stable** for 6 months. Both SP test targets stay online and steady. Every `nv` upgrade in the window gets a green Calix validation publicly within 24h …[truncated] 2.2 Who does this work support? [ "Network Infrastructure", "Storage Providers", "Application Builders", "Onramps" ] 2.3 Total Funding Requested (USD) $17,000.00 2.4 Milestones & Budget [ { "title": "Milestone 1 - Calibration operations + SLO publish (Blueshift-covered month, $500 delta)", "description": "Continuous operation of the CalibrationNet stability surface - two stable SP test targets (`t0143103`, `t0144416`), the Plumbline faucet (tFIL + USDFC), Calix nv-upgrade validation, and daily network monitoring - plus formalising **public SLOs** and a **public status page**.\n\n> **Funding note.** July maintenance is funded by the existing Blueshift side letter (TSE Reiersen, Org 929074912) at $3,500/mo. This ProPGF milestone covers only the **$500 delta** on top - the added scope (public SLOs, status page, on-call formalisation, builder-support channel) the side letter does not fund. No double-funding: side letter and milestone cover *different dollars* of the same $4,000/mo target.\n\n**Concrete tasks**\n- Keep both SP test targets online & steady, and Plumbline + Calix live & serving, for the full month.\n- Publish written SLOs: Plumbline (p99 drip latency ≤ 60s tFIL / ≤ 90s USDFC; ≥ 99% monthly uptime), Calix (validation live within 24h of any `nv` activation), SP test-target availability (≥ 99%).\n- Wire a Prometheus exporter on each service; stand up a public status page (the `plumbline-monitor` sibling).\n- Open a public builder-support channel (Slack/Telegram) for calibration on-ramp questions.", "dueDate": "2026-07-31", "fundingRequested": "$500", "completionCriteria": "- ✅ All services live & serving across July (status-page history shows it).\n- ✅ Public SLOs published on faucet.reiers.io and calix.reiers.io, plus SP availability on the status page.\n- ✅ Public status page live at a stable URL (e.g. `status.reiers.io` or per-service `/status`).\n- ✅ Prometheus metrics endpoint exposed for each service.\n- ✅ Public builder-support channel announced and reachable." }, { "title": "Milestone 2 - Calibration operations + on-ramp tooling (Blueshift-covered month, $500 delta)", "description": "Continuous operation of the surface for August, plus shipping the **quick on-ramp tooling** and a **public builder API** for calibration funding/status.\n\n> **Funding note.** August maintenance is funded by the Blueshift side letter at $3,500/mo — its *final* covered month (the side letter winds down Sept 1). This milestone covers the **$500 delta** to reach $4,000/mo, funding the on-ramp tooling + builder API the side letter does not.\n\n**Concrete tasks**\n- Keep all services live & serving for the full month.\n- Ship quick on-ramp tooling: a one-command / one-click path for a new builder to get funded on calibration (tFIL + USDFC) and pointed at the right endpoints.\n- Ship a public read-only builder API (faucet status, drip endpoints, calibration network health) so downstream tooling integrates without scraping HTML.\n- Document the on-ramp flow publicly.", "dueDate": "2026-08-31", "fund …[truncated] 3.1 Impact pathway **Output** → a continuously-funded, monitored, human-on-call CalibrationNet stability surface. Two stable SP test targets (`t0143103`, `t0144416`) stay online and steady. Plumbline keeps developers funded with both tFIL and USDFC. Calix validates every `nv` upgrade end-to-end and surfaces the result publicly within 24h of activation. New builder on-ramp tooling + a public builder API let teams self-onboard to calibration funding in one flow. **Outcome** → FoC integration work (`synapse-sdk`, FilecoinPay, PDPVerifier client integrations, flagship-client onboarding rehearsals) proceeds without the friction of a broken or under-funded calibration stage. Developers don't lose hours per week chasing faucet drips that didn't land, hunting a stable SP to test PDP against, or triaging a calibration upgrade with no public validation. **Impact** → shorter cycle time from "we built a paid-deal integration" to "it's on mainnet." The KPI move is **upstream** - we don't add a paid deal directly; we make every team *trying* to add one go faster by removing the calibration-stage tax, and we keep `nv` upgrades from regressing on the way to mainnet. 3.2 Verification metrics | Metric | Data source | How it's measured | Target (end of grant) | |---|---|---|---| | Plumbline monthly uptime | Public status page at faucet.reiers.io/status | 1 − (minutes-down ÷ minutes-in-month) | **≥ 99%** each month | | Plumbline drip success rate | Server-side logs (monthly public summary) | successful drips ÷ total drip requests | **≥ 98%** | | Calix nv validation within 24h of activation | Public Calix timestamps + on-chain nv activation block | hours between activation block and dashboard-green | **≤ 24h, every nv** | | SP test-target availability (`t0143103`, `t0144416`) | On-chain power on calibration.filfox.info + status page | % of grant period both SPs online & steady | **≥ 99%** | | Builder on-ramp adoption | Public builder API request logs (monthly summary) | # of distinct builders self-onboarding via the on-ramp | **report monthly, growing** | | SynapS3 + downstream success via Plumbline | SynapS3 release-notes / dev-channel citation of faucet.reiers.io | citation present: yes/no | **Yes, retained** | 3.3 References 1. **Andrew Jackson (@snadrus)** - Curio core team (FilOz). Familiar with the Calix + nv28 "Fire Horse" rollout and the broader operational record. Contact via Slack (@snadrus). 2. **LexLuthr** - Curio core team (FilOz). Familiar with the CalibrationNet operational surface from the Curio team's own use of it. Contact via Slack (@LexLuthr). 3. **Lee - SynapS3 integrator.** Direct downstream consumer of Plumbline: *"Perfect, that's exactly what I needed. I'll integrate the endpoint into SynapS3."* First real public adopter of the dual-asset (tFIL + USDFC) faucet pattern. Contact available on request. 4.1 Monthly Operating Burn [ "$10-$100K (small team)" ] 4.2 What % of total team monthly burn depends on this grant? Solo operation (TSE Reiersen). For the calibration-stability surface specifically, this grant is the funding line: from **September 2026 it is the sole funding source** once the Blueshift side letter winds down. During the overlap months (Jul + Aug) the side letter covers $3,500/mo and this grant covers the remaining **$500/mo delta** to reach the $4,000/mo target; from September the grant covers the **full $4,000/mo**. The share of this surface's burn dependent on the grant rises from **~12.5% (Jul/Aug) → 100% (Sep onward).** (The lead engineer's salary is covered by our separate Curio Core + Lantern application; this proposal funds only the calibration-ops line, exactly as that application's budget carves it out.) 4.3 If this grant is not awarded, what happens? The CalibrationNet stability surface (two stable SP test targets, the Plumbline faucet, Calix nv-validation, daily monitoring, builder on-ramps) is funded today by a Curio/Blueshift side letter that **winds down Sept 1, 2026**; without a successor grant the funded commitment ends at that seam and the surface drops to unfunded best-effort - putting the public SLOs, the builder on-ramp tooling, and reliable nv-upgrade validation at risk **exactly as FoC integration testing on calibration ramps up.** 4.4 Core Team **Lead engineer / operator: Nicklas Reiersen (TSE Reiersen, Org. 929 074 912).** 8+ years in the Filecoin ecosystem. SAFT participant 2017; community contributor since 2019. Protocol Labs 2021–2023 (Lotus + Boost technical-support engineer). Curio core team 2023–2026 (through engagement close-out May 2026). Active member of all MinerX cohorts; first-name relationships with a substantial fraction of the current mainnet SP set. Marketing degree alongside the engineering. [github.com/Reiers](https://github.com/Reiers) · [linkedin.com/in/nicklas-reiersen](https://linkedin.com/in/nicklas-reiersen) · [reiers.io](https://reiers.io/) > **Same operator as our Curio Core + Lantern application** ($130k, submitted). That application funds the engineering salary line and **explicitly scopes the calibration-ops bandwidth — Plumbline, Calix, the mainnet SP operations — to this proposal at proposal-specific rate.** The two reconcile by design; neither cross-funds the other. **Infrastructure footprint (Norwegian datacenter)** - Production fleet hosting the two CalibrationNet SP test targets (`t0143103`, `t0144416`), the public faucet, and the Calix validation dashboard. Curio batch sealing + fast snap deals + a CalibrationNet-optimized Boost are what let Plumbline add hundreds of TiB of QAP during peak campaigns. - Multiple independent internet providers for redundancy at the colocation site — this is the uptime story behind the SP targets, the faucet, and Calix. - Datacenter operations partner maintains the physical fleet on a long-standing colocation contract; software-side operations sit with TSE Reiersen. **Honest project-specific budget (6 months, $17,000 total)** | Line item | Rate | Notes | |---|---|---| | Calibration ops + on-call engineering (daily monitoring, incident response, nv-validation, faucet operation, builder on-ramp + API build, public reporting) | **$4,000/mo target** | Jul + Aug the Blueshift side letter covers $3,500 of this; ProPGF funds the $500 delta. Sep–Dec ProPGF funds the full $4,000. | | **ProPGF ask** | **$17,000** | $500 + $500 + $4,000 × 4 | This is the successor to the Curio/Blueshift calibration side letter (TSE Reiersen, Org 929 074 912), which pays $3,500/mo through August and winds down Sept 1. **App 1 (Curio Core + Lantern) is where the engineering salary lives; this proposal funds the calibration-ops line specifically** — the marginal delta during overlap months, the full rate after the side letter sunsets. **Track record (all on-chain / public)** - Operate two long-running CalibrationNet SPs as stable test targets: [t0143103](https://calibration.filfox.info/en/address/t0143103) (raw 104.15 TiB / QAP 935.53 TiB) and [t0144416](https://calibration.filfox.info/en/address/t0144416) (raw 14.12 TiB / QAP 14.12 TiB) — both online & steady. - Shipped the **Plumbline faucet** ([faucet.reiers.io](https://faucet.r …[truncated] 4.5 Has your team received a ProPGF grant or funding from PLFIF before? [ "Yes" ] 5.1 Key risks & dependencies **External dependencies** - **USDFC mainnet supply** for the M5 mainnet-preview drip - gated on modest USDFC liquidity on the dispenser address. *Mitigation:* M5 is explicitly capped (e.g. 5 USDFC/address/week, hard monthly cap); the working capped endpoint is the deliverable, not unconditional supply. - **Calibration upgrade cadence** - we can't predict exactly when the next `nv` lands; M3–M6 nv-validation is tied to "whatever lands in the window." *Mitigation:* Calix is reusable across upgrades; if no `nv` lands in a milestone window, that milestone delivers a dry-run validation report against the latest manifest. - **Datacenter / colocation reliability** for the SP test targets and public services. *Mitigation:* long-standing operator relationship; multiple independent uplinks; both SPs have stayed online & steady across nv boundaries to date. **Technical risks** - **Faucet abuse / Sybil** - public-path drips are gated by Cloudflare Turnstile + 24h per-asset per-address cooldown, but determined attackers can rotate addresses. *Mitigation:* per-asset hard caps on the dispenser balance, alerting on drip-rate anomalies, key-based auth for high-volume consumers (CI, SDK integrations). - **Builder API / on-ramp is net-new build** (M2 onward). *Mitigation:* the umbrella README already names `plumbline-monitor` and `plumbline-cli` in the build order - this is executing an existing roadmap, not greenfield design. **Team risks** - **Solo operator.** *Mitigation:* everything public, decisions captured in writing, advisors with deep context (LexLuthr, @snadrus) exist, and the M6 runbooks are scoped so a successor could pick up the suite from public docs alone. - **Single operator across both TSE proposals** (App 1 Curio Core + Lantern, App 2 this one). If reviewers fund only one, that's fine - the proposals are intentionally separable; neither cross-funds the other. Any feedback you have on the application process? Well-structured form. Anything else you want to share that we didn't ask? Three things worth surfacing for reviewers: **(1) This is the successor to an existing, cleanly-delivered grant - not a new ask out of nowhere.** The CalibrationNet stability surface is funded today by a Curio/Blueshift side letter (TSE Reiersen, Org 929 074 912) at $3,500/mo for June, July and August 2026, for "maintaining Filecoin calibration infra work." That side letter winds down Sept 1, 2026 unless a successor is executed by Aug 15. **This proposal IS that successor.** **(2) No double-funding - the dollars don't overlap.** The target rate for the full surface (two stable SP test targets, the public tFIL+USDFC faucet, daily monitoring, nv-upgrade validation, and the new builder on-ramp + API) is $4,000/mo. For the two months the side letter still covers (Jul + Aug), ProPGF is asked for only the **$500/mo delta** on top of the side letter's $3,500. From September, when the side letter has sunset, ProPGF funds the full $4,000/mo. The milestone table reflects this exactly: $500 + $500 + $4,000 × 4 = **$17,000** over six months. **ProPGF only ever pays for dollars the side letter does not.** **(3) Deliberately distinct from our other Batch 3 applications.** - vs. my **Curio Core + Lantern** application ($130k): that one funds *building software* (a pure-Go FoC SP + light node) and is Objective 1 **Direct**; this one funds *operating infrastructure* (keeping CalibrationNet stable & usable) and is Objective 1 **Indirect**. App 1's budget explicitly carves the calibration-ops bandwidth out to this proposal. Fund either alone - neither cross-funds the other. - vs. the **Stax-Infra snapshot** application: that one owns the calibnet *snapshot* deliverable; this one owns faucet + SP test targets + nv-validation + on-ramps. **No deliverable appears in two applications.** This proposal funds the operational layer that complements implementation work elsewhere in the ecosystem. It doesn't compete with any Filecoin implementation; it keeps CalibrationNet stable, funded, and usable regardless of which implementation a builder runs - the right structural posture for a public-good operational commitment. Contributing to Core Infrastructure? The operational layer of the Filecoin CalibrationNet: two long-running, deliberately-stable Storage Provider test targets (t0143103 primary, t0144416 backup), the public dual-asset tFIL + USDFC faucet at faucet.reiers.io, daily network monitoring, and end-to-end nv-upgrade validation (Calix) run before every mainnet adoption. Used by SynapS3, the FoC integrator community, and every developer who needs repeatable conditions on calibration. Objective 1 Indirect Objective 2 Indirect Objective 3 Indirect Open Source Context N/A - fully open source under MIT. The `plumbline` umbrella, `plumbline-faucet`, and `calix` are public; the roadmap siblings `plumbline-monitor` (status page + probes) and `plumbline-cli` (operator + builder scripts) ship public under the same license. No closed components.