Ian Norden (@iansnorden) 's Twitter Profile
Ian Norden

@iansnorden

Biochemist turned programmer.
Research Engineer @Polymer_Labs
Previously @laconicnetwork

ID: 1024058552435003393

linkhttps://github.com/i-norden calendar_today30-07-2018 22:25:59

2,2K Tweet

1,1K Followers

1,1K Following

Ian Norden (@iansnorden) 's Twitter Profile Photo

I think this is as much of an application design problem as it is a centralized sequencer problem. Being able to set limit orders would circumvent censorship by sequencer front-running as arixon says here. In the AAVE case, couldn't you prevent censorship by making it so that

Ian Norden (@iansnorden) 's Twitter Profile Photo

Both Hayden and David are correct. The issue with L2 issued assets is not that they can't be withdrawn to the L1 if the sequencer goes down- they can be- the issue is that 1. The value of those withdrawn assets is dubious (subject to weaker social consensus) 2. L2 issued assets

Polymer Labs πŸ›œ (@polymer_labs) 's Twitter Profile Photo

Rise and shine #ETHDenver2025 Catch our all-stars Peter Kim πŸ›œ Bo Du πŸ›œ PolymerUther Tommy πŸ›œ Mav πŸ›œ Ian Norden Liz Ralston at the following eventsπŸ‘‡πŸ» Feb 25 Rollup & Prove It: lu.ma/506nul3h Rollup For Drinks: lu.ma/jga6vw7j Feb 26 Abstract Brunch:

Rise and shine #ETHDenver2025 

Catch our all-stars <a href="/0xPeterKim/">Peter Kim πŸ›œ</a> <a href="/0xbodu/">Bo Du πŸ›œ</a> <a href="/Sadwire23/">PolymerUther</a> <a href="/tommyoc0/">Tommy πŸ›œ</a> <a href="/dpbmaverick98/">Mav πŸ›œ</a> <a href="/IanSNorden/">Ian Norden</a> <a href="/ECRals42/">Liz Ralston</a>  at the following eventsπŸ‘‡πŸ»

Feb 25
Rollup &amp; Prove It: lu.ma/506nul3h
Rollup For Drinks: lu.ma/jga6vw7j

Feb 26
Abstract Brunch:
Polymer Labs πŸ›œ (@polymer_labs) 's Twitter Profile Photo

One Proof. Twenty Fills. All In Real Time Eco's Lead Technical PM Christian demonstrates how Polymer's Prove API can validate multi-party + multi-chain intents with a single proof πŸ›°οΈ Even as the # of fills increase, the cost stays static. That's how Polymer scale intents

Mav πŸ›œ (@dpbmaverick98) 's Twitter Profile Photo

As a PM obsessed with devX and product design, it brings me a lot of joy seeing applications building with the Prove API. Messaging was not built for performance or scale - imagine repaying solvers for 20 fills with 20 bridge transactions costing $1-2 each, - plus the

Ian Norden (@iansnorden) 's Twitter Profile Photo

This is the right way to tokenize equities. Synthetic assets are not real β€œRWAs”. Real RWAs will be crypto first. Synthetic assets can confer some positive properties on the underlying asset like the ability to self custody and transfer and exchange 24/7 but as long as the

Ian Norden (@iansnorden) 's Twitter Profile Photo

CR provided by permissionless block producers is proactive, forking is reactive. Forking is delayed and some amount of social activation energy needs to be overcome before it will kick it. That is not to say that one needs permissionless block building but I'm not convinced that

LI.FI (@lifiprotocol) 's Twitter Profile Photo

Panel Announcement: Push or Pull for Interop πŸ“£ Ian Norden, Christopher Goes & Ossi join Georgios to discuss whether the future of interop is push-based (message passing), pull-based (state reading), or something in between. Register now: lu.ma/vn99pm53

Panel Announcement: Push or Pull for Interop πŸ“£

<a href="/IanSNorden/">Ian Norden</a>, <a href="/cwgoes/">Christopher Goes</a> &amp; Ossi join <a href="/geogont/">Georgios</a> to discuss whether the future of interop is push-based (message passing), pull-based (state reading), or something in between.

Register now: lu.ma/vn99pm53
Polymer Labs πŸ›œ (@polymer_labs) 's Twitter Profile Photo

Watch our own Ian Norden discuss a push vs pull development approach. Push models deliver real-time updates automatically at a higher cost, while Pull models respond on request with more control but added delay. Our Prove API balances both approaches to optimize for user