BASE ID

Twitter

What is base.blog?

A privacy preserving BASE ID gateway for resolving base Name Service records and associated IPFS/IPNS/Skynet content (Web 3.0). Base.blog allows users and dApp developers to effortlessly access and host static sites built with a combination of IPFS/IPNS/Skynet and BASE ID.

Why do we need base.blog?

Core internet infrastructure is becoming increasingly centralized and as such, several existential threats have emerged that undermine the principles of an decentralized, open and free internet:

• Single points of failure (Cloudflare, CDNs, etc)
• All BASE ID gateway infrastructure is currently operated by a single entity (Cloudflare)
• Censorship
• Lack of non-commercial infrastructure
• Opacity of terms of service agreements and moderation policies
• Proliferation of proprietary browser extensions which require centralized services (Unstoppable domains, etc…)
• The erosion of the “commons” and “public space”
• Web 3.0 adoption is still nascent
• Most browsers cannot natively access BASE ID/IPFS/IPNS/Skynet

For end users, this means a limited selection of poor quality services that increasingly resemble a cable TV package.

The Base.blog project brings additional resiliency to dApps by providing an alternative means of access as a public good. Application owners can directly participate in the roadmap of Base.blog, giving key stakeholders influence over the services they depend upon. As the decentralized web continues to grow, it is imperative that community projects facilitate the transition from Web 2.0 to Web 3.0.

How does base.blog work?

Base.blog operates as a reverse proxy for BASE ID names and IPFS content.

Base.blog uses a wildcard DNS record *.base.blog to dynamically capture requests for all BASE ID domains. The Base.blog service automatically resolves the IPFS/IPNS/Skynet contenthash of the requested BASE ID record and returns the corresponding static content over HTTPS. Since native IPFS/IPNS/Skeynet resolution capabilities are missing from the majority of browsers, base.blog represents a bridge from the “normal” internet to the decentralized one.

Zero-configuration is required in order to access or host a site or dApp on base.blog, making base.blog an excellent no-cost solution for providing Web 2.0 access to your project.

Security and Privacy

The Base.blog project enforces strong origin isolation policies for all resources by default. Projects accessed through base.blog automatically receive security hardened browser headers and all client data is encrypted with TLSv1.3 (default) or TLSv1.2 using the latest ciphersuites. All log data is fully anonymized, which prevents the ability to uniquely identify any single user.