Develop with conet-l0d

conet-l0d composes Layer Minus for L1 overlay (Role A) and the intended Web3 Enterprise Gateway (Role B).

Role A is under development / lab-proven. Role B is destination — not a public hosting product. Read the docs before treating either as generally available.

Start here

Keep production join paths and destination architecture labeled separately.

Read Role A vs Role B

Overlay daemon for geth/Prysm peering is not the same claim as a shipped Enterprise Gateway.

Application Protocol draft

Wallet-addressed URI, signed requests, and Origin isolation are application-layer — L0 still only forwards OpenPGP armor.

Reproduce from Resources

Use GitBook Resources for live endpoints and public repos. Do not invent new domains.

Honesty checklist

Do not claim every production proposer has abandoned public listen.
Do not equate Peer Locator completion with a finished Application Protocol.
Backend gateways must strip colliding identity headers and inject only verified values.

Go deeper in the book

Full operator and protocol notes live in GitBook.