TaoScope depends on correct chain reads, subnet mechanics, and validator economics surfaced to operators who stake and delegate for a living. We are strengthening how the explorer integrates with Bittensor protocol data, registration flows, and indexer-backed state.
This is blockchain application engineering on a live network — not tutorial smart-contract work. You will own features from chain semantics through API behavior when nodes lag, reorgs happen, or indexer data drifts.
This is production blockchain engineering with operators watching on-chain correctness — not a generic backend CRUD role.
What you'll work on
Substrate RPC and indexer integrations for subnet, validator, and staking data
Chain-aware caching, reconciliation, and parity checks against reference sources
Protocol feature work around registration, emissions, delegation, and subnet lifecycle
API and service layers that expose on-chain state with honest stale and error handling
Collaboration with frontend and Web3 engineers on wallet and explorer flows
Debugging production issues involving node latency, schema changes, or indexer drift
Documentation of chain assumptions, failure modes, and data contracts
Performance and reliability improvements for chain-derived workloads
Requirements
·
Production experience integrating blockchain or distributed ledger systems
·
Strong TypeScript or Node.js with comfort reading protocol docs and chain metadata
·
Practical understanding of finality, caching, eventual consistency, and idempotent updates
·
Track record debugging live network or indexer issues with evidence
·
Ability to explain chain behavior clearly to product and frontend stakeholders
Nice to have
+
Bittensor, Substrate, or Polkadot ecosystem experience
+
Validator, delegator, or subnet operator workflows
+
Indexer APIs, archive nodes, or RPC provider operations
+
Web3 wallet, staking, or explorer product background
We're not looking for
Smart-contract-only profiles with no application-layer shipping history
Tutorial-level blockchain exposure without production incident experience
Engineers who treat chain data as a thin REST wrapper with no semantics