Frequently asked questions

Create accounts and addresses, read verified balances and History, send regtest Transfers and configure receipt Callbacks. There are 17 implemented methods under /api/v1. Public keys come from the local Signer. A separately enabled confirmed-block scanner and mempool worker save receipts and spending observations; payment and callback workers continue their durable queues. Invoices and automated forwarding remain planned.

No. This release is a local regtest development environment. Regtest coins are test coins; they do not represent mainnet Litecoin. Do not give these addresses to paying customers.

The current creation flow does not ask for an email address or a password. It returns a public Account ID and a one-time Transfer Key. There is no email-based key recovery in this version.

The Account ID identifies the account and can be remembered by the dashboard. The Transfer Key is a secret credential used to unlock protected actions. Never put the key in a public page, widget, screenshot or support message.

The raw key is displayed once when the account is created. The application stores a digest, not a readable copy of that key. Keep a secure backup; there is no self-service recovery feature in the current release.

The dashboard remembers up to 20 public Account IDs in this browser's localStorage. This is a convenience list, not authentication. Removing an ID from the browser does not delete the account in the database.

Protected access lasts up to 10 minutes after unlocking in the current implementation. Locking the dashboard clears that access. The browser's saved Account ID list is independent of this authorization.

Yes. A receiving address belongs to a vault owned by an account. Address derivation uses the public keyset attached to that vault; it does not ask the node to create an unrelated wallet address.

No. A receiving address can be shared to request a payment. Spending requires the corresponding private keys or an authorized signer. Knowing an address or an extended public key is not sufficient to sign a transfer.

Not by itself. Derivation saves the address and its owner without calling the node. Our separate scanners read blocks and mempool and match outputs to saved addresses. Redis and a Sidekiq worker must be running with both scanners enabled; Rails server alone does not scan. History reads saved observations, not a live spendable balance.

Pending means seen in the local mempool without a recorded block. Not seen means absent at the last complete local check, not cancelled. Recorded means observed in a block, not proof that outputs remain unspent. Orphaned preserves evidence from a replaced block and does not prove cancellation. History also includes outgoing Transfers and their payment details. The separate balance reader can return unavailable when source evidence or processing limits prevent verification. The reviewed capacity and recovery defects have been corrected; finite processing budgets remain, and local tests are not production certification.

No. The current working network is Litecoin regtest. Other currency icons and documentation describe intended interfaces, not active production network support.

Use /api/v1. Public examples use https://coinkun.com/api/v1 as the intended base URL; local tests use your local Rails server. The documentation marks implemented and planned endpoints separately.

Not yet. The public builders are design previews with disabled payment controls. Their copyable markup is explicitly a preview, not a working payment integration. They do not send API requests or collect customer details.

Commercial Coinkun prices have not been published. Local regtest quotes expose the blockchain network fee; the current processing fee is zero. That test behavior is not a commercial tariff. The pricing page explains these separate costs.

There are no released Coinkun plugin or SDK packages in this branch. Use the API documentation and local testing guide for now. The resources page links to the tools that actually exist.