vanitygen-plusplus
nixpkgs
vanitygen-plusplus | nixpkgs | |
---|---|---|
8 | 975 | |
232 | 15,753 | |
- | 2.8% | |
2.4 | 10.0 | |
10 months ago | 3 days ago | |
C | Nix | |
GNU Affero General Public License v3.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
vanitygen-plusplus
-
Vanity address giveaway
I am using vanitygen++: https://github.com/10gic/vanitygen-plusplus
- VanityGen++ MotaCoin
-
LTC Address Modification
There is a tool to make 'vanity addresses' here: https://github.com/10gic/vanitygen-plusplus you can specify a prefix and it will make billions of keys to find the key to an address with your prefix. You could then import this key to core, or whatever wallet you prefer.
-
how feasible is brute forcing last 14 chars of a key
One could easily hack the bitcrack code for beckh32 but checkout vanitygen use -Z to specify the known part of the key https://github.com/10gic/vanitygen-plusplus I’m fairly sure it can do bech32 out of the box
-
NixOS 22.11 “Raccoon” Released
I run NixOS, but I'm relatively new to Nix. A couple weeks ago I was trying to get an old vanity key generator to build because it wasn't on nixpkgs (vanitygen++) and on a lark I decided to write my own derivation using some examples of similar C++ packages I found and figuring out what nix packages it needed to build. So I did, and the maintainer accepted the PR: https://github.com/10gic/vanitygen-plusplus/commit/7bcee06f3... Note that I am not a C++ developer and only know the basics about how to get C/C++ things to build.
So what does this get us? In theory, this is now trivially-buildable on any distro that has nix installed, or on nixos. I haven't converted it to a flake yet (still learning that) but if I (or someone else) did, it would be deterministically reproducible anywhere on nix.
I agree that there's a learning curve on figuring out the "recipe" for a thing, but once someone does that work, it's basically done forever. Which is a promise that no other system can even approach.
And once you figure out a certain amount of it, this moment will come where you realize you want every system you deal with to be Nixified. Like the guy elsewhere in this thread who rebuilt his own router using NixOS and loves it.
Getting new developers up to speed in your shop's dev environment? Completely trivial to do with Nix. Getting a machine back up after a failure? Reinstall NixOS and reapply the config you were using (which is in source control). Upgraded Gnome and some things you need broke? Or updated your GPU driver and now your screen just shows black? Simple... Roll back in the bootloader to a previously-working config, then undo your changes to the config definition.
NixOS (and very honorable mention to Guix) are in fact the only ways to run Linux while keeping your sanity intact!
-
TurboWarp Desktop
It probably wouldn't be that hard to package.
For example, I committed this to a fork of a C++ package a few days ago just to be able to build it in Nix; it's literally just 1 step away to go from building it here to putting this in nixpkgs but I don't want to be responsible for it (I've also never taken that step yet) and it also doesn't (yet) use Flakes: https://github.com/10gic/vanitygen-plusplus/blob/master/defa...
In theory, though, you'd just have to find a similar Node example out there and crib off its nix config/build file. And if you converted it to a flake, you'd have a guaranteed-reproducible build (but then you'd also be responsible for updating it). Perhaps that's why nixpkgs has one of the highest package counts in the Linux space of package managers.
- Bitcoin for Christmas
-
[SS] I can generate custom Doge addresses
i think vanitygen++ has a split-key generation feature
nixpkgs
-
Nix: The Breaking Point
I don't think so. The article is probably intended for the Nix community, so the author doesn't need to convince HN that something is going on. If as an outsider you are interested then you need to look into it yourself, the community has no obligation to make their internal conflicts legible to the outside world.
As an outsider myself, it certainly looks like something is going on as more than 20 Nixpkg maintainers left in a week: https://github.com/NixOS/nixpkgs/issues?q=label%3A%228.has%3...
- Maintainers Leaving
-
Air Force picks Anduril, General Atomics to develop unmanned fighter jets
https://github.com/NixOS/nixpkgs/commits?author=neon-sunset
-
Eelco Dolstra's leadership is corrosive to the Nix project
I see two signers in the top 6 displayed on https://github.com/NixOS/nixpkgs/graphs/contributors
-
3rd Edition of Programming: Principles and Practice Using C++ by Stroustrup
For a single file script, nix can make the package management quite easy: https://github.com/NixOS/nixpkgs/blob/master/doc/languages-f...
For example,
```
- NixOS/nixpkgs: There isn't a clear canonical way to refer to a specific package
-
NixOS Is Not Reproducible
Yes, Nix doesn't actually ensure that the builds are deterministic. In fact it works just fine if they aren't. There are packages in nixpkgs that aren't reproducible: https://github.com/NixOS/nixpkgs/issues?q=is%3Aopen+is%3Aiss...
-
The xz attack shell script
I'm not familiar with Bazel, but Nix in it's current form wouldn't have solved this attack. First of all, the standard mkDerivation function calls the same configure; make; make install process that made this attack possible. Nixpkgs regularly pulls in external resources (fetchUrl and friends) that are equally vulnerable to a poisoned release tarball. Checkout the comment on the current xz entry in nixpkgs https://github.com/NixOS/nixpkgs/blob/master/pkgs/tools/comp...
-
Debian Git Monorepo
NixOS uses a monorepo and I think everyone's love it.
I love being able to easily grep through all the packages source code and there's regularly PRs that harmonizes conventions across many packages.
Nixpkgs doesn't include the packaged software source code, so it's a lot more practical than what Debian is doing.
https://github.com/NixOS/nixpkgs
-
From xz to ibus: more questionable tarballs
In this specific case, nix uses fetchFromGitHub to download the source archive, which are generated by GitHub for the specified revision[1]. Arch seems to just download the tarball from the releases page[2].
[1]: https://github.com/NixOS/nixpkgs/blob/3c2fdd0a4e6396fc310a6e...
[2]: https://gitlab.archlinux.org/archlinux/packaging/packages/ib...
What are some alternatives?
vanitygen
asdf - Extendable version manager with support for Ruby, Node.js, Elixir, Erlang & more
VanitySearch - Bitcoin Address Prefix Finder
Home Manager using Nix - Manage a user environment using Nix [maintainer=@rycee]
BitCrack - A tool for cracking Bitcoin private keys
git-lfs - Git extension for versioning large files
desktop - A better offline editor for Scratch 3.
easyeffects - Limiter, compressor, convolver, equalizer and auto volume and many other plugins for PipeWire applications
redditraffler - The raffle system for Reddit submissions.
spack - A flexible package manager that supports multiple versions, configurations, platforms, and compilers.
nix-config - My personal NixOS config
waydroid - Waydroid uses a container-based approach to boot a full Android system on a regular GNU/Linux system like Ubuntu.