Where receiving addresses come from
A destination is not a signing key. Coinkun creates Litecoin receiving addresses from public key material and records who they belong to.
Start with an account and a vault
The account is the merchant workspace. Its vault identifies a currency and network context. Each generated address belongs to that vault, keeping its ownership attached to the account instead of treating it as an anonymous wallet entry.
A public keyset is the source
Account creation prepares a public keyset when the local Signer source is available. Each vault uses its own hardened branch. The keyset stores public derivation material and separate receive/change counters, not a seed phrase. Address issuance needs neither the private source nor a node. Issued coordinates and source bindings must not be reset or reused.
Derivation and observation are separate
Generating an address saves its owner; it does not import the address into Core. The confirmed-block scanner and mempool worker save receipts and spending observations for owned outputs. History displays those observations alongside outgoing Transfers. Balance reads separately verify current node evidence, and report unavailable when verification cannot complete. Scanning, reading and signing remain separate responsibilities.
Spending needs another capability
The regtest Transfer API selects and reserves account-owned inputs, fixes the approved destinations and fee limit, and asks our local Signer to sign the exact plan. The Signer verifies ownership and derives matching private keys, including the account's own change. Tests use Core with wallets disabled to verify and broadcast the result; Core does not sign it. Signed transactions are saved before broadcast so a retry can reuse the same bytes, not spend another account's funds.
Read about regtest testingYour next step starts here.
Explore the dashboard and learn the API. Check the configured network before sending funds.