Create PyreBrowser.md

[DamianRavi]

Project Abstract

Pyre Browser is a Decentralized P2P browser that liberates the world from predatory markets.

It is a normal HTTPS browser (thats 44% faster than Firefox) but also has a secondary P2P internet. If I type in polkadot.com it will go to the main website. If I type in "polkadot" it will take you to a 404 page where you can purchase the domain. After the site is purchased you can upload a folder and save the checksum to the blockchain. Every time a user searches for your domain their client will look for a 7z folder with the same checksum as noted on the blockchain and download it from peers. If you want to change the website you just upload the new folder and save again (It costs 0.1 cent in Glimmer to do this). Each user is then prompted to download the new version from peers.

Grant level

• Level 1: Up to $10,000, 2 approvals
• Level 2: Up to $30,000, 3 approvals
• Level 3: Unlimited, 5 approvals (for >$100k: Web3 Foundation Council approval)

Application Checklist

• The application template has been copied and aptly renamed (project_name.md).
• I have read the application guidelines.
• Payment details have been provided (Polkadot AssetHub (USDC & DOT) address in the application and bank details via email, if applicable).
• I understand that an agreed upon percentage of each milestone will be paid in vested DOT, to the Polkadot address listed in the application.
• I am aware that, in order to receive a grant, I (and the entity I represent) have to successfully complete a KYC/KYB check.
• The software delivered for this grant will be released under an open-source license specified in the application.
• The initial PR contains only one commit (squash and force-push if needed).
• The grant will only be announced once the first milestone has been accepted (see the announcement guidelines).
• I prefer the discussion of this application to take place in a private Element/Matrix channel. My username is: @_______:matrix.org (change the homeserver if you use a different one)

[github-actions]

CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅

[DamianRavi]

I have read and hereby sign the Contributor License Agreement.

[semuelle]

Thanks for the application, @DamianRavi, but please review our guidelines and FAQ on what projects and information we look for in an application. In particular, please note that we do not fund projects that actively encourage gambling.

• FAQ: https://grants.web3.foundation/docs/faq#what-activitiespositions-do-you-fund
• Guidelines: https://grants.web3.foundation/docs/Introduction/intro

[github-actions]

Thank you for submitting a grant application.

We've assessed your submission and have found that it requires a higher level of technical detail in order to be considered for review. We encourage you to expand on it by providing a more precise specification/technical details. The section on project details in the application template is a good reference as to what type of information we expect applicants to provide, and these category-specific requirements contain more precise guidelines depending on what type of software you're building.

An area of the application that we often find to be insufficiently elaborated are the milestone deliverables. At a minimum, please indicate what languages/technologies you will be using to implement each deliverable, and provide a technical summary of its expected functionality. Note that deliverables should be tangible, reusable by other teams and in most cases not already present in the ecosystem. If they are, you will need to provide a comparison to existing implementations and explain why it makes sense to fund your approach. Also see our FAQ for a breakdown of what we fund and what we don't.

Let us know as soon as you're done with your changes, and we'll give your application another look!

[DamianRavi]

Thanks for the application, @DamianRavi, but please review our guidelines and FAQ on what projects and information we look for in an application. In particular, please note that we do not fund projects that actively encourage gambling.

* FAQ: https://grants.web3.foundation/docs/faq#what-activitiespositions-do-you-fund

* Guidelines: https://grants.web3.foundation/docs/Introduction/intro

There is no gambling - I will remove the charity casino from the roadmap

[DamianRavi]

Thank you for submitting a grant application. We've assessed your submission and have found that it requires a higher level of technical detail in order to be considered for review. We encourage you to expand on it by providing a more precise specification/technical details. The section on project details in the application template is a good reference as to what type of information we expect applicants to provide, and these category-specific requirements contain more precise guidelines depending on what type of software you're building. An area of the application that we often find to be insufficiently elaborated are the milestone deliverables. At a minimum, please indicate what languages/technologies you will be using to implement each deliverable, and provide a technical summary of its expected functionality. Note that deliverables should be tangible, reusable by other teams and in most cases not already present in the ecosystem. If they are, you will need to provide a comparison to existing implementations and explain why it makes sense to fund your approach. Also see our FAQ for a breakdown of what we fund and what we don't. Let us know as soon as you're done with your changes, and we'll give your application another look!

I have included all tech used (There is not much beyond Electron and NodeJS)

[semuelle]

Please also fix the development roadmap as per our template. There are default deliverables that are required. Also, all deliverables should be verifiable and reusable (see guidelines and FAQ mentioned above) and specifications as precise as possible to avoid any misunderstandings.

[DamianRavi]

Please also fix the development roadmap as per our template. There are default deliverables that are required. Also, all deliverables should be verifiable and reusable (see guidelines and FAQ mentioned above) and specifications as precise as possible to avoid any misunderstandings.

I've included this now and converted it to one milestone. I'm weary of realeasing source code before we have any users as it can be copied and rebranded within 1 hour. Either it is released when we have around 100 active websites or by June 2025 as a hard deadline. Hopefully this is ok!

[keeganquigley]

Hi @DamianRavi we do require any code written for the grant to be open-source, (and not rely on any closed-source components) but the code doesn't have to be public until the milestone delivery. Would you be willing to open-source all the code upon delivery of the first milestone? See more details in our terms and conditions.

[DamianRavi]

Hi @DamianRavi we do require any code written for the grant to be open-source, (and not rely on any closed-source components) but the code doesn't have to be public until the milestone delivery. Would you be willing to open-source all the code upon delivery of the first milestone? See more details in our terms and conditions.

Yes, of course! I want it to be opensource ASAP. I combined both milestones and set the deadline to 8 months. So by 06/2025 it needs to be open source but hopefully it gains traction before then and I can release the code earlier.

[DamianRavi]

Here is my current roadmap

[DamianRavi]

And here is what Gaia Source will look like soon - the map will be interactive and ping when a purchase is made. A cybernetic system that allows anyone in the world to see global production and purchases and plan their life correctly based on real world data. A true vision of the 1960s cyberneticists mixed with the dreams of free market thinkers of the 1800s! A true free market paradise with the Earth in mind