<?xml version="1.0" encoding="UTF-8" ?> <?xml-stylesheet type="text/xsl" href="rss.xsl"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/"> <channel> <title>HuFi Docs</title><link>https://docs.hu.finance/</link><atom:link href="https://docs.hu.finance/feed_rss_updated.xml" rel="self" type="application/rss+xml" /> <docs>https://github.com/Hu-Fi/hufi</docs><language>en</language> <pubDate>Fri, 01 May 2026 13:31:26 -0000</pubDate> <lastBuildDate>Fri, 01 May 2026 13:31:26 -0000</lastBuildDate> <ttl>1440</ttl> <generator>MkDocs RSS plugin - v1.19.0</generator> <image> <url>None</url> <title>HuFi Docs</title> <link>https://docs.hu.finance/</link> </image> <item> <title>Integrating PancakeSwap into HuFi Using a Custom Subgraph: Why We Built Our Own Subgraph</title> <category>engineering</category> <category>updates</category> <description>&lt;p&gt;HuFi has always aimed to provide its users with the most reliable and comprehensive insight into decentralized finance. Integrating PancakeSwap into our platform was a natural step toward expanding our DeFi offerings—after all, PancakeSwap remains one of the largest automated market makers on the BNB Smart Chain. However, the process was far from straightforward. We encountered repeated issues with publicly hosted subgraphs (the indexing services that power data queries for smart contracts), which resulted in stale data, incomplete records and frequent outages. To solve this, we decided to build and operate our own PancakeSwap subgraph tailored for HuFi’s needs.&lt;/p&gt;</description> <link>https://docs.hu.finance/blog/2026/03/19/integrating-pancakeswap-into-hufi-using-a-custom-subgraph-why-we-built-our-own-subgraph/</link> <pubDate>Fri, 01 May 2026 13:30:38 +0000</pubDate> <source url="https://docs.hu.finance/feed_rss_updated.xml">HuFi Docs</source><guid isPermaLink="true">https://docs.hu.finance/blog/2026/03/19/integrating-pancakeswap-into-hufi-using-a-custom-subgraph-why-we-built-our-own-subgraph/</guid> </item> </channel> </rss>