Musa retweeted
When Pudgy Penguins does things, we bring Web3 with us!
Missionaries, not mercenaries
I don't care if I sound like a broken record, this is what building in crypto should look like
Expand the pie, show our quality to the rest of the world, onboard the next generation
Few.
I want to collab with every web3 artist on a @vibes_tcg card and put those cards in the worlds biggest retailers. 🔜
Musa retweeted
Over the past couple of months, Pudgy Penguins and $PENGU have experienced incredible momentum.
From political leaders pengposting to major collaborations with some of the world’s biggest brands, the progress has been remarkable.
Here some key moments you may have missed:
robotics engineer here and i approve this message
additionally there are other ways to capitalize on the robotics tsunami that’s about to hit the markets
there’s a HUGE lag between Ai and robotics in the markets
it’s literally connecting software breakthrough with hardware one
bet on that gap by choosing the right horses and you’ll x10-1000 your investment easy the next 5 years
hyperliquid:native has now surpassed $8 billion in USDC
That's a lot of future yield from the circle deal in regards to AQAv2 for the AF buybacks.
That's potentially an additional 700k+ per day in future buybacks coming on top of what it's doing today. Assuming no further growth.
Big dips if given, are for adding to the winners
Musa retweeted
the buyers twapping hype this time have alot more money than the buyers twapping hype last time
Musa retweeted
$PENGU is now listed on 130+ exchanges and is tradable across 6+ chains, reaching hundreds of millions of users daily.
Here’s why that’s important 👇
Musa retweeted
Replying to @KelpDAO
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
teapawt.org/mitchellftracy/status/…
teapawt.org/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
Musa retweeted
You literally had MONTHS to buy the LOWS.
95% of you FROZE in FEAR.
Staring at the charts like a deer in the headlights.
BELIEVING we were going to $30,000 for the 'perfect 4 year cycle'.
And now you are sidelined.
Cope & seethe.





























