Skip to content

Add warren namespace codec (0xe9) for on-chain website hosting#395

Open
planetai87 wants to merge 2 commits intomultiformats:masterfrom
planetai87:add-warren-codec
Open

Add warren namespace codec (0xe9) for on-chain website hosting#395
planetai87 wants to merge 2 commits intomultiformats:masterfrom
planetai87:add-warren-codec

Conversation

@planetai87
Copy link

Adds WARREN on-chain website hosting path to the namespace table.

WARREN is a fully on-chain website hosting protocol on MegaETH
that stores HTML/CSS/JS directly on the blockchain via SSTORE2.
This codec is used in ERC-1577 contenthash fields for name service
resolution (similar to how ipfs/swarm/ipns are used with ENS).

  • Name: warren
  • Tag: namespace
  • Code: 0xe9
  • Status: draft

Live at: https://thewarren.app
X account : @thewarren_app

Copy link
Member

@vmx vmx left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds OK to me, though I'd like to have another approval from someone who might be more familiar with WARREN.

@0xBreadguy
Copy link

Commenting here to show support for the OP, who is working with us as a builder within the ecosystem.

@rvagg
Copy link
Member

rvagg commented Feb 18, 2026

there's a bunch of similar namespace entries down the table in the 0xbxxxxx range, would it be OK to move down there with that group?

@planetai87
Copy link
Author

Thanks for the suggestion! I actually placed it at 0xe9 because the 0xe2–0xe8 range already contains the core namespace entries (ipld, ipfs, swarm, ipns, zeronet, dnslink), so 0xe9 felt like the natural next slot in that group. Happy to move it if you still think the 0xbxxxxx range is more appropriate though — just let me know!

@rvagg
Copy link
Member

rvagg commented Feb 23, 2026

if there's not a strong pressure to reduce byte-count and the extra 2 bytes aren't going to cause grief, then it would be great if this were up with the other blockchain-related namespaces in 0xbxxxxx range, and warran-ns @ 0xb59910. As warran is a single-project protocol on an L2 and the namesspaces in 0xex are internet-level namespaces (also not tied to blockchains), the grouping makes more sense.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants