arc56-generated-scholtz-biatec-vault

arc56-generated-scholtz-biatec-vault

Auto-generated typed Algorand smart-contract clients for scholtz/biatec-vault, built from the ARC-56 specs listed below.

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

Install

npm install arc56-generated-scholtz-biatec-vault @algorandfoundation/algokit-utils algosdk

Basic usage

Each contract in this package is re-exported under its own namespace (a hash of its source URL is appended 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. Generated in the client generator's minimal mode - see "Why minimal mode" below - so there is no generated deploy/create Factory.

import { AlgorandClient } from "@algorandfoundation/algokit-utils";
import { BiatecVault_5a435e12 } from "arc56-generated-scholtz-biatec-vault";

const algorand = AlgorandClient.mainNet();
const client = new BiatecVault_5a435e12.BiatecVaultClient({
  algorand,
  appId: 123456789n,
});

// call a contract method, e.g.:
// const result = await client.send.someMethod({ args: [...] });

Why minimal mode

The generator's default full mode also emits a deploy/create Factory class, but its generated code type-checks against non-exported internal shapes of @algorandfoundation/algokit-utils's AlgorandClient that have been observed to break across algokit-utils versions the generator doesn't itself pin against. minimal mode avoids that failure mode entirely, at the cost of no generated deploy helpers - acceptable for a registry whose job is decoding/calling contracts that are already deployed, not deploying new ones.

Contracts included in this package

Versioning

This package uses 1.0.<increment>.<yyyyMMddHH>-style versioning (expressed as valid semver 1.<increment>.<yyyyMMddHH>): 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.