- v0.1.1-beta.1Latest
- v0.1.1-beta.0
- v0.1.0-gamma.1
- v0.1.0-gamma.0
- v0.1.0-beta.49
- v0.1.0-beta.48
- v0.1.0-beta.47
- v0.1.0-beta.46
- v0.1.0-beta.45
- v0.1.0-beta.42
- v0.1.0-beta.41
- v0.1.0-beta.40
- v0.1.0-beta.39
- v0.1.0-beta.38
- v0.1.0-beta.37
- v0.1.0-beta.36
- v0.1.0-beta.35
- v0.1.0-beta.34
- v0.1.0-beta.33
- v0.1.0-beta.32
- v0.1.0-beta.31
- v0.1.0-beta.30
- v0.1.0-beta.29
- v0.1.0-beta.28
- v0.1.0-beta.27
- v0.1.0-beta.26
- v0.1.0-beta.25
- v0.1.0-beta.24
- v0.1.0-beta.23
- v0.1.0-beta.22
- v0.1.0-beta.21
- v0.1.0-beta.20
- v0.1.0-beta.19
- v0.1.0-beta.18
- v0.1.0-beta.17
- v0.1.0-beta.16
- v0.1.0-beta.15
- v0.1.0-beta.14
- v0.1.0-beta.13
- v0.1.0-beta.12
- v0.1.0-beta.11
- v0.1.0-beta.10
- v0.1.0-beta.9
- v0.1.0-beta.8
- v0.1.0-beta.7
- v0.1.0-beta.6
- v0.1.0-beta.5
- v0.1.0-beta.4
- v0.1.0-beta.2
- v0.1.0-beta.1
Capi
Capi is a work in progress. The documentation may not reflect the current implementation. Expect a stable release and proper documentation in early 2023.
Capi is a declarative, TypeScript-first toolkit for crafting interactions with Substrate-based chains. It consists of FRAME utilities and a high-level functional effect system and standard library, which facilitate multistep, multichain interactions without compromising either performance or safety.
- Documentation →
Materials for learning about Capi - Examples →
SHOW ME THE CODE - API Reference →
A generated API reference, based on type signatures and in-source comments.
At a Glance
Generate chain-specific bindings.
deno run -A -r https://deno.land/x/capi/codegen.ts \
--src="wss://rpc.polkadot.io" \
--out="polkadot"
… or use the Node equivalent––
npx capi
–with the same arguments.
Make use of those bindings.
import * as C from "capi";
import { system } from "./polkadot/frame.ts";
// bind to the last inserted key
const key = system.account.keys.first;
// bind to the corresponding value
const value = C.run(system.account.get(key));
The Thesis
In a likely future of specialized, interoperable chains, developers will need to make use of on-chain programs to satisfy varying use cases; the expertise required to interact with these on-chain programs is currently greater than that which should be expected of app developers. Does this mean that app developers must forgo integrating with this blossoming infrastructure? We think not; the open source community can use Capi to abstract over the atomics of the on-chain world. An interaction spanning several chains and dozens of methods can be described with a single effect.
As you read through this documentation, please consider use cases over which you might like to abstract; if you wish to add your use case to Capi’s standard library, please submit an issue.
Code of Conduct
Everyone interacting in this repo is expected to follow the code of conduct.
Contributing
Contributions are welcome and appreciated! Check out the contributing guide before you dive in.
License
Capi is Apache licensed.