Suiball Shuts Down, Refunds Buyers in USDC
Suiball, the first hardware wallet built specifically for the Sui blockchain, is shutting down before its first shipment. The company said on Nov. 11, 2026 that the Sui Foundation decided backing a hardware wallet project was too risky after a run of hardware wallet attacks. Every pre-order will be refunded in USDC, but the process depends on how the buyer paid.
Key Takeaways:
- Suiball is refunding all pre-orders in USDC. About 80% were placed on-chain and get an automatic airdrop within a week; credit-card buyers must provide a Sui wallet address and are paid in a second round.
- The 80% is the share of orders placed on-chain; every refund is paid in full.
- Suiball says the Sui Foundation pulled support after recent hardware wallet attacks. It did not name which incidents drove the decision.
- The refund process does not require a seed phrase, private key, or another payment. Card refunds are requested only by email from
info@citadelwallet.io.
What happened
Suiball is made by Citadel Wallet and was introduced at SuiFest Singapore in October 2025. It was designed as a Sui-native device with native Bitcoin support, clear signing, and integration with Slush, Sui’s wallet app. Pre-orders were promoted at $149 against a $229 retail price.
The project did not fail at the prototype stage. Development was finished, and the device had entered manufacturing, with the first batch ready to ship, Suiball said. On Oct. 21, the founder postponed deliveries to commission additional independent security audits after talks with Mysten Labs and the Sui Network team. That delay was supposed to last several months. The Nov. 11 announcement ended the project instead.
The stated reason is a risk decision. Suiball’s announcement does not describe a breach, lost customer funds, or a compromised device. The Sui Foundation decided that the risk of backing a hardware wallet project was too high after a series of attacks on hardware wallets across the industry, according to Suiball. Suiball accepted the decision.
Why the foundation pulled back
The hardware wallet market has had a rough stretch. Each incident hit a different layer of the wallet stack: customer data, physical supply chain, firmware, and key generation.
In October, Keystone confirmed a website breach that exposed customer names, home addresses, and purchase information. Private keys and recovery phrases were not compromised, but the leaked delivery data is exactly what phishing campaigns use.
Trezor warned that a Safe 5 device bought through former reseller CryptoBilis contained a suspected implant, including an additional circuit board and a cellular component that could potentially transmit recovery phrases shown on the device. That is a physical supply-chain attack rather than a firmware bug.
Earlier in August, BitBox patched two serious vulnerabilities affecting BitBox02 and BitBox02 Nova, including a flaw that could have allowed malicious firmware installation. The company reported no known exploitation.
Coldcard’s July warning was different again: seeds generated on the Mk3 with firmware 4.0.1 or later might be at risk, and the warning landed as investigators examined a 594.48 BTC sweep worth about $38.3 million at the time. The link between the two was not definitively established, but the episode showed how a key-generation flaw can drain wallets without touching the device’s screen or buttons.
The common thread is that a hardware wallet’s security perimeter is larger than the secure element. It includes the reseller, the shipping label, the firmware update path, the seed generator, and the refund process. Suiball did not identify which incidents influenced the foundation. The reasonable reading is that backing a new consumer device looked like assuming a risk the foundation did not want to carry.
Our earlier coverage of Trezor’s shipping breach traced the same pattern: the keys can hold while the surrounding supply chain fails. The difference here is that the support decision came before the first device reached customers.
The refund terms, in plain English
All pre-orders will be refunded in USDC, Suiball said. USDC is a stablecoin designed to track the US dollar, so the refund is denominated in dollars rather than in SUI or another volatile token. You still need a wallet that can receive it.
| How you paid | Share of orders | How the refund arrives | What you need to do |
|---|---|---|---|
| On-chain | About 80% | Automatic USDC airdrop to the wallet holding the soulbound pre-order NFT, within a week | Nothing. Check that wallet. Do not share the seed phrase. |
| Credit card | About 20% | Email asks for a Sui wallet address; USDC is sent in a second airdrop round | Check the email used for the order. Reply only from a message you verify. Never send a seed phrase, private key, or more money. |
The 80% figure describes where the orders were placed: on-chain. Every refund is paid in full. The split describes the payment path: on-chain buyers are paid automatically; card buyers are paid after Suiball collects their Sui addresses.
If you ordered on-chain
On-chain buyers received a soulbound NFT when they reserved a device. A soulbound token is a non-transferable record tied to the wallet that holds it. The USDC refund will be airdropped to the wallet holding that NFT, with no claim form and no extra step, according to Suiball.
Check the wallet you used for the order. The refund should arrive there within the week after the announcement. If the NFT sits in a wallet you do not control, such as a custodial exchange, check with that platform before assuming the airdrop will be credited to you. Do not move the NFT to chase the refund unless the official instructions tell you to; the announcement says no action is required.
The absence of a claim step is also a security warning. Fake “claim your Suiball refund” sites and direct messages will appear. The official process is an automatic airdrop; a site asking you to connect a wallet and sign a transaction falls outside the process described in the announcement.
If you paid by credit card
Card buyers will receive an email asking for a Sui wallet address. Once the addresses are collected, USDC will be sent in a second airdrop round. The announcement does not give a fixed calendar date for that round; the timing depends on how quickly addresses come in.
The email is the sensitive part. The refund process does not require a seed phrase, a private key, or an additional payment. Customers should respond only to emails from info@citadelwallet.io. A Sui wallet address is public and safe to share; a seed phrase or private key is not. If the message asks for either, it is an attack, even if it looks like the company.
Use a Sui wallet you control. If you give an exchange deposit address, confirm that the exchange supports the Sui network and USDC deposits, and that it will credit an airdrop to your account. Otherwise the refund may arrive at an address the exchange does not attribute to you.
The announcement does not spell out how card processing fees, taxes, or shipping charges are handled. Check the amount against the receipt for your order. If the numbers do not match, get the answer in writing before you treat the refund as final.
Data Deletion and the Phishing Window
Customer information collected for device deliveries, including names, email addresses, phone numbers, and shipping details, will be permanently deleted after refunds are complete, Suiball said. Operations will formally cease after the refund process finishes, according to Suiball.
That promise is welcome, but the refund window is still a phishing window. Names, addresses, and order details are valuable even when keys are not exposed; the Keystone and Trezor incidents show that. Treat unexpected refund messages as hostile until you verify them against Suiball’s official account or website.
The Foundation’s Decision and the Support Layer
The foundation’s decision is easier to understand if you separate the device from the support layer around it. A hardware wallet is a small computer that keeps private keys offline. You approve each transaction on the device, so a compromised laptop cannot move funds by itself. The promise depends on the device, the firmware, the supply chain, and the company behind it. Suiball’s exit is a reminder that the last item on that list can fail before the first shipment.
The Sui Foundation’s decision concerned backing a consumer hardware product; the chain’s code is unchanged. It does show that the support layer around a wallet can be as fragile as the device. A foundation that once promoted a Sui-native wallet at SuiFest can decide the risk is no longer acceptable.
For buyers, the practical lesson is to treat the refund as a security event as well as a customer-service event. Check the right wallet or email, verify the sender, and refuse any request for a seed phrase, private key, or extra payment. The money is coming in USDC; the scammers are coming too.
Bottom line
Suiball is shutting down before its first device ships, after the Sui Foundation decided the risk of backing a hardware wallet was too high. All pre-orders are being refunded in USDC. On-chain buyers get an automatic airdrop to the wallet holding the soulbound NFT, within about a week. Credit-card buyers must wait for an email, provide a Sui wallet address, and receive a second airdrop. The 80% figure describes the on-chain share of orders; the refund amount is unchanged.
The refund process does not require a seed phrase, private key, or another payment. If you are a customer, that is the rule to remember when the first convincing fake email arrives.
Related Reading
Sources: Suiball refund announcement on X; Sui blog, “Citadel Launches Suiball, the First Sui-Native Hardware Wallet”; crypto.news, “Sui hardware wallet Suiball shuts down, announces refunds after security concerns”; PANews, “Sui Ecosystem Hardware Wallet Project Suiball Announces Closure and Refund of User Pre-Order Payments”; BleepingComputer, “Trezor warns of suspected crypto-theft implant in hardware wallet”; Sesame Disk coverage of Coldcard and Trezor.