Given a Config value, this package's main generates a CLI interface for
interacting with your instance of smart-handles.
export interface Config {
label?: string;
quiet?: true;
network?: Network;
pollingInterval?: number;
scriptCBOR: CBORHex;
scriptTarget: "Single" | "Batch";
routeDestination: Address;
advancedReclaimConfig?: AdvancedReclaimConfig;
simpleRouteConfig?: SimpleRouteConfig;
advancedRouteConfig?: AdvancedRouteConfig;
advancedRouteRequestMaker?: (
requestInfo: RequestInfo
) => Promise<Result<AdvancedRouteRequest>>;
}Sample Run of Minswap V1 Instance
The generated CLI application offers 3 endpoints:
monitorfor querying the instance's address and performing routes to collect their feessubmit-simplefor submitting a simple route request (i.e. attaching a datum that only carries owner's address)submit-advancedfor submitting an advanced route request. This requiresadvancedRouteRequestMakerto be defined in the givenConfig
1. Install this package along with smart-handles-offchain:
pnpm install \
@anastasia-labs/smart-handles-offchain \
@anastasia-labs/smart-handles-agent \
@commander-js/extra-typings # optionalMinswap V1 instance is a good reference in case you faced some issues.
-
label: An optional name for your instance of Smart Handles -
quiet: Optional flag to suppress warning logs -
network: This can be one of"Mainnet","Preprod","Preview", or"Custom"(defaults to"Mainnet") -
pollingInterval: Length of time in milliseconds between each query of instance's address for themonitorendpoint -
scriptCBOR: Hex formatted CBOR of the fully applied Smart Handles instance -
scriptTarget: Whether the providedscriptCBORis a spend script that can only allow single routes per transaction, or it's a staking script capable of supporting a batch of routes in one transaction -
routeDestination: The address where routes should go to, this is a parameter that should already be applied to your instance -
advancedReclaimConfig: If your instance supports advanced reclaims, you should provide its config (read more atsmart-handles-offchain) -
simpleRouteConfig: This config is what Smart Handles is primarily intended for, e.g. an ADA-to-MIN via Minswap instance would expect simple datums with owners' addresses, and this config would provide the application with proper logic for producing the correct UTxO at Minswap's address (this only applies to instances that do support simple routes) -
advancedRouteConfig: Similar to other two configs, depending on your instance, you might be required to provide this config -
advancedRouteRequestMaker: Thesubmit-advancedendpoint requires a few values to be provided:--lovelaceis the Lovelace count you intend to lock with your request--assetis any additional assets you want locked (can be specified multiple times)--owneroptional address to be specified as the owner--router-feeLovelace count a router agent collects for carrying out the routing--reclaim-router-feeis a sperate fee for router agents in case they invoke the advanced reclaim endpoint (instead of routing)--extra-configpath to a.jsonfile carrying any additional values your instance might need
These are all collected as a
RequestInfoand passed to youradvancedRouteRequestMaker:
export type RequestInfo = {
lovelace: bigint;
asset: Assets;
owner?: AddressDetails;
routerFee: bigint;
reclaimRouterFee: bigint;
extraConfig?: { [key: string]: any };
};This is mostly boilerplate, but can be customized:
#!/usr/bin/env node
import { main, Config, RequestInfo } from "@anastasia-labs/smart-handles-agent";
import { Command } from "@commander-js/extra-typings";
import config from "./config.js";
const program: Command = main(config);
await program
.parseAsync(process.argv)
.catch(console.log);We recommend tsup:
tsup src/index.ts --minify --format esmNote that src/index.ts is the path to the executable source you implemented in
previous step.
Use the -h or --help flag to learn more about each of the 3 endpoints
(monitor, submit-simple, and submit-advanced).
node dist/index.js --help
# or e.g.
node dist/index.js monitor --help