Zap – The First Web Browser Built to a Decentralized Future with BTFS

Zap by FrontLabs – Your Gateway to the Decentralized Web, Powered by BTFS


Basic Information

Project Name: Zap

Project Track: infra-security

Team Name: FrontLabs

Team Members: 2 (@arman, @elluminazk)


Social Info

Telegram: @Arman @elluminazk
Website: https://zap.frontlabs.cloud


Project Overview

Project Goal:
Zap is building the first fully decentralized browser on the TRON-BTFS stack. Unlike traditional browsers or plug-ins, Zap is built into the BTFS ecosystem, with your local BTFS node becoming your gateway and identity. It exposes a new class of dApps “BTFS-native apps” which operate entirely on peer-to-peer protocols without centralized relays, SDKs, or servers.

Unique Value Proposition:
Where current dApps rely on SDKs and APIs to access BTFS data through external services, Zap inverts the stack: your browser is the service. Your BTFS node becomes your online passport. Every dApp you visit sees your BTFS identity and interacts with you directly over the peer network not through intermediaries. This creates an entirely new paradigm of ownership, interoperability, and privacy for users and developers alike.

Zap doesn’t just serve web pages it enables apps like:

  • P2P video calls with no backend
  • Mini-games running on native peer networks
  • Decentralized forums and social apps with self-owned data

The use cases branch endlessly this is not just a browser, it’s a platform for a new class of decentralized applications.

Project Demo:
Coming soon Beta access and project previews planned by Q3 2025.

Expected Completion Date for 2025:
Q4 2025 – Identity SDK and showcase apps integration.

Current Progress (%):
30% – Core Electron app setup completed, BTFS integration and tab architecture initialized.


Technical & Governance Details

Project Test Instructions:
TBA – Testnet installers, integration samples, and developer docs are under preparation.

Technical Details:

  • Stack: Electron (for native browser shell), HTML/CSS/JS (frontend), BTFS CLI integration via IPC (Inter-Process Communication).
  • Security: Isolated IPC environment for secure communication between browser UI and BTFS node.
  • BTFS Integration: Built-in node manager, identity sync via peer ID, automatic bootstrap to the BTFS network.
  • Vision: Seamless injection of BTFS into web context, enabling any site to access BTFS APIs directly via browser context.

Smart Contract Links:
N/A at this stage primarily decentralized file routing and identity at this point.

How is the Project Governed?
Initial centralized development with plans to release the browser under a permissive open-source license. Long-term roadmap includes a plugin ecosystem with governance via community contribution and BTFS identity reputation.


Funding & Business Model

Funding Request:

Category Amount (USD) Purpose
Browser Engine Development $90,000 Building the core browser and BTFS communication layer
Identity System & Wallet $30,000 Enabling peer identity and on-chain integration
UX/UI Design $20,000 Crafting intuitive, developer-friendly user interfaces
App Ecosystem Bootstrapping $10,000 Creating showcase apps and onboarding developers
Community & Hackathons $30,000 Developer outreach, P2P app challenges, and early adopter incentives
Long-Term Maintenance $60,000 Sustaining updates, documentation, and security patches
Miscellaneous $20,000 Keeping it together :eyes:

A total ask of $260,000/-

Revenue Model:
Zap is a public infrastructure project, but it opens commercial opportunities for decentralized app platforms, paid identity layers, and BTFS-based SaaS apps. Revenue will be sustained via:

  • Developer integrations & marketplace for extensions (further in future.)
  • Transaction/interaction fees in “btt”, the way BTFS adds its platform fees.

More importantly, Zap removes the need for centralized SDK backends in dApps replacing:

dApp → SDK → Backend → BTFS → Backend → SDK → dApp

with:

dApp → zap(BTFS) → dApp

This lowers costs and complexity for all TRON-native projects and makes BTFS-first applications truly viable.

Interested in TRON Having a Stake?:
Yes. Zap represents the first full BTFS-native user gateway. TRON DAO’s involvement would help solidify the TRON-BTFS stack as a holistic decentralized ecosystem from protocol to user-facing applications.

Preferred Collaboration Method:

  • Inclusion in TRON/BTFS hackathons as the default frontend stack
  • TRON developer ecosystem onboarding and workshops
  • Support with BTFS infrastructure, bootstrap nodes, and developer portal grants

Ecosystem Impact

Partnerships:
Directly integrated with other FrontLabs products, and products build utilizing zap’s injected identity and its injected functions.. These will serve as the first BTFS-native apps available via Zap. Seeking further collaborations within the TRON dApp ecosystem.

Time on TRON:
Members of FrontLabs have been active in the TRON/BTFS ecosystem since fall-2023.


Project Milestones

Timeline Milestone
Q2 2025 Core browser engine with tab and settings support + basic BTFS routing
Q3 2025 Public Beta: Zap Browser with BTFS injection into sites
Q4 2025 Identity manager + DApp showcase bundle: P2P chat, games, dForum
2026+ Plugin ecosystem, BTFS-native identity-linked wallet, App Store-like UX

Project in 5 Years

Zap will evolve into the default way users interact with decentralized applications, not just on BTFS, but across all peer-based Web3 systems. It will stand as:

  • A user-owned identity gateway
  • A fully P2P operating environment
  • A neutral platform for innovation unconstrained by cloud dependencies
2 Likes

Welcome to TBL, I checked but didn’t see exact figures, what’s the sum total of your funding request?

Welcome to the tbl, can you explain me more about this p 2 p video calling, thank you

Welcome team, all the best

1 Like

Welcome to TBL, wishing you all the best
It seems your funding request is not yet concluded

1 Like

what is p2p video call:
we are referencing to potential use cases to zap: as for a p2p video call. we jus need a initialization messaging between the peers: and for that the native calls to peer is enough: and after the commination via the core function, we can rely on WebRTC to further proceed with the video call.
And that’s how the google.meet and zoom works:
they use mediasoup: that internally rely on webRTC for the same.

Sorry but what is a WebRTC

WebRTC is : Real-time communication for the web
WebRTC-homepage

Ok thank you for the reply

1 Like

Where are updates???

Here it is:

progress on BTFS linking, the browser init its own btfs node behind the curtain to be used for its functionalities.

Logs:

1 Like

Revised the revenue model and the ask.

1 Like

Nice update, do you’ve a better version of the picture in the first frame? It looks like a worthy wallpaper for PC I’d like to use.

Here is a drive link to the images
Drive-link

Feel free to use them, they were clicked by me…

2 Likes

Wow, you did send a library.
Thanks, I really appreciate.

1 Like

One step at a time:

This marks the Effective injection to the browser. Well the release of ZAP-v1 is super close.
:crossed_fingers::crossed_fingers:

5 Likes

Good work in progress, don’t worry everything will make sense soon. Keep building

2 Likes

The design look super cool

2 Likes

Small small
Keep building

2 Likes

The website is really looking fire, good 1

1 Like

Thanks for the extremally warm response.

(hope i didn’t mis-interpreted your reply)

But sorry to bust the bubble, well the zap is not a website: its more of a browser that wraps the btfs-node, The image in context is one of the dashboard-ui to manage the node and its injections. One may ask why do we need this (explained above in first post.)

Mater of fact, this reply was written in the zap-browser it self: :smiley: