One moment.
Opening the next page.
How Limbo works
Understand where the money goes, who can sign, and how you keep control of your keys.
Limbo brings listings, payments, delivery and disputes into one place. BTC, LTC and SOL marketplace funds lock on the blockchain in a two-of-three escrow.
A purchase stays connected to its payment, delivery and resolution. Your order page is the place to follow it.
Review the listing, seller, delivery method and price. Serial keys, presets and services have different delivery paths.
Sign in with a passkey, Discord or your account password. Verify your email, set up authenticator 2FA, and save your separate wallet password and recovery key.
Checkout saves your encrypted order key first, then shows the exact crypto amount and the order’s unique escrow address.
Limbo checks blockchain receipts. Partial or unconfirmed payments do not release goods or complete your order.
Automatic items are handed over after confirmation and processing. Sellers deliver services and mark them delivered.
Confirm when the purchase is right. If something is wrong, open a dispute before the confirmation window ends.
Sellers need a verified email, a linked Discord account and 2FA to publish. Prepare your signing wallet and payout address, create the listing, and submit it for approval. Hosted checkout, storefronts and embeds all keep the order attached to its seller.
BTC, LTC and SOL purchases are secured in the order’s escrow. Spending requires any two of three signatures: buyer, seller and platform.
For a cooperative release, the seller authorizes the payout and the buyer confirms receipt. An eligible automatic release combines the seller’s stored authorization with the platform’s signature. A dispute resolution combines the eligible party’s signature with the platform’s.
The platform’s single key cannot spend the escrow alone. Your signing keys are encrypted in your wallet and unlocked on your device.
Solana uses independent signing keys inside the same wallet. You send SOL and receive SOL; wrapping is handled automatically. New SOL orders first fund an address controlled by your encrypted wallet. You then authorize setup and move the purchase into escrow. Checkout marks it secured after finalized verification.
This illustration moves no money. Real signatures authorize a specific transaction, with its own inputs, recipients and amounts.
The blockchain holds the escrow payment. Limbo coordinates the signed transaction that completes the order or its authorized refund.
The order records the commission, fee payer and destinations before payment. The final transaction includes the seller’s payout, any platform commission and its network fee.
Checkout shows the crypto amount, commission and fee payer before payment. The seller’s plan can affect commission. The order records the applicable rules and payout/refund destinations.
Blockchain transactions need network fees. BTC/LTC fees can affect the final payout or refund. New SOL orders are funded by the buyer, including account setup and a transaction-fee reserve. The normal settlement calculation retains recovered account rent for Limbo, including on a purchase refund. Unused fee reserves and overpayments return to the buyer. These mechanics do not limit mandatory refund rights. Older orders keep their recorded rules.
A broadcast transaction is sent to the network. A confirmed transaction is included in a block. Limbo keeps its transaction record so retries reconcile the same payout instead of paying twice.
Send the amount and chain shown on the invoice. A partial, late or unusual payment needs reconciliation; it does not unlock goods simply because coins reached an address.
A six-digit authenticator code helps verify account access. Accepted codes cannot be reused for the same time step. Saved sign-in recovery codes are single-use.
Passkeys work for sign-in and security confirmation. An encryption-capable passkey can also unlock your wallet locally. Your wallet password, passkey secret, recovery key and decrypted signing keys stay on your device.
The wallet locks when you sign out, switch accounts, leave the page or stop using it for 15 minutes. Brief tab switches keep it available. A purchase, receipt or refund still requires an explicit signing action.
Your wallet password uses Argon2id; compatible passkeys supply a local WebAuthn PRF secret. HKDF-SHA256 and AES-GCM protect the wallet and signing keys with account, vault and key-purpose binding. Server verification checks the passkey’s origin, signature, user verification and one-use session challenge.
“End-to-end” here describes the protection of private signing keys. It does not make the entire marketplace invisible to its operator.
A compromised unlocked device or malicious browser-delivered code can expose keys. Keep your device, passkey account and recovery material protected. Removing a passkey cannot erase a private key that someone already copied.
Sign in on another device and unlock the same wallet with your wallet password or a compatible passkey. The encrypted key for that exact order is retrieved by its immutable public key, so its signing identity stays the same.
A passkey provider is optional. Your wallet password works across devices, and your recovery key is a separate backup. Providers without encryption support can still be added; use your wallet password to unlock.
Wallet recovery also needs retained encrypted vault and order-key records. A password or email reset does not reconstruct those keys, and the platform cannot replace missing private signing material.
If something is wrong, describe it on the order and open a dispute before its confirmation window ends. The claim is recorded before wallet access is requested, so losing access to a passkey cannot stop you reporting an issue.
The support/disputes team reviews the record and the parties’ statements. An authorized resolution can return funds to the buyer or pay the seller, using the relevant party’s signing authorization and the platform’s signature.
A recorded dispute pauses an eligible automatic release. It cannot recall a transaction already broadcast. There is no unilateral timed refund in the current BTC/LTC script, and a refund still requires usable signing material.
Read the refund policyMemberships and listing promotions buy services from Limbo. Their direct crypto payment addresses use a separate platform-service rail, rather than a buyer/seller two-of-three marketplace escrow.
Those payments can activate a plan or promotion after confirmation. They do not change the signing rules for a marketplace order, and their terms and refund conditions are separate.
SOL and EVM payment availability depends on their deployment checks. EVM uses a separate wallet and contract flow; new v3 contracts require two approvals. Real-money rails stay closed until activation.
Read the platform termsKnow which key, code or signature you need before an order reaches its next step.
Use a registered passkey to sign in and confirm security changes. Connect it to your existing wallet in Security for local unlocking when your provider supports encryption. Other passkeys still work for account access; use your wallet password or recovery key to decrypt. Your account password, Discord and enabled two-factor protection remain available.
No. New BTC, LTC and SOL marketplace escrows require two of their three signing keys. Limbo has the platform key, while buyer and seller keys belong to their encrypted wallets. New EVM contracts likewise require two recorded approvals. An approved arbitration adds Limbo’s approval to a party’s authorization; older contracts keep their original rules.
They have separate jobs. Authenticator codes and single-use sign-in recovery codes protect account access. They cannot decrypt your wallet. Your separate wallet password, a compatible passkey or your independent wallet recovery key unlocks signing keys on your device.
Use a saved sign-in recovery code if you lose the authenticator. For wallet access, use your wallet password, a compatible passkey or your saved wallet recovery key. Wallet recovery also needs the encrypted vault and order-key records. If you lose every unlock method, account support cannot recreate your private keys.
Yes. Sign in and unlock with your wallet password or recovery key without needing a passkey provider. Compatible passkeys offer quick unlocking. The wallet retains its signing identity and retrieves the encrypted key for the exact order. Providers without encryption support can still register a passkey; use your wallet password to decrypt.
The current BTC/LTC escrow has no unilateral timed refund. A dispute records the claim and pauses an eligible automatic release. Refunding still needs valid signing material and an authorized resolution. The buyer’s confirmation deadline is shown on the order. An eligible delivered order with no dispute may release using the seller’s stored authorization and the platform’s signature.
Older signing keys keep their original identity. Import an existing key with its original escrow password; Limbo verifies that the derived public key matches the older order or seller identity. New web checkouts generate random order keys inside the encrypted wallet, so you do not set a separate escrow password for each purchase.
Review a listing, prepare your account and wallet, and keep the order page close throughout the deal.