the reason for the evil taint has to do with taproot signatures.

i already started trying to pull in all the necessary things and was lazy and just copying whole sources in the chain of things but this approach quickly led to even moar evil infesting my SSD so there is going to be a more surgical approach, just to find ONLY the pieces required to access the taproot stuff. i don't need to be able to process the whole damn taproot spec just to work with the plain signatures.

also, just want to observe that within 2 levels of indirection i was bumped into imported source code from prior versions of btcd in the current version.

linking code together between two different tagged versions was NOT the intent of go modules, but unfortunately, it has enabled the growth of go modules cache to `node_modules` proportions which also means that when i tried to build some relevant thing on my tiny 7gb hdd VPS almost a gigabyte of storage was eaten by the go modules cache.

this does not happen with my work. idgaf how much fancy terabytes of SSD storage you have, poor bastards in tajikistan don't have it and that makes you an oppressor.