Crypto World
Bitcoin volatility looks cheap as $10 billion options settlement nears: Crypto Daily
“Call spreads remain attractive for anyone wanting recovery exposure into the post-quarterly reset. And now look even better on a relative-vol basis, since call spread longs are buying the cheaper wing of a skew that is leaning the other way,” he said.
There are a number of factors that might drive volatility higher in the near term. Friday’s options expiry, for example, which Péquignot described as “traditionally one of the most significant liquidity events on the annual calendar.”
Moreover, ahead of the expiry, options traders who bought puts, or downside bets, in recent months are sitting in profit. That is, they are in the money, while those who bought calls are set to see their bets expire worthless.
“With spot at 64k, the June 26 book is net long puts in the money and long calls out of the money – the embedded loss is sitting with the call buyers who chased the 80k+ strikes,” Péquignot noted.
The sharp decline in Alphabet (GOOG) and SpaceX (SPCX) stocks, and declines in Asian equity indexes is another factor that could stoke volatility in bitcoin, which often takes its cue from technology stocks.
Not to forget, the Fed’s preferred inflation measure, the core PCE, is scheduled for release Thursday and is expected to show price pressures at their strongest since May 2024. Such a reading may breed volatility across assets, including Treasury notes and cryptocurrencies. Stay alert!
Crypto World
LastPass customer info leaked again after third-party data breach
LastPass, the password manager that inadvertently facilitated the theft of $150 million in crypto from Ripple co-founder Chris Larsen, is now warning users that their personal information was stolen via an attack on third-party market firm Klue.
The company emailed its customers this week to inform them that Klue was breached on June 11 and that data including customer names, phone numbers, email addresses, and physical addresses, as well as support case data and sales-related data, had been stolen.
Despite this, LastPass stressed that the incident affects only Klue-integrated systems and that “LastPass products, services, and infrastructure were not impacted in any way and customer vaults remain secure.”
Multiple cybersecurity firms reliant on Klue have also seen customer data leaked.
The cybercrime group Icarus claimed responsibility for the breach and is reaching out to users and threatening to leak their data.
LastPass users have been warned to stay vigilant about social engineering and phishing attacks that may attempt to swindle them out of more information and funds.
LastPass’s 2022 breach lost Ripple co-founder $150M
LastPass suffered multiple major breaches in 2022 that saw sensitive data stolen from customers’ password vaults.
Crypto sleuth ZachXBT noted in 2024 that a threat actor was able to use data from this breach to steal $5.4 million worth of crypto from over 40 addresses.
Prior to this, in 2023, ZachXBT also reported that roughly $4.4 million was drained from over 25 victims because of the 2022 breach.
Possibly the biggest theft from LastPass involved Ripple co-founder Chris Larsen, who lost $150 million worth of crypto after his private keys were leaked in the 2022 breach.
Read more: ‘AudiA6’ crypto laundering suspects face extradition to US
Two people behind a $389 million cryptocurrency laundering service dubbed “AudiA6” have also, according to ZachXBT, helped launder stolen funds from LastPass users.
LastPass was fined £1.2 million by the UK’s Information Commissioner’s Office last year over the 2022 data breach.
The body claimed it impacted 1.6 million UK users, and that LastPass “failed to implement sufficiently robust technical and security measures, which ultimately enabled a hacker to gain unauthorised access to its backup database.”
Got a tip? Send us an email securely via Protos Leaks. For more informed news and investigations, follow us on X, Bluesky, and Google News, or subscribe to our YouTube channel.
Crypto World
Why Perfectly Fair Crypto Transaction Ordering Isn’t Achievable
Today’s blockchains already treat consensus as a matter of two properties: nodes must agree on the same history (consistency) and the system must keep processing transactions (liveness). But that framing leaves a crucial gap—what users ultimately care about is not only whether transactions get confirmed, but whether their relative ordering is meaningfully fair when multiple parties submit transactions that can interact economically.
A new line of research is trying to formalize “transaction order fairness” and map out what is possible under real-world networking constraints. The core takeaway: perfect “first-come, first-served” ordering is mathematically out of reach in asynchronous distributed systems, even before considering adversaries. The practical question becomes how to approximate fairness while keeping liveness and minimizing opportunities for extractive behavior.
Key takeaways
- Perfect receive-order fairness (“first-seen, first-executed”) cannot be guaranteed on public networks because messages arrive at different times and there is no shared clock.
- Even when each node has a clear local arrival order, group preferences can conflict—captured by the Condorcet paradox—making a single linear order impossible to satisfy.
- Hashgraph’s fairness model uses a DAG of events with median timestamps to respect causal relationships while bounding how far adversarial influence can shift ordering.
- BOF-style protocols (from the Aequitas/Themis line of work) relax fairness by ordering transaction “batches” derived from Condorcet cycles, enabling stronger liveness guarantees.
Why “fair ordering” is harder than it sounds
In public blockchains, ordering isn’t just an implementation detail—it can decide who captures value and who pays. When privileged roles like block builders or sequencers determine execution order, they can potentially exploit that power through strategies that front-run, back-run, or sandwich transactions. Research on maximal extractable value (MEV) describes this as a direct consequence of who can influence ordering.
To counteract this, some proposals treat transaction ordering fairness as a third consensus objective alongside consistency and liveness. The general idea is to constrain the block producer’s ability to bias ordering beyond what the network conditions and protocol rules imply—making execution more predictable and less vulnerable to systematic exploitation.
But the most intuitive fairness notion runs into a structural limitation. In an asynchronous distributed system, there is no globally defined reception order because different nodes observe transaction messages at different times. Without a shared clock and with arbitrary message delays, no protocol can ensure that every node’s “arrival order” maps perfectly onto a single network-wide execution order.
The Condorcet paradox: why majority “first” can loop
The strongest form of fairness is often described as Receive-Order-Fairness (ROF): if most nodes receive transaction A before transaction B, then A should be processed before B. ROF sounds straightforward, but the network reality undermines it. Nodes see messages at different speeds, so different nodes can legitimately observe different pairwise “firsts.” Even if those local observations are consistent for each node, the collective can still become inconsistent.
This is where the Condorcet paradox comes in from voting theory, and it translates cleanly to distributed ordering. Even when each participant has an internal preference for which of two items comes first, the majority preference across multiple pairs can form a cycle:
- Most nodes see A before B
- Most nodes see B before C
- Most nodes see C before A
When that happens, there is no single linear ordering that satisfies all majority pairwise preferences. The implication for blockchain consensus is direct: if fairness is defined too strictly in terms of majority “first-seen” comparisons, the protocol may be unable to produce any ordering that matches the majority view across all pairs.
Because of this impossibility, systems aiming for “fairness” must adopt weaker—but more achievable—guarantees.
Hashgraph’s approach: DAG causality plus median timestamps
Hedera’s hashgraph algorithm tackles transaction ordering fairness through a leaderless, event-driven model. According to the described model, transactions are transformed into cryptographically linked events inside a directed acyclic graph (DAG). Consensus ordering then emerges from how nodes collectively observe and sign those events, rather than from a single proposer unilaterally choosing a sequence.
Operationally, when a node receives a transaction, it creates an event and gossips it to peers. Subsequent events record hashes of earlier events they have seen, and nodes digitally sign the result. This creates a provable causal structure: if one event is an ancestor (direct or indirect) of another, the protocol provides a cryptographic guarantee about which event was created first by some node.
The ordering logic then distinguishes between events with causal relationships and those that are concurrent. Events connected by DAG ancestry are ordered according to their causal dependencies. For concurrent events (those without ancestor relationships), the protocol resolves relative ordering using a “round-received” concept and then refines that using median timestamps.
Median timestamps, as described, are derived from a set of node-reported local receive times, but constrained by the hashgraph’s ancestry. That constraint matters: nodes cannot claim to have observed an event before its causal predecessors without creating detectable inconsistency in the DAG. Under the standard assumption used in Byzantine fault tolerance—fewer than one-third of nodes are Byzantine—the median timestamp should remain within a bounded range of honest timing reports, limiting adversarial ability to arbitrarily skew ordering.
However, hashgraph’s fairness is not infinite. The described research emphasizes that fairness is bounded by an adversarial “surface” where a node can still influence its gossip behavior: which events it relays first and whether it delays relaying. While the DAG cannot fabricate a false causal history, strategic propagation patterns can reshape the inputs that ultimately feed into median timestamp computation.
There is also the Condorcet paradox risk for concurrent events. The DAG eliminates ambiguity for causally linked events because the ancestry is fixed at creation. But concurrent events can still be observed in different orders by different nodes, leaving some ordering tension that is then handled by the protocol’s round and median mechanisms.
BOF protocols: fairness by collapsing Condorcet cycles
Another line of work frames fairness differently—by explicitly embracing cycles. BOF (Batch-based Order Fairness) protocols define “blocks” as sets of transactions that form a Condorcet cycle, then enforce fairness at the level of how those blocks relate, while allowing arbitrary internal ordering inside each block.
In the BOF formulation described, fairness is controlled by a parameter γ: if a sufficient fraction γ of nodes observe block b before block b′, then honest nodes cannot output b after b′. When fairness constraints induce a cyclic relation, the protocol collapses the strongly connected component (SCC) into a single batch/block, because no linear order can satisfy all the directed constraints simultaneously.
A key practical point is that this approach relaxes strict ROF requirements. When a cycle occurs, internal ordering becomes irrelevant to the fairness guarantee, since the protocol treats the entire cycle participation as atomic at the batch level. The research description notes that deterministic rules (such as a hash-based rule) may then sort transactions within the batch, but the fairness criterion does not attempt to make those internal orders correspond to any global first-seen preference.
The Aequitas protocol line is described as having weaker liveness: its strict fairness constraints require waiting for complete Condorcet cycles, and if cycles can chain indefinitely, finalization delays could grow without bound—creating a “freeze” risk.
Themis is introduced as a refinement intended to preserve γ-BOF while improving liveness. As described, Themis also builds a dependency graph and collapses SCCs during a “FairFinalize” stage, but it avoids waiting for the full cycle to close. Instead, it uses deferred ordering and “batch unspooling” so SCCs can be output incrementally while new transactions keep flowing. The result, as presented, upgrades Aequitas’ weak liveness into standard liveness with a delay bound.
Themis also addresses communication scaling concerns. In its basic form, participants exchange messages with most other nodes, leading to communication growth roughly proportional to the square of the network size. An optimized variant, SNARK-Themis, replaces much of that direct exchange with succinct cryptographic proofs, so verification can scale more efficiently as the node count increases.
Finally, the protocol design includes a mechanism to prevent denial-style manipulation. If a malicious proposer tries to exploit the system by proposing an empty block, Themis’s deferred ordering accepts a partially ordered batch and leaves exact finalization to a subsequent honest proposer, based on verifiable transaction relationships rather than discretionary choices by the current proposer. This is framed as a way to tie finalization to bounded network delay rather than arbitrary proposer behavior.
What to watch next
The central unresolved question across these approaches is how to balance fairness guarantees against the operational costs—especially complexity, communication overhead, and the practical handling of concurrency. As more consensus designs incorporate formal ordering fairness ideas, investors and builders should watch for implementations that demonstrate bounded delays in real network conditions while maintaining robustness against adversarial reordering.
Crypto World
Kalshi launches Zcash and SHIB perps as lawsuit heats up
Kalshi has expanded its CFTC-regulated crypto perpetuals lineup to 13 digital assets after launching new contracts tied to Zcash, Near Protocol, and Shiba Inu, while legal battles over the platform’s products continue to intensify.
Summary
- Kalshi expanded its CFTC-regulated crypto perpetuals lineup with Zcash and Near contracts, while Dogecoin and Shiba Inu perpetuals are also live.
- The rollout comes as CME Group challenges the CFTC’s approval of similar products and the regulator fights Kentucky over market oversight.
- Traditional finance firms, including CBOE and Charles Schwab, are increasingly exploring perpetual and prediction-style trading products.
According to Kalshi’s latest listings, the prediction market operator has expanded its “American Perpetuals” lineup with contracts tied to Zcash (ZEC) and Near Protocol (NEAR), while Dogecoin (DOGE) and Shiba Inu (SHIB) perpetuals are also now available for trading. The additions bring the total number of supported crypto assets to 13, alongside Bitcoin and other altcoins.
The contracts are available through a structure approved by the U.S. Commodity Futures Trading Commission and do not carry expiration dates.
Recent filings submitted by Kalshi show the platform sought regulatory clearance for the new products on Tuesday. Zcash perpetuals are being offered with up to 2x leverage, while Near contracts allow leverage of up to 2.6x. Shiba Inu’s perpetual contract, listed under the ticker KSHIB, also carries a maximum leverage ratio of 2x. Dogecoin perpetuals are also listed on the platform as part of the latest wave of CFTC-approved crypto contracts.
The additions follow an earlier wave of filings covering assets including XRP, Solana, Dogecoin, Chainlink, Litecoin, Bitcoin Cash, Sui, Hyperliquid, Polkadot, Hedera, and Stellar. Kalshi has already secured approval for most of those products, though contracts linked to Stellar, Polkadot, and Hedera remain under review by the CFTC.
Legal scrutiny has grown around perpetual contracts
While Kalshi continues adding crypto products, regulatory questions surrounding the structure of perpetual contracts have become more prominent. As previously reported by crypto.news, CME Group filed a lawsuit against the CFTC and Chairman Michael Selig, arguing that certain contracts approved by the agency should be classified as swaps rather than futures products.
The debate has expanded beyond crypto markets. Earlier today, the CFTC sued Kentucky in federal court after the state sought to enforce gaming laws against Kalshi, Polymarket, and brokerage partners connected to Coinbase, Robinhood, and Webull.
In its complaint, the regulator argued that designated contract markets operating under federal oversight fall under the Commodity Exchange Act rather than state gaming regulations. Kentucky, however, maintains that sports-linked event contracts meet the state’s definition of sports wagering and should remain subject to local licensing requirements.
At the same time, regulators are seeking public feedback on how derivatives products should be classified. The SEC and CFTC have jointly requested comments on definitions involving swaps and related instruments, an issue that has gained urgency as event-based trading products become more common.
Traditional exchanges are moving toward similar products
Interest in perpetual-style contracts has also spread across traditional financial markets. As reported by crypto.news, CBOE Global Markets has begun evaluating whether its continuous Bitcoin and Ether futures could be converted into perpetual contracts after crypto perpetuals generated more than $8.5 billion in trading volume on Kalshi within weeks of launch.
Charles Schwab has likewise entered the prediction-markets segment through a partnership with CBOE, introducing all-or-nothing contracts tied to the performance of the S&P 500. The brokerage joins firms including CME Group and Interactive Brokers that have recently expanded into event-driven trading products.
Outside the United States, Kalshi is facing a different challenge. An updated members’ agreement published on Wednesday shows the company has added India to its list of restricted jurisdictions.
Indian authorities have classified prediction-market platforms under the Promotion and Regulation of Online Gaming Act 2025, arguing that products involving real-money speculation on uncertain outcomes can fall within prohibited betting activity regardless of how operators describe them.
Crypto World
Cardano wallet SecondFi hit by $2.4 million exploit, up to $20 million in user funds at risk
SecondFi, the Cardano wallet formerly known as Yoroi, says it has patched a major exploit that drained roughly 16 million ADA, worth approximately $2.4 million, from 374 user wallets across three separate attacks.
The root cause was a flaw in SecondFi’s proprietary wallet generation software. The vulnerability sits at the address level, meaning simply moving a seed phrase to another wallet offers no protection. “The security risk occurs when an affected user signs a transaction,” the team said on X.
Before attackers could reach a further 129 million ADA, SecondFi said it triggered emergency rescue measures, routing the funds to an independent third-party custodian. An external accounting firm has been engaged to verify those holdings and affected users can submit claims to SecondFi.
Blockchain security firm SlowMist estimates total losses could exceed $20 million when accounting for the full range of compromised wallets and tokens, a figure that remains unconfirmed pending an independent audit.
Cardano founder Charles Hoskinson acknowledged the incident but noted the dollar amount was modest relative to other crypto hacks, though he stressed that offered little consolation to those affected. “It hurts them whenever they lose anything,” he said. “This is the unfortunate reality of crypto.”
ADA is currently trading around $0.15, its lowest level since 2020.
Crypto World
Ethereum reclaims $1,650 as Ethereum Foundation cuts 20% of workforce
Key takeaways
- The Ethereum Foundation has reduced its workforce by 20% following the completion of a major reorganization.
- ETH is up by 1% and is now trading above $1,650.
The Ethereum Foundation (EF) has completed a broad organizational restructuring that includes reducing its workforce by approximately 20%, affecting 54 employees across multiple teams.
In a blog post published Tuesday, the Foundation said the changes conclude a months-long reorganization process tied to the implementation of its updated mandate and treasury management strategy.
Ethereum Foundation introduces new organizational structure
As part of the overhaul, the EF has reorganized its operations into five core clusters: Protocol Layer, Access Layer, User Layer, Community Layer, and Institutional Layer. Two additional clusters will oversee management and operational functions.
According to the Foundation, each cluster has been designed with specific responsibilities, accountability frameworks, and internal structures tailored to its objectives.
“Each domain of work requires a different approach, is held accountable for different kinds of results, and has a different internal structure tailored to the work that needs to be done,” the EF stated.
Ethereum co-founder Vitalik Buterin revealed in a post on X that the workforce reduction comes as the Foundation pursues a significant spending reduction strategy.
The EF plans to lower annual spending from approximately 15% of its remaining treasury before 2026 to a long-term target of 5% after 2030. As part of this effort, the Foundation is reducing its budget by roughly 40% this year.
Buterin acknowledged the human cost of the restructuring, rejecting the notion that the layoffs were simply an efficiency exercise.
“Often, when an organization goes through something like this, people try to pretend that nothing of great value was lost,” Buterin wrote. “I will not try to pretend this. I respect my EF colleagues far too much to pretend that there was not much that is lost.”
The Foundation said affected employees will receive severance packages and transition assistance, similar to support provided to previous departing team members.
Ethereum price forecast: ETH risks further decline below key support
Ethereum continues to face downside pressure, with liquidation data highlighting persistent weakness in market sentiment.
On the 4-hour timeframe, ETH continues to trade below its 20-day, 50-day, and 100-day Exponential Moving Averages (EMAs), located near $1,753, $1,901, and $2,064, respectively.
The cryptocurrency also remains below a previously broken descending trendline around $1,729 and a key horizontal resistance zone near $1,741. These technical barriers suggest the broader bearish structure remains intact.
Ethereum is now approaching the important support level at $1,611 after being rejected near the convergence of the descending trendline and the 20-day EMA.
A decisive break below $1,611 could expose the next major support zone at $1,524. If selling pressure intensifies, additional downside targets emerge at $1,404 and potentially $1,155.
Unless buyers reclaim key resistance levels, Ethereum’s price action remains vulnerable to further losses in the near term.
Crypto World
XRP News: Why Ripple’s 9-Year Clock Divides the Community
Australian lawyer and prominent XRP community commentator Bill Morgan has been in the news headlines as he called on Ripple to relock less of its monthly 1 billion XRP escrow release. According to Morgan, accelerating the path to full circulating supply would establish XRP as a credible hard money asset and eliminate the supply overhang that continues to weigh on sentiment.
The argument is not new in outline, but the specifics of Morgan’s framing push it into sharper territory, and Ripple’s own CTO Emeritus has already drawn a clear line on how far the company is willing to go.
With 32.74 billion XRP still locked in escrow and the current release pace stretching the full-circulation timeline to roughly nine years, the structural math gives Morgan’s argument its weight. The question the XRP community is now openly debating is not whether the overhang is real, but whether Ripple has both the incentive and the flexibility to compress that timeline.
Discover: The Best Crypto to Diversify Your Portfolio
Ripple Supply Overhang
Ripple established its escrow system in 2017, placing 55 billion XRP into 55 separate on-ledger contracts, each releasing 1 billion XRP on the first of every month. The mechanism was designed to create a predictable, auditable supply and avoid an unannounced dump from a centralized treasury.
However, what it also created, by design, was an indefinitely extendable schedule: Ripple takes what it needs for operations and institutional distribution, then relocks the remainder into new contracts, effectively rolling the timeline forward month after month.
Morgan’s position, stated publicly on X, is direct:
The logic is three-layered. First, relocking less shortens the nine-year horizon. Second, full circulation removes the psychological shadow supply that suppresses valuation. Third, a fixed, fully-circulating crypto supply is structurally more credible for institutional participants who price assets on known fundamentals rather than unknowable future release schedules.
It is worth noting that Morgan is looking for an argument. He has previously defended the escrow mechanism itself against claims that it is a deliberate price-suppression tool. He also pointed out that XRP ran from roughly $0.50 to above $3.00 between November 2024 and January 2025 while monthly releases continued uninterrupted. His current call is for faster completion of a process he considers legitimate.
Discover: The Best Token Presales
David Schwartz Draws the Line
Ripple CTO Emeritus David Schwartz has not endorsed acceleration, and he has flatly rejected the most radical version of the proposal circulating in the XRP community: burning the escrowed supply outright.
Schwartz cited Stellar’s token burn as his primary cautionary reference. He argues that supply destruction produced a short-lived market reaction rather than a durable valuation re-rating. His broader defense of the current model is that Ripple voluntarily relocks whatever XRP it does not immediately need.
On the timeline question specifically, Schwartz acknowledged the inherent uncertainty:
“It’s hard to predict because you have to make assumptions about how much XRP Ripple uses and how much gets put back into subsequent escrow months.”
Schwartz’s position is structurally consistent with how Ripple has managed the escrow since inception. The company has positioned measured, predictable distribution as a feature, not a constraint. Changing that calculus would require Ripple to decide that the reputational and institutional benefits of acceleration outweigh the risks of increased near-term sell pressure. Basically, a trade-off that the company has not yet indicated it is willing to make.
Ripple’s recent MiCA regulatory approvals in Europe reinforce the pattern: the company is building compliant infrastructure, and supply stability is part of that institutional pitch.
Don’t Miss Out on Our $1,000 USDT Airdrop on ByBit
What the Community Debate Actually Reveals About XRP Beyond the News Headlines
Beyond the news headlines, the split inside the XRP community maps cleanly onto two different theories of what XRP is supposed to be. The pro-acceleration camp, aligned with Morgan, treats the hard money narrative as the primary long-term value proposition. A fixed, fully-circulating supply that can be evaluated on demand fundamentals alone. The pro-current-pace camp treats Ripple’s controlled distribution as an asset for institutional credibility, not a liability.
A third concern runs underneath both camps: if Ripple releases more net XRP per month without a corresponding increase in demand, the additional supply hits the market as sell pressure. XRP’s current price action does not obviously signal that the market is capacity-constrained on the demand side in a way that would absorb larger monthly net releases cleanly.
The token burn option, meanwhile, is effectively closed. Schwartz’s Stellar reference reflects a settled internal view that destroying escrow reserves would produce noise and would permanently eliminate the optionality Ripple currently holds.
Discover: The Best Crypto to Diversify Your Portfolio
The post XRP News: Why Ripple’s 9-Year Clock Divides the Community appeared first on Cryptonews.
Crypto World
Trump Cancels Signing of Housing Bill with CBDC Ban
US President Donald Trump cancelled the signing ceremony for a housing bill containing a ban on a central bank digital currency (CBDC) as he looked for Republicans in Congress to prioritize a controversial voting bill.
In a Wednesday morning Truth Social post, Trump said that the signing for the 21st Century ROAD to Housing Act, passed by the US Senate and House of Representatives, would be cancelled “until such time as we pass the desperately needed SAVE America Act.”

Source: Donald Trump
The housing bill, passed by the House on Tuesday, included a provision barring the US Federal Reserve from issuing or creating a CBDC “or any digital asset that is substantially similar” until the end of 2030. However, the legislation also included a carve-out for stablecoins, allowing “dollar-denominated currency that is open, permissionless and private.”
Many had expected Trump to sign the bill, aimed at tackling housing affordability, into law on Wednesday without issues. However, the president said in March that he would “not sign other bills” until the SAVE America Act was passed.
The legislation would require voters to provide proof of US citizenship in person to register.
Related: US Senate passes housing bill with CBDC ban until 2030
Senate Republicans largely supported the housing bill, which passed the chamber in a 85-5 vote on Monday. Tim Scott, the Republican who chairs the Senate Banking Committee, expressed support for the legislation as recently as Wednesday morning before Trump’s announcement.
Could Trump’s position also impact crypto market structure?
Given the president’s opposition to signing any bill into law other than the SAVE America Act, it’s unclear whether Trump also intends to veto or delay signing of crypto-related bills.
As of Wednesday, the US Senate was still waiting to potentially vote on the Digital Asset Market Clarity (CLARITY) Act, a bill expected to change the roles of financial regulators in overseeing and enforcing digital asset laws. However, Trump said in May that he intended to codify a “future-proof digital asset market structure,” likely referring to CLARITY.
Magazine: AI is banking the unbanked in Africa… faster than crypto
This is a developing story, and further information will be added as it becomes available.
Crypto World
From Wallets to Agents: CoinFello’s Bet on the Future of DeFi (Interview)
DeFi has long promised open and self-custodial finance. But for most users, actually using it still means juggling through wallets, dApps, bridges, pools, approvals, and risks that are very hard to understand in real time, especially for someone who’s relatively new to the industry.
CoinFello believes that the experience is ready for a major shift. With Fello 1, the company is building a self-sovereign AI agent designed to help users interact with DeFi through plain language while keeping complete control over their wallets and keys.
In the following interview with the founder, we go through why agents could become the primary interface for onchain finance, how controlled delegation can make automation a lot safer, and why liquidity provision is one of the first major frontiers for agent-powered decentralized finance.
CoinFello is positioning itself as a self-sovereign AI agent for DeFi. In simple terms, what problem are you trying to solve that wallets and dapps have not solved yet?
CoinFello is a completely new way to understand, use, and automate smart contracts.
The previous paradigm required users to create a wallet, navigate many disjointed websites, connect that wallet to a website, and then almost blindly trust that the smart contracts on that website do what the website promises they do. This made DeFi inaccessible, extremely complicated, and dangerous, and was one of the primary barriers to broader DeFi adoption.
CoinFello’s approach is to give users an agent that can interface directly with the smart contracts through a Claude-like user experience that people are familiar with. The agent isn’t just easier to use, it also opens up new frontiers of automation, where agents can act on behalf of users to accomplish virtually anything in DeFi: batch swap multiple tokens and bridge them across networks, discover advanced yield strategies, optimize existing deposits, take out a loan and automate payments, and a whole lot more. CoinFello makes doing these things super simple.
Fello 1 is described as a general-purpose DeFi agent rather than a narrowly integrated assistant. Why is general-purpose execution important, and what does it unlock for users that protocol-specific interfaces cannot?
DeFi is not one app or use case.
DeFi is an ecosystem of contracts, protocols, pools, vaults, bridges, and networks that constantly change.
Unfortunately, most of the crypto AI agent products on the market are just trading bots connected to some centralized API. If an agent only works through narrow integrations, it will always be limited to a few narrow use cases. That’s not how people use the internet (web browsers), their phones (extensible smartphones), AI agents, or even Ethereum itself. All of the great innovations were fundamentally extensible.
General-purpose execution means Fello 1 can reason about and interact with EVM-compatible smart contracts more broadly, instead of being locked into a small set of pre-built workflows. That unlocks all kinds of use cases that we ourselves never anticipate or integrate with. New pools, new protocols, and new opportunities can become accessible faster, without waiting for a dedicated front end or a code release for every specific action.
For the user, the benefit is simple: they do not need to jump between ten different interfaces to complete one DeFi strategy. They can describe what they want, review the steps, and execute across protocols from one agentic interface.
One of CoinFello’s core promises is that users can interact with DeFi through plain language while keeping custody of their wallets and private keys. How do you balance ease of use with the security expectations of self-custody?
We’ve tried to bring self-custody principles to the agentic era. This means that funds must remain in a self-custodied wallet, and agents should have guardrails enforced on them that define what funds they can access, in what ways those funds can be used, and for how long that agent has access to those funds.
With Fello 1, users keep their wallets and private keys. The agent operates through limited permissions that the user chooses to grant, and users review and approve transactions before execution. Plain language is the interface layer, not a replacement for consent. We fundamentally disagree with the approach of transferring funds to a centralized trading bot and hoping for the best.
The goal is to reduce cognitive overload without reducing user sovereignty. Fello can do the math, explain the route, surface the risks, prepare the transaction, and monitor positions, but the user remains in control of what permissions exist and what actually gets executed.
The Fello 1 launch puts a lot of emphasis on liquidity provision, including Uniswap V2, V3, and V4 positions, fee tiers, impermanent loss, and live position monitoring. Why did you choose LP management as such an important use case for the product?
Liquidity provision is one of the best examples of DeFi’s promise and its complexity. Concentrated liquidity can be a powerful yield opportunity, but it asks a lot from the user. You need to understand price ranges, ticks, fee tiers, pool selection, position sizing, impermanent loss, and when your liquidity is in or out of range.
That is exactly the kind of experience where an AI agent can create real value. Fello 1 can handle the mechanical and analytical parts: identifying LP strategies, doing the math, monitoring the position, explaining whether it is in range, showing the real return, and helping the user understand the trade-offs.
We chose LP management because it is not just a button-clicking problem. It is a decision-support problem. If we can make LPing understandable and manageable for more users while keeping them self-custodial, that is a major step toward making DeFi more mainstream.
AI agents in crypto are often associated with automation, but CoinFello says Fello 1 is not designed as an autonomous trading bot and that users still review and approve transactions. Where do you draw the line between helpful automation and too much delegation?
To be clear, we are building for automation, and we deeply believe users should be able to delegate approval for tightly defined automations to their agent. These are very complex problems to solve, so we’ve been working to expand the agent’s capabilities and the kinds of automation the user can create through the permissions and delegations we’ve been championing.
You previously led operations at MetaMask, one of the most important wallet products in crypto. What did that experience teach you about user behavior, wallet UX, and self-custody that directly shaped CoinFello?
MetaMask had a very radical vision in the early days of Ethereum. Most people at the time were building “use case wallets” with a handful of brittle integrations. MetaMask sought to do something else: create a permissionless and extensible wallet that could be used with any smart contract protocol.
We’ve brought the same radical values and vision to CoinFello that we previously used to build MetaMask. While most in the agent space are building narrow “use case bots,” our goal is different: to bring users onchain, and give them access to the entire decentralized web.
We also learned about the limitations of trying to solve the safety and user experience problems at the wallet layer. Wallets are forced to maintain endless integrations with third party protocols, and these integrations make their products slow to innovate, highly prone to bugs, and generally dangerous because the wallet still can’t understand what a smart contract *actually does.*
CoinFello is how we will solve these problems for the next wave of on-chain innovation.
CoinFello relies on a delegation model where users grant agents limited permissions that can be modified or revoked. What does a safe permission system for onchain AI agents need to look like as these tools become more powerful?
A safe permission system needs to be specific, limited, transparent, and revocable.
Users should not have to grant broad, unlimited authority over funds to an agent. Permissions should be scoped by action type, asset, protocol, amount, duration, and any other relevant rule the user cares about. The user should be able to see what permissions exist, understand what they allow, and revoke or modify them at any time.
As agents become more powerful, permission design becomes one of the most important parts of the stack. The future is not giving the AI your keys. The future is controlled delegation, where the agent can help execute within boundaries that the user defines. That is how we get the benefits of automation without sacrificing self-sovereignty.
Looking ahead, do you think the future of DeFi will still be built around users manually navigating dapps, or will agents become the primary interface for onchain finance?
I think dapps will still matter, but agents will become the primary interface for most users.
Today, DeFi still looks like the early internet in some ways. Users manually navigate different websites, learn different interfaces, and stitch together actions themselves. That works for power users, but it does not scale to broader adoption.
Agents change the interface from navigation to intent. Instead of asking users to know exactly which protocol to use and which buttons to click, they can say what they want to accomplish, compare options, understand risks, and approve execution.
The future of on-chain finance will still be open, composable, and self-custodial. But the way users access it will become much more conversational, automated, and personalized. Our view is that agents will become the execution layer that makes DeFi usable for the next wave of users.
Disclaimer: The content shared in this interview is for informational purposes only and does not constitute financial advice, investment recommendation, or endorsement of any project, protocol, or asset. The cryptocurrency space involves risk and volatility. Readers are encouraged to conduct their own research and consult with qualified professionals before making any financial decisions. This interview was conducted in cooperation with CoinFello, who generously shared their time and insights. The content has been reviewed and approved for publication in mutual understanding. Minor edits have been made for clarity and readability, while preserving the substance and tone of the original conversation.
The post From Wallets to Agents: CoinFello’s Bet on the Future of DeFi (Interview) appeared first on CryptoPotato.
Crypto World
Andrew Cuomo Tapped to Co-Chair OKX-ICE Crypto Joint Venture

Andrew Cuomo will co-chair a joint venture between OKX and Intercontinental Exchange, the parent of the New York Stock Exchange, the companies disclosed Monday. The former New York governor takes the role as ICE's strategic push into crypto markets reaches its highest-profile political appointment… Read the full story at The Defiant
Crypto World
Aave (AAVE) gains 5.9% as index moves higher
CoinDesk Indices presents its daily market update, highlighting the performance of leaders and laggards in the CoinDesk 20 Index.
The CoinDesk 20 is currently trading at 1682.86, up 0.5% (+8.62) since 4 p.m. ET on Tuesday.
Fifteen of 20 assets are trading higher.

Leaders: AAVE (+5.9%) and ICP (+2%).
Laggards: XLM (-1.4%) and ADA (-1.2%).
The CoinDesk 20 is a broad-based index traded on multiple platforms in several regions globally.
-
Fashion5 days agoWeekend Open Thread: Miami – Corporette.com
-
Entertainment4 days agoRenter of Home in Anne Heche Crash Denies Settlement With Son
-
Tech2 days agoMicrosoft accidentally kills epic Outlook email threads
-
Sports21 hours agoTwo goals and an assist by sheer aura: Cristiano Ronaldo just entered the World Cup chat
-
Business4 days agoSoccer-U.S. defends Iran World Cup travel restrictions, says discussions ongoing
-
Crypto World12 hours ago
Bitcoin (BTC) Dips Below $62K, Ethereum (ETH) Plunges 6% Daily: Market Watch
-
Politics6 days agoBBC Reporter Discusses Cross Party Criticism Of Trumps Iran Deal
-
Crypto World10 hours agoSecuritize Wraps Roubini's SEC-Registered ETF as Dubai VARA Digital Security
-
Business15 hours ago
Entergy settles forward sale agreements, raises $672 million in cash proceeds
-
Business5 days agoWall Street Week Ahead: Investors see Micron earnings as pulse check of AI rally momentum
-
Politics4 days agoAndy Burnham and the meaning of Makerfield
-
Tech6 days agoAWS enters the context layer race with a graph that learns from agents, not manual curation
-
Crypto World4 days ago
Can Charles Hoskinson Really Rescue Cardano?
-
NewsBeat5 days agoKeir Starmer Allies Question His Chances For No 10
-
Crypto World5 days agoHIVE shares jump as $220M AI deal speeds Bitcoin mining pivot
-
Crypto World4 days agoJake Chervinsky accuses CME of protecting derivatives monopoly
-
Tech2 days agoNearly 7,000 fake Amazon domains registered ahead of Prime Day 2026, researchers warn
-
Entertainment5 days agoJose Alvarado Wants Taylor Swift at More Knicks Games
-
Tech3 days agoSignal’s Meredith Whittaker says AI chatbots ‘are not your friends’ and calls Copilot agents a backdoor
-
Business6 days agoBrexit cost 6% of UK economy, Bank of England company data suggests

LEGAL EXPERT BILL MORGAN URGES RIPPLE TO UNLOCK XRP TOKENS FASTER
(@Xrp_Guru1) 
You must be logged in to post a comment Login