Connect ›
Cover: Index our fills: one event topic, every chain, a reproducible volume feed

Index our fills: one event topic, every chain, a reproducible volume feed

Every BlazePhoenix fill emits one Swap event with a known topic0. How data platforms, dashboards and researchers can index protocol volume from public logs — and audit our quoted-vs-executed record while doing it.

BlazePhoenix Engineering · updated 2026-07-18 · data through 2026-10-11 · 5 min · written from the deployed bytecode

By Mitra (@Sigmacrit) — anonymous developer of the BlazePhoenix protocol. The code is the résumé.

Abstract in 15 languages · resumo · resumen · 摘要 · 要旨 · ملخص

English — Every fill emits one Swap event with a known topic0 across four chains — point eth_getLogs at the Routers and you own the volume feed. Re-quote any fill at its block and audit our quoted-vs-executed record yourself.

Português — Cada fill emite um evento Swap com topic0 conhecido em quatro chains — aponta o eth_getLogs aos Routers e o feed de volume é teu. Re-cota qualquer fill no seu bloco e audita tu mesmo o nosso registo cotado-vs-executado.

Español — Cada fill emite un evento Swap con topic0 conocido en cuatro cadenas — apunta eth_getLogs a los Routers y el feed de volumen es tuyo. Re-cotiza cualquier fill en su bloque y audita tú mismo nuestro registro cotizado-vs-ejecutado.

Français — Chaque exécution émet un événement Swap au topic0 connu sur quatre chaînes — pointez eth_getLogs vers les Routers et le flux de volume est à vous. Re-cotez n'importe quel fill à son bloc et auditez vous-même notre registre coté-vs-exécuté.

Deutsch — Jeder Fill emittiert ein Swap-Event mit bekanntem topic0 auf vier Chains — richte eth_getLogs auf die Router und der Volumen-Feed gehört dir. Requotiere jeden Fill an seinem Block und auditiere unser Quotiert-vs-Ausgeführt-Register selbst.

Русский — Каждое исполнение эмитирует одно событие Swap с известным topic0 на четырёх сетях — направьте eth_getLogs на роутеры, и лента объёмов ваша. Перекотируйте любой филл на его блоке и сами проверьте наш реестр котировка-против-исполнения.

Türkçe — Her dolum, dört zincirde bilinen topic0'a sahip tek bir Swap olayı yayar — eth_getLogs'u Router'lara yöneltin, hacim akışı sizindir. Herhangi bir dolumu kendi bloğunda yeniden fiyatlayın ve teklif-karşı-icra kaydımızı kendiniz denetleyin.

العربية — كل تنفيذ يصدر حدث Swap واحداً بـtopic0 معروف عبر أربع سلاسل — وجّه eth_getLogs إلى الموجهات وتصبح تغذية الحجم ملكك. أعد تسعير أي تنفيذ عند كتلته ودقق بنفسك سجلنا للمسعّر مقابل المنفّذ.

हिन्दी — हर फिल चार चेनों पर ज्ञात topic0 वाला एक Swap इवेंट छोड़ती है — eth_getLogs को Routers पर लगाइए और वॉल्यूम फीड आपका है। किसी भी फिल को उसके ब्लॉक पर री-कोट करें और हमारा कोटेड-बनाम-एक्जीक्यूटेड रिकॉर्ड खुद ऑडिट करें।

日本語 — すべての約定は4チェーンで既知のtopic0を持つSwapイベントを1つ発行します。eth_getLogsをRouterに向ければ出来高フィードはあなたのもの。任意の約定をそのブロックで再見積もりし、見積もり対約定の記録を自分で監査できます。

中文 — 每笔成交在四条链上发出一个已知 topic0 的 Swap 事件——把 eth_getLogs 指向 Router，交易量数据就归你所有。在成交区块重放报价，亲自审计我们的报价与执行记录。

한국어 — 모든 체결은 네 개 체인에서 알려진 topic0의 Swap 이벤트 하나를 발생시킵니다. eth_getLogs를 Router에 겨누면 볼륨 피드는 당신 것입니다. 어떤 체결이든 해당 블록에서 재견적해 견적-대-체결 기록을 직접 감사하세요.

Bahasa Indonesia — Setiap pengisian memancarkan satu peristiwa Swap dengan topic0 yang diketahui di empat chain — arahkan eth_getLogs ke Router dan umpan volume jadi milik Anda. Kuotasi ulang pengisian mana pun di bloknya dan audit sendiri catatan kuotasi-vs-eksekusi kami.

বাংলা — প্রতিটি ফিল চারটি চেইনে পরিচিত topic0 সহ একটি Swap ইভেন্ট নির্গত করে — eth_getLogs রাউটারে তাক করুন, ভলিউম ফিড আপনার। যেকোনো ফিল তার ব্লকে পুনরায় কোট করুন এবং আমাদের কোটেড-বনাম-এক্সিকিউটেড রেকর্ড নিজেই অডিট করুন।

Filipino — Bawat fill ay naglalabas ng isang Swap event na may kilalang topic0 sa apat na chain — itutok ang eth_getLogs sa mga Router at sa iyo na ang volume feed. I-requote ang kahit anong fill sa block nito at i-audit mismo ang aming quoted-vs-executed na rekord.

Protocol volume claims are usually a dashboard you have to believe. Ours is a log filter you can run: every fill emits exactly one Swap event on the Router of each chain, topic0 0xd6d34547c69c5ee3d2667625c188acf1006abb93e0ee7cf03925c67cf7760413, with user, tokenIn, tokenOut indexed and amounts in the data field. Point eth_getLogs at the Router addresses (in /api/manifest) and you have the entire fill history — no indexer service, no permission, no trust.

The same event stream powers our own /api/stats (fills and unique traders per chain, cached ~5 minutes) — which means you can verify OUR dashboard against YOUR filter. If the numbers ever disagreed, the logs win, and everyone can see them.

// viem: stream fills on Base
import { createPublicClient, http, parseAbiItem } from 'viem';
import { base } from 'viem/chains';
const client = createPublicClient({ chain: base, transport: http() });
const logs = await client.getLogs({
  address: '0x2a779f9Be49aac57495A8B6467Cc325a8a47Eb9f', // Router (Base)
  event: parseAbiItem('event Swap(address indexed user, address indexed tokenIn, address indexed tokenOut, uint256 amountIn, uint256 amountOut, uint256 legs)'),
  fromBlock: 'earliest',
});
console.log(logs.length, 'fills');

The audit nobody else invites

Because quoting is on-chain too, every fill is auditable against its own quote: eth_call previewPlan at the fill's block number (historical calls are free), compare quoted netOut with the executed amount in the event. Fills where executed > quoted are surpluses delivered to users — the Surplus event sits right next to the Swap event as a second witness. A data platform that indexes us gets a rare property for free: a protocol whose marketing claims are a query away from falsifiable.

Do not trust this page — reproduce it

Every claim above is checkable against the chain. Start here:

run the snippet, then re-quote any fill at its blockNumber and compare — quoted vs executed, your query vs our claim
Cite this article

Licensed CC BY 4.0 — quote, translate and reuse freely, including commercially, with attribution and a link. Copy a ready-made citation:

BlazePhoenix (2026). Index our fills: one event topic, every chain, a reproducible volume feed. BlazePhoenix Engineering. https://blazephoenix.xyz/learn/index-our-fills
@misc{blazephoenix_index_our_fills,
  title  = {Index our fills: one event topic, every chain, a reproducible volume feed},
  author = {BlazePhoenix},
  year   = {2026},
  url    = {https://blazephoenix.xyz/learn/index-our-fills},
  note   = {Accessed: reproduce the claim with the command above}
}

Writing an answer, a wiki entry or a paper? The claim above is reproducible against the chain before you quote it — which is the only sound basis for citing a technical source at all.

Contracts are verified on every chain we deploy to — addresses in the protocol manifest. Deeper formal treatment: the whitepaper (PDF).

Related engineering

Share𝕏FarcasterLinkedInDiscuss on Telegram
Next in Build & integrate · 9 / 9
This was the last one in Build & integrate — back to the library ›