ɪ ᴛʀɪᴇᴅ ᴛᴏ ʙᴜʏ $5 ᴡᴏʀᴛʜ ᴏꜰ ᴛᴏᴋᴇɴɪᴢᴇᴅ ᴀᴘᴘʟᴇ ꜱᴛᴏᴄᴋ ᴏɴ ꜱᴘᴏᴜᴛ ꜰɪɴᴀɴᴄᴇ.
I had $20 test USDC and enough devnet SOL for gas—but the transaction still could not proceed.
That failed transaction exposed the biggest lesson from my Spout Finance beta test:
The financial model is compelling, but the onboarding, risk disclosures and mobile UX need serious work before a wider launch.
Here is my complete teardown of
@SpoutFi 🧵—except this is intentionally one detailed post.
𝗪𝗛𝗔𝗧 𝗜𝗦 𝗦𝗣𝗢𝗨𝗧?
Spout is building a Solana-based brokerage for buying tokenized equities and borrowing stablecoins against them at 0% interest.
The core proposition is simple:
• Buy eligible tokenized US equities
• Use those equities as collateral
• Borrow up to 50% of their value in USDC
• Keep exposure to the underlying position
• Pay no recurring interest
The beta currently supports trading and equity-backed borrowing, while its Earn/lending vault product is still marked “Coming Soon.”
I tested the mobile beta on Android using:
• $20 externally funded test USDC
• Devnet SOL for transaction fees
• Beta version v1.0.0
• A newly connected Solana wallet
Here is what happened.
𝗧𝗛𝗘 𝗢𝗡𝗕𝗢𝗔𝗥𝗗𝗜𝗡𝗚 𝗘𝗫𝗣𝗘𝗥𝗜𝗘𝗡𝗖𝗘
Spout provides direct links to external Circle and Solana faucets.
Getting test USDC was straightforward, but obtaining devnet SOL was difficult. The official faucet rejected my GitHub account because it was too new, and the app offered no alternative funding method or gas sponsorship.
I eventually obtained SOL elsewhere, but then encountered a second blocker: KYC.
My profile showed:
“Verification pending — no identity on-chain yet.”
However, I had never started a verification process.
There was no:
• Start Verification button
• Resume Verification button
• KYC-provider link
• Explanation of the required documents
• Estimated verification time
• Supported-country information
• Human support escalation
Attempting to trade produced an identity/KYC restriction, making the transaction impossible to complete.
This is a critical onboarding flaw. The app correctly enforces token-level compliance, but it gives users no path to become compliant.
Worse, “Pending” is inaccurate if the user has never submitted anything. The appropriate status should be “Not Started,” accompanied by a clear verification CTA.
𝗧𝗛𝗘 𝗦𝗨𝗣𝗣𝗢𝗥𝗧 𝗘𝗫𝗣𝗘𝗥𝗜𝗘𝗡𝗖𝗘
The in-app “Ask Spout” chatbot repeatedly failed to understand basic support questions.
When asked how to obtain devnet SOL after the faucet rejected my GitHub account, it returned a list of supported assets.
When asked how to start KYC, it explained why KYC was required but did not explain how to complete it.
When asked how to contact a human agent, it returned wallet-connection instructions.
This creates a dead end precisely when users need help most.
The chatbot needs better intent recognition, direct links to relevant actions and an obvious “Contact Human Support” escalation route.
𝗧𝗥𝗔𝗗𝗜𝗡𝗚 𝗨𝗫
The trade interface is visually clean, and searching for supported assets is straightforward. Asset pages provide charts, time ranges and clear Buy/Sell actions.
However, several issues appeared during testing:
1. The leverage control did not work
After entering both $5 and $10 purchase amounts, the leverage selector remained at 1.0x.
Dragging the slider and tapping 1.25x, 1.5x or 2.0x did nothing.
There was no disabled state or explanation telling me whether leverage was unavailable because of KYC, minimum order size, asset eligibility or another requirement.
2. The order summary is confusing
The preview combines “Amount / Stocks borrowed” into one field, even though transaction value and borrowed shares are different concepts.
These should be separated into:
• Cash contributed
• Total exposure
• Shares purchased
• Amount financed
• Resulting debt
• Effective LTV
• Estimated liquidation price