View Source API Reference Diode Client v1.2.5

Modules

DiodeClient secure end-to-end encrypted connections between any two machines. Connections are established either through direct peer-to-peer TCP connections or bridged via the Diode network. To learn more about the decentralized Diode network visit https://diode.io/

A listener for incoming connections.

BitMessage implementation used for Diode P2P cold messages.

Block related helper functions

Wrapper for BNS smart contract to register and resolve names.

Location of the BNS smart contract on Diode Network.

Imported contract to read group memberships. Useful to recursively resolve BNS names to individual devices.

Location of the BNS smart contract on Moonbase Alpha.

EIP-712 implementation

Meta transaction to submit pre-signed transactions to the blockchain.

All objects are made of tuples {:type, value1, value2, ..., valueN, signature} The number of values are different but the last signature is a signature is always is the signature of BertExt.encode!([value1, value2, ..., valueN])) Also the signatures public key is always equal to the key

Encoding and Decoding of Recursive Length Prefix (RLP) https://eth.wiki/fundamentals/rlp

DiodeClient.Shell is the interface to the blockchain state. It allows fetching accounts and block header information. Data fetched is by default checked against a merkle proof.

DiodeClient.Shell is the interface to the blockchain state. It allows fetching accounts and block header information. Data fetched is by default checked against a merkle proof.

DiodeClient.Shell is the interface to the blockchain state. It allows fetching accounts and block header information. Data fetched is by default checked against a merkle proof.

DiodeClient Transport interface for use with Cowboy2 Adapter and :hackeny. Potentially more depending on interface compatibility

Representation of an Ethereum Wallet. This struct can hold keys in three levels of completeness