Files
pezkuwi-api/packages/api-derive
Satoshi Qazi Muhammed 7c6cac97da Fix the lint errors
Most are object keys out of order after the rename (dicle, pezkuwi,
bizinikiwi, teyrchains and zagros sort differently from the names they
replaced); they are sorted, behaviour is unchanged. The rest:

- createClass: header.hash is already the BlockHash type; the
  `as any` cast is removed
- ScProvider: WellKnownChain is a string union in @bizinikiwi/connect,
  so `string | WellKnownChain` was `string`; the spec parameter says so
- ScProvider: the jsonRpcResponses loop is a named async function whose
  rejection (chain removed, client terminated) is caught explicitly
  instead of a floating promise
- the fake chain in the spec no longer needs a non-null assertion
- Extrinsic.hash: redundant non-null assertion removed
- metadata-get.mjs writes the 2026 header
2026-10-08 03:23:10 +04:00
..
2026-10-08 03:23:10 +04:00

@pezkuwi/api-derive

Collection of high-level utility functions built on top of the @pezkuwi/api library. Designed to simplify the process of querying complex on-chain data by combining multiple RPC calls, storage queries, and runtime logic into a single, callable function.

Instead of manually fetching and processing blockchain data, developers can use api.derive methods to retrieve information.

Available Derive Namespaces

The derive functions are categorized into namespaces based on different common Bizinikiwi modules. Accesible by calling api.derive.NAMESPACE (e.g. api.derive.balances). The available modules are as follows: