Mapping of ASA name to deployment log
Checks if checkpoint is deleted for a particular transaction if checkpoint exists and is marked as deleted, throw error(except for opt-out transactions), else pass
Transaction execution parameters
Optional
scTmplParams: types.SCParamsCreates and deploys ASA defined in asa.yaml.
ASA name - deployer will search for the ASA in the /assets/asa.yaml file
deployment flags. Required.
flags.creator
must be defined - it's an account which will sign the constructed transaction.
NOTE: support for rekeyed accounts is limited (creator must have updated sk to properly sign
transaction)
Optional
asaParams: Partial<{ Creates and deploys ASA without using asa.yaml.
ASA name
ASA definitions
deployment flags
flags.creator
must be defined - it's an account which will sign the constructed transaction.
NOTE: support for rekeyed accounts is limited (creator must have updated sk to properly sign
transaction)
Optional
clawback?: stringOptional
defaultOptional
freeze?: stringOptional
manager?: stringOptional
metadataOptional
name?: stringOptional
note?: stringOptional
noteb64?: stringOptional
optOptional
reserve?: stringOptional
unitOptional
url?: stringDeploys stateful smart contract.
is the signer of the transaction.
is an object providing details about approval and clear program.
clear program filename (must be present in assets folder)
AppDeploymentFlags
Transaction Parameters
Smart contract template parameters (used only when compiling PyTEAL to TEAL)
name of the app to deploy. This name (if passed) will be used as the checkpoint "key", and app information will be stored agaisnt this name
Optional
scTmplParams: types.SCParamsOptional
appName: stringExecute single transaction or group of transactions (atomic transaction)
executes ExecParams
or Transaction
Object, SDK Transaction object passed to this function
will be signed and sent to network. User can use SDK functions to create transactions.
Note: If passing transaction object a signer/s must be provided.
Check out https://algobuilder.dev/guide/execute-transaction.html#execute-transaction|execute-transaction
for more info.
transaction parameters or atomic transaction parameters https://github.com/scale-it/algo-builder/blob/docs/docs/guide/execute-transaction.md or TransactionAndSign object(SDK transaction object and signer parameters)
This function will send Algos to ASC account in "Contract Mode".
name of the smart signature (passed by user during mkContractLsig/mkDelegatedLsig)
Deployments flags (as per SPEC)
as per SPEC
Funds logic signature account (Contract Account). @fileName: filename with a Smart Signature code (must be present in the assets folder)
Transaction Parameters
Smart contract template parameters (used only when compiling PyTEAL to TEAL)
Optional
scTmplParams: types.SCParamsOptional
asaParams: Partial<{ Optional
clawback?: stringOptional
defaultOptional
freeze?: stringOptional
manager?: stringOptional
metadataOptional
name?: stringOptional
note?: stringOptional
noteb64?: stringOptional
optOptional
reserve?: stringOptional
unitOptional
url?: stringQueries blockchain using algodv2 for asset information by index
Queries metadata key in all checkpoint files of current network. If the key is not defined
in any checkpoint then undefined
is returned. Can be run in both run and deploy mode.
Loads logic signature info(contract or delegated) from checkpoint (by lsig name)
name of the smart signture (defined by user during mkContractLsig/mkDelegatedLsig)
Return receipts for each transaction in group txn
confirmed tx info of group
list transaction in group
Returns true if ASA or DelegatedLsig or SSC were deployed in any script. Checks even for checkpoints which are out of scope from the execution session and are not obtainable using get methods.
Allows user to know whether a script is running in a deploy
or run
mode.
Loads deployed asset definition from checkpoint. NOTE: This function returns "deployed" ASADef, as immutable properties of asaDef could be updated during tx execution (eg. update asset clawback)
ASA name - name of ASA in the /assets/asa.yaml file
Loads contract mode logic signature (TEAL or PyTEAL)
Smart Contract filename (must be present in assets folder)
Smart contract template parameters (used only when compiling PyTEAL to TEAL)
Extracts multi signed logic signature file from assets/
.
Create an entry in a script log (stored in artifacts/scripts/
Stores logic signature info in checkpoint for contract mode
name of lsig (checkpoint info will be stored against this name)
ASC file name
: Smart contract template parameters (used only when compiling PyTEAL to TEAL)
Makes delegated logic signature signed by the signer
.
name of smart signature (checkpoint info will be stored against this name)
Smart Signature filename (must be present in assets folder)
Signer Account which will sign the smart contract
Smart contract template parameters (used only when compiling PyTEAL to TEAL)
Creates an opt-in transaction for given ASA name, which must be defined in
/assets/asa.yaml
file. The opt-in transaction is signed by the account secret key
Creates an opt-in transaction for given ASA name, which must be defined in
/assets/asa.yaml
file. The opt-in transaction is signed by the logic signature
Opt-In to stateful smart contract (SSC) for a contract account The opt-in transaction is signed by the logic signature
application index
Transaction flags
Optional parameters to SSC (accounts, args..)
Send signed transaction to network and wait for confirmation
TxnReceipt which includes confirmed txn response along with txID
Signed Transaction(s)
Update programs(approval, clear) for a stateful smart contract.
name of the app to deploy. This name (if passed) will be used as the checkpoint "key", and app information will be stored agaisnt this name
Account from which call needs to be made
Transaction Flags
ID of the application being configured or empty if creating
Optional parameters to SSC (accounts, args..)
Optional
scTmplParams: types.SCParamsQueries blockchain for a given transaction and waits until it will be processed.
Generated using TypeDoc
Sets metadata key value for a current network in the chckpoint file based on the current deployment script. If run in a non deployment mode (eg
algob run script_name.js
) it will throw an exception.