UNBLOCKED.PROFILE

Choose your publishing model

One template system.
Three levels of control.

Start free with a template that stays updated for you. Move to a version made only for your ENS name, or download every file and run the system yourself. You can begin at any stage and move up when you need more control.

Included at every stage UBNET SDK

The same network-ready foundation, whichever path you choose.

Template path

Choose how much you want to manage

  1. Stage 1 · Free default Best place to start

    Use the template. We maintain it.

    The free default template is made for adoption and learning. It gives every ENS user a working Unblocked Profile experience without asking them to download files, manage hosting, or keep replacing a CID key.

    What you get

    • A free, shared default template
    • Automatic template updates
    • A stable template key you do not need to change
    • No code or server maintenance

    How visitors open it

    Use an ENS-to-IPFS browser gateway such as .limo or ipfs.name. These services resolve the shared Unblocked template for browsers that do not open decentralized ENS websites directly.

    Choose this when: you want the easiest way to learn, launch, and see how the full system works.

    Start with the free template
  2. Stage 2 · ENS hardcoded Personalized

    Your ENS name, built into the template.

    This advanced template is generated for one ENS domain. Your name is hardcoded into the files, so the finished template is tied to your identity and cannot be reused as another user's profile.

    What changes

    • Your ENS name is permanently set in the template
    • The template is pinned through the UBP gateway
    • You receive a dedicated CID for the finished files
    • You add that CID to your ENS content hash

    How visitors open it

    In browsers with native ENS website support, such as a properly configured Brave browser, visitors can enter yourname.eth directly. Gateway URLs can still be used as a compatible fallback.

    Choose this when: you want a ready-to-use personal build without becoming the developer or hosting operator.

    Request a hardcoded template
  3. Stage 3 · Developer source Full control

    Own the files. Change the system.

    The developer template is the open-source path for engineers, builders, and advanced users. Download the complete package, edit the design and functions, deploy it to IPFS, and connect it to the network setup you choose.

    What you control

    • Every HTML, CSS, JavaScript, and asset file
    • Themes, layouts, features, and integrations
    • Your deployment, pinning, gateway, and updates
    • Your own network services and infrastructure

    What you take on

    You are responsible for testing, publishing, pinning, and maintaining your version. When you publish changed files, you manage the resulting CID and update your ENS content hash when needed.

    Choose this when: you want to build a distinct product or operate an independent version of the template.

    Download the template ZIP

At a glance

What is different between the three stages?

Decision 01 Free default 02 ENS hardcoded 03 Developer source
Setup Fastest; no code Delivered ready for your ENS You configure and deploy it
Identity Shared template reads the user Your ENS name is built in You define the identity logic
Updates Automatic; handled for you New builds use a dedicated CID Handled entirely by you
Browser access .limo or ipfs.name gateway Direct .eth in supported browsers Depends on your deployment
Code control Use the maintained default Personalized, managed build Full source and infrastructure control
Best for New users and adoption Advanced ENS users Developers and engineers

Shared foundation

Every template includes access to the UBNET SDK system.

Choosing a stage changes who maintains the files and how the site is resolved. It does not remove the UBNET foundation. Free users, hardcoded-template owners, and independent developers can all build on the same SDK-connected system.

Wallet-native identity Network-connected features Content and media tools Room to extend

Plain-language guide

Where the CID key fits

01

The template is the website

It contains the interface, code, assets, and UBNET connections that make your profile work.

02

The CID points to published files

A CID identifies a version of files on IPFS. It is a content address, not a password or private key.

03

ENS connects your name to the site

Your ENS content hash tells compatible browsers and gateways where to find the decentralized website.

Not sure which stage you need?

Start with the free default. You will learn the system without locking yourself into hosting or maintenance, and you can move to a personalized or developer template later.

Read the setup guide