@onrampmoney@onrampmoney I am trying to buy ETH on Base through your platform but getting “Something went wrong, contact support” during payment. Can’t submit a ticket either since no Order ID/UTR was generated. Please help or direct me to the right team.
I've completed the Fundamentals of Zero-Knowledge Proofs course!
A 1-hour course to learn:
- ZKP Fundamentals
- ZKP requirements
- Keywords, Trusted Setups, and more!
Completely for free. Check it out 👇 https://t.co/trRmVfS0tM
With restaking expanding shared security beyond L1,
are we still treating it as a feature,
or is it redefining Ethereum’s role as a generalized security marketplace? @eigencloud@renzoai#Restaking#Ethereum#EigenLayer
Here's what I built at HackMoney 2026 hosted by @ethglobal:
⚡ PulseBet – Instant sports betting with zero gas fees using Yellow Network state channels on Base Sepolia.
Check it out here: https://t.co/sbDLeQrXFw
8/
TL;DR: Remix isn't doing anything special. ABI tells it how to encode calls, address tells it where to send them. Proxies work because delegatecall runs implementation code in proxy's storage context—but only if layouts match.
Still learning this—corrections welcome
1/
Something clicked for me about Solidity proxy patterns today.
When using Remix with upgradeable contracts, you can load the implementation's ABI, point it at the proxy's address, and call functions directly.
Here's what's actually happening under the hood 🧵
7/
Two patterns solve upgrade safety differently:
Transparent Proxy: upgrade logic in proxy (gas-heavy)
UUPS: upgrade logic in implementation (lighter, more flexible)
Both prevent function clashing and storage collisions, but UUPS is now the recommended approach.