alberta-buck-core
The Python side of the Alberta Buck platform: one testing API over every EVM backend, with expectation checking and journaling.
Web3Session-- the ChainSession API. Send, call and deploy against anvil, a public testnet, or in-process pyrevm with the same code. Every state-changing operation declares whether it is expected to succeed or revert, so expectation mismatches are first-class results rather than surprises.- Journal -- an append-only JSONL record of every operation: tag, op, sender, expectation, outcome, gas, tx hash, block, error. Journals are auditable, diffable across backends and across languages (the JavaScript platform writes the same schema), and replayable.
load_artifact-- contract artifacts from a repo checkout'sout/when there is one, falling back to the installedalberta-buck-contractsotherwise, so an installed package can deploy a world with no checkout.
Install
pip install alberta-buck-core
The distribution is prefixed; the import is not:
from buck_core import Web3Session, Expect, load_artifact
The compiled kernels are optional
buck_core.buck_math, buck_core.buck_identity, buck_core.buck_wallet
and buck_core.buck_registry are shims that delegate to
alberta-buck-kernel when
it is installed (pip install alberta-buck-core[kernel] brings it along,
where a wheel exists). This package is deliberately a pure-Python wheel: keeping
the binaries out means depending on the session API does not drag a
per-platform wheel matrix behind it.
In a repo checkout the built .so sits beside the shim and CPython prefers
the extension, so a freshly rebuilt kernel takes effect immediately.
Status
0.2.0, prototype. Unaudited software for a monetary system, published so the simulation and identity work can be reproduced and built on.
Licence
CAL-1.0 (Cryptographic Autonomy License v1.0). Beyond the usual copyleft, CAL requires that anyone you provide this software's functionality to receives their own data and is not locked out of it by cryptographic or technical means. See LICENSING.md.
Repository: https://github.com/alberta-buck/alberta-buck
Release files for alberta-buck-core 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| alberta_buck_core-0.2.0.tar.gz | 18.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| alberta_buck_core-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 30.1 kB
Release files / alberta_buck_core-0.2.0.tar.gz
| Download URL | alberta_buck_core-0.2.0.tar.gz |
|---|---|
| Size | 18.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
15f32b4a6b83f551610c5e9817a6198772cb8c6fc667ff64c514a42b9a71c8ea
|
|
BLAKE2b-256 checksum How to use checksums |
0682bee0f4447b404ff0617f81fd25d2f31fa9551526ea788fa62258adb6f5b2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 25, 2026.
Transparency logRelease files / alberta_buck_core-0.2.0-py3-none-any.whl
| Download URL | alberta_buck_core-0.2.0-py3-none-any.whl |
|---|---|
| Size | 11.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
75be95a0fed1e5d1b755130437e7f2c444a6e6226fb4d55ed1df1cb3b4ede1a9
|
|
BLAKE2b-256 checksum How to use checksums |
c33209321bb79e88c017393fe1b60a6d404a87223df12ec06d2d8b89651b4ba3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 25, 2026.
Transparency log