daedalus VS nixpkgs

You can download daedalus from https://daedaluswallet.io/

First, you'll need to download and install the Daedalus wallet on your computer from https://daedaluswallet.io/

I don't think Daedalus has the option anymore (there's an open request to reimplement it) so you'll need to use a different wallet that supports it.

Use https://daedaluswallet.io/ for ADA. Add your stake to a pool that's not in the high percentage share for a fairer reward

Apple M1 has been working for some time, but those binaries are not yet signed apparently. Check the hash after download: https://github.com/input-output-hk/daedalus/issues/2677

Daedalus (Desktop) - Resource heavy, no DaPP capabilities, safer than web wallets

Daedalus is a full node wallet, which means that it takes a while to sync up to the blockchain. It will probably ask you to run an upgrade, which is fine. Be aware that there are scammers that try to get you to download fake wallets, so make sure the source is from: https://daedaluswallet.io/. Once the application runs, you can restore your wallet, create a new wallet with your own keys, and then transfer your ADA to your own secure wallet. Otherwise, you just have to trust me - but crypto is about trusting nobody! Take control over your own money.

Download from: https://daedaluswallet.io/

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...

https://github.com/NixOS/nixpkgs/commits?author=neon-sunset

I see two signers in the top 6 displayed on https://github.com/NixOS/nixpkgs/graphs/contributors

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,

```

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...

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...

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

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...