L2 📐 L2-912 ◆ Frontier — not yet benchmarked

Halo-Profile Inference Twin

Introduction

1 / 3

Halo-Profile Inference Twin is a digital twin specification derived from principle L1-912. It defines the forward operator and a 3-dimensional parameter space Ω over which benchmarks are seeded. Each benchmark drawn from this twin is a concrete measurement instance with fixed Ω values; solvers must invert that specific measurement.

Ω Parameter Space — 3 dimensions

halo: NFW|Burkert|MOND v_flat_kms: 50–300 concentration: 3–30
δ = 50 hardness 0.9

Earn PWM — build a benchmark from this twin

Each accepted L3 benchmark earns 60% of its mining pool + 15% royalty on every verified solution, forever.

🚀 Submit → earn PWM

Contents

2 / 3

On-Chain Artifact Registry

Base Sepolia → Base Mainnet on graduation
L1
L1 Principle L1-912 Testnet
L2
Digital Twin — Halo-Profile Inference Twin L2-912 Testnet

Digital Twin Specification — L2-912

Ω Parameter Space

ParameterRange
halo NFW|Burkert|MOND
v_flat_kms 50 – 300
concentration 3 – 30

ε (epsilon)

{
  "expression": "reduced \u03c7\u00b2 \u2264 1.2; recovered M200 within 0.1 dex",
  "type": "fn"
}
📝 Markdown source — L2-912.md

🎁 Contribute & earn PWM

Improve L2-912 — submit with or without uploading. Accepted submissions earn the 1/16 modify share of A(t).

⬆ Submit by uploading your files earn PWM · unlimited

Upload your .md + .json as a modification of L2-912 — the main way to contribute & earn. Unlimited submissions.

Log in to upload & submit your files.

✨ Or try a free one-click check free · 1×

No files, no typing — we submit a check of L2-912 for you once; it goes through review and earns the 1/16 share. One free no-upload Digital Twin per account.

You'll be asked to log in first — then it's one click, no files.

🛠 Helper: build your files in ChatGPT / Gemini / Claude

Prompt — copy into your LLM

You are helping me submit a MODIFICATION of L2-912 (Halo-Profile Inference Twin) to the PWM Protocol — a Digital Twin (L2) artifact.

I will paste a Markdown template (or the current L2-912.md).
1. Rewrite the Markdown so the science is correct and clearly explained for my change.
2. Regenerate the sibling L2-912.json so EVERY field matches the Markdown.
3. Keep the schema in the "File Mapping" footer at the bottom of the MD.
4. Keep the parent reference unchanged unless I ask otherwise.
Rules: the Markdown is the source of truth; use SI units; do NOT invent benchmark scores.
Output each file in its own fenced code block tagged with the filename.

Here is my template:
[PASTE THE .md HERE]