Mirrored from filpgf.io — ProPGF Batch 3 (Karma program 1479, application 6a3184a16e2b9bde36d202fc, status: pending). Contact details redacted; canonical application lives on filpgf.io. 1.1 Project Name Chain.Love 1.2 Project Github https://github.com/chain-love 1.3 Project Website https://filecoin.chain.love 1.4 Team Lead/Point of Contact Arsenii Petrovich - CTO - Telegram (@mrcommander) 1.5 Category [ "Core Infrastructure", "RFP 3 - AI infrastructure products on Filecoin" ] 1.6 Open Source Status Partial 2.1 Project Summary The goal of this proposal is to keep providing the premium Node Hosting services for the Filecoin community and development team as we have been providing for years as Glif Nodes. Given the recent extreme spikes in a hardware pricing, Chain.Love suggest moving RPC infrastructure from PL-subsidized AWS to a more cost-efficient location. This drives the visual cost increase comparing to the previous grant application, however, it actually reduces cost if we combine service prices and infra prices, that were subsidized previously. Get a PDF version of a Grant application [here](https://drive.google.com/file/d/1Z5Hu59aD2XuRbcknEVDBwQ2R5ikPh88s/view?usp=sharing). 2.2 Who does this work support? [ "Onramps", "Application Builders", "Application Users", "Network Infrastructure" ] 2.3 Total Funding Requested (USD) 106866.67 2.4 Milestones & Budget [ { "title": "Premium Node Hosting services for the Filecoin community", "description": "We are hosting public and private nodes in Mainnet and Calibnet, receiving around 1.2B requests per month, also working closely with the ecosystem to continuously improve the infrastructure tooling. We provide user-facing services - Docker Images, automation scripts, API endpoints with information about circulating supply and current market deals.\nBeing deeply involved in the Filecoin ecosystem we provide crucial service to core teams of the Filecoin ecosystem, providing custom services, helping the ecosystem to grow while keeping the node running [with nearly 100% uptime](https://status.node.glif.io).\n\nComparing existing service providers:\n| Service / Feature | Glif | Ankr | DRPC | Lava Network |\n|---|---|---|---|---|\n| RPS | 1.2B | 150M | unknown | 12–30M |\n| Recent-state nodes | Yes (Public, not limited) | Yes (Limited) | Yes (Limited) | Mainnet (Limited) |\n| Archival Nodes | Premium plan | Premium plan | No | No |\n| FVM Archival Nodes | Premium plan | No | No | No |\n| WSS Endpoints | Yes | Premium plan | Yes | Yes |\n| State Market deals archive | Yes | No | No | No |\n| Circulating supply API | Yes | No | No | No |\n| Public docker images | Yes | No | No | No |\n| Public Terraform scripts | Yes | No | No | No |\n| User Support | Yes | Enterprise plan | Limited | Limited |\n\nAs a part of this grant entitled administrator from the Filecoin ecosystem will be issued with a credit of ~$60,000 worth of Chain.Love tokens that can be used by said administrator to grant access to the Chain.Love nodes to the important ecosystem partners under the assumption that Chain.Love would have provided the same service fully covered by the clients funds using the bare metal infrastructure. Thus, the credits are calculated as if clients that are approved for free usage of Chain.Love services were paying the infrastructure and services price fully themselves + $5,000 to have an expansion gap for any additional clients that might arise during 2026-2027.", "dueDate": "2027-05-31", "fundingRequested": "40666.67", "completionCriteria": "Support:\n- 100 free requests per minute per IP address\n- Users (community) support with at least 16/5 availability\n- Support of the dedicated (private) nodes for users whitelisted by Filecoin\n- Answer requests in 2h tops\n- Support Filecoin teams with testing new upcoming features\nImprovements:\n- Keep improving our solution and bring new features for the end users\n- Improve caching to cache more requests thus reducing node load and infra costs\n- Support finance department with updating list of wallets excluded from circulation\n- Continuous improvement of Filecoin ecosystem with custom development worth at least 40 hours of developers work monthly.\n- Keep working on public docker images and terr …[truncated] 3.1 Impact pathway The grant aims to indirectly strengthen Network Profitability & Cryptoeconomics funds via the continued operation of dedicated Filecoin RPC infrastructure that developers, wallets, dApps, and application users rely on. RPC is used over 150k different IPs monthly, resulting in over 1.2B of requests. # Output => Outcome => Impact The output is stable, maintained RPC capacity for Filecoin over the grant period, reducing the risk of degraded access, downtime, or unavailable endpoints. => This improves the system by making Filecoin applications easier to build, test, operate, and use without every team needing to run its own infrastructure. => The outcome is higher reliability for builders and end users interacting with Filecoin-based applications. => This supports Network Profitability & Cryptoeconomics and Flagship Client Adoption by lowering infrastructure friction, improving user experience, and helping more onchain activity succeed. 3.2 Verification metrics N/A 3.3 References We got to the top of all the Retro-PGF rounds winning the first one, and impacting the life of nearly all the ecosystem stakeholders. Uptime dashboard: https://status.node.glif.io/ (uptime page published under old Glif Nodes domain) [Requests dashboard](https://monitoring.chain.love/public-dashboards/0a5fe2d9bdc24af680e1a9a59fc18380) Stakeholders: Name: Eva Shon Role: FilPonto/Ecosystem lead Name: Chris Brocoum Role: Finance Director (?) Name: Sarah Thiam Role: FilBuilders lead Name: Molly Mackinlay Role: ProtocolLabs Eng + Research WG Lead 4.1 Monthly Operating Burn [ "$10-$100K (small team)" ] 4.2 What % of total team monthly burn depends on this grant? 10% 4.3 If this grant is not awarded, what happens? We will keep supporting Filecoin with our best efforts, however, to keep ourselves afloat we will have to significantly rise prices and reduce free access capabilities. Additionally, since Full Archival node is required only on case by case basis - we likely would have terminated it completely. 4.4 Core Team Name: Arsenii Petrovich Role: Co-founder & CTO Background: 10+ years in IT, 8+ years in blockchain engineering, building primiarily outsourcing projects, 5+ years in technical leadership across Web3 platforms, RPC infrastructure, and high-availability systems. Responsibilities: designing product's architecture, defining technical vision and supervise the implementation roadmap; leading and mentoring engineering teams, ensuring reliability, scalability, and security; coordinating with ecosystem partners and clients teams. Name: Dzmitry Kliapkou Role: Fullstack Engineer + DevOps Background: Fullstack engineer with DevOps expertise, experienced in building, deploying, and operating production-grade blockchain services. Responsibilities: Developing application code and operating infrastructure, including CI/CD, monitoring, and reliability. Name: Ales Dumikau Role: Fullstack Engineer + DevOps Background: Fullstack and DevOps engineer focused on scalable backend systems and operational automation in blockchain environments. Responsibilities: Building backend services and ensuring stable, automated, and scalable infrastructure. Name: Yan Lozovskiy Role: Fullstack Engineer (Go, Node.js) Background: Fullstack engineer specializing in backend development for distributed and blockchain-based systems. Responsibilities: Implementing backend services and APIs for blockchain infrastructure and developer tooling. Name: Taras Vasylkiv Role: Fullstack Engineer (Go, Node.js) Background: Fullstack engineer specializing in backend development for distributed and blockchain-based systems. Responsibilities: Developing and maintaining backend components for blockchain infrastructure services 4.5 Has your team received a ProPGF grant or funding from PLFIF before? [ "Yes" ] 5.1 Key risks & dependencies **Risk**: single-DC failure **Mitigation**: disitrubtion across 2 geo-distributed bare-metal servers **Risk**: restore times for the Full Archival Node **Mitigation**: backups, restore time reduces to days instead of months **Risk**: backup cost volatility **Mitigation**: waived from this proposal, Chain.Love is responsible for that risk **Risk**: on-call coverage **Mitigation**: red phone number to call directly to CTO if something goes wrong **Risk**: demand exceeds capacity **Mitigation**: this infrastructure is scalable easily to handle over 2B of requests. Over that - may require additional server renting. Anything else you want to share that we didn't ask? Our previous grant is still ongoing till October. We are more than half-way through the grant. On top of regular node hosting our promises were: + User management of the subgraphs (upgrading subgraphs, restarting them, getting logs from subgraphs, etc.) + More auth methods including Google Auth and GitHub auth + Implementation of the improved UI that Stef Magdalinski helped us to create + Platform API keys to allow end users monitor the compute unit spend via automated systems, generate more user keys and manage billing +/- Advanced caching that will further improve amount of requests hitting cache instead of nodes thus reducing infra costs - Administration panel for the entitled engineers from Filecoin team to be able to grant access to the nodes. - Methods limitation - community was asking for this as they afraid of token leakage With (+) sign we marked promises that we already achieved, (+/-) - partially achieved, (-) - did not achieve yet. On top of that we raised funds from within a Protofire DAO and added the following features, that Filecoin users are also benefitting from: + Toolbox - a service to discover and compare services available on the Filecoin network in 15+ categories. Includes Service Adding Wizad, MCP server and AI model in ChatGPT + Advanced load balancer - a solution that allows dApp developers to balance the RPC load between several RPC providers in a round-robin or failover mode. Load balancer automatically discovers the difference between recent-state and archival requests and send the requests to the appropriate endpoint. + Agentic discovery - ERC-8004 contracts deployed on Filecoin with ability to register new agents through UI interface. (in development) Crypto payments enablement - for users to be able to purchase service using USDFC. Contributing to Core Infrastructure? Everyone who uses Filecoin Network via wallet (Metamask, etc.), using Filecoin dApps, smart contracts and exchanges. Karma Profile 0xc2eda7715129182fa651b7c5900e73c2b9dea5c5ef8c13cfdf864220c985f732 Objective 1 Indirect Objective 2 Indirect Objective 3 Indirect Open Source Context Part of the Chain.Love stack was developed using venture fund investment to ensure that Chain.Love becomes more independent and become less of a burden for the network's ecosystem. This grant request is focused on server renting, and all the automation components, required to operate Filecoin nodes on bare-metal servers (such as Ansible scripts) will be completely open-source.