Joe Pegler @Joepegler

Web3 Infrastructure Engineer - ERC-4337 execution infrastructure, smart accounts, and cross-chain SDK systems peglerweb.services Cork Joined July 2012

Tweets

142
Followers

79
Following

176
Likes

56

Joe Pegler @Joepegler

3 months ago

In 2018 I published a TradingView Pine Script called “Simple profitable trading strategy.” It got traction, but the real lesson was not the equity curve. It was how a 100x fee-assumption mistake changed the outcome. I wrote a technical retrospective on backtests vs execution reality: fees, slippage, fills, latency, and automation risk. peglerweb.services/blog/backtests…

0 0 0 65 0

View Details

Joe Pegler @Joepegler

3 months ago

peglerweb.services/resume.html

0 0 0 21 0

View Details

Joe Pegler @Joepegler

3 months ago

Available for my next role. Staff/infrastructure engineer focused on low-latency execution systems, SDKs, smart accounts, and production reliability across EVM/Solana. Best fit: serious infra, protocol-adjacent product, execution, devtools, or founding-engineer-style IC work. Remote preferred. Cork, Ireland. DMs open.

1 0 1 56 0

View Details

Joe Pegler @Joepegler

3 months ago

If your viem.sh tests are getting harder to extend than the code they’re testing, this is probably why. Statecraft keeps chain state explicit, forks pinned, and helper sprawl out of the test body. Docs: statecraft.services GitHub: github.com/joepegler/stat…

0 0 0 25 0

View Details

Joe Pegler @Joepegler

3 months ago

The useful part is that fixture order is setup order. You can read a test and see: which chain it runs on whether the fork is pinned which wallet exists which balances/contracts were injected Deterministic beats clever.

1 0 0 23 0

View Details

Joe Pegler @Joepegler

3 months ago

Most Ethereum integration tests start clean, then collapse into beforeEach soup. Fork setup in one helper. Wallet funding in another. Token state somewhere else. By the time a test fails, nobody can tell what state it actually depends on.

1 0 0 42 0

View Details

Joe Pegler @Joepegler

4 months ago

@ZubyMusic Most people are fully versed in second order thinking when it suits their POV. I fixed it.

0 0 0 16 0

View Details

Joe Pegler @Joepegler

4 months ago

@abstractooor withMultichain could be a useful addition🤔💡

0 0 1 28 0

View Details

Joe Pegler @Joepegler

4 months ago

I’ve been thinking about this friction a lot too. A lot of EVM test pain isn’t the test body, it’s the setup: funded wallets, deployments, balances, fork state, chain-specific config. Been building toward that from the scenario/runtime side with statecraft.services. Feels very complementary.

1 0 0 36 0

View Details

Joe Pegler @Joepegler

4 months ago

@decentrek Hey Derek great post, I'll join the chat tomorrow. Any place we might be able to play around with them yet, like a test geth branch buried somewhere that I don't know about? I've poked around but I've not been able to put my hands on anything

1 0 4 423 0

View Details

Joe Pegler @Joepegler

4 months ago

Wrote up an approach I'm calling "bring your own bundler" for sponsored ERC-4337 on EntryPoint v7. Strip the UserOp to almost nothing, no gas-price or paymaster RPCs before signing, parallelize the rest. Faster and cheaper than I expected: peglerweb.services/blog/faster-sp…

0 0 1 56 0

View Details

Joe Pegler @Joepegler

4 months ago

@dwr What's the KYC situation?

0 0 1 49 0

View Details

Joe Pegler @Joepegler

5 months ago

Crossmint, but it actually works: – consistent token payloads – funds released before completion – respects user slippage – 1inch → OKX fallback – no slippage bugs – no VPN blocking – no KYC for stables – real error messages Feels like putting them out of their misery 😂

0 0 1 74 0

View Details

Joe Pegler @Joepegler

5 months ago

@ox_shaman Stay safe sir

0 0 0 28 0

View Details

Joe Pegler @Joepegler

9 months ago

@biconomy @askginadotai Do people really want to 'chat' in order to have their trades executed? 'Chatting' to me is mostly unserious, ill defined, prone to error, throwaway / light hearted & easily forgotten.

2 0 1 172 0

View Details

Joe Pegler @Joepegler

12 months ago

Try it on defi.app with zero native balance and swap a 2612‑enabled token (approvals are inherently free/sponsored for the supported tokens). If you hit odd variants or unsupported edge cases, ping me - keen to tighten the flow

0 0 0 64 0

View Details

Joe Pegler @Joepegler

12 months ago

domain = { name, version: '1' | on‑chain, chainId, verifyingContract }, message = Permit(owner, spender, value, nonce, deadline). This has been reliable across multiple 2612 implementations.

1 0 0 92 0

View Details

Joe Pegler @Joepegler

12 months ago

The trap: “no gas, no approval, no ERC‑20 swap.” External wallets can hold plenty of tokens, but with zero native balance they can’t send the approval tx. You’re in a cul‑de‑sac.