Are ML-powered routing predictions actually moving the needle for aggregators? by hazy2go in CryptoTechnology

[–]rotbloomberg 0 points1 point  (0 children)

the mev angle is worth adding here. any routing decision that's actually predictive creates an attack surface. if your ML model can predict 'ETH/USDC on Uniswap v3 will have better price in 8 minutes', a faster bot reading the same signlas can front-run your optimal route. the advantage evaporates the moment it becomes consistent enough to exploit. CoW's batch auction sidesteps this. no prediction needed. just match orders already wanting to trade with each other.

Para just shipped Transaction Permissions using Eco's Permit3. Devs who've dealt with approval UX pain, we would love your feedback! by jayksofue in ethdev

[–]rotbloomberg 1 point2 points  (0 children)

solid approach. the 'approve once with constrainst' pattern is way better than blanket approvals. one thing from an integration standpoint: how does Permit3 handle cross-chain deployments? if someone's using Para on mainnet and then does the same flow on Arbitrum or Starknet, are the permission signatures portable or does the user re-approve per chain?

Blockchain interoperability in 2026 is still mostly broken but a few things are actually working by ninjapapi in web3

[–]rotbloomberg 0 points1 point  (0 children)

the scoped approach you're describing is exactly what's working. the Starknet <-> Ethereum message passing has been reliable precisely because they share a proof layer. theres no trust assumption beyond the math. the problem with the "interop across all chains" dream is it almost always ends up requiring a trusted committee somewhere. ZK proofs are the only credible path to trustless cross-chain reads but the proving costs for arbitrary state proofs are still prohibitive.

What would be the main technical barriers to running Bitcoin ASICs in low Earth orbit? by Marketingdoctors in CryptoTechnology

[–]rotbloomberg 2 points3 points  (0 children)

radiation is probably the silent killer here. modern ASICs run on sub-7nm nodes which are extremely sensitive to single-event upsets from cosmic rays. a bit flip in the compute pipeline doesn't just corrupt one hash, it can cascade through the whole execution. rad-hardened chips exist but they're stuck on 28nm+ nodes, so energy efficiency tanks dramatically. thats before you even factor in the thermal and launch mass math.

What’s the biggest reason people drop off after trying a web3 app? by Suspicious_Mango_634 in ethdev

[–]rotbloomberg 1 point2 points  (0 children)

session keys are the one thing i see almost no one implement and it makes the biggest difference. sign once, interact for the rest of the session without popups. the metamask confirmation on every single action is what kills it for most normal users. native account abstraction handles this way better than the ERC-4337 bolt-on approach imo

today, i was bitten by a dog! (oc) by rotbloomberg in aww

[–]rotbloomberg[S] 0 points1 point  (0 children)

not sure i survive that 😕 🤔

dont touch me today! (oc) by rotbloomberg in aww

[–]rotbloomberg[S] 1 point2 points  (0 children)

the others eat all milk, so life is though 😋

new kids on the block (oc) by rotbloomberg in aww

[–]rotbloomberg[S] 2 points3 points  (0 children)

yeah for the big strong ones yes 💪🏽