
Tech Product Manager at @GetBlockio. Helping developers build decentralized applications with ease.
Germany, Berlin
Joined June 2022
- Tweets532
- Following136
- Followers227
- Likes1.5K
Pinned Tweet
I've been working on this solution for a couple of weeks.
Viable overlay_getLogs methods are still terra incognita, actually. So, we have no choice but to be trailblazers here!
The folks at @getblockio have been amazing partners.
We needed a working overlay_getLogs on a Base node, and they delivered fast.
They coordinated required fixes with the op-erigon team, patched some additional found issues themselves, and got the node running smoothly.
Top team to build with 🤝
three add-ons now live on dedicated nodes:
erc-4337 methods for account abstraction traffic
beacon api for consensus layer access, blob data included
overlay methods to replay calls against modified state at any historical block
attach any of them at order time in the configurator.
Ask AI is live on GetBlock
five assistants, five entry points. pick one from any page and it opens with the question already written for that context: general fit, product choice, or integration.
answers reflect our current pricing, not whenever the model was trained.
we also cut what an assistant has to read before it can answer, which is most of why the answers come back accurate: getblock.io/blog/ask-ai-butt…
limitless node is self-serve as of today. deploy from your account the same way you deploy a dedicated node: fixed rps, unlimited requests, no compute unit metering, no sizing call. bsc added to supported chains.
First self-reply:
limitless node, full self-serve: account.getblock.io/limitles…
operational detail from the eez workshop: eez calls cannot go through the public l1 mempool.
a proxy called outside the composer bundle reverts, the lookup table is not there. orderflow has to reach the composer via bundle or account abstraction.
full workshop digest: docs.fileverse.io/d/02000129…
shipped: higher rps ceilings on every paid shared node plan, same price.
starter 100 to 250, pro 500 to 800. up to 2.5x on the entry tier.
nothing to migrate or reconfigure, compute unit allocation unchanged. already live on the plan you hold.
shared nodes, up to 150% higher rps: getblock.io/pricing/
robinhood chain is live on getblock
- shared nodes: mainnet, https + wss, hosted in us east
- dedicated: mainnet + testnet, new york / frankfurt / singapore, soc 2-attested hardware
free plan works
favorite design decision: the sequencer takes transactions in arrival order, so priority gas auctions have nothing to bid on. blocks land every ~100ms. try to keep up.
four names off the board in a week:
- zapper winding down aug 3
- summerfi shut after an exploit
- sablier into maintenance mode till 2028
- grove winding down after 9 years
the last bear did not clear the field this fast.
agentic tooling is live at GetBlock. new agents tab in the dashboard.
first up is migration. point your ai agent at one runbook.
> assess: env vars, config files, hardcoded urls.
> plan: maps each endpoint to getblock, waits for approval.
> implement: rewrites, verifies with eth_chainid.
Give it a try: get docs.getblock.io/migration/m…
new status page is live.
better stack pings every node once a minute, so status reflects the last 60 seconds, not the last hour.
every major protocol, testnet and mainnet, split by cluster: sg, ny, fra.
COMMENT: fewer tickets, more signal: status.getblock.io/
the ownership fight misses the engineering. one-shot payment objects trace to bitcoin's utxo model in 2009, before cardano shipped.
wahrstätter's native utxo post reuses that to skip permanent account state on simple transfers: ~99.8% less state on simple payments, general smart-contract state untouched.
the real question is whether one-shot outputs and account balances coexist without wrecking composability or serializing hot state under contention. and it's a research post,
no eip, no hard fork yet. priority claims ship nothing, running code does.
NEW: Flashblocks support on our Optimism and Base RPC
what it does: instead of waiting ~2s for a full block, you get preconfirmed state in ~200ms subblocks.
the chain streams incremental updates as transactions land, not after the block closes
no upgrade, no migration.
point your OP or Base traffic at our nodes and Flashblocks are here:
getblock.io/nodes/base/
SOC 2 Type II: done.
An independent auditor testing our controls over a sustained window and confirming they held under real operating conditions.
security, availability, confidentiality. verified, documented, and now on the record for any team that needs it before they can integrate.
COMMENT:
What does SOC 2 Type II actually mean, technically?
Three things worth mentioning: getblock.io/blog/soc-2-type-…
GITEX AI Europe in Berlin was a lit one.
it made a point the discourse keeps missing: it's too early to bury European tech.
blockchain, AI, deeptech, cybersec, all showing up strong on the floor. the pessimism travels faster than the facts.
and a note for builders: the point of these events was never networking or the flex. it's the ideas you walk out with that change how you approach the work.
that's the whole ROI
great show. already putting what I learned to use.
New shared plans live at GetBlock:
– growth ($99): 150 RPS, 105M CU, 15 endpoints. 1.5x starter throughput, roughly half the 429s under load
– scale ($349): 400 RPS, 400M CU, 35 endpoints. team mode — multiple seats, one key
– premium ($699): 700 RPS, 900M CU, 75 endpoints. fastest shared config we've run
eight shared tiers now.
specs and calculator: getblock.io/pricing/
If your request rate is predictable, Limitless Node is a smart bet: getblock.io/limitless-node/
.@tempo is on getblock.
stripe + paradigm's payments chain: stablecoin gas, dedicated blockspace for payments, memo fields for clean reconciliation.
endpoint in 3 clicks → json-rpc or websockets, testnet + mainnet, shared or dedicated.
Try: getblock.io/nodes/tempo/
aztec, hacked twice in a week, ~$2.15M each. same class of bug: public input binding issues
thursday's hit the escapeHatch, an emergency withdrawal function. attacker sets crafted proofId + publicOutput, contract releases funds it shouldn't. the proof wasn't bound to the output tightly enough
aztec says the contracts were immutable and deprecated since 2022-23. both true, and both irrelevant to the people who lost 1,158 ETH. immutable means you can't fix it. deprecated means you stopped watching it. funded means it was still worth attacking
14 bridge exploits in 2026, $340M+ total. deprecated contracts with live balances are the softest target in the space right now
shipped: Crypto Address Audit.
one API key, three checks:
> wallet risk → go/no-go in <100ms
> full audit → full behavioral profile of a wallet
> rug pull → scores the deployer + LPs behind a token
5 free checks/day, then $0.20.
Docs: docs.getblock.io/crypto-addr…
Dmitrii retweeted
Latergram from Solana Summit Germany, courtesy of our Berliner-in-chief @GetBlockProd
Great time with cracked guys from @velia_net - server infrastructure done right! - and Solana powerhouse @triton_one
Always better in person. Berlin delivers.
Danke vielmals @SuperteamDE 🇩🇪





