7 yrs crypto. AI obsessed. While others talk — I ship. 🔥
Metaverse
Joined March 2019
- Tweets2.7K
- Following202
- Followers234
- Likes8.9K
io36x.eth 🥡🥢 retweeted
Everything you love is now inside your pocket!
Jupiter Gacha is now native on mobile.
Same packs, same worlds, same grails now one tap away. Open the app, rip a pack, anywhere and anytime.
No need for a browser or desktop just download the superapp.
Catch 'em all on Jupiter.
io36x.eth 🥡🥢 retweeted
You don’t need a bridge anymore.
Introducing Universal Deposit.
Send a token from any supported chain and receive USDC in your Solana wallet.
Universal Deposit handles the routing, bridging, and swapping automatically:
- Send funds from the wallet you already use
- Deposit from Ethereum, Base, Arbitrum and Sui
- No bridge apps, network switching and extra transactions
- Flat $0.30 fee, whether you send $100 or $10M
The most seamless cross-chain transfer experience is here.
All roads lead to Solana
io36x.eth 🥡🥢 retweeted
Learn how to put your tokens to work.
If you hold ANSEM, the Rock Makes Money campaign hosted by @EcosystemCall is a simple way to start LPing it.
→ LP into the ANSEM-SOL pool
→ Keep your liquidity active for 7 days
→ Collect tickets for a share of $5,000
io36x.eth 🥡🥢 retweeted
Claude, Robinhood, Lighter, Binance and other protocols will be taken into account for your kaito pulse score
exclusive. currently, you can only link X, Polymarket and Hyperliquid at kaito. but i checked whats inside and found much more apps will be plugged in in the future:
> Binance
> Bybit
> ChatGPT
> Claude
> @HyperliquidX
> @Lighter_xyz
> @OKX
> @Polymarket
> @tradexyz
> @Variational
> @IBKR
> @RobinhoodApp
and the qualification scaffolds are already sitting hardcoded in the shipped code, which is the part that tells you what this thing is being built for (its def gonna change anyways):
1. Binance:
> account value >= 10,000 USDT
> holdings
> positions
> 30-day validity
2. tradexyz - cumulative volume > $100K, with Tier bump (no deposit) and Sign-up bonus (may need deposit)
3. Lighter:
> orders
> positions
> trading volume
> threshold and campaign TBD
4. Claude & ChatGPT
> subscription tier
> account age
> status
> usage
verified accounts unlock Aura, prove track record, and make you eligible for kaito campaigns. so. you
> trade perps/hold balances/using ai subs/gamble pm/farm engagement
> extension proves it
> you gain aura credits
> rank increases
> you are eligible for kaito campaigns
you can connect hyperliquid, polymarket and x currently at s.kaito.ai/UG3Z7H
mind sharing this with others?
@Punk9277 good job
Introducing Kaito Pulse – a social layer for the internet, starting with X.
The internet was built around what people post.
It's now increasingly shaped by what people build, trade and back. Most of that never reached the timeline.
Until today: kaito.ai/aura
io36x.eth 🥡🥢 retweeted
Unfortunately this proposal doesn't achieve the outcome it tries to achieve and is actually hurtful for Ethereum.
It caps Ethereum staking rewards to 0% when over 50% of supply staked.
What this mean is that Ethereum staking yield becomes unpredictable and even fully uneconomical activity for many, which is a negative factor for any institutional buyer who would considering taking ETH position (instead of other networks with predictable cash flows). This uncertainty has a significant adoption cost.
This also means unpredictable yield for solo stakers who might be even more sensitive on pricing.
For DeFi, with moving to 0% reward, this essentially makes ETH borrowing strategies mostly unviable and killing ETH borrowing and yield use-cases for ETH (only reason to borrow ETH ironically would be to short it). The only way to get ETH yield would be to stake, lock into a time period (instead of instant withdrawals in DeFi) and also have hopium ETH doesn't reach 50% staked of supply.
My concern is also that those who are fine with ETH beta and yield might also sell ETH for other yielding assets such as stables for yield, very common move when rates go down in TradFi, funds flowing from stables to equities but here we will have the other way around. Could be good for DeFi but not for ETH in DeFi.
From my personal take, this just makes ETH less viable as an asset and restricts its potential. I hope this proposal doesn't move fwd, otherwise we see lot of people moving their interest in other networks. There are many who share the same view.
Ethereum should not be punished for its growth.
🚨 New EIP: Tapered Issuance Burn
We just submitted an EIP to ethereum/EIPs: a minimal, market-driven fix to Ethereum's issuance policy removing the incentive for stake growth beyond 50% of ETH supply.
EIP-8361 by @pintail_xyz, @jdetychey, @dapplion, @pa7x1, @ladislaus0x & @drakefjustin 🧵
io36x.eth 🥡🥢 retweeted
Top 15 onchain apps by protocol revenue: $HYPE, $PUMP, $CAKE, $SKY, $JUP, $AAVE, $AERO, $WLFI, $LDO, $MET, $ETHFI, $LIT, $CARDS, $UNI, $RAY
Some of the top onchain apps by revenue have real cash flows, low overhead, and single-digit multiples, and with the CLARITY Act potentially weeks away, we believe investors are facing an attractive entry point today.
Read more from @LowBeta's latest Stack article here: grayscale.com/the-stack/reve…
io36x.eth 🥡🥢 retweeted
The $10B TCG market just gained access to onchain credit.
First Edition Charizards are held like treasury assets.
A Pikachu Illustrator sold for over $16M.
These aren't just cards, they never were, but here's the part nobody solved, until now.
Turn your cards into money, without selling them👇
io36x.eth 🥡🥢 retweeted
As promised, every Thursday we’ll be summing up the weekly results of the Vault — epoch #11.
BredoStrategy Vault:
app.hyperliquid.xyz/vaults/0…
The Vault started on February 17, when BTC was at $67,960.
—————————————————————
BTC since last week: +6.22% ($76,500 → $81,260)
Vault profit since last week: +$574,139
—————————————————————
BTC since the Vault launch: +19.57% ($67,960 → $81,260)
Vault profit since launch: +$597,503
Vault all-time high.
Feels like there is a lot to say, and at the same time I don’t really want to say much.
This was exactly what the Vault was created for.
We could have waited a year+ for moments like this, or they could have happened this week.
They happened.
I’d say 20–30% of what I created the Vault for has already played out. Now we wait for the remaining 70–80%, then close the Vault, wait for new pullbacks, and so on.
Thanks everyone.
Everything is just getting started!
Previous reports:
April 30 — t.me/DoCryptoBred/1458
April 23 — t.me/DoCryptoBred/1432
April 16 — t.me/DoCryptoBred/1395
April 9 — t.me/DoCryptoBred/1311
April 2 — t.me/DoCryptoBred/1255
March 26 — t.me/DoCryptoBred/1200
March 19 — t.me/DoCryptoBred/1147
March 12 — t.me/DoCryptoBred/1039
March 5 — t.me/DoCryptoBred/966
February 26 — t.me/DoCryptoBred/868
————————————————————
BredoStrategy Vault:
app.hyperliquid.xyz/vaults/0…
Hyperliquid referral:
app.hyperliquid.xyz/join/BRE…
BredoStrategySubs:
docs.google.com/forms/u/0/d/…
#Hyperliquid #HYPE #Vault #Bitcoin #BTC #DeFi #Crypto $BTC $HYPE
io36x.eth 🥡🥢 retweeted
A ton of this is just completely untrue.
1) Kelp originally used the defaults which were MultiDVN or DeadDVN and manually migrated to a 1/1 config later
2) Almost 100% of the volume on a 1/1 config was rsETH
3) Not using a 1/1 for production applications is mentioned many times in the documentation.
The defaults Kelp is referencing in their screenshot were multiDVN or DeadDVN, which force-rejects an application using the defaults at all and requires them to manually set configuration.
rsETH was originally configured to use the default LayerZero configuration of a multiDVN setup of LayerZero Labs + Google:
Here are the exact transactions where that happens
Ethereum → Arbitrum:
etherscan.io/tx/0xd7c864adbc…
at 2024-02-06 03:09:47 UTC
Ethereum → Optimism:
etherscan.io/tx/0x7075bfe9a3…
at 2024-02-06 03:09:59 UTC
KelpDAO then manually changed these to 1/1 configs:
For the original Feb 6 Ethereum routes to Arbitrum/Optimism, KelpDAO’s Ethereum contract switched from defaults to manual OApp-scoped config on 2024-04-01:
Send-side manual config:
etherscan.io/tx/0x7485c16c9b…
2024-04-01 07:12:11 UTC
Receive-side manual config:
etherscan.io/tx/0x21e967c99a…
2024-04-01 07:12:23 UTC
From this point on, Kelp began deploying all of their configurations as 1/1 configs. Here is Kelp’s deployment on Unichain:
Unichain → Ethereum was opened on 2025-04-01 18:55:41 UTC.
Pathway-open / setPeer tx:
uniscan.xyz/tx/0x31ea2b10a73…
The manual ULN config followed 6 seconds later in uniscan.xyz/tx/0xd8ef5416a53….
During this time the Unichain -> Ethereum and Ethereum -> Unichain defaults were set to DeadDVN which is a contract which makes it impossible for any application to transact without manually configuring their DVNs, this was not possible on the defaults of this pathway.
Here is the code in the DeadDVN (etherscan.io/address/0x747C7…) that specifically prohibits this.
(Screenshot 1)
This is called out many many times in the docs:
1. Integration Checklist — "Do" list
- Last edited: 2025-11-26 (Nazreen)
- Content: "Do: … Use more than one DVN for each production pathway instead of relying on a single DVN."
- File: v2/tools/integration-checklist.mdx:244
- URL: docs.layerzero.network/v2/to…
2. Integration Checklist — "Don't" list
- Last edited: 2025-11-26 (Nazreen)
- Content: "Don't: … Configure only one DVN for a pathway and treat it as production‑ready."
- File: v2/tools/integration-checklist.mdx:251
- URL: docs.layerzero.network/v2/to…
3. Integration Checklist — Defaults are not safe
- Last edited: 2025-09-25 (Tino Martínez Molina)
- Content: "Do not assume defaults are safe for production. Always check explicitly: getSendLibrary, getReceiveLibrary, and getConfig. If these resolve to defaults, confirm whether the defaults are valid for the intended pathway. Unintentional fallbacks to defaults are a common cause of blocked or failing pathways."
- File: v2/tools/integration-checklist.mdx:126-128
- URL: docs.layerzero.network/v2/to…
4. Integration Checklist — Default fallback warning
- Last edited: 2026-02-26 (migration; same wording predates it)
- Content: "Warning: If no configuration is set, the OApp will fallback to the default settings set by LayerZero Labs."
- File: v2/tools/integration-checklist.mdx:222-238
- URL: docs.layerzero.network/v2/to…
5. ONFT Quickstart — Production guidance
- Last edited: 2025-02-20 (Radek Sienkiewicz)
- Content: "DVN Settings: Use multiple DVNs in production to ensure message verification is robust."
- File: v2/developers/evm/onft/quickstart.mdx:700
- URL: docs.layerzero.network/v2/de…
6. ONFT Quickstart — Strong recommendation to configure
- Last edited: 2025-03-10 (Radek Sienkiewicz)
- Content: "We strongly recommend reviewing these settings carefully and configuring your security stack according to your needs and preferences."
- File: v2/developers/evm/onft/quickstart.mdx:366
- URL: docs.layerzero.network/v2/de…
7. Starknet FAQ — "Should I use multiple DVNs?"
- Last edited: 2026-01-21 (Nazreen)
- Content:
▎ Should I use multiple DVNs?
▎ Recommended for production. Multiple DVNs provide:
▎ - Increased security (multiple independent verifiers)
▎ - Resilience (no single point of failure)
▎ - Trust minimization
- File: v2/developers/starknet/troubleshooting/faq.mdx:290-296
- URL: docs.layerzero.network/v2/de…
Here are the exact recommendations we gave KelpDAO when asked about DVNs (typically 2/3)
(Screenshot 2)
Other LayerZero applications speaking on exactly what is advised by the team
xitter.cf/mitchellftracy/status/…
xitter.cf/jasperflux/status/2046…
For how much volume was actually configured on 1/1 here is the exact data.
(Screenshot 3)
We will publish a complete post-mortem as soon as the external security firms have completed it.
All I can share after launching an OFT is:
- @LayerZero_Core told us to always to use multiple DVNs never just 1
- interop would look very different without a permissionless stack that allows for configurable security