@brolag Yo probe gemma y qwen en un servidor local con rtx4070ti. Con q4 y haciendo ofloaf al ram, funciona pero bastante lento, creo que es necesario la 4090 para evitar el ofload a ram. My 2cents
Este quipo necesita vuestra ayuda para participar en la final mundial de Robotica.
Ya están un 5% mas cerca de su meta.
Ayudémoslos!! No dejes que el talento se quede en tierra. Entre todos lograremos que cumplan sus sueños!!
https://t.co/0aKwTgW9D6
Claude Security is now in public beta for Claude Enterprise customers.
Claude scans your codebase for vulnerabilities, validates each finding to cut false positives, and suggests patches you can review and approve.
You're the missing piece for this team.
If you love technology, innovation, STEM education,Lego, and robots, help these young engineers qualify for the world finals in Sydney.
Let's support them!
https://t.co/GJ19RpNqn8
https://t.co/PU60GpKtnG
#lego#tesla#Educación#tech
@im1337_eth@griffgreen@arbitrum They can literally pick and chose transactions to include in the block and reject the ones they do not want, if the majority of miners decide not to include certain transaction then it is not going to happen
@agustin_kassis@mattunchi Entonces hay que dejar que el hack siga? Defi no esta listo todavia para ser 100% descentralizado lamentablemente. Ojala pronto llegue ese dia
@Fhermontiel_ Asi es, sin embargo, Si solo depositaste tu eth estas bien, el miedo hizo que por falta de liquidez quedes atrapado momentáneamente pero no estas en riesgo
Unpopular opinion
Layer Zero, Aave y Kelp la cagaron si..
Pero ademas de que defi y eth es riesgoso, lo stakeaste para generar rendimiento, luego lo pusiste en restaking (mas riesgo) luego desbloqueaste liquides con liquid restaking (mas riesgo) luego lo usaste como colateral para endeudarte (mas riesgo)
Nadie cree que pase nada hasta que pasa.
El manejo del Riesgo es clave!
I understand your point, but thats not the answer to the problem.
the answer to "security councils can be social engineered" isn't "have no security council." It's "design them with better process."
Drift's failure was solvable. The lesson from that hack is how to build better councils, not that councils are broken.
Drift council got social engineered because of a specific combination. zero timelock on governance migrations +durable nonces
Drift multisig Signers didn’t know what they signed and they had no window to catch it.
Arbitrum Security Council has timelocks for most actions, publicly doxxed members and the kind of institutional scrutiny that comes with running a top L2.
Compromising 9 of those people simultaneously, with all eyes on them post-Drift, is a very different attack than what Lazarus supposedly pulled off in April.
Is it impossible? No. Is the risk zero? No