@re reUSDe is now transferable to @Base.
$reUSDe is Re’s reinsurance performance token, designed to capture returns generated by its diversified reinsurance portfolio.
Our 1:1 bridge makes it usable beyond Ethereum - on Base, @RobinhoodApp, and more DeFi ecosystems.
@Liam_Haki@MEADGod@TheIndexFi Well, that's a good alpha. And hear me out too, as per their Reflection Token contract: "The 3% each-way tax is NOT here: it's taken in native ETH by IndexFeeHook on the pool". So it seems that they make good use of the Uniswap V4 Hook for their auto distributions.
@Uniswap v4 Hooks have one major limitation.
You can only add one Hook. Unless you're a dev who can deploy a custom contract, you'll want to keep an eye on Morphook: Modularity for V4 Hooks.
✦ 1 Hook = Unlimited Modules
✦ Anyone can list a Module for others to compose in their Hook
✦ Immutable or Upgradable, giving an owner the ability to edit their Hook's Modules (e.g., add another one).
✦ Every Module in your Hook is called on every swap.
✦ All via UI
✦ Rewards for devs who build the most reused Modules.
Launching Morphook soon :-)
Some people ask, "Why can't I just create my own wrapper contract that swaps tokens AND calls something afterward?" - for example, burn some, send to treasury, call external contract, etc.
A wrapper can always be bypassed by someone swapping directly through the pool (e.g., via the Uniswap UI).
V4 Hooks enforce this logic. Execution doesn't matter if the swap is called programmatically or via any interface. Essentially, the Hook's logic becomes an integral part of the swap.
Some people ask, "Why can't I just create my own wrapper contract that swaps tokens AND calls something afterward?" - for example, burn some, send to treasury, call external contract, etc.
A wrapper can always be bypassed by someone swapping directly through the pool (e.g., via the Uniswap UI).
V4 Hooks enforce this logic. Execution doesn't matter if the swap is called programmatically or via any interface. Essentially, the Hook's logic becomes an integral part of the swap.
@me8_x1782@pulsedotfund Cool, just bought a bag. Good luck with the project :-)
You can check mine too, although X suspended my Predistate project's account for some reason, and I'll probably need to create a new one at this point :-/
https://t.co/FVylBdyHqD
@gornx0x At least you got the attention. I’m building eg https://t.co/gv25fS48MB or @loyfin_com and can’t find anyone interested :-) but maybe it just sucks lol idk
Hi man, appreciate your work @gornx0x :-) comfy in my $wire spot. That being said I have a question - are you building prediction markets from scratch or integrating with something? I’m building https://t.co/ctI1MBUPTa (which for some reason is now suspended on X) prediction markets for anything onchain eg any token price on Uniswap, any total supply (eg bet on stock adoption), FDV, account balance, Aave/Morpho position, any onchain state as a market.
@minchoi Creating a game will be the new "writing a book".
This is the medium that attracts the current audience; tools will become available for everyone, but you'll still be responsible for a good story.
Indeed it does.
We believe this is also true while allowing OFTs to be permissionlessly created (e.g. an Ondo / xStock / Robinhood Stocks) on destination chains on their first transfer (our approach) while:
1. Passing owner() to the destination
2. Letting owner() on the destination set the blacklist mapping / ICompliance contract address checked on every transfer.
3. Passing owner() on every transfer from origin to destinations to keep them up to date (or set if it was empty before).
There are some caveats, but in general this combines the best of two worlds - permissionless by default, controllable for RWAs - while dynamically created on destinations (no setup/deploys for token teams).
Bridge base:0xb2000000000000000000007bf6d5cbb0e24cb301 to Robinhood Chain and help test the protocol :-)
$OMNI to be launched on the upcoming LayerZero blockchain - Zero.