Welcome
The team behind Float has been building subgraphs for several years. First for wildcards.world, and since then, they have been contracted to build out multiple production critical graphs for clients (as avolabs.io) and most recently for their own protocol, Float.
Through working extensively with subgraphs, common problems seen repeatedly in subgraph development are issues of loading undefined entities, not setting or initializing all values of entities, and race conditions on loading and saving entities, respectively. Mishandled entities cause subgraphs to crash, which can be very disruptive for projects that are dependent on the graph. The unavailability of subgraphs can result in unavailability of the overall system and adverse business impacts.
The Float team has found strategies to make subgraphs more type-safe via a variety of helper functions that make many classes of common graph bugs impossible, and have been used with great effect in developing and upgrading Float’s subgraphs.
In August 2022, the Float team decided that the use of this tool would benefit any subgraph developer and ultimately benefit overall Graph ecosystem, and applied for a grant with The Graph Foundation. After successful application, Float received funding to decouple the tool from its current hard-coded integration, package the code generation tool into a stand-alone application, open-source it, and integrate with the Graph CLI.
🎉 The Graph Foundation Allocates Nearly $1M in Wave 6 of Grants 🎉
“Credits are owed to the amazing team running The Graph Foundation Grants Program. Float is extremely grateful to be contributing to the graph ecosystem and providing builders with more confidence in their subgraph development.” - Jason Smythe, Co-Founder at Float
Any project building or upgrading a subgraph can use this tool to make their subgraphs “uncrashable” and ensure continuous uptime 🚀
