This repository was archived by the owner on Feb 25, 2026. It is now read-only.
This repository was archived by the owner on Feb 25, 2026. It is now read-only.

Open Grant : Third Storage #249

Closed
Closed
Open Grant : Third Storage#249
Assignees
realChainLife

Description

@hackyguru
hackyguru
opened on Oct 21, 2022

Open Grant Proposal: Third Storage

Name of Project: Third Storage

Proposal Category:devtools-libraries, integration-adoption

Proposer:hackyguru

Do you agree to open source all work you do on behalf of this RFP and dual-license under MIT, APACHE2, or GPL licenses?: Yes

Project Description

Most of the self-proclaimed web3 applications use centralized databases behind the hood and nullify the whole concept of decentralization by putting the privacy and security of user's data at risk. Confidential user data such as passwords, emails, KYCs and other critical information are often stored without encryption and are vulnerable to data breaches. Further, the developers can also access the private data of their users since the whole data is custodial to the developer without access control limitations.

The biggest problem with the currently used web3 data storage solutions is that they lack composability, performance and scalability. Additionally, developers have a steep learning curve to get started with web3 data storage mechanisms and will have to spend a lot of time in setting up their development environment and storage nodes. The only positives of web2 databases is that they are easily scalable and can be used by web2 developers without any prerequisite knowledge about web3 jargons. But, web2 databases can not be ideal in a decentralized and privacy-preserving web. Migrating between two web3 databases can consume immense amount of time and the lack of data composability can sometimes make it an impossible task to automate. Developers are required to setup their own nodes on different geographical locations to boost their data-availability, performance, Geo-redundancy and decentralization. Further,
all these nodes are 'stand alone' and developers will have to manually sync in all the nodes. The whole web requires a new generation standard to build and use data storage. The new standard should value the privacy and self-soverignity of data more than any other aspect. Developers will have to spend hundreds of hours just to create an infrastructure that can meet all their production requirements.

In most of the cases, web3 data storage options are not 'batteries ready'. This demotivates the developers to take up web3 options and finally the end up using low-code web2 alternatives that seem to do the job but compromise the data privacy that web3 offers.

Value

Developers usually face the following problems in web2 and web3 databases repectively,

Web2 DatabasesWeb3 Databases
Data sovereignty and ownership✅
Access control✅
Scalability✅
Speed and perfomance✅
Costs✅Cheaper than Web2 (Filecoin and IPFS)
Data composabilityStill in early stages

Third Storage solves all the above highlighted problems by providing mutant databases that leverage the pros from both web2 and web3 databases in the following ways :

Data soverignity :
All the user data is self soverign and hosted on Filecoin. The data can not be tampered by external sources. The user has the governing power over his data whereas web2 data governance is external.

Access control :
Decentralized access control is faciliated by using cryptography and lit protocol. Third Storage divides the user data into public and private based on the preference of user and developer.

Scalablity :
Third Storage can be scaled horizontally and vertically based on the preference of the developer. The infrastructure can be deployed into distributed and geo-redundant infra with minimal costs.

Speed and perfomance :
Third Storage does not compromise speed and perfomance in the name of 'decentralization'. We use caching mechanisms to make sure data retrival and writing is as fast as possible.

Costs :
A big misconception about web3 is 'Storage is very expensive'. But surprisingly, storage on Filecoin and other web3 native solutions are cheaper than centralized web2 solutions. Third Storage also facilitates 'perpetual file storage'.

Data composability

Data composability is one of the crucial elements that was missing in web2. For example, if you hosted a file in AWS - it is not possible for content addressing it on another storage provider.

Revolutionary technologies like IPFS can enable content addressing and data composability in web3. Third Storage leverages this capability to enable data composability between different storage paradigms. For example, if you wish to migrate from one storage paradigm to another in the future, you can do it without much hassle.

Decentralized hosting

You can seamlessly host your dapps on web3 native hosting options with Third Storage. Decentralized hosting only available in Third Storage Cloud. We provide multiple cloud deployment options which include :

  • IPFS Hosting : Hosting static web content on Filecoin and serving over IPFS.
  • Cloud Hosting : Third Storage also facilitates Cloud hosting for dynamic dapps. You can opt to host using our native cloud hosting solution or alternatively use third-party providers.

Multi-node scaling

With multi-node scaling you can boost data redundancy, data availability, vertical and horizontal scaling and level of decentralization. Multi-node scaling is only available for Third Storage Cloud users.

Deliverables

We will be launching Third Storage Localhost as the core deliverable of this open grant. More information about Third Storage Localhost can be found here

Development Roadmap

Roadmap

Q4 2022 :

October :

  • Hiring developers and expanding team
  • Ship Third Storage SDK
  • Ship Third Storage CLI
  • Ship Third Storage Client

November:

  • Ship examples on React and NextJS
    • Hiring developers and expanding team

December :

  • ETHIndia Launch
  • Work on branding

Q1 2023 :

  • Launch stable version of Localhost
  • Setup managed IPFS Nodes with Web3.storage
  • Start the work on Third Storage Cloud
  • Product monetization

The product roadmap and timelines can be found on Third Storage website

Total Budget Requested

MilestoneSummaryFunding requested (USD)
Milestone #1Launching beta of SDK, CLI and Client. Expanding the team and setting up workspace70,000
Milestone #2Research and define technical specifications on decentralized K8 containers, hosting and multi-node scaling. Expanding devops team80,000
Milestone #3FVM Integration and getting started with Third Storage Cloud30,000

Total budget requested : 180,000 USDC

Maintenance and Upgrade Plans

We are looking to continue this project and fundraise from VCs and angels by this quarter to support further growth. We are expecting to hire a team to take care of the development cycle.

Team

Team Members

Point of contact :

Kumaraguru T - Founder of Third Storage
LinkedIn | Email

Team Website

Website : https://thirdstorage.com
Docs : https://docs.thirdstorage.com
Github : https://github.com/hackyguru
Discord : https://discord.thirdstorage.com
Brand : https://thirdstorage.com/brand

Relevant Experience

Our team successfully completed all the milestones in the previous iteration of this project. More details can be found here

Team code repositories

Github Organization : https://github.com/thirdstorage
Developer documentation : https://docs.thirdstorage.com

Additional Information

We are expecting to complete our seed round by Q4 2022. We already completed a successful iteration of this project previously and are looking for more funds to scale up.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

    , 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Add copy buttons to all 
     blocks\n(function() {\n function addCopyButtons() {\n document.querySelectorAll('pre code').forEach(function(codeBlock) {\n if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;\n codeBlock.parentElement.setAttribute('data-copy-added', 'true');\n \n var btn = document.createElement('button');\n btn.textContent = 'Copy';\n btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';\n btn.onmouseover = function() { this.style.opacity = '1'; };\n btn.onmouseout = function() { this.style.opacity = '0.7'; };\n btn.onclick = function() {\n navigator.clipboard.writeText(codeBlock.textContent).then(function() {\n btn.textContent = 'Copied!';\n setTimeout(function() { btn.textContent = 'Copy'; }, 1500);\n });\n };\n codeBlock.parentElement.style.position = 'relative';\n codeBlock.parentElement.appendChild(btn);\n });\n }\n \n addCopyButtons();\n \n // Re-run on dynamic content\n var observer = new MutationObserver(addCopyButtons);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Add Copy Buttons to Code Blocks");
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '

    Skip to content
    
This repository was archived by the owner on Feb 25, 2026. It is now read-only.

    
This repository was archived by the owner on Feb 25, 2026. It is now read-only.

    Open Grant : Third Storage #249
    Closed
    Closed
    Open Grant : Third Storage#249
    Assignees
    realChainLife
    Description
    @hackyguru
    hackyguru
    opened on Oct 21, 2022
    Open Grant Proposal: Third Storage
    Name of Project: Third Storage
    Proposal Category:devtools-libraries, integration-adoption
    Proposer:hackyguru
    Do you agree to open source all work you do on behalf of this RFP and dual-license under MIT, APACHE2, or GPL licenses?: Yes
    Project Description
    Most of the self-proclaimed web3 applications use centralized databases behind the hood and nullify the whole concept of decentralization by putting the privacy and security of user's data at risk. Confidential user data such as passwords, emails, KYCs and other critical information are often stored without encryption and are vulnerable to data breaches. Further, the developers can also access the private data of their users since the whole data is custodial to the developer without access control limitations.
    The biggest problem with the currently used web3 data storage solutions is that they lack composability, performance and scalability. Additionally, developers have a steep learning curve to get started with web3 data storage mechanisms and will have to spend a lot of time in setting up their development environment and storage nodes. The only positives of web2 databases is that they are easily scalable and can be used by web2 developers without any prerequisite knowledge about web3 jargons. But, web2 databases can not be ideal in a decentralized and privacy-preserving web. Migrating between two web3 databases can consume immense amount of time and the lack of data composability can sometimes make it an impossible task to automate. Developers are required to setup their own nodes on different geographical locations to boost their data-availability, performance, Geo-redundancy and decentralization. Further,
    
all these nodes are 'stand alone' and developers will have to manually sync in all the nodes. The whole web requires a new generation standard to build and use data storage. The new standard should value the privacy and self-soverignity of data more than any other aspect. Developers will have to spend hundreds of hours just to create an infrastructure that can meet all their production requirements.
    In most of the cases, web3 data storage options are not 'batteries ready'. This demotivates the developers to take up web3 options and finally the end up using low-code web2 alternatives that seem to do the job but compromise the data privacy that web3 offers.
    Value
    Developers usually face the following problems in web2 and web3 databases repectively,
    Web2 DatabasesWeb3 Databases
    Data sovereignty and ownership✅
    Access control✅
    Scalability✅
    Speed and perfomance✅
    Costs✅Cheaper than Web2 (Filecoin and IPFS)
    Data composabilityStill in early stages
    Third Storage solves all the above highlighted problems by providing mutant databases that leverage the pros from both web2 and web3 databases in the following ways :
    Data soverignity :
    
All the user data is self soverign and hosted on Filecoin. The data can not be tampered by external sources. The user has the governing power over his data whereas web2 data governance is external.
    Access control :
    
Decentralized access control is faciliated by using cryptography and lit protocol. Third Storage divides the user data into public and private based on the preference of user and developer.
    Scalablity :
    
Third Storage can be scaled horizontally and vertically based on the preference of the developer. The infrastructure can be deployed into distributed and geo-redundant infra with minimal costs.
    Speed and perfomance :
    
Third Storage does not compromise speed and perfomance in the name of 'decentralization'. We use caching mechanisms to make sure data retrival and writing is as fast as possible.
    Costs :
    
A big misconception about web3 is 'Storage is very expensive'. But surprisingly, storage on Filecoin and other web3 native solutions are cheaper than centralized web2 solutions. Third Storage also facilitates 'perpetual file storage'.
    Data composability
    Data composability is one of the crucial elements that was missing in web2. For example, if you hosted a file in AWS - it is not possible for content addressing it on another storage provider.
    Revolutionary technologies like IPFS can enable content addressing and data composability in web3. Third Storage leverages this capability to enable data composability between different storage paradigms. For example, if you wish to migrate from one storage paradigm to another in the future, you can do it without much hassle.
    Decentralized hosting
    You can seamlessly host your dapps on web3 native hosting options with Third Storage. Decentralized hosting only available in Third Storage Cloud. We provide multiple cloud deployment options which include :
    • IPFS Hosting : Hosting static web content on Filecoin and serving over IPFS.
    • Cloud Hosting : Third Storage also facilitates Cloud hosting for dynamic dapps. You can opt to host using our native cloud hosting solution or alternatively use third-party providers.
    Multi-node scaling
    With multi-node scaling you can boost data redundancy, data availability, vertical and horizontal scaling and level of decentralization. Multi-node scaling is only available for Third Storage Cloud users.
    Deliverables
    We will be launching Third Storage Localhost as the core deliverable of this open grant. More information about Third Storage Localhost can be found here
    Development Roadmap
    Roadmap
    Q4 2022 :
    October :
    • Hiring developers and expanding team
    • Ship Third Storage SDK
    • Ship Third Storage CLI
    • Ship Third Storage Client
    November:
    • Ship examples on React and NextJS
      • Hiring developers and expanding team
    December :
    • ETHIndia Launch
    • Work on branding
    Q1 2023 :
    • Launch stable version of Localhost
    • Setup managed IPFS Nodes with Web3.storage
    • Start the work on Third Storage Cloud
    • Product monetization
    The product roadmap and timelines can be found on Third Storage website
    Total Budget Requested
    MilestoneSummaryFunding requested (USD)
    Milestone #1Launching beta of SDK, CLI and Client. Expanding the team and setting up workspace70,000
    Milestone #2Research and define technical specifications on decentralized K8 containers, hosting and multi-node scaling. Expanding devops team80,000
    Milestone #3FVM Integration and getting started with Third Storage Cloud30,000
    Total budget requested : 180,000 USDC
    Maintenance and Upgrade Plans
    We are looking to continue this project and fundraise from VCs and angels by this quarter to support further growth. We are expecting to hire a team to take care of the development cycle.
    Team
    Team Members
    Point of contact :
    Kumaraguru T - Founder of Third Storage
    LinkedIn | Email
    Team Website
    Website : https://thirdstorage.com
    
Docs : https://docs.thirdstorage.com
    
Github : https://github.com/hackyguru
    
Discord : https://discord.thirdstorage.com
    
Brand : https://thirdstorage.com/brand
    Relevant Experience
    Our team successfully completed all the milestones in the previous iteration of this project. More details can be found here
    Team code repositories
    Github Organization : https://github.com/thirdstorage
    
Developer documentation : https://docs.thirdstorage.com
    Additional Information
    We are expecting to complete our seed round by Q4 2022. We already completed a successful iteration of this project previously and are looking for more funds to scale up.
    Activity
    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
    Metadata
    Metadata
    Assignees
    Labels
    No labels
    No labels
    Type
    No type
    Projects
    No projects
      Milestone
      No milestone
      Relationships
      None yet
      Development
      No branches or pull requests
      Issue actions
      
, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Force GitHub README to respect dark mode\n(function() {\n var style = document.createElement('style');\n style.textContent = '\n .markdown-body {\n color-scheme: dark light;\n }\n .markdown-body pre { background: #161b22 !important; }\n .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }\n .markdown-body table th, .markdown-body table td { border-color: #30363d !important; }\n .markdown-body img { background: #0d1117; }\n .markdown-body blockquote { border-left-color: #8b949e; }\n .markdown-body hr { border-color: #30363d; }\n ';\n document.head.appendChild(style);\n})();", "GitHub Dark Mode README Fix");
}
} catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

      Skip to content
      
This repository was archived by the owner on Feb 25, 2026. It is now read-only.

      
This repository was archived by the owner on Feb 25, 2026. It is now read-only.

      Open Grant : Third Storage #249
      Closed
      Closed
      Open Grant : Third Storage#249
      Assignees
      realChainLife
      Description
      @hackyguru
      hackyguru
      opened on Oct 21, 2022
      Open Grant Proposal: Third Storage
      Name of Project: Third Storage
      Proposal Category:devtools-libraries, integration-adoption
      Proposer:hackyguru
      Do you agree to open source all work you do on behalf of this RFP and dual-license under MIT, APACHE2, or GPL licenses?: Yes
      Project Description
      Most of the self-proclaimed web3 applications use centralized databases behind the hood and nullify the whole concept of decentralization by putting the privacy and security of user's data at risk. Confidential user data such as passwords, emails, KYCs and other critical information are often stored without encryption and are vulnerable to data breaches. Further, the developers can also access the private data of their users since the whole data is custodial to the developer without access control limitations.
      The biggest problem with the currently used web3 data storage solutions is that they lack composability, performance and scalability. Additionally, developers have a steep learning curve to get started with web3 data storage mechanisms and will have to spend a lot of time in setting up their development environment and storage nodes. The only positives of web2 databases is that they are easily scalable and can be used by web2 developers without any prerequisite knowledge about web3 jargons. But, web2 databases can not be ideal in a decentralized and privacy-preserving web. Migrating between two web3 databases can consume immense amount of time and the lack of data composability can sometimes make it an impossible task to automate. Developers are required to setup their own nodes on different geographical locations to boost their data-availability, performance, Geo-redundancy and decentralization. Further,
      
all these nodes are 'stand alone' and developers will have to manually sync in all the nodes. The whole web requires a new generation standard to build and use data storage. The new standard should value the privacy and self-soverignity of data more than any other aspect. Developers will have to spend hundreds of hours just to create an infrastructure that can meet all their production requirements.
      In most of the cases, web3 data storage options are not 'batteries ready'. This demotivates the developers to take up web3 options and finally the end up using low-code web2 alternatives that seem to do the job but compromise the data privacy that web3 offers.
      Value
      Developers usually face the following problems in web2 and web3 databases repectively,
      Web2 DatabasesWeb3 Databases
      Data sovereignty and ownership✅
      Access control✅
      Scalability✅
      Speed and perfomance✅
      Costs✅Cheaper than Web2 (Filecoin and IPFS)
      Data composabilityStill in early stages
      Third Storage solves all the above highlighted problems by providing mutant databases that leverage the pros from both web2 and web3 databases in the following ways :
      Data soverignity :
      
All the user data is self soverign and hosted on Filecoin. The data can not be tampered by external sources. The user has the governing power over his data whereas web2 data governance is external.
      Access control :
      
Decentralized access control is faciliated by using cryptography and lit protocol. Third Storage divides the user data into public and private based on the preference of user and developer.
      Scalablity :
      
Third Storage can be scaled horizontally and vertically based on the preference of the developer. The infrastructure can be deployed into distributed and geo-redundant infra with minimal costs.
      Speed and perfomance :
      
Third Storage does not compromise speed and perfomance in the name of 'decentralization'. We use caching mechanisms to make sure data retrival and writing is as fast as possible.
      Costs :
      
A big misconception about web3 is 'Storage is very expensive'. But surprisingly, storage on Filecoin and other web3 native solutions are cheaper than centralized web2 solutions. Third Storage also facilitates 'perpetual file storage'.
      Data composability
      Data composability is one of the crucial elements that was missing in web2. For example, if you hosted a file in AWS - it is not possible for content addressing it on another storage provider.
      Revolutionary technologies like IPFS can enable content addressing and data composability in web3. Third Storage leverages this capability to enable data composability between different storage paradigms. For example, if you wish to migrate from one storage paradigm to another in the future, you can do it without much hassle.
      Decentralized hosting
      You can seamlessly host your dapps on web3 native hosting options with Third Storage. Decentralized hosting only available in Third Storage Cloud. We provide multiple cloud deployment options which include :
      • IPFS Hosting : Hosting static web content on Filecoin and serving over IPFS.
      • Cloud Hosting : Third Storage also facilitates Cloud hosting for dynamic dapps. You can opt to host using our native cloud hosting solution or alternatively use third-party providers.
      Multi-node scaling
      With multi-node scaling you can boost data redundancy, data availability, vertical and horizontal scaling and level of decentralization. Multi-node scaling is only available for Third Storage Cloud users.
      Deliverables
      We will be launching Third Storage Localhost as the core deliverable of this open grant. More information about Third Storage Localhost can be found here
      Development Roadmap
      Roadmap
      Q4 2022 :
      October :
      • Hiring developers and expanding team
      • Ship Third Storage SDK
      • Ship Third Storage CLI
      • Ship Third Storage Client
      November:
      • Ship examples on React and NextJS
        • Hiring developers and expanding team
      December :
      • ETHIndia Launch
      • Work on branding
      Q1 2023 :
      • Launch stable version of Localhost
      • Setup managed IPFS Nodes with Web3.storage
      • Start the work on Third Storage Cloud
      • Product monetization
      The product roadmap and timelines can be found on Third Storage website
      Total Budget Requested
      MilestoneSummaryFunding requested (USD)
      Milestone #1Launching beta of SDK, CLI and Client. Expanding the team and setting up workspace70,000
      Milestone #2Research and define technical specifications on decentralized K8 containers, hosting and multi-node scaling. Expanding devops team80,000
      Milestone #3FVM Integration and getting started with Third Storage Cloud30,000
      Total budget requested : 180,000 USDC
      Maintenance and Upgrade Plans
      We are looking to continue this project and fundraise from VCs and angels by this quarter to support further growth. We are expecting to hire a team to take care of the development cycle.
      Team
      Team Members
      Point of contact :
      Kumaraguru T - Founder of Third Storage
      LinkedIn | Email
      Team Website
      Website : https://thirdstorage.com
      
Docs : https://docs.thirdstorage.com
      
Github : https://github.com/hackyguru
      
Discord : https://discord.thirdstorage.com
      
Brand : https://thirdstorage.com/brand
      Relevant Experience
      Our team successfully completed all the milestones in the previous iteration of this project. More details can be found here
      Team code repositories
      Github Organization : https://github.com/thirdstorage
      
Developer documentation : https://docs.thirdstorage.com
      Additional Information
      We are expecting to complete our seed round by Q4 2022. We already completed a successful iteration of this project previously and are looking for more funds to scale up.
      Activity
      Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
      Metadata
      Metadata
      Assignees
      Labels
      No labels
      No labels
      Type
      No type
      Projects
      No projects
        Milestone
        No milestone
        Relationships
        None yet
        Development
        No branches or pull requests
        Issue actions
        
, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Highlight search terms from Google/DuckDuckGo/Bing referrer\n(function() {\n var ref = document.referrer;\n var terms = [];\n \n if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {\n var url = new URL(ref);\n var q = url.searchParams.get('q') || url.searchParams.get('p');\n if (q) {\n terms = q.split(/\\s+/).filter(function(t) { return t.length > 2; });\n }\n }\n \n if (terms.length === 0) return;\n \n var style = document.createElement('style');\n style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';\n document.head.appendChild(style);\n \n function highlight(node) {\n if (node.nodeType === 3) { // text node\n var text = node.textContent;\n var found = false;\n terms.forEach(function(term) {\n var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\\]\\\\]/g, '\\\\') + ')', 'gi');\n if (regex.test(text)) {\n found = true;\n var frag = document.createDocumentFragment();\n var parts = text.split(regex);\n parts.forEach(function(part, i) {\n if (i % 2 === 0) {\n frag.appendChild(document.createTextNode(part));\n } else {\n var span = document.createElement('span');\n span.className = 'userscript-highlight';\n span.textContent = part;\n frag.appendChild(span);\n }\n });\n node.parentNode.replaceChild(frag, node);\n }\n });\n } else if (node.nodeType === 1 && node.childNodes) { // element\n var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];\n if (!skipTags.includes(node.tagName)) {\n Array.from(node.childNodes).forEach(highlight);\n }\n }\n }\n \n highlight(document.body);\n \n // Re-highlight on dynamic content\n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1 || node.nodeType === 3) highlight(node);\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Highlight Search Terms");
}
} catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

        Skip to content
        
This repository was archived by the owner on Feb 25, 2026. It is now read-only.

        
This repository was archived by the owner on Feb 25, 2026. It is now read-only.

        Open Grant : Third Storage #249
        Closed
        Closed
        Open Grant : Third Storage#249
        Assignees
        realChainLife
        Description
        @hackyguru
        hackyguru
        opened on Oct 21, 2022
        Open Grant Proposal: Third Storage
        Name of Project: Third Storage
        Proposal Category:devtools-libraries, integration-adoption
        Proposer:hackyguru
        Do you agree to open source all work you do on behalf of this RFP and dual-license under MIT, APACHE2, or GPL licenses?: Yes
        Project Description
        Most of the self-proclaimed web3 applications use centralized databases behind the hood and nullify the whole concept of decentralization by putting the privacy and security of user's data at risk. Confidential user data such as passwords, emails, KYCs and other critical information are often stored without encryption and are vulnerable to data breaches. Further, the developers can also access the private data of their users since the whole data is custodial to the developer without access control limitations.
        The biggest problem with the currently used web3 data storage solutions is that they lack composability, performance and scalability. Additionally, developers have a steep learning curve to get started with web3 data storage mechanisms and will have to spend a lot of time in setting up their development environment and storage nodes. The only positives of web2 databases is that they are easily scalable and can be used by web2 developers without any prerequisite knowledge about web3 jargons. But, web2 databases can not be ideal in a decentralized and privacy-preserving web. Migrating between two web3 databases can consume immense amount of time and the lack of data composability can sometimes make it an impossible task to automate. Developers are required to setup their own nodes on different geographical locations to boost their data-availability, performance, Geo-redundancy and decentralization. Further,
        
all these nodes are 'stand alone' and developers will have to manually sync in all the nodes. The whole web requires a new generation standard to build and use data storage. The new standard should value the privacy and self-soverignity of data more than any other aspect. Developers will have to spend hundreds of hours just to create an infrastructure that can meet all their production requirements.
        In most of the cases, web3 data storage options are not 'batteries ready'. This demotivates the developers to take up web3 options and finally the end up using low-code web2 alternatives that seem to do the job but compromise the data privacy that web3 offers.
        Value
        Developers usually face the following problems in web2 and web3 databases repectively,
        Web2 DatabasesWeb3 Databases
        Data sovereignty and ownership✅
        Access control✅
        Scalability✅
        Speed and perfomance✅
        Costs✅Cheaper than Web2 (Filecoin and IPFS)
        Data composabilityStill in early stages
        Third Storage solves all the above highlighted problems by providing mutant databases that leverage the pros from both web2 and web3 databases in the following ways :
        Data soverignity :
        
All the user data is self soverign and hosted on Filecoin. The data can not be tampered by external sources. The user has the governing power over his data whereas web2 data governance is external.
        Access control :
        
Decentralized access control is faciliated by using cryptography and lit protocol. Third Storage divides the user data into public and private based on the preference of user and developer.
        Scalablity :
        
Third Storage can be scaled horizontally and vertically based on the preference of the developer. The infrastructure can be deployed into distributed and geo-redundant infra with minimal costs.
        Speed and perfomance :
        
Third Storage does not compromise speed and perfomance in the name of 'decentralization'. We use caching mechanisms to make sure data retrival and writing is as fast as possible.
        Costs :
        
A big misconception about web3 is 'Storage is very expensive'. But surprisingly, storage on Filecoin and other web3 native solutions are cheaper than centralized web2 solutions. Third Storage also facilitates 'perpetual file storage'.
        Data composability
        Data composability is one of the crucial elements that was missing in web2. For example, if you hosted a file in AWS - it is not possible for content addressing it on another storage provider.
        Revolutionary technologies like IPFS can enable content addressing and data composability in web3. Third Storage leverages this capability to enable data composability between different storage paradigms. For example, if you wish to migrate from one storage paradigm to another in the future, you can do it without much hassle.
        Decentralized hosting
        You can seamlessly host your dapps on web3 native hosting options with Third Storage. Decentralized hosting only available in Third Storage Cloud. We provide multiple cloud deployment options which include :
        • IPFS Hosting : Hosting static web content on Filecoin and serving over IPFS.
        • Cloud Hosting : Third Storage also facilitates Cloud hosting for dynamic dapps. You can opt to host using our native cloud hosting solution or alternatively use third-party providers.
        Multi-node scaling
        With multi-node scaling you can boost data redundancy, data availability, vertical and horizontal scaling and level of decentralization. Multi-node scaling is only available for Third Storage Cloud users.
        Deliverables
        We will be launching Third Storage Localhost as the core deliverable of this open grant. More information about Third Storage Localhost can be found here
        Development Roadmap
        Roadmap
        Q4 2022 :
        October :
        • Hiring developers and expanding team
        • Ship Third Storage SDK
        • Ship Third Storage CLI
        • Ship Third Storage Client
        November:
        • Ship examples on React and NextJS
          • Hiring developers and expanding team
        December :
        • ETHIndia Launch
        • Work on branding
        Q1 2023 :
        • Launch stable version of Localhost
        • Setup managed IPFS Nodes with Web3.storage
        • Start the work on Third Storage Cloud
        • Product monetization
        The product roadmap and timelines can be found on Third Storage website
        Total Budget Requested
        MilestoneSummaryFunding requested (USD)
        Milestone #1Launching beta of SDK, CLI and Client. Expanding the team and setting up workspace70,000
        Milestone #2Research and define technical specifications on decentralized K8 containers, hosting and multi-node scaling. Expanding devops team80,000
        Milestone #3FVM Integration and getting started with Third Storage Cloud30,000
        Total budget requested : 180,000 USDC
        Maintenance and Upgrade Plans
        We are looking to continue this project and fundraise from VCs and angels by this quarter to support further growth. We are expecting to hire a team to take care of the development cycle.
        Team
        Team Members
        Point of contact :
        Kumaraguru T - Founder of Third Storage
        LinkedIn | Email
        Team Website
        Website : https://thirdstorage.com
        
Docs : https://docs.thirdstorage.com
        
Github : https://github.com/hackyguru
        
Discord : https://discord.thirdstorage.com
        
Brand : https://thirdstorage.com/brand
        Relevant Experience
        Our team successfully completed all the milestones in the previous iteration of this project. More details can be found here
        Team code repositories
        Github Organization : https://github.com/thirdstorage
        
Developer documentation : https://docs.thirdstorage.com
        Additional Information
        We are expecting to complete our seed round by Q4 2022. We already completed a successful iteration of this project previously and are looking for more funds to scale up.
        Activity
        Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
        Metadata
        Metadata
        Assignees
        Labels
        No labels
        No labels
        Type
        No type
        Projects
        No projects
          Milestone
          No milestone
          Relationships
          None yet
          Development
          No branches or pull requests
          Issue actions
          
, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Strip utm_, fbclid, gclid, etc. from all links on page\n(function() {\n var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',\n 'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',\n 'ref', 'ref_src', 'source', 'medium', 'campaign'];\n \n function cleanUrl(url) {\n try {\n var u = new URL(url, window.location.origin);\n var changed = false;\n trackingParams.forEach(function(p) {\n if (u.searchParams.has(p)) {\n u.searchParams.delete(p);\n changed = true;\n }\n });\n return changed ? u.toString() : url;\n } catch (e) {\n return url;\n }\n }\n \n function cleanLinks() {\n document.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n \n cleanLinks();\n \n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1) {\n if (node.tagName === 'A') cleanLinks();\n node.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Remove Tracking Parameters from Links");
}
} catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); }
})();
(function(){
try {
var __m = "youtube.com";
var __re = new RegExp('^' + "youtube\\.com" + '

          Skip to content
          
This repository was archived by the owner on Feb 25, 2026. It is now read-only.

          
This repository was archived by the owner on Feb 25, 2026. It is now read-only.

          Open Grant : Third Storage #249
          Closed
          Closed
          Open Grant : Third Storage#249
          Assignees
          realChainLife
          Description
          @hackyguru
          hackyguru
          opened on Oct 21, 2022
          Open Grant Proposal: Third Storage
          Name of Project: Third Storage
          Proposal Category:devtools-libraries, integration-adoption
          Proposer:hackyguru
          Do you agree to open source all work you do on behalf of this RFP and dual-license under MIT, APACHE2, or GPL licenses?: Yes
          Project Description
          Most of the self-proclaimed web3 applications use centralized databases behind the hood and nullify the whole concept of decentralization by putting the privacy and security of user's data at risk. Confidential user data such as passwords, emails, KYCs and other critical information are often stored without encryption and are vulnerable to data breaches. Further, the developers can also access the private data of their users since the whole data is custodial to the developer without access control limitations.
          The biggest problem with the currently used web3 data storage solutions is that they lack composability, performance and scalability. Additionally, developers have a steep learning curve to get started with web3 data storage mechanisms and will have to spend a lot of time in setting up their development environment and storage nodes. The only positives of web2 databases is that they are easily scalable and can be used by web2 developers without any prerequisite knowledge about web3 jargons. But, web2 databases can not be ideal in a decentralized and privacy-preserving web. Migrating between two web3 databases can consume immense amount of time and the lack of data composability can sometimes make it an impossible task to automate. Developers are required to setup their own nodes on different geographical locations to boost their data-availability, performance, Geo-redundancy and decentralization. Further,
          
all these nodes are 'stand alone' and developers will have to manually sync in all the nodes. The whole web requires a new generation standard to build and use data storage. The new standard should value the privacy and self-soverignity of data more than any other aspect. Developers will have to spend hundreds of hours just to create an infrastructure that can meet all their production requirements.
          In most of the cases, web3 data storage options are not 'batteries ready'. This demotivates the developers to take up web3 options and finally the end up using low-code web2 alternatives that seem to do the job but compromise the data privacy that web3 offers.
          Value
          Developers usually face the following problems in web2 and web3 databases repectively,
          Web2 DatabasesWeb3 Databases
          Data sovereignty and ownership✅
          Access control✅
          Scalability✅
          Speed and perfomance✅
          Costs✅Cheaper than Web2 (Filecoin and IPFS)
          Data composabilityStill in early stages
          Third Storage solves all the above highlighted problems by providing mutant databases that leverage the pros from both web2 and web3 databases in the following ways :
          Data soverignity :
          
All the user data is self soverign and hosted on Filecoin. The data can not be tampered by external sources. The user has the governing power over his data whereas web2 data governance is external.
          Access control :
          
Decentralized access control is faciliated by using cryptography and lit protocol. Third Storage divides the user data into public and private based on the preference of user and developer.
          Scalablity :
          
Third Storage can be scaled horizontally and vertically based on the preference of the developer. The infrastructure can be deployed into distributed and geo-redundant infra with minimal costs.
          Speed and perfomance :
          
Third Storage does not compromise speed and perfomance in the name of 'decentralization'. We use caching mechanisms to make sure data retrival and writing is as fast as possible.
          Costs :
          
A big misconception about web3 is 'Storage is very expensive'. But surprisingly, storage on Filecoin and other web3 native solutions are cheaper than centralized web2 solutions. Third Storage also facilitates 'perpetual file storage'.
          Data composability
          Data composability is one of the crucial elements that was missing in web2. For example, if you hosted a file in AWS - it is not possible for content addressing it on another storage provider.
          Revolutionary technologies like IPFS can enable content addressing and data composability in web3. Third Storage leverages this capability to enable data composability between different storage paradigms. For example, if you wish to migrate from one storage paradigm to another in the future, you can do it without much hassle.
          Decentralized hosting
          You can seamlessly host your dapps on web3 native hosting options with Third Storage. Decentralized hosting only available in Third Storage Cloud. We provide multiple cloud deployment options which include :
          • IPFS Hosting : Hosting static web content on Filecoin and serving over IPFS.
          • Cloud Hosting : Third Storage also facilitates Cloud hosting for dynamic dapps. You can opt to host using our native cloud hosting solution or alternatively use third-party providers.
          Multi-node scaling
          With multi-node scaling you can boost data redundancy, data availability, vertical and horizontal scaling and level of decentralization. Multi-node scaling is only available for Third Storage Cloud users.
          Deliverables
          We will be launching Third Storage Localhost as the core deliverable of this open grant. More information about Third Storage Localhost can be found here
          Development Roadmap
          Roadmap
          Q4 2022 :
          October :
          • Hiring developers and expanding team
          • Ship Third Storage SDK
          • Ship Third Storage CLI
          • Ship Third Storage Client
          November:
          • Ship examples on React and NextJS
            • Hiring developers and expanding team
          December :
          • ETHIndia Launch
          • Work on branding
          Q1 2023 :
          • Launch stable version of Localhost
          • Setup managed IPFS Nodes with Web3.storage
          • Start the work on Third Storage Cloud
          • Product monetization
          The product roadmap and timelines can be found on Third Storage website
          Total Budget Requested
          MilestoneSummaryFunding requested (USD)
          Milestone #1Launching beta of SDK, CLI and Client. Expanding the team and setting up workspace70,000
          Milestone #2Research and define technical specifications on decentralized K8 containers, hosting and multi-node scaling. Expanding devops team80,000
          Milestone #3FVM Integration and getting started with Third Storage Cloud30,000
          Total budget requested : 180,000 USDC
          Maintenance and Upgrade Plans
          We are looking to continue this project and fundraise from VCs and angels by this quarter to support further growth. We are expecting to hire a team to take care of the development cycle.
          Team
          Team Members
          Point of contact :
          Kumaraguru T - Founder of Third Storage
          LinkedIn | Email
          Team Website
          Website : https://thirdstorage.com
          
Docs : https://docs.thirdstorage.com
          
Github : https://github.com/hackyguru
          
Discord : https://discord.thirdstorage.com
          
Brand : https://thirdstorage.com/brand
          Relevant Experience
          Our team successfully completed all the milestones in the previous iteration of this project. More details can be found here
          Team code repositories
          Github Organization : https://github.com/thirdstorage
          
Developer documentation : https://docs.thirdstorage.com
          Additional Information
          We are expecting to complete our seed round by Q4 2022. We already completed a successful iteration of this project previously and are looking for more funds to scale up.
          Activity
          Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
          Metadata
          Metadata
          Assignees
          Labels
          No labels
          No labels
          Type
          No type
          Projects
          No projects
            Milestone
            No milestone
            Relationships
            None yet
            Development
            No branches or pull requests
            Issue actions
            
, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Auto-enable theater mode on YouTube\n(function() {\n function tryTheater() {\n var btn = document.querySelector('button[aria-label=\"Theater mode\"], ytd-player #player button[title=\"Theater mode\"]');\n if (btn && !btn.classList.contains('activated')) {\n btn.click();\n }\n }\n \n // Try immediately\n tryTheater();\n \n // Try after navigation (SPA)\n var lastUrl = location.href;\n setInterval(function() {\n if (location.href !== lastUrl) {\n lastUrl = location.href;\n setTimeout(tryTheater, 500);\n }\n }, 1000);\n \n // Also try on player load\n var observer = new MutationObserver(tryTheater);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "YouTube Theater Mode Default");
}
} catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

            Skip to content
            
This repository was archived by the owner on Feb 25, 2026. It is now read-only.

            
This repository was archived by the owner on Feb 25, 2026. It is now read-only.

            Open Grant : Third Storage #249
            Closed
            Closed
            Open Grant : Third Storage#249
            Assignees
            realChainLife
            Description
            @hackyguru
            hackyguru
            opened on Oct 21, 2022
            Open Grant Proposal: Third Storage
            Name of Project: Third Storage
            Proposal Category:devtools-libraries, integration-adoption
            Proposer:hackyguru
            Do you agree to open source all work you do on behalf of this RFP and dual-license under MIT, APACHE2, or GPL licenses?: Yes
            Project Description
            Most of the self-proclaimed web3 applications use centralized databases behind the hood and nullify the whole concept of decentralization by putting the privacy and security of user's data at risk. Confidential user data such as passwords, emails, KYCs and other critical information are often stored without encryption and are vulnerable to data breaches. Further, the developers can also access the private data of their users since the whole data is custodial to the developer without access control limitations.
            The biggest problem with the currently used web3 data storage solutions is that they lack composability, performance and scalability. Additionally, developers have a steep learning curve to get started with web3 data storage mechanisms and will have to spend a lot of time in setting up their development environment and storage nodes. The only positives of web2 databases is that they are easily scalable and can be used by web2 developers without any prerequisite knowledge about web3 jargons. But, web2 databases can not be ideal in a decentralized and privacy-preserving web. Migrating between two web3 databases can consume immense amount of time and the lack of data composability can sometimes make it an impossible task to automate. Developers are required to setup their own nodes on different geographical locations to boost their data-availability, performance, Geo-redundancy and decentralization. Further,
            
all these nodes are 'stand alone' and developers will have to manually sync in all the nodes. The whole web requires a new generation standard to build and use data storage. The new standard should value the privacy and self-soverignity of data more than any other aspect. Developers will have to spend hundreds of hours just to create an infrastructure that can meet all their production requirements.
            In most of the cases, web3 data storage options are not 'batteries ready'. This demotivates the developers to take up web3 options and finally the end up using low-code web2 alternatives that seem to do the job but compromise the data privacy that web3 offers.
            Value
            Developers usually face the following problems in web2 and web3 databases repectively,
            Web2 DatabasesWeb3 Databases
            Data sovereignty and ownership✅
            Access control✅
            Scalability✅
            Speed and perfomance✅
            Costs✅Cheaper than Web2 (Filecoin and IPFS)
            Data composabilityStill in early stages
            Third Storage solves all the above highlighted problems by providing mutant databases that leverage the pros from both web2 and web3 databases in the following ways :
            Data soverignity :
            
All the user data is self soverign and hosted on Filecoin. The data can not be tampered by external sources. The user has the governing power over his data whereas web2 data governance is external.
            Access control :
            
Decentralized access control is faciliated by using cryptography and lit protocol. Third Storage divides the user data into public and private based on the preference of user and developer.
            Scalablity :
            
Third Storage can be scaled horizontally and vertically based on the preference of the developer. The infrastructure can be deployed into distributed and geo-redundant infra with minimal costs.
            Speed and perfomance :
            
Third Storage does not compromise speed and perfomance in the name of 'decentralization'. We use caching mechanisms to make sure data retrival and writing is as fast as possible.
            Costs :
            
A big misconception about web3 is 'Storage is very expensive'. But surprisingly, storage on Filecoin and other web3 native solutions are cheaper than centralized web2 solutions. Third Storage also facilitates 'perpetual file storage'.
            Data composability
            Data composability is one of the crucial elements that was missing in web2. For example, if you hosted a file in AWS - it is not possible for content addressing it on another storage provider.
            Revolutionary technologies like IPFS can enable content addressing and data composability in web3. Third Storage leverages this capability to enable data composability between different storage paradigms. For example, if you wish to migrate from one storage paradigm to another in the future, you can do it without much hassle.
            Decentralized hosting
            You can seamlessly host your dapps on web3 native hosting options with Third Storage. Decentralized hosting only available in Third Storage Cloud. We provide multiple cloud deployment options which include :
            • IPFS Hosting : Hosting static web content on Filecoin and serving over IPFS.
            • Cloud Hosting : Third Storage also facilitates Cloud hosting for dynamic dapps. You can opt to host using our native cloud hosting solution or alternatively use third-party providers.
            Multi-node scaling
            With multi-node scaling you can boost data redundancy, data availability, vertical and horizontal scaling and level of decentralization. Multi-node scaling is only available for Third Storage Cloud users.
            Deliverables
            We will be launching Third Storage Localhost as the core deliverable of this open grant. More information about Third Storage Localhost can be found here
            Development Roadmap
            Roadmap
            Q4 2022 :
            October :
            • Hiring developers and expanding team
            • Ship Third Storage SDK
            • Ship Third Storage CLI
            • Ship Third Storage Client
            November:
            • Ship examples on React and NextJS
              • Hiring developers and expanding team
            December :
            • ETHIndia Launch
            • Work on branding
            Q1 2023 :
            • Launch stable version of Localhost
            • Setup managed IPFS Nodes with Web3.storage
            • Start the work on Third Storage Cloud
            • Product monetization
            The product roadmap and timelines can be found on Third Storage website
            Total Budget Requested
            MilestoneSummaryFunding requested (USD)
            Milestone #1Launching beta of SDK, CLI and Client. Expanding the team and setting up workspace70,000
            Milestone #2Research and define technical specifications on decentralized K8 containers, hosting and multi-node scaling. Expanding devops team80,000
            Milestone #3FVM Integration and getting started with Third Storage Cloud30,000
            Total budget requested : 180,000 USDC
            Maintenance and Upgrade Plans
            We are looking to continue this project and fundraise from VCs and angels by this quarter to support further growth. We are expecting to hire a team to take care of the development cycle.
            Team
            Team Members
            Point of contact :
            Kumaraguru T - Founder of Third Storage
            LinkedIn | Email
            Team Website
            Website : https://thirdstorage.com
            
Docs : https://docs.thirdstorage.com
            
Github : https://github.com/hackyguru
            
Discord : https://discord.thirdstorage.com
            
Brand : https://thirdstorage.com/brand
            Relevant Experience
            Our team successfully completed all the milestones in the previous iteration of this project. More details can be found here
            Team code repositories
            Github Organization : https://github.com/thirdstorage
            
Developer documentation : https://docs.thirdstorage.com
            Additional Information
            We are expecting to complete our seed round by Q4 2022. We already completed a successful iteration of this project previously and are looking for more funds to scale up.
            Activity
            Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
            Metadata
            Metadata
            Assignees
            Labels
            No labels
            No labels
            Type
            No type
            Projects
            No projects
              Milestone
              No milestone
              Relationships
              None yet
              Development
              No branches or pull requests
              Issue actions
              
, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Remove or un-stick sticky/fixed headers that block content\n(function() {\n function unstick() {\n document.querySelectorAll('header, nav, [role=\"banner\"], .header, .navbar, .sticky, .fixed-top, [style*=\"position: fixed\"], [style*=\"position:sticky\"]').forEach(function(el) {\n if (el.style.position === 'fixed' || el.style.position === 'sticky' || \n getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {\n el.style.position = 'static';\n el.style.top = 'auto';\n el.style.zIndex = 'auto';\n }\n });\n }\n \n unstick();\n \n var observer = new MutationObserver(unstick);\n observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });\n})();", "Kill Sticky Headers");
}
} catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

              Skip to content
              
This repository was archived by the owner on Feb 25, 2026. It is now read-only.

              
This repository was archived by the owner on Feb 25, 2026. It is now read-only.

              Open Grant : Third Storage #249
              Closed
              Closed
              Open Grant : Third Storage#249
              Assignees
              realChainLife
              Description
              @hackyguru
              hackyguru
              opened on Oct 21, 2022
              Open Grant Proposal: Third Storage
              Name of Project: Third Storage
              Proposal Category:devtools-libraries, integration-adoption
              Proposer:hackyguru
              Do you agree to open source all work you do on behalf of this RFP and dual-license under MIT, APACHE2, or GPL licenses?: Yes
              Project Description
              Most of the self-proclaimed web3 applications use centralized databases behind the hood and nullify the whole concept of decentralization by putting the privacy and security of user's data at risk. Confidential user data such as passwords, emails, KYCs and other critical information are often stored without encryption and are vulnerable to data breaches. Further, the developers can also access the private data of their users since the whole data is custodial to the developer without access control limitations.
              The biggest problem with the currently used web3 data storage solutions is that they lack composability, performance and scalability. Additionally, developers have a steep learning curve to get started with web3 data storage mechanisms and will have to spend a lot of time in setting up their development environment and storage nodes. The only positives of web2 databases is that they are easily scalable and can be used by web2 developers without any prerequisite knowledge about web3 jargons. But, web2 databases can not be ideal in a decentralized and privacy-preserving web. Migrating between two web3 databases can consume immense amount of time and the lack of data composability can sometimes make it an impossible task to automate. Developers are required to setup their own nodes on different geographical locations to boost their data-availability, performance, Geo-redundancy and decentralization. Further,
              
all these nodes are 'stand alone' and developers will have to manually sync in all the nodes. The whole web requires a new generation standard to build and use data storage. The new standard should value the privacy and self-soverignity of data more than any other aspect. Developers will have to spend hundreds of hours just to create an infrastructure that can meet all their production requirements.
              In most of the cases, web3 data storage options are not 'batteries ready'. This demotivates the developers to take up web3 options and finally the end up using low-code web2 alternatives that seem to do the job but compromise the data privacy that web3 offers.
              Value
              Developers usually face the following problems in web2 and web3 databases repectively,
              Web2 DatabasesWeb3 Databases
              Data sovereignty and ownership✅
              Access control✅
              Scalability✅
              Speed and perfomance✅
              Costs✅Cheaper than Web2 (Filecoin and IPFS)
              Data composabilityStill in early stages
              Third Storage solves all the above highlighted problems by providing mutant databases that leverage the pros from both web2 and web3 databases in the following ways :
              Data soverignity :
              
All the user data is self soverign and hosted on Filecoin. The data can not be tampered by external sources. The user has the governing power over his data whereas web2 data governance is external.
              Access control :
              
Decentralized access control is faciliated by using cryptography and lit protocol. Third Storage divides the user data into public and private based on the preference of user and developer.
              Scalablity :
              
Third Storage can be scaled horizontally and vertically based on the preference of the developer. The infrastructure can be deployed into distributed and geo-redundant infra with minimal costs.
              Speed and perfomance :
              
Third Storage does not compromise speed and perfomance in the name of 'decentralization'. We use caching mechanisms to make sure data retrival and writing is as fast as possible.
              Costs :
              
A big misconception about web3 is 'Storage is very expensive'. But surprisingly, storage on Filecoin and other web3 native solutions are cheaper than centralized web2 solutions. Third Storage also facilitates 'perpetual file storage'.
              Data composability
              Data composability is one of the crucial elements that was missing in web2. For example, if you hosted a file in AWS - it is not possible for content addressing it on another storage provider.
              Revolutionary technologies like IPFS can enable content addressing and data composability in web3. Third Storage leverages this capability to enable data composability between different storage paradigms. For example, if you wish to migrate from one storage paradigm to another in the future, you can do it without much hassle.
              Decentralized hosting
              You can seamlessly host your dapps on web3 native hosting options with Third Storage. Decentralized hosting only available in Third Storage Cloud. We provide multiple cloud deployment options which include :
              • IPFS Hosting : Hosting static web content on Filecoin and serving over IPFS.
              • Cloud Hosting : Third Storage also facilitates Cloud hosting for dynamic dapps. You can opt to host using our native cloud hosting solution or alternatively use third-party providers.
              Multi-node scaling
              With multi-node scaling you can boost data redundancy, data availability, vertical and horizontal scaling and level of decentralization. Multi-node scaling is only available for Third Storage Cloud users.
              Deliverables
              We will be launching Third Storage Localhost as the core deliverable of this open grant. More information about Third Storage Localhost can be found here
              Development Roadmap
              Roadmap
              Q4 2022 :
              October :
              • Hiring developers and expanding team
              • Ship Third Storage SDK
              • Ship Third Storage CLI
              • Ship Third Storage Client
              November:
              • Ship examples on React and NextJS
                • Hiring developers and expanding team
              December :
              • ETHIndia Launch
              • Work on branding
              Q1 2023 :
              • Launch stable version of Localhost
              • Setup managed IPFS Nodes with Web3.storage
              • Start the work on Third Storage Cloud
              • Product monetization
              The product roadmap and timelines can be found on Third Storage website
              Total Budget Requested
              MilestoneSummaryFunding requested (USD)
              Milestone #1Launching beta of SDK, CLI and Client. Expanding the team and setting up workspace70,000
              Milestone #2Research and define technical specifications on decentralized K8 containers, hosting and multi-node scaling. Expanding devops team80,000
              Milestone #3FVM Integration and getting started with Third Storage Cloud30,000
              Total budget requested : 180,000 USDC
              Maintenance and Upgrade Plans
              We are looking to continue this project and fundraise from VCs and angels by this quarter to support further growth. We are expecting to hire a team to take care of the development cycle.
              Team
              Team Members
              Point of contact :
              Kumaraguru T - Founder of Third Storage
              LinkedIn | Email
              Team Website
              Website : https://thirdstorage.com
              
Docs : https://docs.thirdstorage.com
              
Github : https://github.com/hackyguru
              
Discord : https://discord.thirdstorage.com
              
Brand : https://thirdstorage.com/brand
              Relevant Experience
              Our team successfully completed all the milestones in the previous iteration of this project. More details can be found here
              Team code repositories
              Github Organization : https://github.com/thirdstorage
              
Developer documentation : https://docs.thirdstorage.com
              Additional Information
              We are expecting to complete our seed round by Q4 2022. We already completed a successful iteration of this project previously and are looking for more funds to scale up.
              Activity
              Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
              Metadata
              Metadata
              Assignees
              Labels
              No labels
              No labels
              Type
              No type
              Projects
              No projects
                Milestone
                No milestone
                Relationships
                None yet
                Development
                No branches or pull requests
                Issue actions
                
, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Universal Dark Mode - works on any site\n(function() {\n var enabled = true;\n \n function applyDarkMode() {\n if (!enabled) return;\n \n // Create style element if it doesn't exist\n var style = document.getElementById('universal-dark-mode-style');\n if (!style) {\n style = document.createElement('style');\n style.id = 'universal-dark-mode-style';\n document.head.appendChild(style);\n }\n \n // Dark mode CSS - inverts colors but preserves images/video\n style.textContent = '\n /* Invert everything except media */\n html {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #1a1a2e !important;\n }\n \n /* Restore images, videos, iframes, canvas */\n img, video, iframe, canvas, svg, picture, [style*=\"background-image\"] {\n filter: invert(1) hue-rotate(180deg) !important;\n }\n \n /* Preserve specific elements that should not be inverted */\n .no-dark-mode, .no-dark-mode *,\n [data-theme=\"light\"], [data-theme=\"light\"],\n .ace_editor, .ace_editor *,\n .CodeMirror, .CodeMirror *,\n .monaco-editor, .monaco-editor *,\n .markdown-body pre, .markdown-body pre *,\n .highlight, .highlight *,\n pre code, pre code * {\n filter: none !important;\n }\n \n /* Fix common UI elements */\n .modal, .popup, .dropdown-menu, .tooltip, .popover {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #2d2d44 !important;\n border-color: #444 !important;\n }\n \n /* Scrollbars */\n ::-webkit-scrollbar { background: #1a1a2e !important; }\n ::-webkit-scrollbar-thumb { background: #444 !important; }\n ::-webkit-scrollbar-thumb:hover { background: #555 !important; }\n \n /* Selection */\n ::selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ';\n }\n \n function removeDarkMode() {\n var style = document.getElementById('universal-dark-mode-style');\n if (style) style.remove();\n }\n \n // Toggle with Alt+Shift+D\n document.addEventListener('keydown', function(e) {\n if (e.altKey && e.shiftKey && e.key === 'D') {\n e.preventDefault();\n enabled = !enabled;\n if (enabled) {\n applyDarkMode();\n console.log('[Universal Dark Mode] Enabled');\n } else {\n removeDarkMode();\n console.log('[Universal Dark Mode] Disabled');\n }\n }\n });\n \n // Apply on load\n applyDarkMode();\n \n // Re-apply on dynamic content\n var observer = new MutationObserver(function(mutations) {\n if (enabled && !document.getElementById('universal-dark-mode-style')) {\n applyDarkMode();\n }\n });\n observer.observe(document.head, { childList: true });\n \n console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle');\n})();", "Universal Dark Mode");
}
} catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); }
})();
})();

                Skip to content
                
This repository was archived by the owner on Feb 25, 2026. It is now read-only.

                
This repository was archived by the owner on Feb 25, 2026. It is now read-only.

                Open Grant : Third Storage #249
                Closed
                Closed
                Open Grant : Third Storage#249
                Assignees
                realChainLife
                Description
                @hackyguru
                hackyguru
                opened on Oct 21, 2022
                Open Grant Proposal: Third Storage
                Name of Project: Third Storage
                Proposal Category:devtools-libraries, integration-adoption
                Proposer:hackyguru
                Do you agree to open source all work you do on behalf of this RFP and dual-license under MIT, APACHE2, or GPL licenses?: Yes
                Project Description
                Most of the self-proclaimed web3 applications use centralized databases behind the hood and nullify the whole concept of decentralization by putting the privacy and security of user's data at risk. Confidential user data such as passwords, emails, KYCs and other critical information are often stored without encryption and are vulnerable to data breaches. Further, the developers can also access the private data of their users since the whole data is custodial to the developer without access control limitations.
                The biggest problem with the currently used web3 data storage solutions is that they lack composability, performance and scalability. Additionally, developers have a steep learning curve to get started with web3 data storage mechanisms and will have to spend a lot of time in setting up their development environment and storage nodes. The only positives of web2 databases is that they are easily scalable and can be used by web2 developers without any prerequisite knowledge about web3 jargons. But, web2 databases can not be ideal in a decentralized and privacy-preserving web. Migrating between two web3 databases can consume immense amount of time and the lack of data composability can sometimes make it an impossible task to automate. Developers are required to setup their own nodes on different geographical locations to boost their data-availability, performance, Geo-redundancy and decentralization. Further,
                
all these nodes are 'stand alone' and developers will have to manually sync in all the nodes. The whole web requires a new generation standard to build and use data storage. The new standard should value the privacy and self-soverignity of data more than any other aspect. Developers will have to spend hundreds of hours just to create an infrastructure that can meet all their production requirements.
                In most of the cases, web3 data storage options are not 'batteries ready'. This demotivates the developers to take up web3 options and finally the end up using low-code web2 alternatives that seem to do the job but compromise the data privacy that web3 offers.
                Value
                Developers usually face the following problems in web2 and web3 databases repectively,
                Web2 DatabasesWeb3 Databases
                Data sovereignty and ownership✅
                Access control✅
                Scalability✅
                Speed and perfomance✅
                Costs✅Cheaper than Web2 (Filecoin and IPFS)
                Data composabilityStill in early stages
                Third Storage solves all the above highlighted problems by providing mutant databases that leverage the pros from both web2 and web3 databases in the following ways :
                Data soverignity :
                
All the user data is self soverign and hosted on Filecoin. The data can not be tampered by external sources. The user has the governing power over his data whereas web2 data governance is external.
                Access control :
                
Decentralized access control is faciliated by using cryptography and lit protocol. Third Storage divides the user data into public and private based on the preference of user and developer.
                Scalablity :
                
Third Storage can be scaled horizontally and vertically based on the preference of the developer. The infrastructure can be deployed into distributed and geo-redundant infra with minimal costs.
                Speed and perfomance :
                
Third Storage does not compromise speed and perfomance in the name of 'decentralization'. We use caching mechanisms to make sure data retrival and writing is as fast as possible.
                Costs :
                
A big misconception about web3 is 'Storage is very expensive'. But surprisingly, storage on Filecoin and other web3 native solutions are cheaper than centralized web2 solutions. Third Storage also facilitates 'perpetual file storage'.
                Data composability
                Data composability is one of the crucial elements that was missing in web2. For example, if you hosted a file in AWS - it is not possible for content addressing it on another storage provider.
                Revolutionary technologies like IPFS can enable content addressing and data composability in web3. Third Storage leverages this capability to enable data composability between different storage paradigms. For example, if you wish to migrate from one storage paradigm to another in the future, you can do it without much hassle.
                Decentralized hosting
                You can seamlessly host your dapps on web3 native hosting options with Third Storage. Decentralized hosting only available in Third Storage Cloud. We provide multiple cloud deployment options which include :
                • IPFS Hosting : Hosting static web content on Filecoin and serving over IPFS.
                • Cloud Hosting : Third Storage also facilitates Cloud hosting for dynamic dapps. You can opt to host using our native cloud hosting solution or alternatively use third-party providers.
                Multi-node scaling
                With multi-node scaling you can boost data redundancy, data availability, vertical and horizontal scaling and level of decentralization. Multi-node scaling is only available for Third Storage Cloud users.
                Deliverables
                We will be launching Third Storage Localhost as the core deliverable of this open grant. More information about Third Storage Localhost can be found here
                Development Roadmap
                Roadmap
                Q4 2022 :
                October :
                • Hiring developers and expanding team
                • Ship Third Storage SDK
                • Ship Third Storage CLI
                • Ship Third Storage Client
                November:
                • Ship examples on React and NextJS
                  • Hiring developers and expanding team
                December :
                • ETHIndia Launch
                • Work on branding
                Q1 2023 :
                • Launch stable version of Localhost
                • Setup managed IPFS Nodes with Web3.storage
                • Start the work on Third Storage Cloud
                • Product monetization
                The product roadmap and timelines can be found on Third Storage website
                Total Budget Requested
                MilestoneSummaryFunding requested (USD)
                Milestone #1Launching beta of SDK, CLI and Client. Expanding the team and setting up workspace70,000
                Milestone #2Research and define technical specifications on decentralized K8 containers, hosting and multi-node scaling. Expanding devops team80,000
                Milestone #3FVM Integration and getting started with Third Storage Cloud30,000
                Total budget requested : 180,000 USDC
                Maintenance and Upgrade Plans
                We are looking to continue this project and fundraise from VCs and angels by this quarter to support further growth. We are expecting to hire a team to take care of the development cycle.
                Team
                Team Members
                Point of contact :
                Kumaraguru T - Founder of Third Storage
                LinkedIn | Email
                Team Website
                Website : https://thirdstorage.com
                
Docs : https://docs.thirdstorage.com
                
Github : https://github.com/hackyguru
                
Discord : https://discord.thirdstorage.com
                
Brand : https://thirdstorage.com/brand
                Relevant Experience
                Our team successfully completed all the milestones in the previous iteration of this project. More details can be found here
                Team code repositories
                Github Organization : https://github.com/thirdstorage
                
Developer documentation : https://docs.thirdstorage.com
                Additional Information
                We are expecting to complete our seed round by Q4 2022. We already completed a successful iteration of this project previously and are looking for more funds to scale up.
                Activity
                Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
                Metadata
                Metadata
                Assignees
                Labels
                No labels
                No labels
                Type
                No type
                Projects
                No projects
                  Milestone
                  No milestone
                  Relationships
                  None yet
                  Development
                  No branches or pull requests
                  Issue actions