ustas.eth pfp

ustas.eth

@ustas

83 Following
349 Followers


ustas.eth pfp
ustas.eth
@ustas
Big brother finally came back
0 reply
0 recast
0 reaction

ustas.eth pfp
ustas.eth
@ustas
After an incredible ride, I’m no longer with Hexens. I’ve loved every second of this journey - the team is absolutely phenomenal, and I’m so proud of what we pulled off together: - Long days keeping black hats out - Countless hours mastering new tech - Running the biggest CTF in the web3 history - That epic trip to Thailand Huge thanks to my mentors, friends, and colleagues. You’ll always hold a special spot in my heart. Deepest gratitude for everything. My path is still hazy, but the plans are ambitious - stay tuned. gg wp
0 reply
0 recast
4 reactions

ustas.eth pfp
ustas.eth
@ustas
Near the assembly, you can find helpful comments that indicate what the stack memory currently holds. Observe the changes after each opcode. For example, the following code will push a constant onto the stack, then push and load the storage slot for the excess value. The constant is first shifted deeper into the stack by the slot, then `SLOAD` "consumes" the slot and replaces it with the value it contains. See https://www.evm.codes/ to get a reference with an example on each opcode. Good luck 🍀
0 reply
0 recast
0 reaction

ustas.eth pfp
ustas.eth
@ustas
As an example, you can see the Withdrawal code here: https://github.com/lightclient/sys-asm/blob/main/src/withdrawals/main.eas It implements EIP-7002, which gives validators the ability to request a withdrawal on the consensus layer directly from the execution layer. https://eips.ethereum.org/EIPS/eip-7002 The contract is written in geas, an assembler language for EVM with just a couple of features to make development easier, such as labels for variables or jump destinations. https://github.com/fjl/geas In the EIP, you can see that pseudocode is provided for a more high-level understanding. Compare it to the opcodes and you'll quickly grasp the assembly code.
1 reply
0 recast
1 reaction

ustas.eth pfp
ustas.eth
@ustas
The new @ethereum system smart contracts to be introduced in Pectra are insanely good for understanding how the low-level EVM works! Loaded with comments and pseudocode in the EIPs, you can see how the stack and opcodes function very clearly. 🧵👇
1 reply
0 recast
1 reaction

ustas.eth pfp
ustas.eth
@ustas
The most useful LLM out there. The answers are actually useful, not downplaying, and up-to-date. So sad it's proprietary (not for long, as always).
0 reply
0 recast
0 reaction

ustas.eth pfp
ustas.eth
@ustas
The world is burning, but my house will be filled with light tonight 🫴✨ This was my first Solana review. I'm glad I finally had the opportunity to make some sense out of the SVM account model. This is also my first 2nd place and the biggest reward after the zkSync 1.1M contest. Thanks pals!
0 reply
0 recast
2 reactions

ustas.eth pfp
ustas.eth
@ustas
Yesterday, I published my first dashboard on @dune.eth ✨ It provides basic real-time analysis for each deal on @legiondotcc using the data from onchain events: https://dune.com/os/legion-stats You can see the total numbers of investors, collected amounts, and the latest investments all in one place. Send me a DM if you have any features in mind, I'll try to implement them. If enough people are interested, I'll open source the queries later. And ⭐️ the dashboard if you find it helpful! Thanks!
0 reply
0 recast
3 reactions

ustas.eth pfp
ustas.eth
@ustas
Yesss, finally!
1 reply
0 recast
7 reactions

ustas.eth pfp
ustas.eth
@ustas
This is brilliant :D
0 reply
0 recast
1 reaction

ustas.eth pfp
ustas.eth
@ustas
How do you see the impact of lobbyism on DAOs? Check DMs, please!
1 reply
0 recast
0 reaction

ustas.eth pfp
ustas.eth
@ustas
Happy new beginnings
0 reply
0 recast
1 reaction

ustas.eth pfp
ustas.eth
@ustas
By the way, check this out! My guide on how to run Copilot in VSCodium has become the most popular discussion in the repo over the years. Recently I had to play with it a bit and update the instructions, because there was some new release that broke everything 😛 See how I did it here: https://github.com/VSCodium/vscodium/discussions/1487#discussioncomment-11866388
0 reply
0 recast
0 reaction

ustas.eth pfp
ustas.eth
@ustas
My ledger tool, 4 deps! Basically a wrapper for a couple of libraries. Could be even smaller if implemented with a native CLI and txs parsers, but there'll be maintanence issues (I'm lazy).
0 reply
0 recast
1 reaction

ustas.eth pfp
ustas.eth
@ustas
It always was
0 reply
0 recast
0 reaction

ustas.eth pfp
ustas.eth
@ustas
I didn't check what is it doing because I'm pretty sure it a standard credentials/wallets/cookies stealer or RAT
0 reply
0 recast
0 reaction

ustas.eth pfp
ustas.eth
@ustas
The repository
1 reply
0 recast
0 reaction

ustas.eth pfp
ustas.eth
@ustas
And the malware payload, tabbed in one of the files to get on my nerves
1 reply
0 recast
0 reaction

ustas.eth pfp
ustas.eth
@ustas
Another one bites the dust... A typical developer job scam, this time with a cherry on top.
1 reply
1 recast
1 reaction

ustas.eth pfp
ustas.eth
@ustas
Is the algorithm public? This kind of protection is usually easy to bypass by emulating some basic browser env, I'd like to look at it if possible
1 reply
0 recast
1 reaction