UX

Typical-Snow3034

Hey. CoinRabbit team here. The payment itself is often the shortest part of the process. Most of the friction happens before checkout. A user first has to find a merchant that accepts the asset, confirm the supported network, make sure the balance is in the correct wallet and understand whether the merchant receives crypto directly or through a processor. Then there are fees, exchange rates, refunds and the fact that an incorrect blockchain transfer may be irreversible. At CoinRabbit, we approach merchant discovery and wallet UX as parts of the same flow. The wallet allows users to store, exchange, send and spend assets through one account, while our Spend Crypto directory identifies companies that accept Bitcoin, Ethereum, stablecoins and other digital assets. Reducing the number of separate apps helps, but truly simple crypto payments also require merchants to present the accepted asset, network, final amount and refund terms clearly before the user confirms anything.

Upset-Guard383827

Exactly. The real breakthrough will be when users stop caring that the payment is powered by crypto. If I can tap, pay, and move on without thinking about wallets, chains, swaps or gas fees, that's when crypto has actually won the UX battle.

aliyamin267

Address formats, network switching, and gas fee estimates are still huge UX friction.

sciencetaco

If you actively use the wallet for sending transactions, then upgrading might be nice since beer wallets offer better UX and stuff. But if your plan is to just hold, then it’s not worth upgrading. Just keep your seed words safe.

gore_master_48

If you suspect a genuine UX issue or edge case in the Coldcard Mk

xGsGt

I mean you can choose not to roll a dice a use passphrase or use a multisig, there are other options, I have never roll dices and I'm not going to, wallets UX and security are going to get better after this, wallets having security issues has happen all the time the only difference right now it's that it happen to a Bitcoin only cold wallet

Imp-Classic17

It's only natural for them to try and capture more users by offering better products. I also find it very convenient that I can trade both crypto and stocks, all in one place, and using a familiar UX, rather than creating a tradfi account somewhere. I don't like the fact that these are taking volume away from crypto, but it is what it is

Sufficient_Fuel5269

People don’t pay with crypto because it complicates life: taxes, volatility and weak UX. A perfect crypto card would have to feel the same as a Visa, but without friction or scares.

No_Alternative_8373

I don't think crypto payments have a technology problem anymore—they have a UX problem. If sending crypto becomes as easy as sending a text message, adoption will grow much faster. Platforms like Handle Pay are moving in that direction, which is great to see.

didactic_artistry_lo

UX is the silent killer, the second I have to hunt for a basic function I'm out.

Odd-Improvement-316

A lot of the 'crypto payments are pointless' takes come from people who've only ever lived somewhere with good banking. I've spent a lot of time in Central Asia and parts of the Middle East, and there the pain is real: carrying physical USD across borders because cards barely work, or watching the local currency lose value every month. A stablecoin on your phone genuinely beats that. In the US or EU tap-to-pay already works, so of course it feels like a solution looking for a problem. The tech isn't really the blocker, it's that the people who'd benefit most aren't the ones the UX gets built for.

Gkwzjsz

Crypto needs better/simpler UX generally.

MadSL1m

The friction you're describing is the thing the industry already gave up on solving. Merchant acceptance never really arrived, so the payment layer that works is still the old one. Of the 138 live crypto cards I track, 137 run on Visa or Mastercard. That's the whole trick. No address to fumble, no app switching, and 115 of them sit in Apple Pay. The merchant just sees a normal card. What it doesn't fix is the fee, it hides it better. The cost moves into the conversion spread at the till, and most issuers keep that off the pricing page. In the US there's a second catch: every swipe is technically a sale of crypto, so paying with ETH logs a gain on a coffee. Funding with stablecoins keeps that near zero. So the blocker isn't wallet UX. It's that nobody accepts crypto, and cards are the workaround everyone quietly settled for. Fee and custody breakdown is on my own site: [sweepbase.net/cards](http://sweepbase.net/cards)

Dave_1030

I think it's the UX. Most people don't want to think about networks, gas fees, or wallet addresses—they just want to pay. Crypto won't feel mainstream until all that complexity is hidden.

No_Cartographer1492

this is a problem at the level of the wallet, the wallet should flag any address that is a lookalike of another to prevent the user from copying an address from the previous transaction (something users should not do anyway). This is a UX problem.

dm8try

First impression from Liana’s team, online presence, the product is very complimentary and soothing as opposed to the trauma received from Nunchuk. Yet, I don’t like their desktop app UX much, I liked Nunchuk’s desktop app more. Hope Liana improves it in the future. Sparrow would be the wallet of my choice if they supported Miniscript, but they don’t. Miniscript is by far the best latest innovation in Bitcoin, with all those great features like time locks, decaying multisig (e.g 2-out-of-3 and 1-out-of-3 after an inactivity period, in case 2 out of 3 signers are lost or inaccessible) or expanding multisig (e.g. 2-out-of-2 initially and 2-out-of-3 after an inactivity period, adding a recovery key, which prevents from one key being lost). Simple inheritance is supported in a free version of the service but I ve got to look into that yety. Liana has custodians as partners in certain jurisdictions (Europe, Singapore and UAE, if I’m not wrong) that could provide paid support and inheritance services.

ZookeepergameOld6699

Future tech only can solve dilemma between self custody or financial sovereignty and UX problem. Self custody is hard because of our natural tendency to laziness and human blind spots. Setting up a multisig wallet and obeying by best practices, easy to say but hard to do.

Potential_Balance223

A post in 2022 - "Coincard MK4 UX Flaw" described this exact scenario. Posted by Economy_Cash6726

pako-bitbox

No offense taken at all, it is actually a pretty good and fair question. And yes, I might know a thing or two, that's why I've been tasked with helping people out on Reddit :P (Really, I'm talking from a company related account, competitors to Coldcard, way smaller than Trezor, too bad this is the situation we are in, would have loved to interact with more people under different circumstances). I think you might be referring the Model One, which didn't have a Secure Element, that's why the pin could be cracked with some voltage manipulation. Secure elements are standard in the industry by now, no HWW manufacturer would dare launching a device without one unless their UX gets incredibly hampered by it, and in such case the best practice would be to let users know, but AFAIK, no single competitor is launching devices without one, and the ones who don't have a physical one have a virtual one. The secure element is a complete separe part of the device and Trezor's libraries have been battle tested, peer reviewed, audited and actively attacked multiple times, yet they still stand the test of time.

ChicksX

I agree it’s probably both. Better UX can bring more people in, but hiding all the complexity can also create new risks if users don’t understand what they’re giving up. The challenge is making crypto simple without making people unaware.

Potential_Balance223

The post was titled Coldcard MK4 UX flaw in 2022.

Typical-Snow3034

Hey. CoinRabbit team here. It probably has to be both: simpler technology and enough education to understand the consequences of using it. A user should not need to understand every technical detail, but they still need to know whether they control the keys, whether a transaction is reversible, which network is being used and who can help if access is lost. CoinRabbit reduces part of that complexity through a custodial, account-based wallet. Users do not have to manage private keys or a recovery phrase, and access can be restored if a device or credentials are lost. That makes onboarding and recovery simpler, but it also transfers custody responsibility to the provider. Good UX should make that trade-off clear before a user deposits anything, rather than hiding it behind an easy interface.

IInsulince

I think you’re out of touch with the average person’s attention span and interest in such things. Trying to explain this stuff to people who don’t understand bitcoin at all will make their eyes glaze over. It’s not realistic to expect them to go to these lengths with the current state of Bitcoin UX. Over time, maybe that will change. As we safely and securely abstract away the friction points, maybe grandma will be inclined to roll the dice. I just have trouble envisioning how we get to such a point, and expect it to take a long time to get there, with many more painful and egregious missteps like this one along the way. But today? Absolutely no shot the average person will do not what you say. It’s hard enough as-is to get people who do understand bitcoin to do these things.

indolering

> From this, we would expect that wallet manufacturers will be hyper-vigilant about their entropy code I've ground some meat in my time and it's **absurd** how hard this sort of thing is *even when you are hyper-vigilant*. The field just hasn't caught up to the point that it's financially feasible to implement formal methods or pay for end-to-end certification. > users will (hopefully) use things like passphrases, dice-roll, and multi-sig.   As much as I want that to be true, I'm a UX engineer who has worked in crypto and it's not that simple.  Every additional unit of labor and skill decreases the usability of self-custody. I know soooooooooooooooo many people that forget or fat finger passwords, including myself. > This is almost certainly a one-time event RNG failures happen ALL the time across the industry.  It's really complex to implement well and difficult to test. > And the blame lies solely with ColdCard, not with the way Bitcoin works. It's unfortunate, but nothing more. If you want to sell your Bitcoin because of that, no one is stopping you, but I don't think it's a logical conclusion to come to in this case. I invest using an ETF, that way the bank is on-the-hook for security failures.

MMinjin

Because they don't care about the ideals of Bitcoin anymore. All of those people made their money and left. Who is left? Get rich quick folks and gamblers. Why do you think the network no longer sees any improvements? Why devices all suck? Why the UX has never been improved? Because the people who care have already left. All that's left is the grifters and griftees. Very disappointing.

grraarr

Fair enough, I haven't used Jade, but I think any wallet with native dice roll will have this UX.

Exorcisme

Yes and no, a guy I know got drained for $3M+ (different case) after which hacker lost everything by interacting with a fake UX the same day.

bitusher

The problem is they might not be. Thus this is more of a systemic issue where large amounts in self custody should always be recommended to use either an extended passphrase(easiest solution to setup and recover) , SSS, or multisig. This IMHO is too much of a stumbling block for future mainstream adoption. There are plenty of solutions being developed like Vaults and using miniscript and better UX to address this but its not mature yet

Crypto-Guide

Depending on the firmware and model is may have been another example of the flawed UX in coldcard letting you create a low entropy deterministic seed. I did a video on this a few years back https://youtu.be/oj_W3xOlt6U The funds are not recoverable, I'm sorry for your loss.

ginete_tech

You're right that shared infra doesn't automatically solve user acquisition. A frontend still has to earn its users. But it does change the market maker side significantly. Right now a market maker has to decide which of 500 venues to provide liquidity on, and each one is a separate integration, separate risk, separate capital commitment. Most just pick the top 2-3 and ignore the rest, which is why everything below the leaders has garbage liquidity. If the matching and liquidity layer is shared, a market maker quotes once and every frontend on that infrastructure inherits the depth. That lowers the barrier enormously. The frontend still competes on UX and community, but it's not starting from an empty book. On whether crypto liquidity ever becomes less fragmented, I think it has to eventually. Fragmentation is a phase, not an endpoint. Every maturing market consolidates its liquidity layer over time. Traditional equities went through the same thing before settling into shared clearing and settlement infrastructure.

master-beast-72

Cross-chain liquidity fragmentation is one of the most underappreciated UX problems in DeFi right now. When the same token trades at slightly different prices on 13 different chains, arbitrageurs capture that spread rather than end users benefiting from unified depth. What "Aqua" is attempting is essentially a virtual liquidity layer — instead of bridging assets first and then swapping, you aggregate quoted rates from all 13 chains simultaneously and route the execution to wherever the fill is cheapest. The user sees one quote, one transaction. The technical challenge is latency + finality. Getting quotes from 13 chains fast enough for the price to still be accurate when the user confirms requires either intent-based architecture (solvers commit to fill at a stated price, absorbing the timing risk themselves) or very tight oracle synchronization. Intent-based is the cleaner model and it's what UniswapX uses too. The 13-chain coverage is interesting — that's broad enough to capture most real liquidity but narrow enough to maintain quality control on the solver network. Protocols that tried to go too broad too fast (some cross-chain bridges) ended up with thin solver coverage and bad fills on the tail chains. Worth watching whether they use canonical bridges for settlement or their own smart contract layer. The former is safer but slower; the latter is faster but adds smart contract risk.

TalkWithSaeed

I think it's a mix of poor UX, regulation, and incentives. Most people still see crypto as an investment, not money to spend. Until paying with crypto is as easy as tapping a card, mainstream adoption will stay limited.

Excellent-Advice-948

For USDT → native BTC without a centralized exchange, the cleanest answer is THORChain — it does native cross-chain swaps, so you get real BTC on the Bitcoin network, not a wrapped IOU. Access it through a front-end (THORSwap, ASGARDEX, Rango, etc.), connect a wallet, and swap USDT (on whichever chain you hold it) straight to native BTC at your own BTC address. Other genuinely non-custodial routes: - Bisq — decentralized P2P, no accounts, runs over Tor. Very non-custodial, but liquidity and UX are clunkier and it's slower. - RoboSats — P2P over Lightning, good for smaller amounts if you want zero middleman. One important distinction, since you specifically said native BTC: don't just buy wrapped BTC (WBTC and the various chain-specific wrapped versions) if what you actually want is coins on the Bitcoin blockchain. Wrapped BTC is a token on another chain backed by a custodian/bridge — it carries that counterparty and bridge risk and isn't the same as holding real BTC. THORChain settling to a native BTC address avoids that. Practical cautions: - Watch slippage/liquidity, especially on a large amount — check you're getting an execution price close to spot before confirming, and consider splitting a big swap into a few. - Triple-check the destination is your own BTC address, and do a small test swap first if it's meaningful money. - These routes are non-custodial by design, so there's no support desk if you fat-finger something — go slow. THORChain is the direct answer to your exact ask; Bisq/RoboSats if you want to lean even harder toward pure P2P.

ChangeNOW_Community

There's still a big market for all things non-custodial, take wallets for example: great UX in 2026, great infrastructure with in app swaps, the more people onboard the better, yet the question about adoption remains, people aren't willing to remember 12 words, same as trading decentralized assets on CEXs

TheCryptoJourno

Been using Kraken for years. Can’t complain, clean UX, decent range of tools and markets and the support team is helpful if something does go awry

Routine-Surprise-601

This checklist is good, but I'd flag that "secure your seed phrase somewhere safe and offline" is where most beginners actually get hurt. In practice new users photograph the words, paste them into a notes app, or type them into a phishing site pretending to be wallet support. The seed phrase model is elegant cryptography with brutal UX. Disclosure: I'm on the support team of Ballet, a cold wallet brand. If you go the standard hardware wallet route: write the words by hand, never digitize them, and consider a metal backup for fire/water. Buy the device directly from the manufacturer, never Amazon third-party sellers or eBay. There are also seedless approaches now — including physical card wallets like ours, where the key is generated in two independent factors so no single party (including the manufacturer) ever holds a complete key, and there's no phrase to memorize or leak. Tradeoff is you're trusting the manufacturing process rather than your own ceremony, so pick whichever failure mode you'd rather own. Either way, the commenter's core sequence is right: buy, learn, move off the exchange, hold. The learning step matters more than the gear.

AutoModerator

Post is by: ScknSrp and the url/text [ ](https://goo.gl/GP6ppk)is: /r/CryptoMarkets/comments/1uxi9uw/i_got_so_sick_of_twitter_gurus_deleting_their_bad/ Hey everyone, I’ve been in crypto for a while and the "I told you so" culture on Twitter and Telegram is driving me crazy. These "analysts" post 10 different predictions, delete the 8 that failed, and then hype up the 2 that hit to sell their VIP groups. There’s zero accountability. So, I decided to build a platform to put an end to this: Schrod.io. How it works: You lock in a prediction (e.g., "BTC goes up in 1 hour"). Once the timer hits zero, a Supabase Edge Function automatically pulls the exact price from Binance API and resolves it as success or failure. You can't delete it, you can't edit it. Your profile gets a weighted accuracy score, and you climb the leaderboard based on actual performance, not hype. Why I'm posting here: It's 100% free to use. I’m a solo developer with zero marketing budget. I just want to know if this actually solves a pain point for you guys, or if there's anything I should change. Go ahead, check it out, try to break it, and give me your honest feedback (or just roast my UI/UX, I can take it). Link: [schrod.io](http://schrod.io) *I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/CryptoMarkets) if you have any questions or concerns.*

Klutzy-Sea-4857

Cross-chain is necessary, but calling it THE missing piece is a stretch. The missing piece is UX that does not make normal people want to throw their laptop out the window. Bridges keep getting exploited for hundreds of millions, and that is not a small concern. The tech will mature, but we are not there yet.

counterboy12

Ethereum has become a victim of its own success. What was supposed to be the world’s decentralized computer now often feels like a maze of Layer 2s, bridges, wrapped assets, and confusing UX that punishes ordinary users. Instead of fixing its scaling problems at the base layer, Ethereum increasingly expects users to stitch together a patchwork of rollups and networks just to achieve reasonable fees. Flow takes the opposite approach: it prioritizes simplicity, predictable performance, and an experience that doesn’t require a PhD in blockchain infrastructure to send a transaction. Ethereum may dominate in TVL and developer activity, but for many users it has become an ecosystem where complexity is treated as a feature rather than a flaw. If a blockchain needs an entire stack of additional networks just to be practical for everyday use, it’s fair to question whether the base layer is truly delivering on its original promise**.**

nopara73

This was my main philosophical project for the past decade and I talked about it and improved upon it in many places before, so excuse me if I'm a bit too dogmatic here. I derive everything from my custom interpretation of the properties of good money: [Durability, portability, divisibility, scarcity, acceptability and fungibility](https://nopara73.medium.com/why-bitcoin-f67d56bf48f2). I treat these as a [developer’s specification for improving Bitcoin](https://www.youtube.com/watch?v=-BayL7sBEU0&t=6182s), with the unfinished work concentrated around fungibility and portability: privacy, cost and speed, with Lightning playing a central role. From that follows the [implementation vision](https://nopara73.medium.com/quest-for-the-perfect-bitcoin-wallet-c03e7d065d0): security, privacy, trustlessness, open source, accessibility, stability and sustainability; every language and every relevant platform; desktop and mobile; Windows, macOS, Linux, Android and iOS; hardware wallets, full nodes, Tor and Lightning; usable privacy by default; and APIs and tooling through which other developers and businesses can extend the system. I later summarized the practical expansion path as [localization, mobile and other platforms, native hardware-wallet CoinJoin, developer tooling and private Lightning integration](https://www.youtube.com/watch?v=dZg7YvoC60M&t=4805s). I'd also like to point out the importance of UX here. The standard is much higher than the normal non-custodial bitcoin wallet user is used to. It must be seamless and everything must be in the background. I cannot emphasize how much harder this makes the job, but it's necessary if we want anonymous uninflatable money to dominate the world. At least that's my end goal. The only thing that changed is AI came about which brings new platforms to target those are unclear at this point what they'll be and it comes with some serious privacy complications as well. On the bright side AI makes it 100x easier to create the software so no need for billions anymore.

counterboy12

Layer 2s fragment liquidity, can censor/delay your transactions and have horrible UX. It was always regarded as a short term workaround, not the solution. ETH and its monolithic chain architecture is rotten from the core, only a multi node chain can fix this

pc1e0

UX was great, now it's even better! Works on Android Chrome browser. Continue in background button shows after 5-10 seconds and I can view and start mining immediately after. Thanks for keeping up the good work!

NoBrosCrypto

As others have said, it does require a level of understanding of what you’re doing and the various different chains and protocols. Sending something via the wrong network will lead to immediate loss of funds. Having said that, Dapps and wallets could do a much better job of improving UX and UI to better protect users. Something as simple as reducing the available network options for selection based on the coin or token you’re trying to move is simple and basic, yet some applications still don’t do this. Things are improving over time but we still have a long way to go!

ChicksX

This is the real UX problem. Most people won’t feel safe using a system where one confusing approval can drain everything. Wallets need clearer warnings, spending limits by default, and easier separation between long-term funds and DeFi wallets. Until then, serious funds should stay in wallets that never connect to random apps.

Quickprepper

I have used Debridge a lot mainly bec of the UX but man like you said they don't really show the actual fees we pay, it's very difficult to check how much we paying for a bridge. I need to go back and check now.

nonkeywayzee

These things are being solved proactively. All of these solutions are centralized, but what actually matter is trust minimization. Both Ark servers are equally as centralized a the SSP. Unilateral exit is possible, just not part of the SDK. Arks don't necessarily require a monthly fee, all they need is for you to refresh, but the fee is up to the provider. I believe that Spark offers a way better set of trade-off just because of how good the UX is, but this is what we have. The good thing is that nobody stops anyone else from building something with the UX of Spark and the trust assumptions of Ark.

nonkeywayzee

\> But from a UX point of view it needs to be on par with current banking Dude you are going to love Spark and both Ark implementations.

SpikeyOps

We can make bitcoin frictionless, then it’ll win thanks to its monetary properties. But from a UX point of view it needs to be on par with current banking, which in many cases is currently superior in terms of experience and friction 15 years ago it was ahead. That’s the sad part. Centralised systems can improve their UX faster.

Dramatic_Cow_2656

Ok but what do I do with a lightning QR code? Can I send bitcoin to it or do I need to get myself a custodied lightning channel and make sure there’s liquidity and rebalance after ? Lightning is a UX mess

CODE_HEIST

lean ethereum is interesting because complexity is one of the quiet adoption costs. users never see the protocol internals, but every extra moving part eventually shows up as fragility, fees, or weird UX at the app layer.

Spirited-Box-2802

Hmmm, if the assumption is that complexity is the biggest barrier then a simpler UX/UI definitely helps. I don't think it is the biggest barrier though. Information is already incredibly accessible. YouTube, X, Discord, Reddit, newsletters, it's everywhere. The challenge isn't finding information to learn from, it's knowing which information deserves your attention and UX can reduce friction, but it can't replace credibility. At the end of the day, everyone learns from someone, whether directly or indirectly so knowing who to learn from is the biggest challenge in my opinion, fix trust before fixing an interface.

Niceguy955

Because what we need is another stable coin... We already have USDC, USDG, PYUSD, RLUSD, and tons more (skipping USDT here, as institutions avoid Tether like the plague due to their, shall we say, iffy corporation and financials). Instead of unification we get more market fracture. And we'll need more pools to convert the stables we already use to new ones. These companies should concentrate on making the experience easier for lay people, solving the onboarding/offboarding challenges, solving the wallet UX, making it easy to pay with stables - not launch a new one every month.

AutoModerator

Post is by: ApplicationNew4144 and the url/text [ ](https://goo.gl/GP6ppk)is: /r/CryptoMarkets/comments/1uhbhco/cross_margin_is_how_a_15_btc_wick_cost_me_the/ I got liquidated on June 4 even though my biggest position was a BTC long at 3x. Not because BTC moved too much, but because I had SOL and AVAX perps open on the same account and cross margin meant they all shared one collateral pool. When the wick hit, alts dumped harder than BTC, and the combined drawdown pulled the whole account below maintenance. The BTC position on its own would have survived easily. A 3x long does not liquidate on a 15% move. That is the part that still annoys me. Cross margin felt safer on paper because unused margin backs every position, but what it really does is let your weakest trade kill the rest. I started checking how different platforms handle the isolated vs cross choice. Some make you dig through settings before you can switch. BYDFi makes you pick isolated or cross per position before confirming the order. It is one extra click but it would have kept my BTC walled off from the alt liquidation. Not saying that platform is special, just that the UX choice is the kind of guardrail I wish I had hit. Now I open everything isolated with individual stops. If one trade blows up it takes only that collateral. Cross still makes sense if you are hedging the same pair or running a tight arb, but I will not run a portfolio of volatile alts on shared margin again. Learned it the expensive way. *I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/CryptoMarkets) if you have any questions or concerns.*

pc1e0

What I like about this cryptocurrency experiment the most is the simplicity of its UI/UX. No need to install Metamask, no need to download mining software, no need to go through KYC on CEX.

TheBitSignal

I’m tired and have a newborn. Honest mistake. While I did read it, the app UX was not the best trying to post. This was also my first ever post, so sorry for my mistake.

Sure-Benefit2023

I think the main issues are volatility, UX, taxes, and consumer protection. For normal people, paying with crypto is usually more complicated than using a card or bank app. On top of that, price swings make it awkward as a daily currency, and tax treatment can make small payments annoying. Crypto is useful in some specific cases, but “common day-to-day currency” needs boring reliability, simple recovery, low friction, and clear rules. We are not really there yet.

cryptodizzle67

Fair enough, I was thinking about someone who has never seen an exchange, so a good UX / UI would help them out with some good information / customer service.

coolfarmer

It's really just a UI/UX issue. I use a Ledger wallet, so I never see those transactions or spam tokens anyway, I only pay attention to my own holdings. They're far easier to ignore than phone scammers who keep leaving voicemails. My voicemail box only holds 3 messages, so I end up having to delete them every day....

-Baloo

Well honestly a lot of the blame lies on the core developers and incentive structure. If it was cheap and easy to use, people would use it.. but it isn't.. it's too complex and awkward for most people to engage with. Seed phrases they need to keep secure, on ramps, tax obligations etc.. The whole UI/UX experience needs to be seamless and smooth, it has to be ***better*** than what Visa or Mastercard offer - else why would consumers switch? In parts of SE Asia they already have blockchain integrated into the banking systems, and you just pay by scanning a QR code with your phone and it settles cross chain inter bank within seconds. It needs to be like that.. users shouldn't need to adapt to BTC, crypto should adapt to consumer behaviour. And yes - from a business perspective crypto rails are actually much better to use today, you get settled almost immediately. But the issue is that consumers aren't interested because the whole onboarding process is a nightmare (which does also come down to governments and existing financial players gatekeeping).

Organic_Horse88

I think it’s a mix of all of these, but the good thing is each layer is improving over time. Wallet UX is getting simpler, fees are coming down on newer networks, and merchant adoption is slowly growing too

Miltank12345

Not only centralized, but they fragment liquidity, have a horrible UX and often come with secrutiy threats due it's bridge. Layer 2s are TRASH. (And Bitcoin with it's Proof of Work Concept is Trash too)

SpendHefty6066

People are building wallets that do these with a much easier UX. Right now the protocol is still very "techy". Some may remember getting online pre web, and not AOL. Similar vibe. We are still in the "what can the Internet do that fax doesn't?" stage of Bitcoin adoption.

hyperbiznes

\[Warning\] MEXC's matching engine vs. manual orders: a cautionary tale about UI/UX traps and forced liquidations https://preview.redd.it/34dry0ja387h1.jpeg?width=1179&format=pjpg&auto=webp&s=4033770e96649ddaad476e02d59bae932226d192 I want to share a technical breakdown of my recent experience with MEXC. This isn't just about a lost position; it’s about a fundamental issue in how the platform's UI interacts with their liquidation engine. The Situation: I held a Long position on ESPORTS/USDT. As the price approached the liquidation threshold, I attempted to exit the position manually using market orders. The Timeline (UTC+2):  13:52:37: 1st attempt to close (Rejected: "Price close to liquidation")  13:52:41: 2nd attempt to close (Rejected: "Price close to liquidation")  13:52:45: 3rd attempt to close (Rejected: "Price close to liquidation")  13:52:46: Forced liquidation by the system. The Technical Issue: After escalating the case with support, they confirmed that my manual orders were rejected because the market price was below the liquidation threshold. Why this is a trap for traders: 1. UI Misleading: The platform's interface allowed me to place market orders, creating the illusion that manual control was still possible, even though the backend engine had already effectively locked the position. 2. Liquidation Priority: The system ignored 3 manual exit attempts over a 10-second window, prioritizing the liquidation engine over user input. 3. "Fair Price" Logic: Support claims this is a "protective measure." My argument is that if an order cannot be executed due to system constraints, the UI should prevent the order from being placed in the first place, rather than allowing users to "waste" precious seconds trying to exit. The Official Response: MEXC support explicitly stated that the cancellation of orders was not a platform anomaly but a "protective measure" during volatility. They refused any compensation, effectively admitting that their UI allows interactions that the engine has already blocked. Key Takeaway: If you trade on MEXC, be aware that during high volatility, their interface may lead you to believe you can still close a position when the engine has already decided to liquidate you. Your manual exit attempts are secondary to their liquidation engine. I’m sharing this so others don't get trapped by the same system behavior.

Ge_Yo

UX is probably one of the biggest barriers to adoption. A lot of these ideas only matter if normal people can actually use them without needing to be experts. The more seamless Bitcoin-based services become, the more interesting the long-term picture gets. TBVs are a good example of that, since accessibility can be just as important as the use case itself.

Blackiris-Code

The things is, ETH and SOL already have solutions for quantum security. Afaik the devs are now trying to figure out the optimal balance between impact on network performance and smoothness of the transition (compatibility with old protocols notably). But it is not a priority at all. It's very unlikely that we start to see a shadow of a real threat within the next 5 years. Improving the UX and increasing adoption is much more urgent because being the first on a market gives a huge advantage. So refining existing protocols, developing dApps, finding TradFi partners... those things are put before optimizing quantum security implementation. But it will happen in time for sure. So for the networks that already have quantum security, the question is: What is their advantage compared to other major chains that already figured out a solution? If a network can't bring something more than quantum security I'm 99% sure that it will disappear in a bear market in the 2040s. I will be shorting the coins of those networks very aggressively.

Equivalent_Menu_1096

Hyperliquid getting that kind of mainstream recognition is wild but honestly not surprising. Their perp DEX UX is genuinely better than most CEXs I've used, which is rare in DeFi. Still, these lists always feel like paid placement or hype timing—curious if anyone here actually uses their platform regularly or if it's just the *idea* of it that’s getting the nod. The real test will be how they handle a major drawdown event, not just a bull run.

osem23

Thank you, this is a very fair and useful read of the model. Yes, the key idea is exactly that: the native-language layer is display/input only, while the English BIP39 mnemonic remains the canonical seed input to PBKDF2. The goal is to improve comprehension without adding a new cryptographic path. I agree that the main risk is UX confusion. A wallet implementing this must make the distinction very clear: the native words help the user understand and enter the backup, but the English BIP39 phrase is the portable fallback for recovery in standard wallets. On wordlist quality, I agree as well. Even though these are not standalone BIP39 replacement lists, confusion risk still matters. Near-homophones, spelling ambiguity, diacritics, regional meanings, and memory collisions all need language-level review. That is part of why the project is public. The native-speaker review point is also valid. Some languages are already reviewed more deeply than others, but broader review is needed before treating every list as equally mature. And I agree on the adoption path. A reference library is probably the right next step, especially something wallet developers can integrate without maintaining the mappings themselves. Appreciate the thoughtful feedback. This is the kind of criticism that is actually useful for making the project safer and easier to implement.

whatwilly0ubuild

The approach is sound. Display-layer translation with English as the canonical seed input to PBKDF2 means you're not introducing new cryptographic surface area. The index-pairing keeps the mapping deterministic and reversible. A few considerations from the implementation and adoption side: The UX risk is users not understanding the distinction. If someone backs up their native-language phrase and later imports it into a wallet that only accepts English BIP-39, they may think their funds are lost. The display layer needs extremely clear messaging that the English phrase is the portable standard and the native display is wallet-specific. Documentation alone won't prevent this confusion at scale. Wordlist quality matters more than it seems. BIP-39's English wordlist was carefully constructed to avoid similar words, minimize prefix collisions (first 4 characters are unique), and exclude offensive terms. Do your translated lists maintain similar properties? A wordlist where two words differ by only a diacritical mark, or where words are near-homophones, creates backup error risk that doesn't exist in English. The 31 languages without native-speaker review is a liability. Machine translation or non-fluent selection can produce words with unintended meanings, regional ambiguity, or cultural problems. The request for native-speaker corrections is the right call, but wallets adopting this before thorough review would be taking on risk. Adoption path is the harder problem. This only helps users if wallets implement it. Most wallet developers won't add 31 language mappings for a feature that serves UX rather than functionality. A reference implementation as a library (JS, Rust) that wallets can drop in would lower the barrier significantly.

M4cHiin360

Damn so fiat with extra step and worse UX. Generational tech

osem23

I understand your position, but you are still criticizing a different model. I am not saying the English BIP39 wordlist is more authoritative than the other BIP39 wordlists. I am saying that in this implementation, English is the chosen compatibility base layer. That is an engineering and UX decision, not a claim that English is “better” or more valid than Spanish, Korean, Japanese, or any other canonical BIP39 list. If a wallet creates a Spanish BIP39 wallet from the start, then the Spanish BIP39 mnemonic is the source of truth for that wallet. Same for Korean, Japanese, French, etc. But this project is addressing a different case: A wallet that intentionally uses English BIP39 as its portable recovery base, while giving non-English users a native-language display/input layer so they can understand what they are backing up. Creating new canonical BIP39 wordlists for additional languages is a valid path, but it is not the same problem. A new canonical BIP39 wordlist creates an independent mnemonic system for that language. This project creates a semantic layer over an English BIP39 mnemonic, so the user can understand the backup while still keeping the standard English recovery fallback. Those are different goals. You are arguing that native users should use native canonical BIP39 lists where they exist, and I agree. But that does not invalidate an application-layer model where a wallet chooses English BIP39 for portability and adds native-language comprehension on top. So the distinction is simple: Canonical native BIP39 wordlists are for creating native BIP39 mnemonics. This project is for displaying and entering native-language meanings over an English BIP39 recovery base. That is the model.

osem23

That is the intended model. The user is not locked into the native-language display words. They can recover in the native language inside a wallet that supports this display/input layer, and they can also recover with the canonical English BIP39 words in any standard wallet that supports English BIP39. That is the base layer. The native-language words exist to help the user understand and enter the backup in their own language. But the recovery source of truth remains the canonical English mnemonic, and the English words are always the portability fallback. So nothing is “lost” if another wallet does not support the native display layer. The user still has the English BIP39 backup path. That is the point of the model: native-language UX for understanding, English BIP39 for universal recovery compatibility.

osem23

Yes, that is closer to the intended use case. This is primarily a UX and comprehension layer for wallet software, not a proposal to replace BIP39 wordlists or create a new independent seed standard. The user can still have the English BIP39 words as the universal recovery fallback. The native-language layer helps them understand what they are backing up, instead of copying foreign words blindly. A true additional BIP39 wordlist for each language would also be valuable, but that is a different goal and a much higher standardization process. This project is focused on a more practical layer: keep English BIP39 compatibility underneath, while making backup and recovery clearer for non-English users inside wallets that choose to support it.

osem23

Specific language feedback is welcome, and that is why the lists are public. A lot of work was done to reduce issues across each language as much as possible, but no multilingual UX layer is perfect without broad native-speaker review. The important point is that this does not put the backup at risk. The recovery source of truth remains the canonical English BIP39 mnemonic. The native words are a display/input layer, not a replacement seed standard. So yes, individual words can be reviewed and improved. But that does not invalidate the model or make the recovery path unsafe.

osem23

You are mixing two different things. The recovery path has not changed. The underlying recovery path is still the standard English BIP39 mnemonic. The native-language words are only a translation/display layer that maps back to the same canonical English BIP39 words before recovery. A user can back up in the native language for understanding, or back up the English BIP39 words directly. The English words remain available as the universal recovery fallback and can be restored in any standard wallet that supports English BIP39. So this is not “enter a non-standard mnemonic into a non-standard wallet” as the only recovery path. The model is: Native language for user understanding English BIP39 for universal wallet recovery Translation layer only No change to seed generation No change to PBKDF2 input No change to the actual recovery path You can disagree with the UX choice, but saying the recovery path was replaced is misleading. The whole point is to preserve the English BIP39 recovery path while making the backup understandable to users who do not speak English.

osem23

I think we are talking about two different goals. If a wallet is creating a new Spanish BIP39 wallet from scratch, then yes, the canonical Spanish BIP39 list is the right tool. But this project is not trying to create standalone Spanish BIP39 mnemonics. It is a display/input layer for wallets that intentionally keep English BIP39 as the compatibility and recovery source of truth. In that model, the native words are aliases for the English BIP39 words, not a separate mnemonic to hash. Your counterproposal also requires special wallet logic. The wallet must know not to hash the Spanish mnemonic normally, but to decode it to entropy, re-encode that entropy as English, and then hash the English mnemonic. So both models require explicit wallet behavior. The difference is UX: Your model shows a standard Spanish BIP39 mnemonic that does not semantically match the English words the wallet ultimately needs. This model shows native-language meanings that map directly to the English BIP39 words, while keeping the English mnemonic available as the recovery fallback. I am not saying this replaces canonical native BIP39 lists. It solves a different problem: making an English-BIP39-based wallet understandable for non-English users without changing its recovery path.

osem23

I understand the question, but this is exactly the issue I am trying to point out. I am not saying English is morally or linguistically superior to the other BIP39 wordlists. The reason English is used as the source of truth in this model is because the existing non-English BIP39 lists are not translations of the English list, and they are not semantically aligned with each other by index. They are independent wordlists. That means the word at index N in Spanish, Korean, Japanese, French, etc. usually does not mean the same thing as the English word at index N. So for a normal user, this creates a strange UX problem: If their wallet shows an English mnemonic and then tries to “show it in Spanish” using the canonical Spanish BIP39 list, it cannot do that. The canonical Spanish word at the same index is not the Spanish meaning of the English word. It is a different word that happens to occupy the same entropy index. That may be valid cryptographically, but it is not a translation layer. This project is trying to solve that specific gap. It keeps one canonical cryptographic floor, the standard English BIP39 mnemonic, and adds native-language display/input words that are semantically paired to that English mnemonic by index. So when the English word is “abandon”, the native display word is actually the native-language equivalent of “abandon”, not an unrelated word from an independent native BIP39 list. That matters for user understanding. The goal is not to claim that English is the only valid BIP39 list. The goal is to avoid the destructive UX mismatch where users think they are seeing a translation, but in reality they are seeing a completely different independent wordlist. If someone wants to propose new full canonical BIP39 wordlists for languages that do not have them, that is a valid path too. But that solves a different problem. This project is not trying to replace canonical native BIP39 lists. It is trying to create a clear display/input convention where the native words actually mean the same thing as the mnemonic being backed up, while keeping recovery compatible through the English BIP39 source of truth.

osem23

That is fair pushback on the framing. The UX problem is still real: many non-English users struggle with English recovery phrases. That is the problem this project is trying to address. At the same time, recovery UX touches real funds, so wording, review, and limitations matter a lot. That is not the intended model. The intended model is a native-language display/input layer that maps back to the canonical English BIP39 list, with English remaining the source of truth. We have already updated the README and documentation to make this clearer, including stronger guidance around limitations, backup format, and what these lists should not be used for. I appreciate the detailed criticism. This is exactly the kind of feedback that helps make the project safer and clearer.

osem23

I don’t think the answer is that this method is universally “better” than having a canonical BIP39 wordlist in every native language. If a language has a well-reviewed canonical BIP39 wordlist, designed with the same constraints as the original lists, supported by wallets, and accepted across the ecosystem, then that is obviously a very good solution. The problem is that most languages do not have that today. So the value of this approach is different: It gives the user native-language understanding while preserving immediate compatibility with the existing English BIP39 ecosystem. A new canonical native BIP39 list requires broad review, standardization, wallet adoption, long-term support, and user confidence that other wallets will accept it in the future. That is a much higher bar, and it is not available for most languages right now. Our approach keeps the English BIP39 mnemonic as the source of truth, but adds a native display/input layer on top of it. So the tradeoff is: Canonical native BIP39 list: cleaner if it exists and is widely adopted Native display/input layer mapped to English BIP39: more compatible today, easier to integrate in one wallet, and gives non-English users a way to understand what they are backing up without leaving the existing English BIP39 recovery path That is the point. I am not saying this replaces the need for proper native BIP39 wordlists. I am saying it can help users now, especially in wallets that want to preserve English BIP39 compatibility while improving recovery UX for people who do not understand English.

osem23

Yes, exactly. That is very close to the intended model. The native-language words are meant to help the user understand and confidently record the backup, but the English BIP39 words should remain available as the universal recovery fallback. A good wallet UX could show both side by side during backup: native word for the user’s understanding canonical English BIP39 word for compatibility That way the user gets the benefit of a recovery phrase they actually understand, while still having the English BIP39 version available if another wallet only accepts the standard English list. So the goal is not to hide the English words or create a separate recovery world. The goal is to make backup clearer for non-English users while preserving the existing recovery path. In practice, I agree that a recommended policy should probably be: if a wallet uses a native display/input layer, it should give the user the option, or maybe the default, to back up both the native word and the canonical English word together. That gives users the best of both sides: local-language understanding and standard BIP39 portability.

osem23

The value is UX and recovery confidence. For a native English speaker, the English BIP39 list feels natural, so this problem is almost invisible. But most of the world does not speak English as a native language. For many users, an English mnemonic is not really a “sentence” or even a meaningful set of words. It is a sequence of foreign symbols they are asked to copy perfectly and trust with their savings. I have worked with thousands of non-English-speaking Bitcoin users, and backup/recovery is consistently one of the hardest parts. This is where many people make mistakes, lose confidence, or fail to understand what they are actually saving. That creates real recovery risk: They may not understand what they wrote down They may confuse similar-looking English words They may make spelling mistakes They may not feel confident verifying the words later They may rely on screenshots, translation apps, or someone else for help A canonical native BIP39 wordlist would be ideal where it exists and where the user’s wallet supports it. But BIP39 only has a limited number of official wordlists. Most users do not have a canonical BIP39 list in their native language. The point of this approach is not to create a new seed scheme. It is to give users a native-language display/input layer while keeping compatibility with the existing English BIP39 standard underneath. So the wallet can say to the user: “Here are words you actually understand,” while internally preserving the same BIP39 indexes and canonical English flow. That makes backup and recovery more understandable without requiring a new cryptographic standard. For English speakers this may feel unnecessary. For non-English users, it can be the difference between copying foreign words blindly and actually understanding what they are backing up.

na3than

> The goal is to make recovery UX more understandable for non-English users while still relying on the existing English BIP39 standard underneath. Why? What's the value in presenting a non-English mnemonic to the user, then converting it to English before hashing it to create a seed? How does that "make recovery UX more understandable for non-English users" compared to presenting the non-English user a mnemonic sentence using a canonical BIP-39 word list for their native language?

osem23

I understand the concern, but I think there is an important distinction here. These lists are not intended to replace BIP39, and they are not used as independent seed wordlists. In our implementation, the canonical source of truth remains the standard English BIP39 wordlist. The wallet maps the displayed native-language words back to the canonical English BIP39 indexes before any seed operation. PBKDF2 is not run on the translated words, and the cryptographic seed flow is not changed. So the user is not creating a new German BIP39 seed based on a German replacement list. They are using a localized display/input layer that resolves back to the standard English BIP39 mnemonic. That said, your point about users shortening words to 4 characters is a valid concern in a general public-wordlist context. If someone tried to use these lists as standalone BIP39-compatible wordlists, or engraved shortened versions of the localized words on metal, that would be unsafe unless the list guarantees the same uniqueness and clarity rules. But that is not the intended use case here. The intended model is: canonical BIP39 English remains the source of truth native words are display/input aliases wallet validation resolves them back to the English BIP39 index seed generation remains unchanged no wallet should treat these as standalone BIP39 replacement lists without additional guarantees So I agree this distinction needs to be made very clearly in the README to avoid misuse. The goal is not to create new BIP39 wordlists. The goal is to make recovery UX more understandable for non-English users while still relying on the existing English BIP39 standard underneath.

osem23

Thank you, this is a very fair point. I agree that the original BIP39 wordlists were not designed as direct translations, and that their priorities around avoiding confusion, spelling ambiguity, similar-sounding words, and short-prefix uniqueness are important. To clarify my intention: I am not trying to replace the existing BIP39 lists, change the seed generation flow, or suggest that wallets should adopt this as a standard. This project is more of an open contribution / experiment for multilingual Bitcoin UX. It gives wallets and developers an additional reference if they want to explore native-language display or input layers, but there is no expectation that anyone must use it. The canonical BIP39 flow remains the source of truth. If a wallet needs strict 4-character uniqueness, metal backup compatibility, or full BIP39-style wordlist guarantees, then it should absolutely require that before using any list in production. So I agree with the concern. This repo should be understood as optional, experimental, and open for review, not as a claim that direct translations are better than the original BIP39 wordlist design principles. Appreciate the thoughtful feedback.

bitusher

Interesting... For those wondering the original BIP39 lists are here https://github.com/bitcoin/bips/tree/master/bip-0039 and list 10 different language lists The reason these lists did not use direct translations is because they prioritized - Avoiding words that are easily confused. - Avoiding words with multiple common spellings. - Avoiding words that sound nearly identical. - Ensure the first few letters uniquely identify the word. A direct translation of an English word might violate those rules in the target language. >We would appreciate review, criticism, native-speaker corrections, I am just wondering why a direct translation should be prioritized over the above concerns ? Also I read this - >"4-char prefix uniqueness is not guaranteed across all scripts. Wallets relying on prefix autocomplete should fall back to full-word matching." Which IMHO should be a non starter because this is needed for most wallets and even many metal seed backups It is critical for UX that wallets can auto complete the word after 3-4 characters rather than typing in many more characters

SpendHefty6066

Sparrow and Electrum are both solid wallets. Sparrow has one less dependency when connecting to your node than Electrum, and Electrum has a great UX (Sparrow's is not bad). Both are open source and have lots of eyeballs on them. Both are Bitcoin only which is a hard requirement. To OP, I recommend downloading either of these wallets and learn the ins and outs. When you move a nominally small amount of sats to it, burn a few sats in transaction fees just sending and receiving to addresses in your wallet. Get your seed phrase written down and then do this: uninstall your wallet software and delete it completely. Then restart your computer. Re-install Sparrow or Electrum and recover your funds from your seed phrase. Learn the core truth that your Bitcoin is **\*\*not\*\*** in your wallet or your signing device. Your Bitcoin is on the blockchain and your seed phrase are the keys that grant you access to them. This truth needs to be deeply embedded in your brain so that you know that if you lose your signing device, you have not lost your Bitcoin. But if you lose your seed phrase, or someone else gets them, then your Bitcoin is gone. Bitcoin is a sovereign bearer asset. The keys are the what needs to be protected. Chiseled into steel and stored safely. Sovereign bearer assets come with responsibility.

Difficult-Repair1295

I like the UX on River more. It feels more like brokerage account. Both are good if setup recurring buys.

MinimalGravitas

Why the random capitalization? The fragmentation and UX are being solved through interoperability, ultimately users won't need to know which rollup their assets are on or where the assets they want are... it will all just be abstracted away as the Ethereum Economic Zone. > security threats through it's bridging nature, If you use the rollup's native bridge there is no security threat. If you chose to use a non-native bridge then you are trading security for speed of transfer, if you are concerned more about security then just don't make that trade-off. > It was never meant as a solution, only as a short term workaround. Rollups like Deutsche Bank's and Sony's are the solution for entities wanting to build in the Ethereum ecosystem but retain the ability to enforce rules which don't exist on the L1. A bank in Germany and a bank in Singapore are likely to operate under different legislative frameworks. L2s allow different regulations to be in place while still allowing interoperability.

Miltank12345

Dude, The Layer 2 concept is a FAILURE. It was never meant as a solution, only as a short term workaround. It comes with trade-offs like fragmentation, security threats through it's bridging nature, decentralization and a HORRIBLE UX.

Top_Performance_732

It's not as decentralized as you think. And if that's your concern with base, then why settle for Solana? Ethereum is far more decentralized, and despite being slow and expensive it still has UX advantages with rabby and debank, jump is trash in comparison. And have you ever used solscan? It's horrific

osrsbtcandporn420

I'm talking about next to "daily profit" you can't click on that to sort by top/bottom. The site feels like a scam anyway. I wouldn't recommend it. Enjoy your free UX advice, referral pajeet.

Last_Meat3940

I’ll tell ChatGPT to teach you how to read column headers. 'Price' sorting is already right there on the right. 🙃 Taking UX advice from a guy named osrsbtcandporn420 wasn't on my bingo card today. Honestly I’ll take the 'ai crap' comment as a compliment on the UI design.

absurdcriminality

Yeah. The point about crypto products being built for crypto-native users first is pretty accurate. It’s just fascinating to me that the industry is over a decade old and we are still dealing with UX issues lol

FTP_FTP_

The IRS. Spending crypto isn't what most people do with crypto. The UX is fine. 

Miltank12345

The Layer 2 approach has FAILED. It fragments liquidity, has HORRIBLE UX and will always pose a securitiy threat due it's bridging nature. Development has HALTED on Layer 2 and most projects seek a reliable Layer 1

Equivalent_Menu_1096

The bridge point you mentioned deserves more attention. "Bridges that get hacked every six months" isn't just an inconvenience — it's the biggest structural weakness in the current multi-chain model. Here's why that matters for decentralization: almost every bridge in production relies on a trusted third party — a multisig, an oracle set, or a validator committee signing off on state transitions. That means any chain connected to the ecosystem through a bridge is only as decentralized as the bridge's signers. And we've seen what happens when those signers get compromised (Wormhole, Ronin, Nomad, Bybit). The key split most people miss is between: 1. Trust-based bridges (multisig + oracles) — fast UX, but you're depositing into what's effectively a multisig wallet on the source chain and trusting operators to unlock on the destination. That's custodianship with extra steps. 2. Trust-minimized approaches like atomic swaps via HTLC — slower, more limited, but no intermediary can steal your funds by design. Most users don't realize that when they bridge, they're giving up the very property that makes crypto useful: sovereign control. A chain can have perfect validator distribution, but if it's connected to everything through a 3/5 multisig, the whole system inherits that weakest link. The OP is right about 90% of crypto not being truly decentralized. But even among the projects that get consensus right, most fail at the interoperability layer. And interoperability is where the real value lives.

Crypto_future_V

Coldcard MK5 UX upgrades looking clean as hell Coinkite keeps delivering for serious bitcoiners

Large-Cress900

really appreciate the kind words! and yeah the limitations section deserved more space, you're right. the scanning latency on slow connections is a real UX problem that i kind of glossed over. super curious about your solution tho, please do share when you publish. the scanning bottleneck is imo the main thing holding back adoption rn, if someone cracks that elegantly its a big deal

crooks4hire

The damn keyboard doesn’t even look straightforward; how are we supposed to believe the UX is any different?

Beneficial_Crab6954

Great breakdown of MEV/privacy spectrum. The real shift is execution layer abstraction + intent-based trading. Biggest gap remains UX + institutional-grade compliance rails for mainstream adoption of these solutions today

Admirable_Fan_9530

Solid breakdown, MEV is basically an invisible tax most retail users never price in. The real takeaway is there’s no single “privacy fix,” just tradeoffs between trust, UX, and security. Most people will likely default to private RPCs or intent-based systems, while full zk or enclave solutions stay niche but powerful.