$EXPIRY follow

HISTORY EXPIRED.

the chain forgets the past. so should you.
a community meme for EIP-4444, lighter nodes and self-hosted ethereum.

CA launching on sender.family · TBA
buy $EXPIRY what is 4444?
~12hto sync a node
<0.5 TBdisk, aggressive settings
300–500 GBpre-merge history pruned
1,000,000,000$EXPIRY fixed supply

// the story

the chain learned to forget.
most of yall still cant.

for years, running an ethereum node meant hoarding every block ever made. terabytes of history nobody asked you to read. a server-rack flex.

EIP-4444 changed the deal: old history expires, nodes carry what matters, and syncing drops to about half a day. $EXPIRY is a meme for that idea. drop the dead weight, keep the chain, own your rpc.

// eip-4444: history expiry

then vs now

then

  • every node stores all history since 2015
  • multi-day sync, huge disks
  • most people just trust someone else's rpc

now

  • pre-merge history pruned, 300–500 GB saved
  • sync in ~half a day, under 0.5 TB with aggressive settings
  • your laptop can be the rpc. localhost is home

  1. partial history expiry goes live. all execution clients can drop pre-merge block data.

    ethereum foundation blog ↗

  2. vitalik: nodes now sync within half a day, under half a terabyte on aggressive settings, thanks to EIP-4444 and snap sync work by client teams.

    read the post ↗

  3. glamsterdam improves sync further, and rolling-window history expiry is the long-term goal.

fun fact: uniswap v4's PoolManager lives at 0x000000000004444c5d… — the pool your $EXPIRY trades in literally says 4444.

// token

launched fair on sender.family

liquidity locked forever

the whole supply sits in a uniswap v4 position held by a locker with no withdraw path. nobody can pull it, including the deployer.

fixed supply

1,000,000,000 $EXPIRY. no mint function, no owner, no team allocation. the dev buys on the same curve as everyone.

snipe protection

first 3 blocks are guarded: max 2.5–4% of supply per buy and 5% per wallet. dev buy is public on the token page.

1% trade fee

70% of every trade fee goes to the creator side, 30% to the $SEND burn and protocol.

// how to buy

four steps, no browser drama

  1. 01

    get a wallet

    any ethereum wallet works. hardware wallet if you are serious.

  2. 02

    get ETH on mainnet

    $EXPIRY lives on ethereum mainnet, paired with ETH.

  3. 03

    verify the CA

    only trust the contract posted here and on @expired_eth. fakes will show up in replies.

  4. 04

    swap on sender

    open the token page on sender.family and buy. or route it through any uniswap v4 aware router.

// bonus: localhost is home

run your own node this weekend

the meme has a point: point your wallet at a node you run yourself. no hardcoded rpc watching your every call.

  • 2 TB NVMe SSD (under 0.5 TB used with aggressive pruning)
  • 16 GB+ RAM, decent broadband
  • an execution client + a consensus client
  • ~half a day of patience
check your node's sync →
bash
# 1. run an execution + consensus client pair
# (reth / geth / nethermind  +  lighthouse / nimbus)

# 2. expose rpc locally only
--http --http.addr 127.0.0.1 --http.port 8545

# 3. point your wallet / scripts here
RPC_URL=http://127.0.0.1:8545

✓ history expired. rpc is yours.

// faq

questions

is this affiliated with vitalik or the ethereum foundation?

no. $EXPIRY is an independent community meme inspired by EIP-4444. it is not endorsed by vitalik buterin, the ethereum foundation or any client team.

does $EXPIRY have utility?

no roadmap, no promises, no utility. it is a meme for people who would rather sync than scroll.

can the dev rug the liquidity?

the liquidity is locked in a contract with no withdraw path, so it cannot be pulled. the dev can still sell tokens they bought, like anyone. the dev's opening buy is shown on the sender token page.

where is the official contract address?

only on this site and pinned on @expired_eth. we will never DM you a CA.