Transaction templates

Cardano template library: cut & paste CLI commands, with forms for data they require

The Frankenwallet is designed to anyone can use it exactly how they want, but we're offering here some procedures that have worked for some of the most repetitive, sensitive, and error-prone operations in Cardano.  Please feel free to suggest any new templates, or changes to these templates, here.

➤ Currently we haven't tested any operations for token minting or smart contract creation, but look forward to doing so soon.  If anyone feels like coding these or other operations as templates

If you've skipped to this section without reading the general Usage of the Frankenwallet, please have a look on how and why we divide the information in this section into templates (procedures which are constant) and data (which is assembled every time the template is used):

Usage > Transaction templates & data

➤ Note some of the data & template may need to be modified under certain conditions... e.g. if you're trying to take funds out of an address which is split into multiple UTxO's, and the template only has one argument for --tx-in.

We trust that users will be able to adapt to this... since the main purpose of the Frankenwallet documentation is to illustrate the air-gapped environment rather than provide complete coverage for every task that might be run on it (in every blockchain besides Cardano as well).

To Cardano Stake Pool Operators (SPOs): if you've never used any of the open source, third-party stake pool management scripts, you still won't have to if you follow these examples.  All the operations in this section are composed of "raw" cardano-cli commands and derive from the examples in the official Cardano documentation (Operate a Stake Pool).

Disclaimer: You are solely responsible for whatever happens when you copy & paste these commands anywhere, as well as whatever happens when you run the transactions that are generated.

In any case it should be a pleasure for the discriminating Cardano user, developer, smart contract designer, token minter, or stake pool operator to see the CLI commands before they very deliberately run them… which they should do only after deliberately reviewing them to certify that what they are doing is both complete and safe.

Last updated: