© 2025 Cordy StackX (@cordystackx) · Licensed under the MIT License.

Install

npm install @cordystackx/cordy_minikit
# or
pnpm add @cordystackx/cordy_minikit

3.0.5 documentation

Read the complete documentation in the docs/ folder:

• Documentation index
• Environment configuration
• 3.0.5 API reference
• 3.0.0 migration guide
• Provider and wallet UI setup

Current API

import { cordy } from "@cordystackx/cordy_minikit";

const wallet = await cordy.cons_verify();
const balance = await cordy.balance();
const transfer = await cordy.transfer("1", recipient);
await cordy.cons_disconnect();

The current 3.0.5 API is:

• cordy.configure({ assets })
• cordy.cons_verify()
• cordy.cons_disconnect()
• cordy.transfer()
• cordy.balance()
• cordy.swap(amount, from, to)

cordy.cons_verify() checks whether an EVM or Stellar wallet is connected in the browser. It returns status 200 when connected and 401 when disconnected; it does not make an HTTP request or authenticate wallet ownership to your server. cordy.cons_disconnect() disconnects the wallet locally. Legacy controller helpers remain available for compatibility, but new integrations should use the cordy.* API.

Experimental API

cordy.bridge() is experimental in 3.0.5 and currently supports test USDT between BOT Chain Testnet and Ethereum Sepolia only. See the bridge API example.

cordy.swap(amount, from, to, tolerancePercent?) is available for configured EVM and Stellar assets. EVM networks need a Uniswap V2-compatible swapRouterAddress; native EVM swaps also need wrappedNativeTokenAddress. Stellar swaps use Horizon strict-send path payments and require a live liquidity path. The optional fourth argument is a percentage: 1 means 1% tolerance, and omission defaults to 1%.

Links

• NPM package
• GitHub repository
• Changelog
• Contributing guide
• Security policy