Hacker Newsnew | past | comments | ask | show | jobs | submit | globuous's commentslogin

Apparently [1], he managed to put them as collateral on a lending platform. That allowed him to borrow ETH. The way it works is that if you don't pay back the loaned ETH, the lenders can take the collateral. Except that here the collateral is itself frozen. So apparently, the ETH as now safe in the hacker's wallet and the lenders just lost a bunch of money.

I wonder why not swap them? And had he, would it have bricked the swap pool?

[1] https://x.com/czesmaill/status/2115988477905080716


Maybe swap pools and/or law enforcement working together with stablecoin issuers are more vigilant about pools than they are about various DeFi lending pools, given that one usually represents a change of ownership while the other does not?


Thanks for sharing, very smart move from the badboys.


That's smart


[flagged]


statistics, of course


Actually, that doesn't sound like a bad meeting place and time! I just asked ChatGPT if it could figure out the best place to meet for two people randomly placed in Manhattan with the constraint that only the N line (I'm not from NYC, but it looks like it stops at the Empire State Building. This constraint models the lack of file system, internet etc). I was hoping it would answer the Empire State Building, but it answered Time Square at noon.

Turns out there's something called the Schelling coordination problem [1] I didn't know about that essentially asks the exact same question (lacking my metro line constraint). And the N line apparently also goes through Time Square.

So I guess empire State Building at 2pm is probably not such a random answer given the proper set of constraints.

[1] https://en.wikipedia.org/wiki/Focal_point_(game_theory)


What I missed most were let bindings (https://ocaml.org/manual/5.3/bindingops.html)

ReasonML has custom operators that allows for manipulating monads somewhat sanely (>>= operators and whatnot). rescript (reasonml’s “fork”) did not last time I checked. But it does have an async/await syntax which helps a lot with async code. reasonml did not last time I checked, so you had to use raw promises.

I believe Melange (which the article briefly talks about) supports let bindings with the reason syntax.

And this kinda changes everything if you React. Because you can now have sane JSX with let bindings. Which you could not until melange. Indeed, you can PPX your way out of it in ocaml syntax, but I’m not sure the syntax highlight works well in code editors. It did not on mine anyway last time I checked.

So for frontend coding, Melange’s reason ml is great as you have both, and let bindings can approximate quite well async syntax on top of writing readable monadic code.

For backend code, as a pythonista, I hate curlies. and I do like parenthesis-less function calls and definitions a lot. But I still have a lot of trouble, as a beginner ocamler, with non-variable function argument as I need to do “weird” parenthesis stuff.

Hope this “helps”!


Looks very interesting, thanks for sharing! The pricing section is very informative btw, congrats to the author for sharing it


Fabien is a Hacker News darling, I'd highly recommend both the DOOM black book and Wolfenstein black book, I have them and love every page. Give him your support!

Masters of Doom is also required reading for any hacker.


No way! I didn't know that was part of the standard! Very useful "trick" indeed, unless of course, the USB port is placed vertically...


AMD support would be amazing <3

I get the boot concern, and the maintenance concern (!!!), but as you say, these models are already quite huge anyway :)


Interestingly, the last slide mentions:

``` Today: we are able to certify realistic bytecode compilers and abstract machines.

Tomorrow: certification of optimizing native-code compilers? ```

Xavier Leroy actually got the ACM Software System Award in 2021 for CompCert, an optimizing native-code compiler! It's first version seems to have been released in 2005, just 3 years after this presentation was written. Though CompCert is a C compiler, which isn't really a functional language.

- https://en.wikipedia.org/wiki/ACM_Software_System_Award - https://en.wikipedia.org/wiki/CompCert


CakeML is a formally verified implementation of a subset of Standard ML which generates native code. Not sure about what it optimises though.


Is that not what you’d do? That sounds like an unusually useful review tbh.


The point of their comment, I think, is that a restaurant's grand opening is not always indicative of future experiences. The cooks/chefs, and front of house staff are all fairly new to the environment, menus might change as they find out that certain menu items are throwing off their timing or they don't have a great way to procure certain ingredients, and it will take time to all settle into a routine that works.

I think they were saying that is akin to the state of kubernetes, where everything is too new to really judge it today. Let me make clear my bias before I get to my opinion: I'm a big fan of what kubernetes has accomplished with managing the deployment of applications. But I think comparing current day kubernetes to a restaurant's grand opening is naïve. Kubernetes is amazing at what it does, and for how highly flexible it is. But it is highly flexible because of how advanced it has become, which in turn requires more knowledgeable administrators. You can take off with Docker Swarm because... it's very simple. It doesn't aim to be flexible, it just aims to be the docker-compose of distributed systems. Which is fine if you don't need the flexibility that kubernetes offers anyway.

And while I do appreciate kubernetes for all of its strengths, going back towards the point of this OP, I do believe it's a bit of a security nightmare. For example, the kubernetes operator pattern often just requires this application to run in your cluster with a ClusterRole granting it read and potentially write levels of access to ConfigMaps and Secrets around your cluster. Often without much in the ways of a method of telling the kubernetes API server what namespaces it is allowed to view those objects in. Worth mentioning though that secrets management is something that Docker Swarm also handles fairly poorly, and honestly isn't much of a security regression from the normal "deploy a VM that has all your decrypted secrets sitting on the system" anyway.


If you liked war and peace, you should check out grossman’s life and fate, it’s WWII’s version, fantastic. And blacklisted by the soviet government because critical of it.


I don’t understand how people don’t like War and Peace, aside from its size and the weird discursive turns he takes in the appendices. I’ve read it three times and every time it’s a page-turner. So good. But Tolstoy was an infinitely better literary artist than Dostoevsky could ever hope to be. (Tolstoy’s novella, Hadji Murad, is 100 pages of literary crystal, cleverly concealing itself from you as you look on through the transparent glass of words into the world Tolstoy points out to you, until you realize the whole thing is just Tolstoy and his astonishing talent).

But Dostoevsky had the real big heart, and I love him for it.


I don’t understand how people don’t like War and Peace

Easy, try mandatory-reading it in the summer when you’re around 15. I told my teacher that I will not do it and I don’t care what comes with it.


I don’t think you can objectively say Tolstoy was a worse literary artist than Dostoyevsky.

For me it’s absolutely the other way around. Dostoyevsky saw into men’s souls in a way no other writer perhaps barring Shakespeare could. Tolstoy for me is more mechanically or technically good, but Dostoyevsky was a true artist and saw through life and humanity at another level.


That's what they said

> But Tolstoy was an infinitely better literary artist than Dostoevsky could ever hope to be.


Right. Dostoevsky was perfect on the human element. Tolstoy on the writing.


War and Peace starts pretty slow. It took me a long time to get through the first 100 pages or so. Once I was into it, I couldn't put it down, but it took a while to get there.


Definitely looking forward to reading this soon. Thanks for recommending it, friend!


That's true, and I was impressed first time someone showed me that. But the cost of this luxury might not be worth it. Indeed, you mostly (only ?) communicate through an API. And if it's properly documented, which is now essentially automatic, you can easily generate your types from the frontend. To me, the cost of bringing JS to the backend dominates this luxury to the point where it's just not worth it. I'll just generate my types from the frontend and be done with it.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: