SDK packages
@decentralchain scope and five that live in the monorepo workspace. Knowing which is which saves a confusing half hour: an example written from inside the repository can import a workspace package, and the same line run outside it resolves to nothing.npm i @decentralchain/transactions @decentralchain/ts-lib-crypto
@decentralchain/types
Shared TypeScript types.
@decentralchain/protobuf-schemas
Generated protobuf definitions.
@decentralchain/node-api
A typed node client.
@decentralchain/data-service-client
Client for the internal data service.
@dcc-amm/sdk
AMM helper. Reads over fetch and returns unsigned InvokeScriptTx objects.
Nothing on the published list depends on one of these at runtime, so the nineteen stand on their own. Declare your own types where @decentralchain/types would have supplied them.
Published to Maven Central under the io.decentralchain group.
io.decentralchain:java-sdk
JVM client for the chain.
io.decentralchain:transactions
Transaction building on the JVM.
io.decentralchain:curve25519
Ed25519 and Curve25519.
io.decentralchain:blst
BLS12-381 pairing.
io.decentralchain:groth16
Groth16 ZK-SNARK verification.
io.decentralchain:lang_3
The RIDE language, and lang-testkit_3 alongside it.
To read the chain you need nothing at all: the REST API answers a plain fetch. Reach for the packages when you start building transactions, at which point transactions and ts-lib-crypto are the two that matter, and bignumber the moment you handle an amount.
Next
@decentralchain on npm
The published packages, their versions and their release history.