Pylon, the gateway to the inner part of an Ancient Egyptian temple or Christian cathedral - Wikipedia

Pylon is an Internet Computer HTTP Gateway that provides a more trustless and decentralized way to access the Internet Computer blockchain.

Internet Computer HTTP Gateways translate Internet Computer API calls into standard HTTP calls that a browser can understand. Without an HTTP Gateway, a browser is unable to interact with the Internet Computer network.

1. Introduction
2. Technical Introduction
3. Roadmap
4. Installation
5. Build Verification
6. Contributing

Pylon is similar, in theory, to an Internet Computer Boundary Node, which is currently the only way to interact with the Internet Computer network. The main practical difference is that it runs locally on your own computer rather than on a centrally controlled remote server.

The Internet Computer Boundary Nodes provide two flavors of HTTP Gateways:

• ICX Proxy: A service that runs entirely on an Internet Computer Boundary Node. Every time a request is sent through ICX Proxy, the end user is trusting the Boundary Node.
• Service Worker: When a Service Worker is downloaded to an end user's browser, the end user is trusting the Boundary Node to give it the correct Service Worker. Assuming that the user receive's the correct Service Worker, further requests are performed in a trustless manner.

Pylon solves the problem of needing to trust the Boundary Node to deliver the correct Service Worker to your browser. Pylon is open-source and the executable that is downloaded to your computer can be deterministically verified against the codebase, no trust needed. Check the build verification for instructions on how to verify builds.

With the HTTP Gateway logic running locally on an end user's computer, they are able to interact with the Internet Computer in a trustless manner. However, it is still not completely decentralized. Pylon still relies on the API Node of the Internet Comptuer Boundary Nodes to route API calls to the relevant canisters. These API calls are verified locally by Pylon, but they are still routed through centralized servers. This will improve once the API Boundary Nodes are decentraliezd, see this forum post for more details.

Under the hood, Pylon is essentially a Chromium browser with many browser features stripped out. This function is provided by the Electron framework.

Pylon provides the HTTP Gateway functionality by intercepting HTTP requests made by the internal browser and translating them into Internet Computer API calls. This is similar to how the Service Worker implements the HTTP Gateway Protocol.

Pylon aims to become an Internet Computer homepage, providing a browsing experience tailored to the Internet Computer blockchain.

• Standard browser features
  • Keyboard shortcuts
  • Tab management
  • Bookmarks & reading lists
  • Caching
  • System notifications
• dApp directory
• Privacy and security customization
  • Blocking of centralized analytics and tracking
  • Blocking of other centralized services
    • Content delivery networks
    • Centralized API servers
  • Verification of blackholed or DAO controlled canisters
    • See this article for more information.
• Self-sovereign identity support
  • Internet Identity
  • Metamask
  • NFID
• Decentralized integrations:
  • Search providers
  • News feeds
  • Notifications inbox
  • Crypto wallets