docs ⦿ dedot 🧑‍💻
TypinkXTelegramGithub
dedot 🧑‍💻
dedot 🧑‍💻
  • Welcome to Dedot
  • Why Dedot?
  • Getting started
    • Installation
    • Connect to network
    • @polkadot/api -> dedot
    • Packages structure
  • Clients & Providers
    • Providers
    • Clients
  • Client API
    • ChainApi
    • Constants
    • Runtime APIs
    • Storage Queries
    • Transactions
    • Events
    • Errors
  • ink! Smart Contracts
    • Introduction
    • Generate Types & APIs
    • Deploy contracts
    • Queries
    • Transactions
    • Events
    • Handle errors
  • CLI
  • Keyring & Signer
  • Runtime upgrades
  • Type system
  • Utilities
    • HexString
    • Uint8Array (U8a)
    • String
    • Hash functions
    • Address
    • BigInt & number
    • Balances
    • Merkleized Metadata
  • Help & FAQ
    • Tutorials
      • Develop ink! dApp using Typink
    • Built with Dedot
    • Forum Posts
    • Telegram
    • Github
    • API Reference
Powered by GitBook
On this page
  • Packages
  • dedot subpath packages

Was this helpful?

Edit on GitHub
  1. Getting started

Packages structure

Dedot's source code is splitted into multiple packages for different purposes, all of the packages and their purposes are listing in the table below.

Packages

Name
Description

High-level abstraction apis (clients, API executors...)

Providers for connection to JSON-RPC servers (WsProvider, SmoldotProvider)

Generic shared types across the packages

Explicit Runtime API definitions to use for chains only supports Metadata V14

Basic codecs/shapes for scale-codec encode/decode

APIs to interact with ink! smart contracts

Known codecs for generic purposes ($Metadata, $AccountId32, $Extrinsic ...)

Useful utility functions

Storage API for different purposes (caching, ...)

Types & APIs generation engine for chaintypes & ink! smart contracts

Dedot's CLI

Umbrella package re-exporting primitives & APIs from other packages, including subpath packages

dedot subpath packages

By default dedot package only re-exports primitives from @dedot/api, @dedot/providers, @dedot/shape, giving you enough APIs to connect to the network & making on-chain interactions. It also comes with a few subpath packages giving access to APIs to working with ink! contracts, known-codecs, utility functions...

Name
Description

dedot

Re-exports @dedot/api, @dedot/providers & @dedot/shape packages

dedot/contracts

Re-exports @dedot/contracts package

dedot/codecs

Re-exports @dedot/codecs package

dedot/utils

Re-exports @dedot/utils package

dedot/types

Re-exports @dedot/types package

dedot/types/json-rpc

Re-exports @dedot/types/json-rpc package for Substrate JSON-RPC API types information (both new & legacy)

dedot/runtime-specs

Re-exports @dedot/runtime-specs package

dedot/shape

Re-exports @dedot/shape package

dedot/merkleized-metadata

Re-exports @dedot/merkleized-metadata package

Previous@polkadot/api -> dedotNextClients & Providers

Last updated 5 days ago

Was this helpful?

Implementation, with utilities to calculate metadata hash/digest & proof for extrinsic, extrinsic payload...

@dedot/api
@dedot/providers
@dedot/types
@dedot/runtime-specs
@dedot/shape
@dedot/contracts
@dedot/codecs
@dedot/utils
@dedot/storage
@dedot/codegen
@dedot/cli
@dedot/merkleized-metadata
RFC-0078
dedot