DimKos

bad♧boy

[DimKos @DimKos5]

@Recoverlt Yes, certainly. Here is the wallet address where the ATOM coins were transferred:
cosmos19tzwf85z433xx20h0xksuq66xrfp0kq82j4aq4

And here is the wallet address where the TIA coins were transferred:
celestia19tzwf85z433xx20h0xksuq66xrfp0kq8mcyd6c

[DimKos @DimKos5]

@NouraHam35 I don't know how the account was hacked. I just kept staking coins there. and at 5 o'clock in the morning i woke up with a message from the wallet that I was transferring my funds somewhere to another account

[DimKos @DimKos5]

@Bruce__Ledger The subsequent transfers were already from the Kepler team—to safeguard against further attacks on my wallet.
This wallet number is on the list.

[DimKos @DimKos5]

@Bruce__Ledger I have proof! Support chat confirmed that the address to which my funds were sent belongs to a scammer. Furthermore, earlier today, more tokens disappeared from my account.

[DimKos @DimKos5]

@mantas11 @TheHackersNews And everything of mine disappeared later, too. It’s absurd, but unfortunately, it’s the reality we live in today. No wallet is safe anymore.

[DimKos @DimKos5]

@0xMirageX47 @TheHackersNews Earlier today, all the tokens disappeared from my account. I always thought a wallet was very secure, but now I don’t know what security even means.

[DimKos @DimKos5]

@Tracecoreintel Unfortunately, I couldn’t do anything. They didn’t stop there; they continued making further withdrawals, and I didn’t even have time to take any action.

[DimKos @DimKos5]

@HotFiredrops 10b

[DimKos @DimKos5]

@realDonaldTrump Я таких людей раньше только в кинокомедиях видел.

[vitalik.eth @VitalikButerin]

There have recently been some discussions on the ongoing role of L2s in the Ethereum ecosystem, especially in the face of two facts:

* L2s' progress to stage 2 (and, secondarily, on interop) has been far slower and more difficult than originally expected
* L1 itself is scaling, fees are very low, and gaslimits are projected to increase greatly in 2026

Both of these facts, for their own separate reasons, mean that the original vision of L2s and their role in Ethereum no longer makes sense, and we need a new path.

First, let us recap the original vision. Ethereum needs to scale. The definition of "Ethereum scaling" is the existence of large quantities of block space that is backed by the full faith and credit of Ethereum - that is, block space where, if you do things (including with ETH) inside that block space, your activities are guaranteed to be valid, uncensored, unreverted, untouched, as long as Ethereum itself functions. If you create a 10000 TPS EVM where its connection to L1 is mediated by a multisig bridge, then you are not scaling Ethereum.

This vision no longer makes sense. L1 does not need L2s to be "branded shards", because L1 is itself scaling. And L2s are not able or willing to satisfy the properties that a true "branded shard" would require. I've even seen at least one explicitly saying that they may never want to go beyond stage 1, not just for technical reasons around ZK-EVM safety, but also because their customers' regulatory needs require them to have ultimate control. This may be doing the right thing for your customers. But it should be obvious that if you are doing this, then you are not "scaling Ethereum" in the sense meant by the rollup-centric roadmap. But that's fine! it's fine because Ethereum itself is now scaling directly on L1, with large planned increases to its gas limit this year and the years ahead.

We should stop thinking about L2s as literally being "branded shards" of Ethereum, with the social status and responsibilities that this entails. Instead, we can think of L2s as being a full spectrum, which includes both chains backed by the full faith and credit of Ethereum with various unique properties (eg. not just EVM), as well as a whole array of options at different levels of connection to Ethereum, that each person (or bot) is free to care about or not care about depending on their needs.

What would I do today if I were an L2?

* Identify a value add other than "scaling". Examples: (i) non-EVM specialized features/VMs around privacy, (ii) efficiency specialized around a particular application, (iii) truly extreme levels of scaling that even a greatly expanded L1 will not do, (iv) a totally different design for non-financial applications, eg. social, identity, AI, (v) ultra-low-latency and other sequencing properties, (vi) maybe built-in oracles or decentralized dispute resolution or other "non-computationally-verifiable" features
* Be stage 1 at the minimum (otherwise you really are just a separate L1 with a bridge, and you should just call yourself that) if you're doing things with ETH or other ethereum-issued assets
* Support maximum interoperability with Ethereum, though this will differ for each one (eg. what if you're not EVM, or even not financial?)

From Ethereum's side, over the past few months I've become more convinced of the value of the native rollup precompile, particuarly once we have enshrined ZK-EVM proofs that we need anyway to scale L1. This is a precompile that verifies a ZK-EVM proof, and it's "part of Ethereum", so (i) it auto-upgrades along with Ethereum, and (ii) if the precompile has a bug, Ethereum will hard-fork to fix the bug.

The native rollup precompile would make full, security-council-free, EVM verification accessible. We should spend much more time working out how to design it in such a way that if your L2 is "EVM plus other stuff", then the native rollup precompile would verify the EVM, and you only have to bring your own prover for the "other stuff" (eg. Stylus). This might involve a canonical way of exposing a lookup table between contract call inputs and outputs, and letting you provide your own values to the lookup table (that you would prove separately).

This would make it easy to have safe, strong, trustless interoperability with Ethereum. It also enables synchronous composability (see: https://t.co/9jy6v1X6Fw and https://t.co/gZmu3YjebM ). And from there, it's each L2's choice exactly what they want to build. Don't just "extend L1", figure out something new to add.

This of course means that some will add things that are trust-dependent, or backdoored, or otherwise insecure; this is unavoidable in a permissionless ecosystem where developers have freedom. Our job should make to make it clear to users what guarantees they have, and to build up the strongest Ethereum that we can.

[DimKos @DimKos5]

Пам’ятаєте, коли ви приєдналися до X? Я пам’ятаю! #MyXAnniversary

[DimKos @DimKos5]

@DIAdata_org gm

[DimKos @DimKos5]

@blumcrypto Gm

[Bondex @bondexapp]

$BDXN was launched on @Binance, @Coinlist, @Bybit_Official, @MEXC_Official, @bitgetglobal, @Gate_io, @Krakenfx and @DEXToolsApp 🌟

These partnerships are set to propel us into the next chapter of our journey, making it easier for you to trade and grow with Bondex. 💱

[DimKos @DimKos5]

@hungrybera @cookedcxnts 0x4Bc5A3f5979C8e7c253f73B5E7E99E8C87e79BCD

[DimKos @DimKos5]

@cookedcxnts 0x4Bc5A3f5979C8e7c253f73B5E7E99E8C87e79BCD

[DimKos @DimKos5]

@hotdao_ Berachain

[DimKos @DimKos5]

@elonmusk @realDonaldTrump This madness will soon come to an end.

[DimKos @DimKos5]

@Bybit_Official please reply and help me the current situation. for several days now i can't send money from web3 wallet to my trading account or to any other account. support asked for the account number and now all days are silent.
0x1d19019286bc6ffa792007fca9225967207b367c

@benbybit