Home > tupelo-wasm-sdk
tupelo-wasm-sdk package
The Tupelo WASM SDK is designed to be used in both nodejs and the browser.
Classes
Class |
Description |
ChainTree |
ChainTree is the main class used for interacting with the data of Tupelo. See https://docs.quorumcontrol.com/docs/chaintree.html for a detailed description of what a ChainTree is. |
Community |
Commmunity is a combination of a Tupelo NotaryGroup and the application ‘Community’ running. The remote p2p community app will also store blocks, and this is the default supported way that the current wasm-sdk works. |
CommunityMessenger |
(BETA) CommunityMessenger handles the overlay pubsub community provides to make sure that nodes correctly relay messages within this community. Community listends to a number of libp2p topics (we call shards here) and internal community topics are broadcast on those libp2p topics so that libp2p will correctly relay those messages. |
Dag |
Underlies a ChainTree, it represents a DAG of IPLD nodes and supports resolving accross multiple nodes. |
EcdsaKey |
EcdsaKey defines the public/private key-pairs used to interact with Tupelo. It also supportes generating new keys either randomly or through a passphrase. |
Repo |
Repo is a typescript wrapper around the IPFS Repo https://github.com/ipfs/js-ipfs-repo |
WrappedBitswap |
A wrapper around an IPFS call-back-based bitswap that turns it into async/await compatible. There is currently an open PR on the bitswap repo that will allow us to switch to the IPFS-maintained bitswap completely. |
WrappedBlockService |
A wrapper around a callback-based IBlockService that allows async/await There is an open PR on the bitswap PR which will allow us to switch to the ipfs-maintained version. |
Functions
Interfaces
Namespaces
Namespace |
Description |
Community |
|
p2p |
|
Tupelo |
Tupelo is the more “raw” namespace, it is generally expected that you would use higher level wrapper classes around this namespace. For example: EcdsaKey or |
Variables