Twine is a non-custodial desk for buying and selling CKB with local fiat. Orders, encrypted chat, and trade actions go over Nostr. The CKB moves on Fiber, between wallets you and the other person control. The naira or dollars move via GTBank or Zelle, directly from their account to yours.
Twine does not hold the fiat, and it does not hold a key that can spend the locked CKB.
Why this exists
Picture this:
Exchanges that support CKB are not permitted to operate in your country. Or an exchange randomly restricts or bans your account, trapping your funds. Or maybe you simply refuse to hand over your passport and personal data for KYC just to trade some crypto.
That is the gap Twine fills.
All you need to do is download Fiber Studio to set up a local wallet, connect to Twine, and transact over end-to-end encrypted channels.
-
“Wait, but I have zero CKB to open a Fiber channel with!”
I thought of that: Twine can open a channel toward you so the money lands in your wallet even when you start with zero CKB.
-
“What if I have issues with the buyer or seller?”
You can file a dispute and share that specific trade’s encryption key with an admin/solver. They can read your chat history, verify payment proofs, and help settle the dispute fairly.
The site, with downloads:
https://twine-web-alpha.vercel.app/
(Available for macOS, Windows, Linux, and Android. iPhone/iPad is not supported yet).
Note: This is an early prototype. Please test exclusively using testnet CKB.
What you install
Two apps. Twine is the desk. Fiber Studio is the wallet.
-
Download Twine from the site. On first launch, create a new key or import an existing
nsec, and save the secret. That key is your account. There is no username, and Twine does not keep a backup. A fresh install points at a default public desk out of the box, but you can point it at any coordinator you want. -
Install or update the latest Fiber Studio and start your node. That is where your CKB stays. Twine never pays an invoice directly and never holds a Fiber key. You handle the Fiber side inside Fiber Studio: connect to peers, open channels, pay hold invoices, and generate receive invoices.
A laptop does not need a public IP. You connect outward to the desk’s hub.
Connect Fiber Studio to the desk
In Twine, open the Account tab. It displays the desk’s Fiber pubkey and multiaddr.
In Fiber Studio:
-
Open Network, then click Add saved peer.
-
Paste the desk’s pubkey and
multiaddr. Click Add & connect.(Make sure to use those two fields directly—the default public-node buttons in Fiber Studio point to a different peer).
If you are selling:
You need active outbound channel capacity to lock the coins:
-
Open Channels, then click Open channel (make sure the hub shows Connected).
-
Set capacity to at least 1,000 CKB so you can pay the hold invoice. Keep about 109 CKB more on-chain for the channel reserve and network fees.
-
Wait until the channel status is Ready. Once confirmed, you can post your sell order.
If you are buying:
-
Stay connected to that hub with at least 99 CKB on-chain, and leave auto-accept enabled.
-
If you cannot receive yet (no inbound capacity), Twine opens a channel to you when the seller releases. Stay online through that process.
A trade
The desk that ships with the app currently takes two payment methods: GTBank (naira, bank transfer) and Zelle (dollars). You send the transfer yourself. Twine only stores the method’s name. Account numbers and banking details are not published on the open listing—they are shared privately in the encrypted trade chat.
-
Post: A seller lists CKB: a price, how much is for sale, a minimum and maximum limit, and a payment method.
-
Take: A buyer picks that listing and an amount inside the limits, names their Fiber node, and pastes a Fiber invoice from the wallet that should receive the CKB. The secret/preimage behind that invoice stays strictly on the buyer’s node.
-
Lock: Twine shows the seller a hold invoice for that same secret. The seller pays it from Fiber Studio. After this step, cancellation is locked out.
-
Pay: The seller sends their bank details in the encrypted chat. The buyer pays outside Twine, uploads the receipt screenshot to the chat, and marks the fiat as sent. The coordinator cannot read that thread.
-
Release: The seller checks their bank account, confirms the money arrived, and clicks Release. Twine pays the buyer’s invoice. That payment reveals the secret and settles the hold invoice. The buyer receives the CKB.
(Only one active trade runs on a listing at a time).
If it goes wrong
-
The seller has 1 hour to lock funds. If they do not, the listing is freed up for others.
-
Once the coins are locked, the buyer has 15 minutes to pay and mark it sent. If they do not, do not release. Fiber automatically returns the CKB to the seller’s channel when the timelock expires.
-
The hold lasts 36 hours. A release has to start at least 30 minutes before it ends. A dispute does not pause this clock.
-
Either person can open a dispute while coins are locked when the desk has a solver configured. Sharing the chat key lets the solver read the thread. The seller can still release during a dispute. The solver can pay the buyer or let the hold expire and return the CKB to the seller.
-
If the CKB payout cannot reach the buyer, the hold stays locked. The buyer generates a replacement invoice with the same payment hash/secret, and Twine retries the payout.
Twine can finish the lock only by paying the buyer first. It does not know the secret before then.
Current prototype limitations
-
The UI/UX is very bad, i was focused on making it work first then fine tune later, so bear with me
-
This software currently charges no trading fees, tracks no user ratings, and requires no security bonds yet. Nothing in it checks bank APIs. The seller verifies their own account directly, and the receipt is simply an image uploaded to the chat.
-
Also, the automated dispute resolution UI is not fully implemented yet in this client build. So if someone goes rogue and refuses to pay or release during this testnet phase, they get to keep your fake money and your test tokens too (lol). A full solver interface is coming next.
-
with many other features and fixes yet to come
Code & background
The deep architectural dive is documented in the earlier Talk thread:
Twine: Buy and Sell CKB Without Depositing on an Exchange (Fiber P2P PoC)
The coordinator is open source, so anyone can run a desk. Both parties on a trade use the same one:
-
Coordinator: github.com/chukwuma619/twine
Testing & feedback
If you try it, I want the blunt, unfiltered version:
-
Did Fiber Studio connect to the hub without hiccups?
-
Did the channel open cleanly?
-
Did the fiat and trade steps make sense?
-
What broke, lagged, or felt confusing?