u/Slight-Brilliant3198

I 100% support BIP-110, and I truly believe it's the real Bitcoin. That is, because it keeps the same spirit and vision of the original project.

Also, in September I'm evaluating the idea to become a miner too, and put my money where my mouth is.

But I have a doubt: let's assume that Bitcoin Core keep being the biggest hash chain, and it's unfortunately very possible, why would any one want to keep the BIP-110 Bitcoins, if not only for ideological reasons?

There are other crypto projects that are serious, ideologically and technologically solid. The main reason Bitcoin is also the most economically valuable is that it's the one that most people trust, for investing purposes.

So you think that is possible that BIP-110 Bitcoin will never match the same USD value of core-Bitcoin?

Is it possible that it will always have a similar value of other alt-cryptos and never be the "big boy" again?

I'm scared of supply chain vulnerabilities. More specifically, after the recent attacks on Arch Linux's AUR, I was wandering how Void Linux is protected from this type of attacks.

I'm not an expert, because I've never submitted a package to void-packages, so I'm not sure if there's an audit process for packages and vetting for maintainer.

Can anybody be a maintainer for a package?

What happens after I push srcpkgs/new-package/template into the main repo?

Will it become an binary that will be available via xbps-install, or will it stay something that must be manually compiled via xbps-src?

Is there an official difference between a void maintainer, and a potentially malicious person pulling some malware blobs in do_fetch(), and installing it in do_build() do_install() ?

I never bothered configuring AppArmor because I use a single user, personal laptop.

However, with all the supply-chain exploits happening lately, I was thinking it could be a good idea to configure it.

I write this specifically on the Void Linux subreddit, because AppArmor acts differently from distro to distro, and Void has the almost unique socklog + runit combo.

Do I really need both aa-genprof and aa-logprof, for an easy and smooth management experience?

Is having auditd suggested, or will syslog suffice on every use case?

Where can I find trusted AppArmor profiles for common apps? Is it better if I work on them from scratch?

What's the best practices, and the typical configuration steps that the Void Linux veterans do, to harden the system with aa?