Brink

536 posts

Brink banner
Brink

Brink

@BrinkTrade

Composable Intent-Centric protocol for Web3 apps | Discord: https://t.co/tyu5acKfoE

Katılım Ağustos 2020
318 Takip Edilen4.4K Takipçiler
Brink retweetledi
Cracked Labs
Cracked Labs@cracked_labs·
@nocontextmemes I know half of y'all got absolutely cooked by a girl with this pfp at one point 😭
Cracked Labs tweet media
English
27
84
6.6K
214.2K
Brink retweetledi
Nomial
Nomial@nomial_io·
Intents for everyone, with everyone. Nomial is proud to support the Open Intents Framework We're building the future of a unified Ethereum, alongside 30+ teams working toward this shared goal
Nomial tweet media
Ethereum Foundation@ethereumfndn

Announcing the Open Intents Framework ✨ Ecosystem-wide interop, accelerated by 30+ teams from all corners of Ethereum. A modular, open framework to make it seamless for any chain to get intents into the hands of users & improve cross-chain UX. ➡️ openintents.xyz

English
1
3
28
3.3K
Brink retweetledi
Offchain
Offchain@Offchain·
Say hello to true interop for @ethereum. In collaboration with many teams, we're building a universal intents engine. The goal? Seamlessly connect @arbitrum chains and other Ethereum L2s with < 3s crosschain swaps and transfers to achieve flawless UX. 🧵
Offchain tweet media
English
145
250
1K
399.2K
Brink retweetledi
Zaryab
Zaryab@zaryab_eth·
Intent-solver systems are the silent engine behind Chain Abstraction I studied 10+ Intent-Solver-Systems and created strong Mental Models for: a. how they work, b. their core components, c. different zones in these system, d. important players & their positioning Grab your popcorn🍿 Enjoy the Short Summary Below. Read the full article for an extensive overview. ( Link Below 👇) --- An Intent-Solver system typically has 5 core components: 1. Intent Expression 2. Solver Selection 3. Intent Fulfilment 4. Proof of Completion 5. Solver Settlement A system's approach toward implementing these components decides its overall efficiency, decentralization, speed & liveness. Let's dive into each component --- 1. Intent Expression The core responsibility of this component is to: - Accurately capture the user’s intent. - Allow users to authorize their funds required for this intent, - Organize captured intent for solvers to interpret accurately. --- 2. Solver Selection Solver selection involves specialized on-chain actors (solvers) competing to fill the user's intents. Ideally, the system should have a fair mechanism to select the right solver for the job. 2.a Who is The Right Solver It varies based user’s need and systems design but the most common metrics include: - Faster Solvers: Solvers who can fill your intent quickly. - Efficient Solvers: Solvers who can provide efficient results, i.e., better rates for cross-chain swaps, for instance. 2.b Why a Fair Mechanism? - Ensures healthy competition, preventing a few solvers from dominating. - Avoids monopoly risks like high fees, delayed executions, and order manipulation. - Reduces liveness risk by not relying on a few solvers, preventing system halts. - Improves user experience with better rates and fairer fees. - Keeps the solver network decentralized, benefiting users and the system. 2.c Ways of Selecting a Solver? - First Come, First Served (FCFS) - Request for Quote (RFQ): Users submit orders, solvers bid within a timeframe, optimizing for price - Batch Auctions: Orders are batched and processed together. - Dutch Auctions: Starts with a high price, decreasing until accepted. Quick Byte: Unfortunately, most systems currently fail to implement a fair selection mechanism and this is primarily due to a lack of solvers in the ecosystem. Operating a solver is hard but with standardizations, efficient settlements, permissionless solver entries, etc, the solver competition and selection should become fair and better. --- 3. Solution Generation/Intent Fulfillment This component is primarily about how quickly and efficiently the selected solver can: - Generate solution for user’s request - Execute the user’s intent. Solvers use different techniques to prove their efficiency in the system such as algorithms to find the best route for swaps, mechanisms to protect users from MEV, implementing optimized mechanisms to save gas, etc. However, the crucial aspect is the access to liquidity to fill the user’s intent as solvers often front-liquidity using their own inventory without waiting for finality. Therefore, The easier the access to liquidity, the faster & more efficiently the solvers can fill the orders, resulting in Better UX for users. 3.a Accessing Liquidity - The common sources are AMM, Dex Aggregators, Private Market Makers, etc. Some Innovative Solutions for this are: a. Direct P2P Order Match - The “Coincidence of Wants” Way ( @CoWSwap , @EverclearOrg ) a. Borrowing Liquidity - The @nomial_io Way b. Solver Co-Operation instead of Competition - The @khalani_network Way c. Settlement via Netting ( and also CoW) - The @EverclearOrg Way. All of these approaches are explained in detail in the article. Check it out. ---- 4. Proof of Fulfilment After successfully filling the user's intent on the destination chain, the solver must to provide some proof to the system to prove that the intent was accurately filled. This is crucial because the solvers have risked finality and used their liquidity to fill user’s intent. However, without proof of their work, the system cannot settle ( reimburse) the solver There are different proof systems available currently that these systems leverage: - General message passing - Oracle Based Systems: - Storage Proofs - Light Clients - ZK proofs Quick Byte: While some proof systems are trust-based, some are trustless ( like storage proofs, zk proofs or light clients ). With the use of trustless proof systems, however, the reliability and security of the system increase. ---- 5. Settlement The Final Component. This is where solvers are reimbursed/settled for all the liquidity they fronted or intents they executed with their funds. 5.a This component must ensure: a. Reliable Settlement: Solvers must be paid accurately and promptly to maintain trust. b. Fast & Efficient Settlement: Quick settlements help solvers maintain liquidity, enabling better execution and pricing. c. Fair & Secure Settlement: Ensure solvers are fairly compensated and prevent system exploitation, with mechanisms to penalize bad actors. 5.b Settlement Techniques a. Cross Chain Messages and Smart Contract Based Settlements: Chain A uses a smart contract to receive messages from Chain B and execute settlement logic when conditions are met. Examples: @Uniswap's Reactor Contract, @deBridgeFinance 's DLN Bridge, CowSwap b. Optimistic Settlement: Assumes transactions ( intent fulfillment) are valid unless their accuracy is challenged, reducing verification time and resources. This significantly reduces the time and resources needed for verification. Examples: @AcrossProtocol , @mach_exchange c. Netting-based Settlements: @EverclearOrg addresses this by allowing most of the rebalancing activities ( approx 80% ) to be netted against one another, leading to a potential tenfold reduction in costs. Now, the crux of Everclear is the fact that it allows solvers, or fillers, to socialize the costs of rebalancing by netting settlements against each other, significantly reducing the financial burden associated with moving funds across chains. --- That was a brief glance at how Intent-Solver Systems work. Read the article to get a clear understanding of each of these components in detail as well as the concerns and improvement scope in some of them ( which I couldn't cover here ). Link Below 👇 Before I wrap, Special thanks to: - @knwang from @khalani_network - @MikeCalvanese from @MikeCalvanese - @hrojantorse from @intheanera - @Innovictor from @AcrossProtocol and @UMAprotocol Head of content - and, @manankpatni from @0xEpochProtocol for all the review and feedback on this article. Thanks to open-resources/technical-docs from @ParticleNtwrk , @SocketProtocol, @anoma, @BrinkTrade and @lifiprotocol. They were super helpful for anyone researching on these systems. Highly Recommended Stay tuned fam. Next Parts coming soon. Cheers 🍷
Zaryab tweet media
English
14
16
85
13.6K
Brink retweetledi
Mike | nomial.io
Mike | nomial.io@MikeCalvanese·
in case you don't already know, @ethanfr is an absolute legend
Nomial@nomial_io

❓How has the Chain Abstraction evolved? ❓What drives demand? ❓Are there liquidity challenges? @MikeCalvanese and @andrew311, co-founders of Nomial, have a conversation with @ethanfr, Head of Developer Relations at @ParticleNtwrk, on these questions and more. Check out the full conversation on the evolution and impact of Chain Abstraction on Youtube: youtube.com/watch?v=RLQ3w0… #Web3 #ChainAbstraction

English
0
1
4
355
Brink retweetledi
Nomial
Nomial@nomial_io·
Join us tomorrow for an AMA with @SocketProtocol and @mach_exchange We'll be nerding out about chA + inventory access 🤓
Mach@mach_exchange

🌐Web3 Interop: The Power of Abstraction We'll be chatting with @SocketProtocol and @nomial_io tomorrow for the second installment of our Chain Abstraction chats, where we discuss the future of an interoperable Web3 experience. Link below to join 👇 🗓️ Wednesday, 11/6/2024 ⏰ 10:00 AM PST x.com/i/spaces/1ypJd…

English
0
3
6
671
Brink retweetledi
Mike | nomial.io
Mike | nomial.io@MikeCalvanese·
Filling cross-chain intents is capital intensive Fillers are constrained by the amount of capital they have available. Filling an order for $100k requires the filler to front $100k of value. Filling 10 orders in < 1hr requires the filler to front $1m Fillers also need inventory available on every chain they support. Filling 10 orders for $100k each on 10 chains in < 1hr requires the filler to front 10 x 10 x $100k = $10m When more users interact with more chains, number go up For Chain Abstraction to work, we need to fix this problem
English
18
3
68
10.3K
Brink retweetledi
Nomial
Nomial@nomial_io·
Where is the liquidity coming from for chain abstracted accounts? Enabling users to have a single wallet across every chain and pay for gas in any token is key to chain abstraction. Making this work means finding mechanisms to execute actions on one chain while paying for those actions on another chain. This almost always means relying on paymasters/fillers/solvers which front capital. This leads to a big problem for chain abstraction: protocols rely on fillers which in turn rely on lots of capital spread across many chains. There aren't many fillers out there with both the capital and the sophistication to manage large sums of assets spread across dozens or hundreds of chains. The trend toward modular rollups and app chains is only making this harder. Consequently, it's hard to bootstrap protocols. What if there was a layer that allowed you to access capital across many chains effortlessly? Would it suddenly become much easier to build fillers for chain abstraction? These questions inspired us to build the Nomial Inventory Access Layer. With Nomial, fillers can programmatically access capital across many chains. There is no need to raise or manage private capital. For example, Universal Accounts on @ParticleNtwrk are one such chain abstracted account system that can benefit from Nomial's Inventory Access Layer. Particle Network relies on a network of Liquidity Providers (i.e., solvers or fillers) to move intermediary tokens between chains. The attached diagram shows how this flow would work between Particle, Particle Network's Liquidity Providers (i.e., 3rd party solver), and Nomial. The flow is: (1) A user with a Universal Account on Particle Network wants to perform an action. The user may or may not be aware that the action requires an asset ("Desired Asset" in the diagram) on a specific chain ("Chain 4"). The solver needs the Desired Asset on Chain 4 to perform the action on behalf of the user. (2) Instead of maintaining their own balance of Desired Asset, the solver uses the Nomial Inventory Access Layer to tap into a reserve of Desired Asset already on Chain 4. They perform the action on behalf of the user. (3) The solver executes the action on behalf of the user. (4) The Particle Network repays the solver from the user's Universal Account using a mix of assets on miscellaneous chains (shown as Chain 1, 2, 3). (5) The solver repays the Nomial Inventory Access Layer using the miscellaneous assets on Chains 1, 2, and 3. The solver doesn't need to perform any bridging. This flow is much more convenient for the solver. It eliminates the need to maintain assets on Chain 4 or bridge assets from Chain 1, 2, and 3. #Web3 #ChainAbstraction #crosschain
Nomial tweet media
English
2
8
35
2.3K
Brink retweetledi
Nomial
Nomial@nomial_io·
@VitalikButerin we are doing our part to fix Liquidity Fragmentation 🫡
English
0
1
4
218
Brink retweetledi
Nomial
Nomial@nomial_io·
The problem that Nomial solves is simple - interacting with multiple rollups in a Chain Abstracted environment requires users to fragment their capital. This is costly and inefficient The solution? Users can deposit on one chain and borrow on many chains What about cost? The cost to borrow becomes exponentially lower compared to the cost of fragmentation as users interact with more chains. This holds true whether you are using ETH, stables, or any other asset What about latency? Nomial allows collateralized users to borrow with near zero latency by validating actions through an off-chain service. Think about this like an EigenLayer AVS - a service that can come to consensus for actions taken in the Nomial protocol, backed by the security of ETH, without maintaining any on-chain state 🧠 Think this problem doesn't apply to you? Consider: - the costs you've incurred using bridges. Both hidden and transparent fees apply here - the gas tokens you hold on multiple rollups - the opportunity cost of holding assets on one chain when your yield could be maximized on a different chain Whether you are an end user interacting through a wallet, an advanced MEV builder or solver, a liquidity provider, or a market maker, you're incurring the cost of capital fragmentation Let's solve this problem together 🚀
English
1
4
16
1.2K
Brink retweetledi
Mike | nomial.io
Mike | nomial.io@MikeCalvanese·
Liquidity scaling is critical for Chain Abstraction In order for Chain Abstraction to scale to the entire ecosystem, new rollups need liquidity rails from the moment they're deployed. The cost of deploying and running rollups is negligible, but adding liquidity for bridging on rollups is extremely costly and complex Newly deployed rollups need to pay bridges to support them. This dynamic should be completely flipped: rollup communities should get paid for supporting their own bridge liquidity @nomial_io is the first bridging solution to prioritize scalable liquidity. No other solution allows a new rollup to deploy community provided capital for bridging starting at block 1 and get paid for doing so We're seeing insane UX gains toward Chain Abstraction from @klaster_io, @ParticleNtwrk, @SocketProtocol and others. But in order for abstracted UX to work across all rollups, we need ultra-scalable, realtime liquidity that meets the pace of modular rollup deployments Nomial helps enable Chain Abstraction through scalable liquidity. This is huge. Feeling bullish today 🐂
English
5
3
34
2.6K
Brink retweetledi
Nomial
Nomial@nomial_io·
Excited to partner with the team at @machfinance to help solvers operate more efficiently 🥳
Mach@mach_exchange

1/4 We're excited to announce our partnership with @nomial_io , the first open liquidity network built for the modular DeFi ecosystem. Mach intends to support liquidity providers (fillers) within our intent network by providing them access to Nomial's extensive liquidity pools across multiple blockchain networks.

English
1
2
10
763
Brink retweetledi
Mike | nomial.io
Mike | nomial.io@MikeCalvanese·
Stargate securing ~$440m of user funds with two owners💡
sand@sandmanarc

Why is Everyone Quiet about the Cross-Chain Honey Pots? $10B+ at risk? This post will cover: 1. DVNs on @LayerZero_Fndn 2. ISMs on @hyperlane 3. OFTs & Warp Assets 4. Non-dormant addresses on @ether_fi and @renzoai multisigs "Decentralised Verifier Network" aka DVNs by LayerZero LayerZero Labs DVN: 2/3 multisig Nethermind DVN: 1/1 multisig Stargate DVN: 1/1 Google Cloud DVN: 2/3 Horizen DVN: 2/2 Source: You gotta go to Etherscan and call the signerSize and quorum functions. Here are the contracts: Link [1] (in the reply) Note: There is no guarantee that these multisigs are actually distributed and not maintained by a single person like in the case of Multichain. The name "DVN" itself is misleading. It certainly mislead me into trusting them more. A DVN is a modular validator entity inside LayerZero. That means, if you choose a single DVN set-up, your cross chain messages will be solely validated by this DVN. You can choose multiple DVNs or m out n DVNs to secure your setup. Most protocols (clients using LZ) have 2 DVN setups at max. I had to create this Dune dashboard myself to look into what's happening on-chain. For instance, Stargate has 2 DVNs. Stargate DVN and Nethermind DVN. Both are 1/1 multisigs. Securing, checks notes, $442.84m. Dune is doing a terrible job here, here's how the distribution of various configurations looks like. Look at the numbers that start tapering off as we go down the list. Dashboard link [2]. So, most protocols (clients using LZ) simply trust this one entity, LayerZero Labs, a 2/3 multisig. It's baffling to me that we're all fine with this and nobody is talking about it. We gotta push these teams towards more secure systems, rather push protocols that are using LayerZero to demand for more security. Let's look at Hyperlane, LayerZero's biggest competitor at the moment. First of all, thank God they call their default setup "Multisig ISM", ISM = "Interchain Security Module". They are at least honest about it. It is a multisig. Period. Hyperlane has setup their default ISM to be a distributed set of validators with different quorums for different chains. Each of these validators in this multisig setups are different entities, like various DVNs on LayerZero. Here's how their default setup looks like: Arbitrum: 3/5 multisig Base: 2/5 Blast: 2/3 BNB: 2/4 Ethereum: 3/7 Optimism: 2/5 (source: Link [3], note: they said this post prompted them to up their numbers, so this may have been updated) It is not very far off from the LayerZero DVN setups. But atleast you can be sure that 3-7 of these entites are actively validating in the system. It also seems better than using a single LayerZero Labs DVN setup. By the way, in a m/n multisig setup, if n is >> m, you are compromised if ANY of the m keys are compromised. In their BNB setup, 2/4, if any of the 2 validators out of 4 are compromised, you are compromised. If you compare these with Wormhole's default 13/19 setup, Wormhole looks a lot better. But I've heard it is upgradable. Do they need 13/19 signers to upgrade? I don't know. There are two main arguments by the GMPs (General Messaging Protocols, LZ & HL in this case) defending the lack of security of individual setups at the moment. 1. You can make it as secure as you want by adding as many DVNs/ISMs as possible. This is a marketplace and the market isn't choosing their security right. 2. You can upgrade to a more secure setup when they are available. Choosing your own security In fact, I'm writing about this after I had to choose my own setup for my protocol built on LayerZero. I had no idea what to choose. LayerZero does not provide any information on the current usage distribution of DVNs, nor do they advice you on a secure setup as they want to be agnostic. Layerzeroscan only provides data on the distribution of messages by different protocols using LZ. But that is not useful to me at all. They don't even tell us what DVNs these protocols are using. That's why I built my own Dune dashboard. Here are the most used DVNs across major EVM chains: Outside of the top 6 DVNs I mentioned at the top of this post, none of the DVNs are getting any volume. Why would a protocol choose to even trust DVNs other than the active ones? What guarantee is there that they are active and will be active in the future? What if you brick your system by choosing a dying DVN? If a DVN is not getting any volume, they would rather turn off their nodes as it costs to run a DVN. It's the same with complex DVNs or ISMs. If there is an ISM that is not being used, that means, it is not battle tested. If it is not securing any value, why would you trust it to secure your protocol? So the argument that these GMPs are agnostic marketplaces does not hold true at all. Someone has to help the crypto protocols choose the right setups. It is as if Amazon offered a default product for all of your searches and gave you a list of other options without product availability, reviews or even a description. In my experience, Hyperlane is more eager to engage their clients with education than LayerZero. It should be easier for more DVNs to start competing in the GMP marketplaces. In reality, there is no way for them to market themselves to the protocols using Hyperlane/LayerZero outside of shouting into the void on Twitter. Apparently the teams(LZ said so) are currently working on dashboards to showcase more data about individual DVNs/ISMs. Maybe this post pushed them to do so. The second main argument is that, protocols should use this trusted setup now, so that they can upgrade to a ZK bridge or a restaked security setup later down the line. The Upgradability of Your Setup First of all, I want to highlight that this is so far from the crypto ethos that got me into this space. Mutability, smh. Let's compare an ERC20 with an omnichain token. An ERC20 1. Has a fixed supply that nobody can change (most of em) 2. Exists on a blockchain where nobody, including the team itself, can mint extra ERC20s An OFT or A Warp Asset 1. Has a fixed supply in theory, but an unlimited number of tokens can be minted if the interop setup is compromised, unless there is a rate limit. 2. Has its interop setup managed by a multisig controlled by the token issuer (protocol). This multisig can change the rate limit as well (lol?). 3. Exists on multiple blockchains where if one of the chains is malicious, they might be able to mint as many tokens as possible, unless there is a rate limit, which can be changed. Let's look at team multisigs for a second. At least they are dormant addresses locked up in a basement, right? Right? @ether_fi is a protocol with $5.5B+ in TVL. Here is the multisig (Link[4]) securing their weETH OFT. 5 out of these 6 wallets have been active in the last 2 months. That means a higher likelihood of getting their private keys stolen.. For context, Ronin ($600m) and Harmony Bridge ($100m) hacks were due to comprises of multisigs. @renzoai is a protocol with $1.5B in TVL. And their ezETH is an xERC20. It is also secured by a 3/5 (multisig Link [5]). All 5 of these addresses have been active recently. And they all seem to be kinda interlinked. But I am not an expert on-chain sleuth to comment on that though. Will Ethena's USDe ever depeg? Perhaps not due to their stablecoin design, but rather because of their interop setup (LayerZero Labs DVN + Horizen DVN, basically a 4/5). At least 7 of their 9 multisig addresses are dormant. So, can we say a total of around $10B+ is at risk here? I am not blaming these GMPs. They are simply selling a setup. I am pushing the community to demand enough security from the protocols that are using these setups. Did we all forget that the bridge hacks have accounted for >50% of all funds we have lost? Now we are offering billions more on a platter to the hackers around the world. Kim Jong-Un is probably rubbing his hands right now. Native Bridges, Ignored, And Left for Dead It is easy to point out problems than to offer solutions. What is the best security for cross-chain messaging/tokens right now then? I would suggest studying wstETH by Lido. It uses native bridges to bridge and also to control the upgradable token setups on L2s. The upgradability is controlled by the Lido DAO on L1. Except the upgradability aspect of this, I have no issues with this setup. There is no way an unlimited amount of wstETH can be minted in this case. There will be solutions based on restaking in the future, hopefully they will offer a much better security than what we have today. Closing Thoughts I used to think very highly of LayerZero as a protocol. A protocol that is marketed x.com/mark_murdock3/… as a peer next to Bitcoin and Ethereum. Bitcoin, Ethereum, LayerZero. But I do not feel strongly about it anymore. I don't think it's even close. Bitcoiners chose the smaller blocks chain, Ethereans still care about the solo stakers, but the protocols using LayerZero are fine with one or two DVN setups. This is not a post targeted towards any of the GMPs/protocols mentioned here. I wanted to voice out my concern because I hold a lot more ETH than I hold ZRO (I do hold some ZRO, sandmanarc.eth). I have also integrated LayerZero into the protocol I am currently building. Although I am having second thoughts about it now. Let's demand better standards from our industry. - A humble community member, Sand

English
0
1
5
412
Brink retweetledi
Mike | nomial.io
Mike | nomial.io@MikeCalvanese·
1/1 multisig is really just a sig
English
0
1
9
518