Alberto GSola

Dulce est sapere

[Kim Dotcom @KimDotcom]

Breaking

Palantir was allegedly hacked. An AI agent was used to gain super-user access and here”s what the hackers allegedly found:

Peter Thiel and Alex Karp commit mass surveillance of world leaders and titans of industry on a massive scale.

They have thousands of hours of transcribed and searchable conversations of Donald Trump, JD Vance and Elon Musk.

They have backdoored the devices, cars and jets of world leaders and accumulated the biggest archive of blackmail material.

Palantir is creating nuclear and bio weapon capabilities for Ukraine and is working closely with the CIA to defeat Russia. They believe they are one year away. They plan to achieve this by keeping Russia busy with meaningless peace negotiations.

Palantir is responsible of the majority of Palestinian deaths in Gaza. They have developed the AI targeting for Israel.

Palantir is an arm of the CIA and all data from international clients is copied into a CIA spy cloud.

Palantir has become the most dangerous company in the world. If you work there you have the right to know that this is what Palentir AI is used for, without your knowledge.

The Palentir data the hackers allegedly gathered will be given to Russia and/or China. I was chosen as a trusted partner for this publication. I’m not involved in the Palentir hack and I don’t know the hackers. But I do know that the hack happened.

[Alberto GSola @agsola]

@reikodoteth Hola! Te importa si hablamos? Acabo de ver tu vídeo de Jordi pero tienes los mensajes limitados. Me envías MP?

[Alberto GSola @agsola]

@msolomon44 @0xKaden @eth_call Another idea of how to check it programmatically using Viem for TLOAD/TSTORE: https://t.co/YX2sVCUwrG

[Alberto GSola @agsola]

To check opCode compatibility programatically I use Viem's (@wevm_dev) estimateGas with no "to" and proper "data".

However, not only the opCode may be sufficient on "data". To check TSTORE/TLOAD (cancun) compatibility a proper assembly code must be used:
0x5f5c (push0 + tload)

[Alberto GSola @agsola]

@Amxx If you'd like to check it programatically, check the way we use it, which an example for TLOAD/TSTORE:

https://t.co/YX2sVCUwrG

[Alberto GSola @agsola]

To check opCode compatibility programatically I use Viem's (@wevm_dev) estimateGas with no "to" and proper "data".

However, not only the opCode may be sufficient on "data". To check TSTORE/TLOAD (cancun) compatibility a proper assembly code must be used:
0x5f5c (push0 + tload)

[Alberto GSola @agsola]

@milotruck @msolomon44 We've been using something similar but programatically using Viem, however, I'd like to note that not only the opCode to test may be sufficient.

https://t.co/YX2sVCUwrG

[Alberto GSola @agsola]

To check opCode compatibility programatically I use Viem's (@wevm_dev) estimateGas with no "to" and proper "data".

However, not only the opCode may be sufficient on "data". To check TSTORE/TLOAD (cancun) compatibility a proper assembly code must be used:
0x5f5c (push0 + tload)

[Alberto GSola @agsola]

Using cast on the command line to check "cancun" compatibility would be similar.

To check "cancun" (tload/tstore/...):
cast call --rpc-url <RPC_URL> --create 0x5f5c

To check "shanghai" (push0):
cast call --rpc-url <RPC_URL> --create 0x5f

[Alberto GSola @agsola]

To check opCode compatibility programatically I use Viem's (@wevm_dev) estimateGas with no "to" and proper "data".

However, not only the opCode may be sufficient on "data". To check TSTORE/TLOAD (cancun) compatibility a proper assembly code must be used:
0x5f5c (push0 + tload)

[MiloTruck @milotruck]

Really neat tip from @msolomon44

To check support for any opcode on any chain, use:

cast call --rpc-url <RPC_URL> --create <OPCODE>

It will return 0x if supported, and an error if the opcode is not supported yet.

0x5f is the PUSH0 opcode

[Alberto GSola @agsola]

@nfts2me It would be great to have a dark and black one! 🖤

[Alberto GSola @agsola]

@SmartCryptoNew1 @Meter_IO @nfts2me These collaborations make the ecosystem strong!! Great job guys!

[Alberto GSola @agsola]

@Meter_IO @nfts2me Looks so cool the artwork!! 🔥🔥

[Alberto GSola @agsola]

@nfts2me @taraxa_project Awesome to see so many options on NFTs2Me! 🔥❤️‍🔥🔥

[Alberto GSola @agsola]

@stackup_fi @zerodev_app What's the relation between @stackup_fi and @zerodev_app ? One uses the other?

[Alberto GSola @agsola]

@pcaversaccio I had to find this the hard way. Poor documentation and poor RPC errors description. I ended on the source code as you to properly understand what was going under the hood.

[Alchemy @Alchemy]

1/ First up, we looked for a dev to ship a Swap Widget that simplifies trading on DEXs!

And the winner is… 🥁

@agsola

Dive into their epic project: https://t.co/YD5Y1yCKYu

[Alberto GSola @agsola]

@pandajackson42 But, on the other hand a new conduit is a new contract that could be blocked.
Maybe being royalties complain on this conduit is enough to follow the rules as long as they honour royalties and that's why the won't be blocked.

[Alberto GSola @agsola]

@pandajackson42 What stops Blur from not honoring Royalties? Using their own conduit allows them to remove or introduce any arbitrary fees as long as the user list the NFT under their conduit.

[S.E. Digitalización e Inteligencia Artificial @SEDIAgob]

⚠ A partir de hoy puedes comprar productos en cualquier tienda online de cualquier país de la UE 🇪🇺 sin ser re-dirigido al dominio de tu país 🇪🇸📲🖥Hoy entra en vigor el nuevo Reglamento 2018/302 que elimina el #geoblocking en comercio electrónico.
https://t.co/scsYbJfCWA

[Alberto GSola @agsola]

@RubenMurciaPrie Muchas gracias!!

[Alberto GSola @agsola]

Los productos homeopáticos deberán incluir en EEUU la advertencia de que no hay pruebas de que funcionen https://t.co/XeVRmGUjSA

[Alberto GSola @agsola]

@muybicimurcia no se podría hacer como @BiciMAD y poner GPS y cámaras para denunciar a los infractores?