Coding Life

A journey of a thousand miles begins with a single step

0%

Why So Many European Tech Websites Still Feel Stuck in 2005

Recently I tried to register for several European VPS providers. What should have been a simple five-minute task somehow turned into a frustrating hour of page reloads, mysterious errors, and endless loading spinners. It made me wonder: why do so many European tech websites still feel like they are built for the internet of 2005?

This isn’t about a single company. After trying multiple providers across different countries, I kept running into the same problems again and again.

Introducing Simple7702Account and Universal7702Account: EIP-7702 Smart Account Implementations

The Ethereum ecosystem is evolving rapidly, and EIP-7702 represents one of the most significant upgrades to account abstraction. In this post, we’ll explore two production-ready implementations: Simple7702Account and Universal7702Account, designed to bring smart contract functionality to Externally Owned Accounts (EOAs).

Why This Project?

In typical scenarios—such as facilitating simple transfers for custodial wallet users—the existing ERC-4337 paymaster solutions present significant challenges:

  • Overly Complex: ERC-4337 requires a full bundler infrastructure, entry point contracts, and complex paymaster logic
  • Third-Party Dependencies: Many solutions rely on external services like Pimlico, Alchemy, or other infrastructure providers
  • High Integration Cost: Setting up and maintaining the entire 4337 stack is resource-intensive

For many use cases, you don’t need the full power of ERC-4337. What you need is a simple, direct way to sponsor transactions for your users.

What is JWT

JSON Web Token (JWT) is an open standard (RFC 7519) that defines a compact and self-contained way for securely transmitting information between parties as a JSON object. This information can be verified and trusted because it is digitally signed. JWTs can be signed using a secret (with the HMAC algorithm) or a public/private key pair using RSA or ECDSA.

Since the COVID-19 outbreak in 2019, we have seen all kinds of de-globalization trends and new restrictions. After the war in Ukraine, people also began to question the ongoing de-globalization of finance. Can the US dollar still be trusted? Can the financial institutions of neutral countries still be trusted? Behind all of these trust crises is a deeper signal: decentralized assets such as BTC and ETH point toward a better long-term direction for humanity.

We are standing at the crossroads of a major transformation.

The AAVE v3 codebase had already been audited and was close to release when this post was written. This version focused mainly on several themes:

  • capital efficiency
  • risk-control strategy
  • decentralization
  • cross-chain support

The AAVE v3 contracts are open source:

https://github.com/aave/aave-v3-core

Let’s look at the major improvements this release introduced.

Redis transactions can be implemented in two ways: with MULTI, or with Lua scripts. Lua scripts are simpler, require fewer client-server interactions, and can be cached by Redis, which makes them especially useful in performance-sensitive scenarios.

Because AAVE contains many contracts, its deployment process is correspondingly complex. AAVE splits deployment into seven tasks, each implemented as a hardhat task, and then uses a full task to orchestrate deployment and initialization end to end.

Full task

Inside package.json, the project defines many deployment commands. The following one deploys to mainnet and verifies contracts: