It signs you into the page using your wallet address and cryptographic signature. The page can verify ownership without asking for a password or email.
Help Center
Frequently asked questions
Quick answers about wallets, ENS, IPFS templates, decentralized hosting, and UBNET.
Questions & Answers
All questions
Select a question to open its answer.
No. A normal wallet connection sends signatures, not private keys. Your wallet app keeps the secret key local.
The domain resolves to the template or CID you chose. Updating that record changes the live front end without needing a centralized hosting panel.
A social profile, business site, content hub, music page, creator portfolio, service marketplace, or custom onchain app. The same wallet and domain can power many layouts.
Nodes replicate the same content references and serve matching data independently. If one node disappears, other nodes can still serve the same verified content.
Hashes, CIDs, and content strings act like stable identifiers. Nodes can compare those strings to verify they are serving the exact same content, which keeps the system consistent across copies.
Yes. You can point ENS to a new template, change the contenthash, or publish new content while keeping the same wallet and domain relationship.
You are not renting an account from a platform. You keep control of the wallet, the domain, and the content flow instead of handing that control to a central login system.
Yes, but the wallet address is part of the identity. If you change wallets, you are changing the signer, so the page may need to be reconnected or reauthorized under the new address.
No. The goal is to let the wallet and ENS relationship stay under your control instead of being held inside a platform account you do not own.
No. The template files can live on IPFS and the ENS contenthash points the name to those files. The content still needs to be pinned reliably so it remains available.
You need an Ethereum wallet, an ENS name you control, and a template CID to place into the contenthash record. ENS registration and record updates may require ETH for network fees.
It is the ENS record that tells resolvers where the decentralized website lives. For Unblocked Profile, that usually means an IPFS CID, often written with the ipfs:// prefix.
Yes. The same domain, wallet, CID, and template model can support business pages, creator portfolios, music releases, marketplaces, service pages, community hubs, and campaign landing pages.
The Docs page explains the setup path, ENS records, IPFS hosting model, connection steps, use cases, and troubleshooting notes.