Birbla

Join the discussion

Write your take first — we'll ask for email only when you're ready to publish.

Sign in
  • Hacker News
  • Nice. I will make sure to turn my WiFi box off at night and pee in the shower to compensate the environmental impact of this.
    by speedgoose
  • kinda bearish for the data center rollouts if the spare compute can be used to solve math puzzles instead of training LLMs
    by someguydave
  • If anyone else has spare GPU hours they don't know what to do with, may I recommend partial hash collisions: https://github.com/DavidBuchanan314/birthday_party

    (The "record" set by me only took about 1 GPU day - easy to beat!)

    by Retr0id
  • If you've already paid for and reserved a whole cluster of GPUs, any idle capacity is capacity you've already paid for. Using it is effectively free. So might as well use it to solve fun math puzzles.

    Though, it would make more financial sense to mine crypto.

    by tristanj
  • Quite bearish on Anthropic if they had nothing better to do with 2048 GPUs for 10 days than finding an RSA number with already existing algorithms.
    by redox99
  • Interesting. Instagram still publishes a 768-bit RSA DKIM key, so I guess factoring it is now just a weekend GPU project?

    https://dns.google/resolve?name=pm._domainkey.instagram.com&...

    by vavkamil
  • More details: https://x.com/sweis/status/2101484464807596264

        I had Claude port CADO-NFS to run on GPUs. Then it orchestrated a fleet to run on scavenged idle capacity. It ran with a max of 2048 GPUs for about of 30 GPU-years over 10 days.
    I asked Claude if it had a message for a public: “The credit belongs first to the people who built the number field sieve and CADO-NFS over several decades, and to the teams who set the earlier records. This run used their algorithm and much of their code.”
    Also to clarify:
    - No new algorithmic factoring improvements. 
    - It’s still exponential.
    - No new threats to deployed keys.
    by madars

Explore Birbla archives