Hacker GitHub

← All repos

tromp/cuckoo

View on GitHub ↗ ★ 865 C++

a memory-bound graph-theoretic proof-of-work system

43 mentions on Hacker News by 5 people: 4 stories, 39 comments · first 2014-01-11 · latest 2025-05-07

Mentions per year 43 mentions · busiest year 2014 (9)
20082026
  1. …is. Unfortunately it cannot mine with the PoW I created [1], or I might be tempted to buy one. [1] https://github.com/tromp/cuckoo
  2. …remaining (simple) cycles. [1] https://www.semanticscholar.org/paper/Cuckoo-Cycle%3A-A-Memo... [2] https://github.com/tromp/cuckoo [3] https://github.com/tromp/cuckoo/blob/master/src/cuckoo/cycle... [4]…
  3. …to password hashing, since a given problem instance can have 0 or 1 or many solutions. [1] https://github.com/tromp/cuckoo [2] https://en.wikipedia.org/wiki/Equihash
  4. …for early miners/adopters. [1] https://www.researchgate.net/publication/31869581_Preserving... [2] https://github.com/tromp/cuckoo
    comment by tromp · 2023-05-01 · in Crypto: My Part in Its Downfall
  5. …number of Chess positions [5] had little impact beyond satisfying my intellectual curiosity. [1] https://github.com/tromp/cuckoo [2] https://tromp.github.io/cl/cl.html [3] https://tromp.github.io/go.html [4]…
  6. …is decentralized currency without the unnecessary complexity, bloat, grifting and speculation. [1] https://github.com/tromp/cuckoo
  7. …force search as well? Because that one is certainly not solved by trying all possible cycles. [1] https://github.com/tromp/cuckoo
  8. …sequential access to 20x more memory still ends up 4x faster (lean miner vs mean miner in [1]). [1] https://github.com/tromp/cuckoo
    comment by tromp · 2022-09-07 · in Weird Al had 100 gigs of RAM
  9. …projects are cash grabs, but that's no excuse for insulting all developers without exception. [1] https://github.com/tromp/cuckoo
  10. …puzzle, that takes lots of SRAM to solve efficiently [1], while remaining instantly verifiable. [1] https://github.com/tromp/cuckoo
  11. …and the solutions are cycles of length L, which have a chance of about 1/L of occurring. [1] https://github.com/tromp/cuckoo
  12. …while still being faster. An example of such a problem is the Cuckoo Cycle Proof-of-Work [1]. [1] https://github.com/tromp/cuckoo
    comment by tromp · 2021-12-05 · in Graviton2 and Graviton3
  13. …Would love to see how well the GPU runs a memory-bound Proof-of-Work like Cuckatoo Cycle [1]. [1] https://github.com/tromp/cuckoo
  14. …These can easily be made to use hundreds of MB in solving, while verification is memory less. [1] https://github.com/tromp/cuckoo [2] https://en.wikipedia.org/wiki/Equihash
  15. …lots of memory, while verification takes none. For example, Cuckoo Cycle and its variants [1]. [1] https://github.com/tromp/cuckoo
    comment by tromp · 2021-08-24 · in Samsung Reveals DDR5-7200 512GB RAM
  16. …of memory, and ASICs for such PoW are dominated by SRAM, which can in principle be repurposed. [1] https://github.com/tromp/cuckoo
  17. …0.5GB SRAM and 0.5GB off-chip DRAM) to find cycles in bipartite random graphs with 2^32 edges. [1] https://github.com/tromp/cuckoo
    comment by tromp · 2021-05-06 · in IBM creates 2nm chip
  18. …is to find a 42-cycle in a random bipartite graph with 2^32 edges. each defined by 2 siphashes. https://github.com/tromp/cuckoo
  19. …schemes (e.g. finding cycles in graphs [1]) are not vulnerable to quantum speedup. [1] https://github.com/tromp/cuckoo
  20. …an alternative solver using 32 times more memory and mostly sequential access is much faster. [1] https://github.com/tromp/cuckoo
    comment by tromp · 2020-07-10 · in Ryzen Threadripper Pro 3995WX Spotted
  21. …PBKDF, where you hash the edge bitmap after a small fixed number of edge trimming rounds. [1] https://github.com/tromp/cuckoo
  22. As the author of the Cuckoo Cycle PoW https://github.com/tromp/cuckoo I don't recall any such dependence. I don't see how the operations described in the paper would benefit a Cuckoo Cycle solver, which in essense looks like…
  23. …universe. It's way easier to brute force the 256-bit private keys of all bitcoin balances... [1] https://github.com/tromp/cuckoo
    comment by tromp · 2019-11-14 · in Optical Proof of Work
  24. Finding (cycles of) collisions in siphash is used as a memory-hard Proof-of-Work: https://github.com/tromp/cuckoo
  25. …is about 4x faster. Blog entry [2] explains how Cuckoo Cycle reduces to a counting problem. [1] https://github.com/tromp/cuckoo [2] http://cryptorials.io/beyond-hashcash-proof-work-theres-mini...
  26. …for more interleaving of operations. On recent iCore i7, the 8-way performs best. The Makefile at https://github.com/tromp/cuckoo/blob/master/src/Makefile has targets cuckoo28stx, cuckoo28stx4, cuckoo28stx8 and cuckoo28stx16 for these…
  27. …invalidating some of its claims. My own, memory latency bound, proof-of-work called Cuckoo Cycle https://github.com/tromp/cuckoo offers $5000 in bounties for invalidating its claims of near-optimal implementations and trade-off resistence.
    comment by tromp · 2016-10-18 · in Scrypt is Maximally Memory-Hard
  28. …which do not suffer from this conflict, can be found at https://github.com/khovratovich/equihash https://github.com/tromp/cuckoo
  29. …by memory latency instead of computation. That's what my Cuckoo Cycle PoW scheme aims for... https://github.com/tromp/cuckoo On the other hand, some people argue that reducing waste is counterproductive as it also lowers the cost of a…
    comment by tromp · 2015-07-27 · in Final Steps
  30. I'm hoping Cuckoo Cycle can change that ( https://github.com/tromp/cuckoo )
  31. but pretty awesome at mining the cpu-friendly Cuckoo Cycle... https://github.com/tromp/cuckoo
  32. …scheme, which David has helped refine, and which has yet to be deployed by any coin. See https://github.com/tromp/cuckoo for details and a whitepaper.
  33. …optimized GPU implementation." That doesn't bode well for my $1000 GPU Speed Parity Bounty at https://github.com/tromp/cuckoo based on my belief that the Cuckoo Cycle graph-theoretic proof-of-work algorithm is more suited to CPUs.
  34. …memory. Then your performance is limited by memory latency. This is what I designed Cuckoo Cycle ( https://github.com/tromp/cuckoo ) for.
  35. Yes, why not a PoW that's all of ASIC resistant GPU resistant botnet resistant My Cuckoo Cycle PoW ( https://github.com/tromp/cuckoo ) configured to require for instance 7GB of memory, is all of the above. And is very power friendly, since…
  36. …a relatively low-power one that mostly (95%) substitutes memory latency for computation, as in my https://github.com/tromp/cuckoo
    comment by tromp · 2014-03-05 · in Arscoin, our own custom cryptocurrency
  37. From the README of my "Cuckoo Cycle" Proof-of-Work at https://github.com/tromp/cuckoo : Mining is generally considered to be inherently power hungry but it need not be. It’s a consequence of making the proof of work computationally…
  38. Cuckoo Cycle at https://github.com/tromp/cuckoo seems like a better proof-of-work system and comes with a full implementation. It has the following features: 1) proofs take the form of a length 42 cycle in the Cuckoo graph, so that…
  39. Dagger appears to be inferior to the Cuckoo Cycle proof of work system I recently developed; see https://github.com/tromp/cuckoo Cuckoo Cycle is a new proof of work system with the following features 1) proofs take the form of a length 42…