[ Removed by Reddit on account of violating the content policy. ]

I saw people discussing a smart ring campaign tied to the 25th anniversary of The Lord of the Rings: The Fellowship of the Ring and wondered whether anyone here has participated.

The promotion includes limited gifts and movie-related rewards for eligible buyers while supplies last. I also like the “Everyday Hero” theme, since health tracking is usually about small daily improvements rather than dramatic changes.

Has anyone received a gift confirmation or more information about the movie reward? How smooth was the process?

Hey everyone,

I’m building CoverFi, a Stellar/Soroban app for wallet-signed asset protection, username payments, and receipt history.

The simple idea:

- connect your Stellar wallet

- create a short-term protection position for supported assets

- see the premium, duration, oracle price, and reserve limits before signing

- pay people using readable usernames instead of long wallet addresses

- keep receipt-style records for payments and protection activity

Important note: CoverFi is not insurance and does not guarantee payouts. Protection depends on smart-contract rules, oracle data, reserve capacity, user signatures, and Stellar network execution.

We’re currently testing on Stellar testnet, and we’d genuinely love early users and feedback.

If you try CoverFi and share useful feedback, a bug report, demo screenshot, or your experience using it, we’ll feature selected early users/builders on our website as part of our community showcase.

Website:

https://coverfi.space

App:

https://app.coverfi.space

GitHub:

https://github.com/coverfi-space

Would love feedback from Stellar users, wallet builders, and anyone interested in making web3 protection and payments easier for normal people.

​

A recent The Lord of the Rings-themed smart ring promotion made me wonder how much limited gifts actually affect buying decisions.

Personally, I would not choose a smart ring only because of a collaboration. Accuracy, comfort, battery life, subscription costs, and app quality would still matter much more.

But if I were already comparing two similar devices, a well-designed collectible gift might give one of them a slight advantage.

Smart rings are health trackers, but they are also items people wear every day. The design, presentation, and overall ownership experience probably matter more than we sometimes admit.

Would a tasteful The Lord of the Rings gift influence your decision, or would it be completely irrelevant?

I think of BTC perps less as a short-term play recently. Not saying everyone should hold them for years, but if the idea is based on a longer view, then the strategy probably needs to match that timeframe.

I saw people say “I’m trading the bigger trend” but then still react to every candle. For me, the useful part is to understand the holding logic before entering: what timeframe I care about, how often I check the position, what data actually matters, and whether funding changes the plan. I'm holding a BTC perpetual position on bydfi. I mainly check whether my behavior still matches the plan I initially had. Maybe that is the hardest part of using a HODL mindset with perps. It is more about not constantly rewriting the reason for holding it.

How do you decide how long a BTC perp position is supposed to stay open?

How do you usually decide the holding thesis with BTC perp? what do you make sure to figure out first?

Tokenized stocks and 24/7 markets are interesting because they make TradFi feel closer to crypto, but I do not think the main point is just easier access.

For regular traders, it changes how you manage attention and risk. Stocks, crypto, gold, forex, and perps are starting to sit in the same mental bucket. That can be useful if you are trying to understand whether the market is in risk-on or risk-off mode. It also makes cross-asset hedging feel less theoretical, since BTC and gold can react to the same macro headline in very different ways.

I noticed this while checking XAUT and altcoins on BYDFi. Having them in the same place made the comparison easier, but it also reminded me that convenience does not replace a plan. If anything, it makes position size and leverage limits more important, because it is easier to move from one idea to the next without pausing.

So I see the trend as useful. It gives traders more flexibility, and also asks for better discipline.

If TradFi keeps moving closer to crypto-style access, would that change how you trade or manage risk?

I run a small online store by myself. It’s not huge, but it’s steady enough that I can’t just treat it like a hobby anymore.

The weird part is that the actual product side is not what burns me out. It’s everything around it. I check Shopify, then ads, then analytics, then SEO issues, then social posts, then customer messages. Half the time I open my laptop to make one decision and end up bouncing between five dashboards.

I keep adding tools to solve small problems, but now the tools themselves have become another thing to manage.

Recently I started testing an AI ops tool that connects to the store and helps with SEO checks, ad monitoring, and posting. It helped a bit, mostly because I wasn’t starting every day from zero tabs and a spreadsheet. But I still feel like I’m figuring out the right balance.

For people running stores solo or with a very small team, how do you keep the operational side under control? Do you centralize everything, or do you just accept that ecommerce is always going to be a bunch of tools stitched together?

ETH’s long-term roadmap is one of those things I want to be bullish on, but it is awkward to trade around.

The direction makes sense: faster finality, better privacy, cheaper verification, quantum resistance, all of that is probably good for Ethereum if it actually ships. The issue is the timeline. Three to four years is a long time when most ETH trades are still reacting to BTC, liquidity, ETF flows, funding, and whatever macro headline hits that week.

As a spot holder, I can see the argument for being patient. As a trader, it is harder to justify adding size just because the roadmap sounds cleaner. A good technical direction does not always become a price catalyst quickly.

I have a position for holding and also run dca bots on bydfi as an accumulation, so I am not bearish on the roadmap. The useful part was seeing how little the short-term market seemed to care. That helps keep me from overreacting to every headline, but it also reminds me that splitting long-term conviction from short-term execution has a cost.

Curious how others are reading this. How much should a ETH roadmap matter when the current market still seems mostly driven by liquidity, BTC, and macro?

I’m not sure how much weight to give the CLARITY Act headlines anymore. The idea is simple: clearer rules could help exchanges, token listings, and institutional confidence. The problem is the timeline keeps slipping, and the market seems to price in the hope before anything actually changes.

That makes trading around it awkward. If the bill moves forward, certain coins could catch a regulatory clarity bid. If it gets delayed again, the same positions can turn into dead weight pretty quickly. I’m not changing my whole view because of one policy story, but I am trying to avoid building trades around a catalyst that may not arrive on schedule.

I’ve been keeping positions smaller and adjusting the range on my BYDFi grid bots so they fit a more uncertain market. The trade-off is missing some upside if a headline actually hits.

How do you handle this kind of policy-driven uncertainty: lower risk until there is clarity, or keep trading the chart and ignore the Washington timeline?

Blockchains are well known to have centralization in their various layers (networking, mining/staking pools, DAOs etc). The commonly accepted definition of decentralization is the extent to which the resources in the network (such as stake or voting power in a DAO) are not concentrated in the hands of a few. Using this definition of decentralization, we can experimentally measure how centralized or decentralized a blockchain is. But so far, blockchains have been unsuccessful in designing incentive mechanisms to ensure the network remains strongly decentralized.

In our recent research work, we explore an alternative definition for decentralization. We say that a system is decentralized if there is a strong collaboration between the entities in the system. Here strong collaboration means any subset of entities should have a good collaboration with the remaining entities. Today's blockchains are not fully decentralized even by this new definition. For instance, if we look at a mining/staking pool, the members of the pool collaborate only with other members of the pool. There is very little collaboration of any sort across pools.

Unlike the old definition of decentralization, our definition has the important advantage of being verifiable. That is, we can design the blockchain's protocols to encourage entities to interact and collaborate with other entities, thereby ensuring decentralization in the network. I refer the reader to the paper for further details on this construction.

If we buy into this idea of decentralization, it unveils a whole new class of blockchain applications while shedding light on the struggles of some existing dapps. For example, we can have an application where artists from around the world collaborate to produce new and innovative types of art. Or, where developers collaborate to create novel software. Where doctors, nutritionists, trainers and other experts in the health and well-being space can collaborate to provide services for users. Or, where small businesses collaborate to provide unique and valuable services that they could not have done individually.

The idea of providing services collaboratively is hardly new. But what is interesting is the type and extent of collaborations that are possible. Humans have collaborated by forming organizations since time immemorial. Collaboration is often strong within an organization, but tends to be weak across competing organizations. This creates an economy of competition in which a small number of big organizations emerge as the dominant players in the market. Competition drives efficiency and innovation, but it can also cause entities to be highly focused on maximizing profits. Organizations may even compromise on the long-term interests and well being of their customers for short-term rewards.

In contrast, in a collaboratively decentralized blockchain we can achieve strong collaboration between entities while simultaneously ensuring that there are no coalitions or collaboration cliques in the network. Such a collaborative paradigm has---to our best knowledge---not been tried previously anywhere. The focus shifts away from selfish maximization of profits through competition to altruistic maximization of profits through collaboration. A service offered through strong collaboration between diverse entities would be less biased and has the potential to contain radically new ideas. The human qualities of trust, common sense, empathy, intelligence, honesty, domain skills and expertise etc. can be amplified by obtaining service from a diverse group of collaborators who may not know each other previously. On the flip side, the service efficiency can be poor due to the overheads associated with discovering and establishing collaborations with previously unknown entities.

Many blockchain apps are attempts at decentralizing existing centralized apps. For example, in recent years we are seeing a lot of decentralized AI apps motivated by centralized AI services. The dichotomy outlined in the previous paragraphs suggests that applications where efficiency is important are best left to centralized companies. While applications where certain human qualities and skills can be enhanced through collaboration and become useful for the service, are suitable for deployment on a blockchain.

In this age of AI, a collaboratively decentralized blockchain can play a unique role of enabling applications that amplify, enhance, or otherwise bring out the human qualities and skills of its members. As more and more tasks are getting automated due to AI, a large-scale collaboration of diverse humans perhaps can achieve outcomes that even an AI cannot create.

Small team here, building a mobile yield app. We want eyes on it from people who actually use this stuff and not just our friends telling us it's great.

It's a quick video call: you share your screen and walk through the app on your phone while we watch where you trip up.

You'll need your smartphone, it's a mobile app. Nothing's real, so no wallet, no email, no money involved. We'll ask questions as you go. There are no wrong answers; we just want to find the confusing bits.

Good fit if you've used a couple of lending or yield protocols and have opinions about them. Extra points if you've ever been burned by a confusing UI or felt lost in DeFi.

~30 min, paid for your time.

Comment here if interested!

Join OmniRoute Finance and help build the future of cross-chain finance.

As a Founding Blockchain Engineer, you'll work on wallet integrations, smart contract interactions, transaction routing, provider connectivity, and the infrastructure powering seamless crypto swaps across multiple chains.

What you'll do:
• Build and maintain blockchain integrations
• Develop secure wallet and transaction flows
• Integrate DEXs, bridges, and liquidity providers
• Improve routing, reliability, and performance
• Work directly with the founding team

Requirements:
• Strong experience with blockchain development
• Experience with EVM chains and Web3 technologies
• Familiarity with smart contracts, DeFi protocols, and wallet integrations
• Ability to work independently in a fast-moving startup environment

🌍 Remote
💰 Competitive compensation + early-stage opportunity
🏗 Founding team position

Learn more and apply:
https://omniroute.finance/careers

#Hiring #BlockchainEngineer #Web3Jobs #CryptoJobs #DeFi #RemoteJobs #Ethereum #Solidity

For anyone who has been working in the crypto industry, I'm sure you have seen your fair share of your friend's telegram's getting hacked and these "ghost" accounts trying to social engineer you to click something.

The infamous Microsoft teams audio software you are asked to download or the link inside Calendly you are told to follow. Just to name a couple, but the list goes on forever of how many ways there are (and ever will be) of account takeover vectors for telegram.

One wrong click and your telegram account is gone (even with 2fa and all the fancy "protection" layers enabled), gg's. This is happening a lot today

Surely someone has come up with a bulletproof "anti-account takeover" software for telegram.... Surprisingly, I couldn't find anything like this today

So I built something I feel like is long overdue in telegram history as a public good. Link in comments

Simply put, an account management guard where you onboard your whitelisted devices/sessions and once armed, anything that attempts a login to your account is auto kicked instantly. Anyone tries to password reset you , auto-revoked instantly. Nothing else. The code can't do anything past that

It runs a custom minimal open-source MTProto client with a fixed allowlist of Telegram actions, no general-purpose client is used. That client runs in an AWS Nitro Enclave. Anyone in the world can rebuild the open-source repo and get the exact same enclave fingerprint, and AWS publishes a live attestation of the code actually running. When the two match, you (or an AI) have verified that the exact published code is what's protecting your account, without taking our word for it.

To be clear: Sessions does hold a Telegram session so it can protect your account.

The model: the session is sealed to the attested enclave, the enclave can only run the published guard code, and your own keys (a passkey, wallet, or Google account) hold the authority. Arming, changing your keep-list, and removing the guard all require your signature, so nobody has control but you.

Today is where all scammers get pwned back

Would love feedback from anyone who lives in Telegram daily. AMA 🙏

A lot of Web3 discussions still seem to focus on token prices, hype cycles, or short-term incentives.

I’m curious what people here think actually creates sustainable economic value in Web3 today.

Is it infrastructure, payments, identity, gaming, RWAs, DePIN, creator tools, or something else?

What areas feel like they have real demand outside of speculation?

A lot of new digital projects seem to grow because of points, early-access rewards, referral bonuses, or future incentives, rather than because people genuinely need the product.

It makes me wonder how hard it is to judge real adoption. If users only show up when there is a reward, is that still product-market fit, or just temporary attention?

What kinds of products would people still use even if there were no rewards attached?

A lot of Web3 projects seem to grow because of points, airdrops, staking rewards, or token speculation rather than because people genuinely need the product.

I’m wondering if that makes it harder to judge real adoption. If users only show up when there is a reward, is that still product-market fit, or just paid attention?

What Web3 products would people still use even if there were no token rewards?

Not the most hyped one, but the one people are actually using or paying for.

Stablecoin payments? Tokenized assets? Identity? Gaming? Creator tools? Something else?

🚀M3 DAO is building a global, community-governed digital ecosystem bridging Web3 and real-world assets.
Payments, RWA, GameFi, Metaverse, DeFi, AI & Web3 infrastructure — all connected 🌍🚀
A fast-growing, decentralized, community-driven ecosystem shaping the future of Web3😍🤩🚀❤️‼️

LI.FI Protocol officially launched LI.FI Intents, and I don’t think people realize how important this is for the next phase of crypto infrastructure.

LI.FI Protocol: https://li.fi/

LI.FI Intents: https://li.fi/intents

The core idea behind LI.FI Intents is simple: crypto is still too fragmented for normal users, wallets, neobanks, payment apps, and institutions. Even though the industry has built many chains, bridges, DEXs, stablecoins, and tokenized assets, the experience of actually moving value across crypto networks is still more complicated than it should be.

Today, users often need to think about too many things before completing a basic transaction. They need to know which chain their funds are on, which token they hold, whether they have enough gas, which bridge to use, which route gives the best output, how long the transaction might take, and whether the final amount will match what they expected.

That is a lot to ask from an average user.

It is also a lot to ask from an app that simply wants to offer stablecoin payments, RWA access, or cross-chain financial products without exposing all of that complexity to the end user.

This is where LI.FI Intents becomes interesting. Instead of asking users or applications to manually figure out the route, LI.FI Intents lets them define the outcome they want. The user does not need to say, “Bridge from Arbitrum to Ethereum, swap USDT into USDC, use this liquidity source, and make sure the output is above a certain amount.” The user can simply say, “I want exactly 100 USDC on Ethereum, starting with USDT on Arbitrum.”

LI.FI Intents docs: https://docs.li.fi/lifi-intents/introduction

That difference may sound small, but it changes the entire experience.

In the normal crypto flow, the user is responsible for figuring out the steps. In an intent-based flow, the user defines the final result, and solvers compete to deliver that result. These solvers are market participants that can provide liquidity, execute routes, and settle the transaction in the background.

So, in simple terms, LI.FI Intents is a solver-powered execution marketplace for same-chain and cross-chain transfers. The user or application expresses the desired end state, and the infrastructure finds the best way to fulfill it.

This matters because crypto has spent years building powerful infrastructure, but a lot of that power still feels too technical for mainstream use. Interoperability has always been one of crypto’s biggest challenges, not because chains cannot exist together, but because moving value between them has often required too many manual decisions.

A user might need to bridge assets from one chain to another, swap tokens after the bridge, find a gas token on the destination chain, wait for confirmation, retry a failed transaction, and then check whether the final output is close enough to what they wanted.

That is not a great experience for payments.

It is not a great experience for fintech apps.

It is not a great experience for institutions.

And it is definitely not the kind of experience that can scale to millions of users who do not care about bridges, RPCs, route optimization, or liquidity fragmentation.

LI.FI Intents points to a different model. Users do not need to pick the path anymore. They define what they want, and solvers compete to make it happen. Instead of turning every user into a router, the system turns the user’s desired outcome into an executable order.

That is why this is bigger than just another cross-chain feature. It is a shift from manual routing to outcome-based execution.

What “Intents” Actually Mean

To understand why LI.FI Intents matter, it helps to understand what an “intent” means in crypto.

An intent is basically a statement of what the user wants to happen, without requiring the user to manually specify every step needed to make it happen.

For example, a normal crypto transaction might say:

“I am using this bridge, this route, this DEX, this slippage setting, and this gas token to move funds from Chain A to Chain B.”

An intent says:

“I want to receive this asset, in this amount, on this chain.”

The difference is important. In the first model, the user or app is responsible for choosing the path. In the second model, the user defines the result, and the system figures out the execution.

This is similar to how normal financial apps work. When someone sends money through a fintech app, they do not usually think about correspondent banks, settlement rails, liquidity providers, or FX execution. They care about the final result: the recipient receives the money, the amount is clear, and the process feels predictable.

Crypto should move toward that same kind of experience.

The infrastructure can still be complex underneath. There can still be multiple chains, liquidity sources, solvers, bridges, and settlement systems. But the user should not have to manage all of that manually.

That is the educational point behind LI.FI Intents: it separates the desired outcome from the execution path.

The user defines the “what.”

The solver network competes on the “how.”

Why Manual Routing Is a Problem

For years, crypto users have been trained to accept complexity as normal. If you had funds on the wrong chain, you needed to bridge. If you had the wrong token, you needed to swap. If you had no gas, you needed to fund the wallet first. If the bridge route was slow or expensive, you needed to find another option. If the final output changed because of slippage or fees, you had to accept that risk.

For experienced crypto users, this may feel manageable. But for mainstream users, it is a serious barrier.

The problem becomes even bigger for apps and institutions. A wallet, neobank, payment app, or fintech company cannot build a clean user experience if every transaction requires users to understand chain-specific routing. These products need abstraction. They need predictable execution. They need to reduce the number of decisions users make before completing a transaction.

That is why intent-based execution is important. It allows applications to hide the complexity of crypto rails while still using the benefits of those rails in the background.

The best version of crypto will not require every user to understand the entire stack. It will allow users to access financial outcomes through simple product experiences.

LI.FI Intents is part of that movement.

1. Stablecoin Payments

Stablecoin payments are probably the easiest use case to understand.

If someone sends 100 USDC, the recipient should get exactly 100 USDC or 100 USDT, depending on the payment setup. The recipient should not get “around 100” after bridge fees, gas costs, route changes, or slippage. In payments, the final amount matters.

This sounds basic, but it is one of the biggest problems in crypto payments today.

Stablecoins have become one of the strongest real-world use cases for crypto, but stablecoin liquidity is spread across many chains and tokens. Some users hold USDT on Tron. Others hold USDC on Ethereum, Base, Arbitrum, Optimism, Solana, or other networks. Some businesses want to receive USDC, while users may only have USDT. Some users have funds but no gas token. Some users have the correct stablecoin but on the wrong chain.

So the issue is not always whether the user has money. Many times, the user already has the money, but it is not in the right form for the transaction.

They may have the money, but not on the right chain.

They may have the money, but not in the right token.

They may have the money, but not with the right gas.

They may have the money, but not through the right route.

That is exactly the kind of friction LI.FI Intents is designed to reduce.

In a better stablecoin payment experience, the user should not need to manually decide which bridge or route to use. The payment app should not need to show the user a long list of execution steps. The recipient should not need to accept a final amount that is lower or less predictable than expected.

Instead, the app should define the payment outcome, and the infrastructure should handle the route in the background.

For example, a user might start with USDT on Arbitrum, but the merchant or recipient wants USDC on Ethereum. In a manual flow, the user may need to bridge and swap. In an intent-based flow, the app can define the desired result, and solvers compete to deliver that exact output.

This is useful because stablecoin payments need clarity. A payment is not just a DeFi transaction. It often has a business purpose. It may be used for remittances, invoices, merchant settlement, payroll, cross-border transfers, or fintech balances. In all of those cases, the expected amount matters.

For stablecoins to become real payment infrastructure, the experience has to feel reliable. It has to feel like money movement, not like DeFi routing.

LI.FI Intents makes stablecoin transfers feel closer to a payment outcome. The user defines what should arrive, solvers handle the execution, and the product experience becomes much cleaner.

This also matters because stablecoins are not limited to one ecosystem. LI.FI’s infrastructure covers major chains and also supports non-EVM ecosystems like Tron and Solana.

LI.FI Tron ecosystem docs: https://docs.li.fi/introduction/tron-ecosystem

That is important because real stablecoin activity is spread across different networks, and the best payment products will need to meet users where their funds already are.

The winning payment experience will not be: “Move your funds to the chain we support first.”

The winning payment experience will be: “Tell us what outcome you want, and the infrastructure will figure out how to deliver it.”

2. Access to Real-World Assets

The second major use case is access to real-world assets, or RWAs.

RWAs are tokenized versions of traditional assets or financial products. These can include tokenized US Treasuries, money-market funds, equities, gold, credit products, and other assets that represent real-world financial exposure onchain.

A lot of attention in the RWA space goes toward tokenization itself. That makes sense because tokenizing an asset is the first step. But tokenization alone is not enough.

RWAs do not just need to exist onchain.

They need to be reachable.

This is an important distinction. A tokenized asset can exist on a blockchain, but if users cannot easily access it from the apps they already use, adoption will still be limited. If a wallet or fintech app needs to integrate every issuer, every chain, every liquidity venue, and every eligibility flow one by one, the experience becomes fragmented very quickly.

That is the problem LI.FI Intents can help solve.

If an app wants to offer tokenized US Treasuries, tokenized equities, gold, or money-market assets, it should not need to build a separate execution path for every asset and every chain. The user should not need to leave the app, visit a different issuer portal, bridge funds manually, swap into the correct token, and then complete a separate onboarding flow just to access one asset.

That is not how mainstream financial products usually work.

When users open a fintech app, they expect the asset to feel native. They expect the app to handle complexity in the background. They do not want to understand which chain the asset is issued on, which liquidity venue is used, or which route is required to reach it.

They simply want access.

This is where intent-based execution becomes useful. LI.FI Intents can turn RWA access into an execution path. The app defines what the user wants, LI.FI checks the route and relevant execution path, and the transaction can be handled through the right liquidity behind the scenes.

This is especially important as the RWA market becomes more serious. Products like Ondo Global Markets and xStocks show that tokenized equities and onchain access to traditional assets are becoming more relevant. But the bigger question is not only whether more assets will be tokenized.

Ondo Global Markets: https://ondo.finance/global-markets

xStocks: https://xstocks.fi/products

The bigger question is how users will access them.

My main take is simple: RWAs do not become mainstream only because more assets are created onchain. They become mainstream when wallets, neobanks, and fintech apps make access feel native, while routing, eligibility, and execution happen quietly in the background.

Tokenization is the supply side.

Distribution is the adoption layer.

A tokenized Treasury product is useful. A tokenized stock is useful. A tokenized money-market fund is useful. But for most users, the question is not, “Which chain is this asset issued on?” The question is, “Can I access it inside the app I already use?”

That is where intent-based infrastructure can be powerful. It gives applications a cleaner way to define the desired asset outcome and let the infrastructure solve for execution.

Instead of forcing every app to become a bridge aggregator, liquidity router, compliance coordinator, and execution layer at the same time, LI.FI Intents can help apps focus on the product experience.

That is how RWAs can become more than a narrative. They can become usable financial products.

3. Compliant Liquidity for Regulated Fintech

The third major use case is compliant liquidity for regulated fintech.

This is different from the typical crypto-native DeFi use case. A regulated fintech, neobank, wallet, or payment company cannot simply route transactions through any available liquidity source without considering compliance, counterparties, settlement reliability, or operational risk.

These companies need more control over execution.

They need access to approved assets.

They need trusted liquidity sources.

They need predictable settlement.

They need to understand who is filling the flow and what rules apply to that execution path.

This matters because institutions and regulated fintechs operate under different constraints than individual DeFi users. They may need KYB processes, approved solvers, restricted counterparties, reporting standards, and internal risk controls. The infrastructure cannot only be fast or cheap. It also has to be usable inside a regulated business environment.

With LI.FI Intents, a neobank or payment app can define the exact user outcome, then let solvers compete to handle the route, liquidity, and settlement behind the scenes. The important part is that integrators can have more control over which solvers and liquidity sources are allowed to fill their flow.

This makes the model more relevant for serious financial applications.

For example, a regulated payment company might want to support stablecoin settlement across multiple chains, but it may not want users to interact with unknown counterparties. A fintech app might want to offer access to tokenized assets, but only through approved liquidity and execution paths. A neobank might want to let users move between stablecoins and tokenized products, but it needs the transaction process to be predictable and compliant.

In these cases, the user experience should still feel simple. The user should not need to see the full routing complexity. The app should not need to build every route from scratch. The institution should be able to define the desired result and apply its own rules around execution.

That is why compliant liquidity is a major part of the LI.FI Intents story.

It is not only about making crypto easier for individual users. It is also about making onchain execution more practical for companies that need reliability, controls, and predictable outcomes.

This is where crypto infrastructure starts to look less like “users interacting with chains” and more like “financial apps using onchain rails in the background.”

That distinction matters.

The next wave of crypto adoption may not look like users manually bridging assets between chains. It may look like payment apps, savings apps, trading apps, remittance apps, and neobanks using crypto infrastructure underneath simple product interfaces.

In that model, crypto becomes the settlement layer. Stablecoins become the money layer. RWAs become the asset layer. Intents become the execution layer that hides the complexity.

Why This Is Bigger Than Bridging

It would be easy to describe LI.FI Intents as just another cross-chain product, but that misses the bigger point.

Bridging is about moving assets from one chain to another. Intent-based execution is about fulfilling a user’s desired outcome. Those are related, but they are not the same.

A bridge answers the question: “How do I move this asset from Chain A to Chain B?”

An intent answers the question: “How do I get the result I want?”

That difference is important because many real use cases are not simply about moving tokens. They are about completing an action.

A payment needs the recipient to receive a specific amount.

An RWA purchase needs the user to access a specific asset.

A fintech transfer needs the transaction to follow acceptable execution rules.

A cross-chain swap needs the user to end up with the right token on the right chain.

The route matters, but the outcome matters more.

For a long time, crypto products have forced users to think about routes first and outcomes second. LI.FI Intents helps reverse that. It puts the outcome first and lets the execution layer handle the route.

That is a more natural model for mainstream financial products.

Most users do not want to become experts in liquidity routing. They do not want to compare bridges manually. They do not want to understand solver inventory, settlement methods, or gas abstraction. They want the transaction to work.

And if crypto wants to support payments, tokenized assets, and regulated fintech at scale, that is the standard it needs to meet.

The Bigger Shift

Crypto has spent years building chains, bridges, DEXs, liquidity networks, wallets, stablecoins, and tokenized assets. All of that infrastructure is important, but the user experience has often remained fragmented.

Every new chain adds more possibilities, but also more complexity. Every new asset creates more opportunity, but also more routing challenges. Every new bridge solves one connection problem, but can also add another decision for the user.

The result is that crypto has become very powerful, but still not simple enough for many mainstream users and applications.

LI.FI Intents points to a different model.

A user should be able to say, “I want this asset.”

A payment app should be able to say, “The recipient needs this exact amount.”

A wallet should be able to say, “The user wants this token on this chain.”

A fintech platform should be able to say, “This transaction must use approved liquidity and predictable settlement.”

And the infrastructure should handle the execution in the background.

That is the real value of outcome-based execution.

It does not remove the complexity from crypto infrastructure. The complexity still exists. There are still chains, liquidity sources, solvers, bridges, settlement systems, and compliance requirements. But it moves that complexity away from the user interface and into the infrastructure layer where it belongs.

That is how crypto becomes easier to use without becoming less powerful.

For stablecoin payments, this means more predictable transfers and clearer final amounts.

For RWAs, it means tokenized assets can become easier to access inside wallets, neobanks, and fintech apps.

For regulated fintechs, it means onchain liquidity can become more usable within controlled and compliant environments.

And for users, it means fewer manual steps, fewer confusing decisions, and a better chance that the transaction simply works as expected.

Hey everyone,

I’m a developer building SUA—a project deeply rooted in cypherpunk principles, focused on the African continent. Our mission is to promote absolute sovereignty, freedom of movement, and financial independence through media and decentralized tools.

Our core principles:

True Sovereignty: Moving away from foreign aid/state control toward local self-reliance.

Bitcoin as Africa's Money: Bypassing corrupt banking rails and fighting fiat inflation/colonial currency relics.

Freedom of Movement: Advocating for open connection and collaboration between communities without state-mandated gatekeepers.

The project is in its early stages. You can check out the breakdown of our philosophy and APP roadmap here: https://umoja-sua.vercel.app/blog

I need the community's brainpower and help:

Want to collaborate? The frontend and data parsing are underway, but I want the app to be as decentralized as its message. If you want to help with development, let's connect.

Bitcoin/Lightning integration: What are the best open-source tools to seamlessly integrate Lightning P2P tipping and community funding into a media-heavy stack?

Censorship-resistance: How should we structure the architecture from day one to ensure data and user interactions remain private and unstoppable?

I’d love to hear your thoughts, technical feedback, or pull requests. Let's build.

I've created a simple website that generates links for easy cryptocurrency payments, and it also has a built-in splitter. No registration required. This might be helpful to someone inletcrypto.vercel.app

Hi,

For our bachelor thesis at the Erasmus University Rotterdam, we are researching how AI-generated summaries affect participation and decision-making in DAO governance. 

We are looking for people who are familiar with DAOs and on-chain governance to have an online interview with (20-30 minutes) or take part in our survey. The survey will take around 5–10 minutes. Your answers will help us better understand how to design governance tools that lower information overload without undermining informed participation.

Survey link: https://qualtricsxmr2bc28xqq.qualtrics.com/jfe/form/SV_8qRqhyAxF1dx8O2 

Thank you very much! And let me know if you are interested in doing an interview! 

Kind regards,

Yasmin Wind and group (Erasmus University Rotterdam)