Juan Blanco

@juanblanco

193 Following

473 Followers

Juan Blanco pfp

The extension that was impersonating vscode solidity (and many others following the same pattern) have been removed. We have seen that a fake extension or virus can spam many downloads (if that was their technique) So how to identify is the right extension? The best way is to look at the published date. The vscode solidity extension was published on the 2015-11-19 at 7:35 am, the published date cannot be faked. The extension was one of the first ones in the marketplace, after the official announcement of the extension sdk the day before. So in case of doubt, when choosing any extension.. check the date.

2 replies

3 recasts

27 reactions

Juan Blanco pfp

I hope you enjoyed it!!!

0 reply

0 recast

3 reactions

polynya pfp

For my personal use, crypto is in a great place. Fees, speeds, wallet UX, applications are perfectly fine for my usecases, and they'll keep getting better. However, I'd like to see some things significantly improved, in order of importance: - CRITICAL: Configurable withdrawal rate limiting in Safe & smart wallets and indeed, in all smart contracts, should be a standard. Without this, I significantly limit my usage of crypto - Custodial standards for smart wallets - Stage 2+ decentralisation for L2s, complete overhaul for Tron (normies receive USDT on Tron) - EUR stables w/ liquidity - Better frontends & standards - More competition & options for minimal hardware wallets - Range order management for Uniswap V4 - Significantly less volatile, reliable, long-term sustainable and high liquidity SoVs (BTC and ETH are far too erratic) - Integration into widely adopted payment networks, both global and domestic - Some inaccessible assets tokenised as RWAs - Farcaster with bustling non-crypto content/discussions

68 replies

353 recasts

1702 reactions

Juan Blanco pfp

Nethereum AOT (.net native support) is happening.. https://github.com/Nethereum/Nethereum/blob/5eccd836aa7897410b56a4604729c8d6013a3244/consoletests/Nethereum.AOTSigningTest/Program.cs This means support for both newtonsoft and system.text.json, new rpc clients etc. What you get a small native self contained executable, per platform.

0 reply

1 recast

1 reaction

Juan Blanco pfp

I have just discovered DeepWiki, index, query generate documentation of any repository. See Nethereum Mud generated documetantion (although just focusing on data part) https://deepwiki.com/Nethereum/Nethereum/4.3-mud-framework-integration

1 reply

1 recast

2 reactions

Justin Drake pfp

If you run Geth, shave 400 GB of storage in two easy steps :) 1) prune pre-merge history with "geth prune-history --datadir <your dir>" 2) restart geth with "--history.chain postmerge"

22 replies

151 recasts

706 reactions

Juan Blanco pfp

I truly understand :(.

0 reply

0 recast

1 reaction

Juan Blanco pfp

Keep hearing how many people miss the "week in eth newsletter", it was THE way to keep everyone in sync and knowledge. @abcoathup @evanvanness Paraphrasing: "Oh I didn't know about X or Y, I miss the Week in Eth".

2 replies

3 recasts

1 reaction

Juan Blanco pfp

This is a funny bot :)

0 reply

1 recast

3 reactions

Juan Blanco pfp

I was 0 km away from today's mystery location 📍. Can you beat me?

2 replies

3 recasts

2 reactions

Juan Blanco pfp

If the problem is the 32 bytes, an improvement will be to encode / decode packed. But for this it will be required to understand the structure of the message before hand, similar to what MUD does with the table schema. This means each contract will require an understanding of the schema, which it could be easily created for verified contracts for backwards compatibility if needed. But it might also allow us to start thinking of data storage patterns / standards like the one used in MUD for general data (not just games)

0 reply

0 recast

0 reaction

Officer’s Notes pfp

Officer’s Notes

Save this post if you've been scammed or hacked!!! First things first, you should contact: t.me/seal_911_bot, or t.me/rata0x • Next, for recovering the rest (untouched assets) please use: hackedwalletrecovery.com made by @buidlguidl @austingriffith ; • Or this tool: https://app.buidlguidl.com/build/yIj6q9TZnzAUMR6B4eFX • For recovering unclaimed tokens from airdrops: https://serveth.notion.site/How-to-securely-transfer-unclaimed-tokens-from-a-compromised-wallet-7c5f5e3762474851b92c159f797e406e ; • Order an investigation (optionally): t.me/rata0x • You should also report your case to chainabuse.com ! Please RT! Stay safe!

2 replies

10 recasts

40 reactions

Juan Blanco pfp

At the integration layer it could be abstracted by matching the ABI representation (JSON or custom) to SSZ, so call data could be "easy" for an end user, but it would impossible to have a big bang approach, as it will break many applications. The only solution is to support both in parallel, the user now will need to be aware of the smart contract type (ie ERC20 ssz) they are targeting and what encoding to use. This adds a similar issue with event decoding that might require a flag to identify the format for decoding. 712, SIWE, Permit2, and just internal smart contract ABI encoding/decoding with integrations will remain the same as the ABI is used as a standard in these scenarios (packed or unpacked) as utility internally and for integration. So it will be very hard to be phased out.

1 reply

0 recast

0 reaction

Juan Blanco pfp

Moving ABI to SSZ will have a huge impact in general, not just at the calldata level, but 712, events, full frameworks (think mud) will need to be rewritten. All current applications will need to change, backend / frontend, and tested, and obviously rewritten in many areas. This might mean, that applications that target different chains due to compatibility might not upgrade and keep old formats. RLP might have a smaller impact if there are new transaction types that overtake others.

1 reply

0 recast

0 reaction

Juan Blanco pfp

My big ask, we need a consolidation like "bouncy castle" for all new crypto primitives targeting all common languages. Fully audited and validated.

0 reply

0 recast

0 reaction

polynya pfp

Uniswap v4 feels like crypto's first complete product. Uniswap v3 was already nearly there, which is one reason why while previous versions took ~1 year, v4 took 4 years. I can see additional functionality (e.g. unified liquidity) and responding to infra changes (e.g. quantum-resistant zkVMs) that will justify a v5, but the core purpose of this application now feels complete for the foreseeable future. What's remaining is now on the governance & social end. Aave v4 is the next candidate for a complete product. Interestingly, the applications are hitting final form years ahead of the infra they're built on, and in cases like Aave v4, being intertwined with infra itself. (Side-note: of course, simple "products" like memecoins or USDT are "complete")

60 replies

189 recasts

925 reactions

Andrew B Coathup pfp

Andrew B Coathup

All Core Devs - Execution (ACDE) #210 * EOF scope (DX impact, possible RISC-V future) * Gas limit defaults * Summary by @tim * Recordings on YouTube/X & @ethcatherders podcast https://ethmag.org/t/acde-210/23502/2

1 reply

3 recasts

5 reactions

Juan Blanco pfp

https://youtu.be/ymGK_p5ru78?si=45FjmDuVcouMXlBO

3 replies

2 recasts

8 reactions

Juan Blanco pfp

Love this set https://www.youtube.com/watch?v=4Q0_Rvpak5U&t=12s

3 replies

2 recasts

4 reactions

Juan Blanco pfp

Lol, it feels like chatgpt likes to laugh about my pains.. (same issue as the past years, the more crypto the harder.. we need a common bouncy for all these new primitives), enable verkles verification and natively (no bindings) cross platform, will enable users to validate and verify the state locally, dapps.

0 reply

0 recast

4 reactions