Blockchain2023
PENDLEBLUEPRINTS
Multi-chain Pendle indexing — factories, routers, SY/PT/YT; Blueprint SDK for positions.
6
Indexed chains
20+
Router bytecode variants
1
Blueprint SDK surface
SCROLL
Multi-chain Pendle indexing — factories, routers, SY/PT/YT; Blueprint SDK for positions.
Pendle V3 markets span six chains with factories, routers, SY/PT/YT instruments, and governance hooks — consumers needed a subgraph that stayed correct as router bytecode forked per deployment.
Mustache-templated manifests per network, exhaustive handler matrices for router edges, and a Blueprint SDK layer for position analytics that tracks the same entities the subgraph exposes.
Router variant explosion, multi-factory versioning, and ensuring user-position SDK helpers didn’t desync from on-chain accounting when new markets launched mid-quarter.
Enumerate Pendle deployments per chain; diff router ABIs where bytecode diverged.
Generate subgraph.yaml + networks.json from one template set.
Track mints, merges, exits, and fee accrual with consistent decimal handling.
Blueprint SDK exposes typed queries for positions and APY rollups aligned to subgraph entities.
Fixture blocks replay router upgrades before mainnet promotion.
Ethereum, Arbitrum, BNB, Optimism, Mantle, and Base each run manifests generated from shared templates so address updates ship as data, not copy-paste subgraph repos.
Ethereum, Arbitrum, BNB, Optimism, Mantle, and Base each run manifests generated from shared templates so address updates ship as data, not copy-paste subgraph repos.
One mapping codebase with data-driven configs prevented six divergent forks.
SDK parity with subgraph entities avoided “two truths” between analytics and on-chain state.
Explicit variant table for routers instead of brittle ABI guessing at runtime.
New Pendle router deploys became config-only changes when bytecode stayed in the supported set.
Axum learning CLI
We take on a small number of projects at a time. If the problem is hard, we're interested.