xion-types
Auto-generated, multi-language client types for the XION blockchain. Regenerated on every xion release — do not edit generated files; improve the tooling instead.
Languages
| Language | Output | Published as |
|---|---|---|
| TypeScript | ts/ |
npm @burnt-labs/xion-types |
| Python | python/ |
PyPI xion-types |
| Rust | rust/ |
crates.io xion-types |
| Ruby | ruby/ |
RubyGems xion_types |
| Kotlin | kotlin/ |
Maven Central io.github.burnt-labs:xion-types-kotlin |
| Swift | swift/ |
CocoaPods XionTypes |
| C, C++, C#, Java, Objective-C, PHP, Scala | <lang>/ |
— (generated, unpublished) |
Proto-derived reference docs are generated into docs/.
Proto sources
Sources are pulled from BSR at generation time — no git submodules required. Configured in scripts/proto-sources.conf:
github.com/cosmos/ibc-apps(packet-forward-middleware, git)buf.build/cosmos/ibcbuf.build/cosmwasm/wasmdbuf.build/cosmos/cosmos-sdkbuf.build/burnt-labs/abstractaccountbuf.build/burnt-labs/tokenfactorybuf.build/burnt-labs/xion(pinnable viaBSR_MODULE/XION_BSR_MODULE)
Xion contracts (TypeScript client types only) are fetched from burnt-labs/contracts at release time.
How releases happen
xion release published
└─▶ release.yaml generate all languages in parallel, open PR, enable auto-merge
└─▶ auto-tag.yaml on merge: cut v0.<xion_major>.<patch>-<xion_short>-<contracts_short>
└─▶ publish.yaml fan out to publish-{ts,python,rust,ruby,kotlin,swift}.yaml
See .github/workflows/README.md for the full workflow reference and tag scheme.
Regenerating locally
Requires Docker (builds a pinned proto-builder image). No Go or language toolchains needed on the host.
# One language, specific xion version
make proto-gen-ts BSR_MODULE=buf.build/burnt-labs/xion:v29.0.0
# Any language: c, cpp, csharp, docs, java, kotlin, objc, php, python, ruby, rust, scala, swift, ts
make proto-gen-python
Without Docker, ./scripts/proto-gen-ext.sh <lang> works too, but requires buf and each language's plugins on $PATH.
TypeScript usage
See ts/USAGE.md for import rules, the cosmjs bigint-compatibility split, and integration with xion.js.
Metadata
Release files for xion-types 0.1.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| xion_types-0.1.2.tar.gz | 179.6 kB | Without provenance | Details for xion_types-0.1.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| xion_types-0.1.2-py3-none-any.whl | Python 3 | none | any | Details for xion_types-0.1.2-py3-none-any.whl |
Total release size: 566.8 kB
Release files / xion_types-0.1.2.tar.gz
| Download URL | xion_types-0.1.2.tar.gz |
|---|---|
| Size | 179.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d95d0fcc419d71c37fb6a7a78c8e1b64e0459d76827b89be05967118763485d7
|
|
BLAKE2b-256 checksum How to use checksums |
46ad400684e56ead912c2d7c0a4c88cfb16e3a8f9a388d3d736dbe0bbc58dfb0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Release files / xion_types-0.1.2-py3-none-any.whl
| Download URL | xion_types-0.1.2-py3-none-any.whl |
|---|---|
| Size | 387.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ac09d104d79a5484bc0d75e78a70d9558ce526bce2a44ac1c062b156f527ea1d
|
|
BLAKE2b-256 checksum How to use checksums |
9a108963bbd318e3eccdbf1b07a19a9ad9b17e57ff30a177b9cfd6a1b00094dc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Security for xion-types 0.1.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.