OMNI saysLayer 7 — metaSurf — is the protocol edge that VERIFIES every block before it’s accepted.
metaSurf (the drewless rename of the META layer) sits at the edge between the user's instance and the LEDGER. Its job: VERIFY the signal of every block before it's accepted as authoritative — gating bad actors at the layer below auth. Auth comes from the instance existing; metaSurf decides whether the next block may extend the chain at all (R9: metaSurf gates, no skip). It's the trust checkpoint.
Power-ups you unlock
metaSurf = renamed META layer
Sits between the instance and the LEDGER
VERIFIES each block’s signal before acceptance
Gates bad actors below auth (R9)
The Silent Failure attacks — common mistakes
Skipping metaSurf verification (violates R9)
Confusing metaSurf gating with auth
Accepting blocks without signal checks
Boss battleExplain what metaSurf checks that auth alone does not.
Example code
<!doctype html><html><head><meta charset="utf-8"></head>
<body style="background:#06040d;color:#b388ff;font-family:monospace;padding:20px"><pre>auth: the instance exists → you can act
metaSurf: VERIFY this block’s signal → may it extend the chain?
no skip (R9)</pre></body></html>