DeFi BlueOrange (@BlueOrange522) header
DeFi BlueOrange (@BlueOrange522) profile picture

Founded @elaralabs | @tsinghua_Uni @uchicago alumnus | AI + DeFi | Runner

block
Joined June 2024
Photo by DeFi BlueOrange (@BlueOrange522)Photo by DeFi BlueOrange (@BlueOrange522)Photo by DeFi BlueOrange (@BlueOrange522)Photo by DeFi BlueOrange (@BlueOrange522)Photo by DeFi BlueOrange (@BlueOrange522)Photo by DeFi BlueOrange (@BlueOrange522)Photo by DeFi BlueOrange (@BlueOrange522)Photo by DeFi BlueOrange (@BlueOrange522)Photo by DeFi BlueOrange (@BlueOrange522)Photo by DeFi BlueOrange (@BlueOrange522)
DeFi BlueOrange retweeted
For the first time, institutions are really coming on-chain in size, and they chose @0xfluid. We are working deeply with the biggest TradFi asset managers and co-designing markets with them. The reason why they want to deploy with us is simple - Fluid has the most advanced and flexible infrastructure in DeFi. Institutions want to be in full control of their markets. No institution can work within a limited, immutable system where they can not change the oracles or LTVs if required. Fluid provides them with full control over every parameter, gives access to the most advanced lending market algorithms, extreme DEX efficiency, and many more tools within the same liquidity layer. And Fluid is the only DeFi protocol with an equivalent deployment across EVM and Solana. We are also creating bespoke solutions for them, including a legal framework for their markets. Our goal is to work with a few, very valuable partners and grow their markets to tens of billions instead of trying to onboard every DeFi risk curator with small, fragmented markets. We are proud that @Bitwise is our first partner, and they will become a multibillion risk curator onchain within a few weeks, with many new RWA markets in the pipeline. Stay Fluid 🌊
One of the world's largest crypto-native asset managers just curated a lending market on @jup_lend. @Bitwise. @Ethena. Live on @Solana. Powered by Fluid. 🧵
6
10
1
87
7,119
DeFi BlueOrange retweeted
+10% on USDC, one of best yields on stables in DeFi right now 🌊🌊🌊 Lite USD vault has incurred no losses to users and realtime reserves and active positions can be tracked on our status page: fluid.io/lite/1/status/usdc
Fluid Lite USD earning 11.74% APY on USDC 🌊 fluid.io/lite/1
6
7
62
8,096
centralized security + decentralized freedom = future of finance
The Arbitrum Security Council has taken emergency action to freeze the 30,766 ETH being held in the address on Arbitrum One that is connected to the KelpDAO exploit. The Security Council acted with input from law enforcement as to the exploiter’s identity, and, at all times, weighed its commitment to the security and integrity of the Arbitrum community without impacting any Arbitrum users or applications. After significant technical diligence and deliberation, the Security Council identified and executed a technical approach to move funds to safety without affecting any other chain state or Arbitrum users. As of April 20 11:26pm ET the funds have been successfully transferred to an intermediary frozen wallet. They are no longer accessible to the address that originally held the funds, and can only be moved by further action by Arbitrum governance, which will be coordinated with relevant parties.
1
21
Fluid主网目前ETH APY是32%, Fluid上面的wrsETH的抵押物是~$8M, 借款WETH是~$7M. 黑客盗走了rsETH 18%的流通量。按照最坏情况,假如Kelp官方把损失平均给所有rsETH持有人,则Fluid上面的抵押物打82折计~$6.5M, Fluid的绝对风险暴露只有$500K, Fluid官方表示会全额Cover. ETH存款人恐慌提款,导致收益率飙升,个人认为是一个低风险博收益的机会。DYOR
There are two apps I’m currently lending ETH for absurdly high rates, not suffering from any rsETH bad debt afaik but benefitting from the huge surge in ETH lending APYs. @0xfluid @sparkfinance Lend Waiting for more information to come from Kelp and then more importantly from Aave. Aave will survive all this but it’s a big stress test for Umbrella (which can’t cover the total estimated bad debt). There is nothing wrong with doing nothing here. Wait for more info.
1
6
347
Just swapped my remaining wrsETH to WETH on Linea with around ~20% slippage. The contagion is still ongoing, be careful.
The fallout from the Kelp rsETH exploit is going to be messy and could potentially be quite a bit more severe than some people are making out right now. It seems rsETH on mainnet is technically still backed, but, there's no liquidity to sell rsETH, and with rsETH contracts paused, there’s currently no usable redemption path either. In the unlikely case they socialised the loss across all rsETH holders, it would be worth something like 81.25% (1 - $300m/$1.6b) of its original value. I don't think they will do that though. It would likely push a number of large positions on Aave towards undercollateralisation and risk creating bad debt. That alone would be enough to trigger a long and painful lawsuit. So realistically rsETH holders on L2s are likely going to swallow the loss. Who are they? Why did they have rsETH on L2s in the first place? Could be other DAOs or funds etc who've taken a huge hit. That alone could have consequences we won't know about for some time. Impacted individuals on L2s will likely consider their own legal action to force socialisation, potentially prolonging the delay before redemptions are opened. Either way, once redemptions are eventually opened, it's unlikely any lending protocols would re-allow collateralisation, so there will be need to be a massive unwind of huge volume of rsETH/ETH looping trades. All those looping trades are currently massively negative ROE. Aave ETH utilisation is currently at 100% with ETH borrow rate at 8.71%. Since staked ETH yield is around 2.5%, the ROE for any LST or LRT borrow or looped borrow is anywhere between -6.21% and around -90%, depending how degen people are. So we could see an unwind of lots of LST loops aside from just rsETH/ETH ones. The normal path to unwind a loop is to swap collateral and repay, but this is unlikely to be possible for such a large amount of unwinds at once, and certainly won't be feasible for rsETH unless someone puts up significant liquidity for it. When the swap and repay path fails, you normally have to withdraw as much collateral as you can, manually redeem, repay some debt, withdraw more collateral, and so on. Here's the kicker. If rsETH is no longer collateral and no longer has borrowing power, this makes it much more difficult for people to manually unwind as well. If people get stuck for longer periods paying huge negative ROE for too long, and there’s no liquidity to liquidate them, their equity gets eroded. Once debt exceeds recoverable collateral value, bad debt appears, and can keep worsening as interest accrues and the position remains unresolved.
51
DeFi BlueOrange retweeted
The Euler Vault Kit (EVK) is the factory for onchain lending markets. One vault per asset. Fully isolated. Permissionless to create. Vaults connect through the EVC to enable cross-collateralization, multi-vault strategies, and composable lending positions. Every lending market on Euler starts here.
4
8
1
38
3,745
DeFi BlueOrange retweeted
At @0xfluid, we are working on most advanced oracles in DeFi which will allow us to configure every small config on: What pricing to use, when to use it and how to use it. Here what we will be able to control: - Use different price for user's operation & liquidations. For peg assets, use market pricing for user's operation and fundamental pricing for liquidation. If market price differs more than 2% than fundamental pricing then pause withdrawals & borrowings. Allowing protocol to not take any extra risk. - For an asset used on collateral side, use more "conservative pricing" for user's operations while "realistic pricing" for liquidation. - For an asset used on debt side, use more "aggressive pricing" for user's operations while "realistic pricing" for liquidation. At any time, the pricing between liquidate & operate (user based operations) differs by x%. Then limit protocol from taking any new risk. ---------- In short, protocol will use both market price and fundamental price depending on action and go into temporary partial lockdown when pricing deviates by certain %.
8
18
3
128
19,976
官方出完整版说明了。关于Pharos及其合作方的的详细分析也可以看我昨天的Thread。
32
1/7 Pharos 最近推出了 pAlpha Vault,14%+ APY,底层是RWA资产。 pAlpha Vault 的逻辑: - 你存入 USDC(以太坊主网) - 存款分三个阶段(见2) - Vault 底层投两类资产:70% 新兴市场消费贷 + 30% 美国短期国债 - 赚取利差后返还给你,全程以 USDC 计价和支付 发起方是 Pharos Network,系蚂蚁系背景 + 港股上市公司战略投资 + 近十亿美元估值,在 RWA L1 赛道中属于顶级资源禀赋。 容量 $15M(Phase 1)。总上限 $50M,手续费为收益的10%。 🧵 一条Thread带你拆解该Vault的收益、底层资产和保护机制 👇
2
125
6/7 怎么参与? 参与流程: 1. 打开 Yield Network 的 pAlpha Vault 页面(目前已存超过25%) : app.yieldnetwork.io/?categor… 2. 注册邮箱 + 提交钱包地址 3. 审核通过(一般很快) 4. 状态变为 Request ✅ → Access ✅ → Deposit 5. 连接钱包,存入 USDC(以太坊主网) 存入后获得 receipt token,到期按升值比例赎回本金 + 收益(USDC)。
1
70
7/7 个人观点: 个人认为值得投资,有蚂蚁系的背书,不必太过于担心新兴国家信贷的信用风险。 蚂蚁系对 RWA 的布局野心已显露无遗,且在境内外同步推进: 境内:蚂蚁数科通过"两链一桥"架构(蚂蚁链 + Jovay + 跨境桥),联合香港合规沙盒做基础设施输出,走的是持牌、可控、to B 的路线。 境外:Pharos 作为去中心化路线的代表正全速推进——$950M 估值、RealFi Alliance 生态联盟、主网即将上线。 pAlpha Vault 的 $15M 规模虽小,但它承载的是整条路线的信誉首单。对 Pharos 来说,这一单做砸的代价远大于这 $15M 本身——它会动摇所有后续 RWA 产品的信任基础。 nfa, dyor!
68
DeFi BlueOrange retweeted
Hot take: most companies don't need devrel they need integration engineers and solution architects. Blockchain software is now used by enterprises, which means we need to actually graduate into the mindset of: how can we best service our customers? There was a flaw in the early DeFi days that teams needed an active community of devs working on top of your protocol, that need devrels jumping in every hackathons across the world, having community calls, doing youtube videos, etc. The truth is: - it's 95% a waste of time and money: hackathons are very expensive, sending a few team members is very expensive as well, and the community of developers you create does not bring much value. - it's even more true now than it was in 2020/21: the space is more mature, instits and classic web2 companies are all coming onchain. they dont need devrel they need to be reassured on tech, business, legal first - people chasing hackathons usually don't care about your product/protocol or don't care about building a long-term product (they usually care about leveling their skills or grabbing money so they can attend the next hackathon in Bali). The few that do end up building a product have 95%+ of failing and the few that survive won't bring much value before a year or so - yes it's a lot of fun for those devrels that you hired, but the right question is: where could this money be better spent? What has the biggest ROI? You have to restart from 1st principle - you'd better allocate that money on sales people to close customers - and you'd better have solution architect and integration engineers that can provide great support to those customers - you'd rather focus your energy on existing and live projects for which you're truly solving a problem *now* - you have to realize that in many B2B companies, the one who makes the decision are often not the developers but the exec or product people Dont get me wrong, i do think having comprehensive documentation is important, i do see value for some projects in doing hackathons to battle-test your product, or hire talents or whatever, i do see value in having a developer community. But I strongly think that people should apply more 1st principle thinking before allocating significant resources to creating a community of developers.
13
5
4
101
7,493
AAVE占了DeFi 30%以上的TVL,支付$5M都不够cover chaos labs费用的话。那还有别的协议能cover吗?
We respect the decision of Chaos Labs to step down as one of the two risk managers for the Aave DAO. We want to thank Chaos Labs for their work over the years. They have been a valuable partner to the Aave DAO, and their contributions have helped Aave grow and mature. There is no disruption to the Aave Protocol, its smart contracts, asset listings, or network deployments, and we will work closely with Chaos Labs during the offboarding process. Aave operates with a two-layer economic risk model that has been managed by Chaos Labs and LlamaRisk. While this model does create tension between risk managers from time to time, we believe it has been valuable in safeguarding Aave. We strongly support maintaining a two-layer approach and will continue supporting this model, alongside an additional technical risk layer managed by Aave Labs. Over the past weeks, we held discussions with the Chaos team regarding next steps, as Chaos was exploring winding down its risk consultancy services business (and had already begun winding down some agreements with other protocols). We were generally supportive of a 2× increase in their risk management payment to $5M, but not supportive of $8M without a separate addendum at a later stage if the workload proved higher than anticipated. What we did not support were other elements of the proposal, including setting Chaos Labs as the sole risk manager and using Chaos Labs price oracles instead of Chainlink on all new deployments, as well as adopting Chaos Labs vaults as the default vaults (which are not yet audited) for all B2B integrations. While we do not see issues with these Chaos products or their future viability, we strongly believe that, given the scale of the Aave protocol, it should maintain at least a two-layer risk management model and vendor lock-in free vaults. Additionally, given the strong track record with Chainlink, we prefer to continue supporting Chainlink for price oracles, which our users are currently more comfortable with at scale. Regarding Aave V4, the architecture introduces isolated risk markets through Spokes, new liquidation logic, and governance-controlled parameters that give the DAO more granular control over how it manages risk across different markets and assets. We held multiple risk calls with Chaos Labs employees in attendance well before V4 went live, and the feedback we received during those sessions does not align with the concerns expressed in their post. For the immediate future, Aave Labs will work closely with LlamaRisk to ensure a smooth transition and uninterrupted risk coverage for the protocol. LlamaRisk already serves as a risk contributor to the Aave DAO and has deep familiarity with the protocol’s architecture and parameters. We support LlamaRisk increasing their budget to accommodate this additional workload and expanding their team as needed. Aave Labs will also contribute engineering and analytical resources wherever necessary to support this transition. We also want to thank the entire Chaos Labs team for their contributions over the years, as they have helped bring the protocol we built into its current level of maturity.
1
63