←
Sentinel.codes142 posts
Sentinel.codes avatar

Sentinel.codes

@Sentinel_codes

Algos & Vaults to optimize #Defi yields & liquidity.

◷ Joined January 2025▧ 25 Photos and videos
Sentinel.codes avatar
Sentinel.codes@Sentinel_codes·Nov 16

24/7 trading is great, but it's not the most important benefit of tokenized equities. The real point is access and usefulness: billions of people who can't buy a stock today, and assets that can do much more once they're onchain (like earn you better yield).

24/7 trading is great, but it's not the most important benefit of tokenized equities. The real point is access and usefulness: billions of people who can't buy a stock today, and assets that can do much more once they're onchain (like earn you better yield).

Liquity avatar
⟳ Sentinel.codes retweeted
Liquity@LiquityProtocol·Sep 10

When the yield is stable and reliable... ... you get a constant influx of funds. Simple, really.

Post attachment
IkeBillion.eth avatar
⟳ Sentinel.codes retweeted
IkeBillion.eth@Ikebillion_·Aug 19

This protocol wants to pay its users $8,000 for something you already do for free. I wrote about the IPOR ETH Carry vault a few weeks ago and recently, @DeFiSaver and @LiquityProtocol just launched a campaign that makes it even harder to ignore. 8,000 BOLD in rewards when you open a Trove through DeFi Saver with a minimum of 10,000 BOLD and keep it open for 30 days. You earn a pro-rata share. If I was new to this and wanted to maximize this campaign, this is the strategy I would use: - Deposit a minimum of 5 ETH into the @ipor_io Fusion vault. That unlocks the 2x multiplier in the reward pool and starts earning immediately. - Convert some ETH to wstETH and open a @LiquityProtocol V2 Trove through DeFi Saver using it as collateral. - Borrow at least 10,000 BOLD with a stop loss in place so you are not watching the health ratio all day. - Send that borrowed BOLD straight into the Stability Pool so it starts earning LQTY on top of everything else. - Hold both positions open for 30 days minimum. The 2x multiplier is the part most people will miss. Being an IPOR Carry vault depositor gives you a 2x multiplier.

Post attachmentPost attachment
Darren Camas | IPOR Fusion avatar
⟳ Sentinel.codes retweeted
Darren Camas | IPOR Fusion@DarrenCamas·Aug 12

102% TVL growth in USD and 151% in ETH terms over the past 3 months at Fusion. Two kinds of demand are showing up at once here: the need for custom yield strategies, and rails that regulated capital can use to access the onchain economy. Fusion vaults answer both. On custom strategies: as curation gets crowded on the leading platforms, operators want something the crowd does not have. Fusion lets a curator tap Aave, Morpho, Spark and 40+ other protocols from one vault, and offer a product no single platform can. Some of the recent interesting examples include: • @LiquityProtocol ETH Carry, which has become the #1 WETH-paying product on the entire mainnet • WBTC Dollar Carry by @BTCDOfficial which has become the top paying Bitcoin vault in the industry • cbETH looping strategy of @628Labs which amassed over 19k cbETH units via automation, resulting in @aave having to lift caps on the market to accommodate this demand. This particular strategy holds the largest cbETH position on the entire Base network, directly contributing to Coinbase Inc's earnings from rewards generated by the cbETH supply In parallel, participation from regulated capital keeps growing through the dedicated client vault constructs built on Fusion. That route is led by @tesseractcrypto, a MiCA-authorised CASP we partnered with earlier this year, now accessed by BitGo (Fortune 500), 21Shares (one of the world's leading crypto ETP issuers) and Bitstamp, among others. Those constructs rest on a few key mechanisms. Role segregation, so execution rights and withdrawal rights sit apart. Access control enforced at the vault itself, so who can deposit is settled before anyone does. A mandate written into the configuration before capital enters, setting which venues can be touched and which actions are permitted. Those constraints hold at the contract level and stay readable afterwards. Fusion vaults come with the mechanisms an entity needs to meet its own compliance requirements, and because every constraint is a parameter, a vault built for a European fund and one built for a US institution start from the same infrastructure and end up with different boundaries. Alongside those controls, the numbers hold up. These dedicated client vault constructs have reached steady double digitson stablecoins and above 4% on Bitcoin, and every figure traces back to a live position anyone can read. If you are running capital that needs this kind of structure, or building strategies that need somewhere to run, come talk with us.

Fusion ecosystem TVL just hit a new all-time high in ETH terms. Through Q2 and Q3, vaults built on Fusion saw steady inflows from regulated capital, with a significant share deployed on Base. What draws that capital in: Fusion is agnostic vault infrastructure. Regulated entities use it to reach onchain markets on terms they define themselves. Role segregation, KYC enforced at the vault level, and mandates fixed before capital enters, setting exactly where it can be allocated and what actions are permitted. On top of those controls sits automation across onchain liquidity venues, letting operators run leveraged looping, carry trades and high-frequency optimizers within boundaries set in advance. Over 170 distinct actions across 40+ protocols are reachable through pre-existing modules, including @aave, @morpho and @sparkfinance. Operators combine them into strategies no single protocol offers on its own. Much of that capital lands on @base, where Fusion vaults are among the larger supply drivers for cbETH. The Fusion infrastructure is open to any team or entity that wants to build this way, and we are seeing increased demand for custom strategies running on it. Whether you are an institutional or regulated entity deploying a first onchain pilot, or an operator looking to expand what your strategies can access, reach out or start here: docs.ipor.io/build-on-fusion

Post attachment