Possible states of API connection to the blockchain.
Ethereum provider injected to the web by MetaMask. If missing, ApiContextBase state must be NoProvider
Function for creating global API context. This function should be called exactly once through the whole application.
Global database context, which is needed for caching information obtained by API
Global notification context, which is needed for letting user know about important API events
Global API context in corresponding state
Generated using TypeDoc
This file defines API context which handles whole communication between web application and Ethereum blockchain. First it ensures whether MetaMask is present and properly configured, then it creates subcontexts (from api/* subfolder) for interacting with blockchain itself and deployed game contracts.