@apophis-sdk/core

Contains the most generic definitions common to most blockchain ecosystems I've worked with. However, by itself, it is probably mostly uninteresting to you.

The core module is concerned with standardizing aspects of web3 development across ecosystems. It contains such things as:

• NetworkConfig with specializations for various ecosystems

  • CosmosNetworkConfig

• Signals, @apophis-sdk/core/signals.js

  • Active network

  • Active signer

  • Some computed helpers

• Generalized pubkey factory and PublicKey type

• Middleware mv subsystem

• RPC abstraction endpoints

• WebSocket abstraction PowerSocket

• Generalized type interfaces, such as TxBase and Signer<Tx extends TxBase>

• protobuf support (WIP)

• Shared business logic with deferrals to middlewares for ecosystem-specific implementations

Most of the SDK is built on NetworkConfigs. Further, each network config is referenced by instance. If your custom systems require generalization, it should generally refer to the network's name or chainId instead.