MAB

[MAB @MAB]

@enspiration_eth Triple digits coming

[MAB @MAB]

so, how's ens v2 going?

[Tat Thang @tatthang]

Nissan sued a computer repairman for $10,000,000 to take the Nissan․com domain.

His legal last name was Uzi Nissan.

He refused to fold, spent $3,000,000 fighting them in federal court for 8 years, and won.

This is the story of Uzi Nissan and why a $20B car giant still can't use Nissan․com.

1980-1994

- Uzi Nissan emigrates from Israel to Raleigh, North Carolina
- opens a small auto repair shop in 1980 using his family surname
- launches Nissan Computer Corporation on May 14, 1991 selling PCs and servers
- registers Nissan․com on June 4, 1994 for $70 while the automaker barely touches the web

December 10, 1999

- Nissan Motor Co. realizes a North Carolina PC shop owns their exact domain
- instead of paying his asking price, the automaker files a $10,000,000 federal lawsuit for cybersquatting
- Uzi refuses to back down and turns the homepage of Nissan․com into a public archive of their legal threats

1999-2007

- the court battle drags on for 8 years across district court, the Ninth Circuit, and a Supreme Court petition
- Uzi spends over $3,000,000 in legal fees and takes out two mortgages on his home
- federal judges rule a corporation can't strip a man of a domain built on his own birth name

July 2020 - Today

- Uzi Nissan passes away from COVID-19 in July 2020 at age 68
- when thieves hijack the domain after his death, a federal judge orders Nissan․com returned to his family estate in April 2024

To this day, Nissan Motors is forced to use NissanUSA․com.

If you type Nissan․com into your browser right now, you still don't get a car dealership.

You get a memorial to the computer repairman who beat a multinational giant over his own last name.

[MAB @MAB]

@TGLetter Should take better care of your security

[sterilized objectivity @AutoDiddakt]

@MarioNawfal Closer shot

[Binance @binance]

Binance's initial investigation suggests that the security incident may involve a compromised DevOps engineer’s laptop, which allowed an attacker to gain access to a service container and submit unauthorized withdrawal transactions. We have found no evidence of any wallet private key leak. We will share a detailed technical post-mortem once the investigation is complete and the facts are fully verified.

The estimated total impact sits at around $6.3B. We have worked with blockchain partners to freeze affected assets, with ~$3 billion frozen on-chain so far.
Binance will cover all losses from the SAFU fund and the company’s funds. User funds are safe. We will also publish an updated Proof of Reserves once the remediation is complete.

As an immediate precaution, Binance has:

- temporarily suspended deposits and withdrawals while security checks are completed;
- revoked the affected address authorisation;
- engaged law enforcement and blockchain intelligence partners to trace and recover funds.

Our teams are working around the clock to resolve this issue safely and thoroughly. We are working closely with our law enforcement partners to confirm the identity of these criminals and bring them to justice.

Please rely only on official Binance channels for updates. Please feel free to contact Binance Customer Support if you have any further questions.

https://t.co/ywB2mKFy0p

[validator.eth @ValidatorEth]

Quote tweet this with your .eth

validator.eth

[Mario Nawfal @MarioNawfal]

Shill me your $ENS domain, looking to possibly ape👇💭

[ZachXBT @zachxbt]

@AnonHbar No, the answer is that Algorand is a poverty ecosystem so exploiters think it is not worth looting since the reward would be so small.

[sns.sol @sns]

The .sol upgrade is coming.

Current .sol holders will end up with two domains:

1. yourname.sns
2. yourname.sol

Here's what that means ↓

[Volcaholic 🌋 @volcaholic1]

A tornado sent a car airborne in Haining, Zhejiang Province in China on Sunday.... �