
Software Engineer @EspressoSys | Teaching you Web3 @composablepod | ex @elliptic | @ETHGlobal Finalist | @developer_dao | πΉπΉπ¬π§π¦πͺ
Joined August 2013
- Tweets3K
- Following2K
- Followers2.7K
- Likes4.1K
Treat all emails as potentially suspicious. Before clicking links or opening attachments, check the senderβs domain and use Gmailβs βShow originalβ to verify SPF, DKIM, and DMARC. If DMARC shows FAIL, do not trust the sender without independent verification. Even a PASS doesnβt guarantee safety.
Alysia π©βπ»β retweeted
Some learning lessons / recs from @binance hack to crypto teams mixed with my own personal ramblings.
- Work devices are for work, personal devices are for personal. No exceptions.
- Never install or perform actions on a destination site from a search result. Google is notorious for shitty ad control policies in cases even displaying the legit domain -> then redirect to a malicious copy
- Software MUST come from approved channels, nowhere else. Your engineers will be annoyed but whitelisitng apps, extensions, cli tools / binaries, etc is a MUST in today's environment.
- Educate your employees and yourself on DPRK attack vectors!!! Every single employee entering your organization must be aware of the common DPRK attack vectors (meeting phishing, contagious interview, pollinrider tactics, etc.).
- Never clone / open a repo locally on your machine. Goes without saying but this a tried and true payload delivery mechanism for DPRK
- Use a freaking MDM to manage software it's 2026 (probs jamf or iru). One of the compromised engineer's got one of his Homebrew tools (pyenv) with a version that gave the attacker remote access. Use MDM to manage verified install channels for binaries and anything else. Push config changes (e.g VS Code task abuse), governance for AI tool usage, hunt across your fleet for vulnerable software, auto-updates, allowlists for app installations, execution allowlisting for binaries, etc.
- Only dedicated devices + dedicated accounts should have access to critical / existential actions. We've been doing this at Monad for a while and encourage eco teams to do the same.
- Make a threat model pls. In the words of @iphelix what are your crown jewels? You must know what are the existential threats to your company and defend them / build the controls so that even if you ARE compromised - it doesn't destroy you.
- Use an EDR (Crowdstrike or Huntress if smaller and need something more managed) and build custom IOAs based on threat intel (e.g this binance post-mortem). EDR did NOT detect for Binance - it doens't mean that's the case for you - write some damn custom detection rulesets.
- Egress controls on every device. Yes i know people don't like Zscaler but your employees are going to fall for the B-team tactics time and time again. Block newly registered domains by default and setup some automation to keep adding new IOCs from your threat intel.
- Speaking of threat intel - do you have any??? If you don't rss feeds are ok - X tho is really the gold mine you should setup custom detection feeds based on your organization's threat model. Otherwise can use cve.[now], cloudlfare zero-wire, and @_SEAL_Org threat intel as a basic starter. A lot of rss feeds are poop so focus on quality.
- No long-lived sessions or tokens on laptops. Short-lived, scoped, device-bound creds. Simple enough but hard to apply across the org.
- Yubikeys won't save you from malware. This is not the only line of defense but for phishing yes they're great so obv have them.
- Vendor risk is literally sky-high rn. You cannot allow employees or yourself to blindly install / run / grant perms to 3rd party platforms. Distrust by default and Oauth grants (hey google workspace admins i'm talking to you) should be set to read-only for ALL apps by default. If you rmr this is how Vercel got pwned.
- Signing policy should be enforced no matter who's calling. Destination allowlists, per-tx and velocity limits, hard block on EIP-7702 from hot wallets.
- Detection and alerting do you have any??? The attackers were incubating since JUNE - months of time to prep for lateral movement until they could escalate. How do you know you're compromised or behavior is suspicious?
- lastly just going to leave this here: teapawt.org/alpeh_v/status/2116172β¦
Super exciting and big congrats! Excited for the @blocknative & @Deloitte teams! @mcutler is such an awesome person, couldn't be more proud!!! πππ
News to share: the Blocknative team has joined Deloitte. It's been eight-plus years. Thousands (more?) of conversations. Too many talks, panels, blog posts, and podcast appearances to track. A team that refused to ship anything we weren't proud of. Grateful for each and every one of you. Onward. π«‘
5
4
299
which twitter accounts/blogs post about every web3 exploit as they happen? i like the @web3sec_news newsletter but are there any realtime ones?
Alysia π©βπ»β retweeted
Seamless crosschain interop isn't coming. It's already here.
@cryptomachia demos Presto, an app letting you mint an NFT on @ApeChainHUB w/ funds on @RariChain in one click. No bridging required.
This is what Espresso's fast finality enables. Check it out at our @EFDevcon booth.
it's been a while since i've watched some project demos! watching this one, Brew house (cross chain apps) youtube.com/live/BURHaihMAJg
Alysia π©βπ»β retweeted
Feels like the right moment for this thread with the Robinhood L2 chain just announced.
Rollups were first conceived as a "scaling solution" for Ethereum. This framing is wrong imo. It's a new paradigm for the future of Web3 that will win out against monolithic chains (1/8) π§΅
Alysia π©βπ»β retweeted
π¨ New ep alert! Are intents even real?
In the latest entry to their "Are they even real?" series, @alysiatech & @ellierdavidson examine how intent bridges work and dive deep into @AcrossProtocol & its proposed Across Prime upgrade.
Timestamps:
01:02 - Intro
01:29 - Understanding intent bridges
03:34 - Liquidity bridges explained
04:34 - UX of intent bridges
05:54 - Risks and security in intent bridging
08:39 - Intent lifecycle
12:36 - Capital efficiency in Across Prime
13:56 - How Across Prime improves capital efficiency
19:35 - Technical details of Across Prime
23:19 - Introduction to relay improvements
23:51 - Challenges in rebalancing funds
26:06 - Capital efficiency and yield
27:54 - Intent bridging & ERC 7683
30:53 - Canonical assets and NFT ridging
36:41 - Fair exchange problem in distributed systems
42:09 - Future of intents in blockchain
44:42 - Final thoughts
Alysia π©βπ»β retweeted
Letβs say you have usdc and you want to deposit into Aave,
What is the process like and what tokens get wrappedβ¦.
If you are curious, watch the video below to find out why from @alysiatech
This is Episode 1 of my video remixing journey with @EspressoSys follow for moreπ€©
Alysia π©βπ»β retweeted
Replying to @EspressoSys
@EspressoSys Team Deck βοΈ Piece 006
Another piece added to the story π
Big shoutout to @alysiatech ,who brings that connecting spark to the teamπ€©
***This cardβs not the end... got a few ideas brewing around this one for the @composablepod
Hope you vibe with it and enjoyπ€
Piece 005 just droppedπ
Sharing another @EspressoSys Team Deck momentβοΈ
This oneβs for @vezzabel π
Made with the same love and creative energy behind it all.
Every card tells a story, but this one is one of my favorites so farπ€©
Hope you vibe with it too π€
Still cooking...βοΈ
Alysia π©βπ»β retweeted
We'll be jumping into a livestream here in 15 minutes to discuss @AcrossProtocol's new model for intent-based crosschain bridging: Across Prime
Weβll unpack:
β’ What is intent-based bridging and how does it work?
β’ How Acrossβs architecture works: relayers, bonding, settlement oracle
β’ What is fair exchange and how is it achieved on Across?
β’ What change does Across Prime introduce?
β’ Why does this improve capital efficiency and security?
β’ Why does the user have to wait two blocks and how protocols like Espresso can help?
β’ Our hot takes and crypto twitter takes
Stay tuned π
Alysia π©βπ»β retweeted
π¨ New ep alert! Are TEEs even real?
In this episode, @alysiatech & @ellierdavidson speak with @OrestTa from @t1protocol about ZK proofs, TEEs, L2 security & how these concepts relate to blockchain finality.
The conversation (timestamps below!) covers:
π @VitalikButerin's recent proposal for a "two out of three" proof system
π TEEs, their strengths & vulnerabilities
π ZK proofs vs TEE proofs
π How t1 uses TEEs + restaking + periodic ZKPs
π How this all relates to L2 security & finality
Timestamps:
1:00 - skip the intro & dive straight in: Ellie introduces @VitalikButerin's 2/3 proof proposal and the episode's guest, Orest from t1
2:29 - Orest shares his experience as an early engineer at @Scroll_ZKP
3:58 - Why ZK rollups haven't succeeded at scaling Ethereum
5:25 - Orest and @kisaguncan, former co-founder of @SecretNetwork, launch t1 protocol to use TEEs to prove rollup integrity
6:24 - What is a TEE? (long explanation)
10:29 - What's a TEE? (concise explanation)
10:59 - How is t1 using TEEs?
12:32 - Remote attestion & why it's a misunderstood term
16:50 - Vitalik's blog post that proposes using a 2/3 proof system (ZK proofs, TEE proofs, optimistic proofs) and proof aggregation to increase security
19:00 - Why aren't ZK proofs enough?
20:29 - Difference between ZK proofs and TEE proofs
28:18 - Side-channel attacks and potential vulnerabilities in TEEs
32:03 - Using TEEs for integrity rather than confidentiality
38:05 - Centralization challenges & security benefits of multiple TEE vendors
41:10 - Mention of projects like Autonomous TEE from
42:35 - Back to Vitalik's post & how t1 uses TEEs + cryptoeconomic security + periodic ZKPs
44:50 - t1's use of restaking
49:43 - Closing thoughts on TEEs and their future use in crypto
Alysia π©βπ»β retweeted
Just shipped the Across Prime paper, a new design for a capital efficient trustless fast bridge authored with @danrobinson, @mrice32, and the @AcrossProtocol team.
Across Prime aims to deliver the near instant speed of intent based bridges but with greater capital efficiency. π§΅
These nail designs by @siannieeee go so hard!!!
dubai fomo is so real right now, missing out on my nail design for @SuiNetwork and @chippedsocial π
fine, i'll paint my own set but be sure to grab yours at sui basecamp okbye!!
1
7
383
Alysia π©βπ»β retweeted
"Sequencer, what big teeth you have!"
Great talk by @charleslu1 @token2049 about interoperability and reorgs.
@linkpoolio is a proud to supporter of @EspressoSys
Orest (@OrestTa) spilled all the tea about TEEs this morning with @ellierdavidson and I!
Canβt wait for this episode of @composablepod to drop next week!!!
Which types of L2s achieve the fastest finality whilst being sufficiently secure & decentralized?
1
10
295
Alysia π©βπ»β retweeted
"Oh, have a problem with your design? Just throw a TEE in there!" π
New episode about to drop. @alysiatech & @ellierdavidson discuss how crosschain messages are secured... yes, including with TEEs
Alysia π©βπ»β retweeted
Who Secures Crosschain Messages?
Dive in w/ @alysiatech & @ellierdavidson as they explore this topic:
01:08 - Focus on crosschain message security
01:24 - Analysis of the Ronin bridge attack
03:25 - Discussion of the Wormhole attack
07:26 - Overview of the Orbit bridge attack
10:22 - Anatomy of a crosschain message
11:37 - Key vulnerabilities in crosschain messaging
12:33 - Multisig security approaches & trust assumptions
15:26 - Analysis of multisig effectiveness & limitations
17:06 - Practical considerations of multisig implementations
19:57 - Liveness issues in multisig systems
21:11 - Introduction to TEEs
22:13 - How TEEs verify crosschain messages
23:17 - Limitations of TEE security approaches
24:57 - Comparison of TEE & multisig security models
28:20 - Discussion of potential improvements to security models
29:45 - Brief mention of ZK proofs as an alternative approach

























