Skip to main content

arc56-generated-fulls_40d31135

Auto-generated typed Algorand smart-contract clients for fullstackferris/algorand-python-workshop, built from the ARC-56 specs listed below.

Generated by the Arc56Registry pipeline, using the algorandfoundation/algokit-client-generator-py ARC-56 client generator. Do not edit these files by hand — they are regenerated automatically whenever the source ARC-56 spec changes.

Install

pip install arc56-generated-fulls_40d31135

Basic usage

Each contract in this package is a separate module (a hash of its source URL is appended to its filename to keep multiple contracts in the same repository from colliding), containing a typed <Name>Client for interacting with an already-deployed instance of that contract, plus a <Name>Factory for deploying new instances.

from algokit_utils import AlgorandClient
from arc56_generated_fulls_40d31135 import PersonalBank_8563dea6

algorand = AlgorandClient.mainnet()
client = PersonalBank_8563dea6.PersonalBankClient(
    algorand=algorand,
    app_id=123456789,
)

# call a contract method, e.g.:
# result = client.send.some_method(args=(...))

full vs minimal generator mode

Contracts in this package are generated with the client generator's full mode by default, which emits both the typed Client and a deploy/create Factory class plus deployment metadata (source code, bytecode, template variables). For the rare contract whose full-mode output fails to generate or fails to byte-compile, this package falls back to minimal mode (Client only, no Factory) for that contract instead of failing outright. The contracts table below flags any contract generated this way; every other contract includes a working Factory.

Contracts included in this package

Module Client class Source ARC-56 spec
PersonalBank_8563dea6 PersonalBankClient https://raw.githubusercontent.com/fullstackferris/algorand-python-workshop/HEAD/projects/algorand-python-workshop/smart_contracts/artifacts/personal_bank/PersonalBank.arc56.json

Versioning

This package uses 1.<increment>.<yyyyMMddHH>-style versioning: a new version is published whenever any of the contracts above change, or whenever the client generator itself is updated. See Arc56Registry for the full generation pipeline and source ARC-56 registry.

Metadata

Release files for arc56-generated-fulls-40d31135 1.2.2026072010

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for arc56-generated-fulls-40d31135 1.2.2026072010
File Size Uploaded Provenance
arc56_generated_fulls_40d31135-1.2.2026072010.tar.gz 7.4 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for arc56-generated-fulls-40d31135 1.2.2026072010
File Interpreter ABI Platform
arc56_generated_fulls_40d31135-1.2.2026072010-py3-none-any.whl Python 3 none any Details

Total release size: 14.7 kB

Release files / arc56_generated_fulls_40d31135-1.2.2026072010.tar.gz

Download URL arc56_generated_fulls_40d31135-1.2.2026072010.tar.gz
Size 7.4 kB
Tags Source
SHA-256 checksum
How to use checksums
07216320236587cfee9d18b31699e77a320a9fdacf4bb3b9fcc878ddbec0f2a6
BLAKE2b-256 checksum
How to use checksums
ffc3984d5b5ccb194208be096618b1224ac4d1a100c7d599593927fd8b43e346
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.12.15

Release files / arc56_generated_fulls_40d31135-1.2.2026072010-py3-none-any.whl

Download URL arc56_generated_fulls_40d31135-1.2.2026072010-py3-none-any.whl
Size 7.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
b62fc54dce71accacf5e5056bcf6f3a27cd7d376fab0c5603e8803a73e76d214
BLAKE2b-256 checksum
How to use checksums
4b5ce4a0771daddf751e4df19735d15bc1d7cd89c1a1835186f34913b5a53562
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.12.15

Security for arc56-generated-fulls-40d31135 1.2.2026072010

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.

Release history Release notifications | RSS feed

This release
Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page