Guix build fix

.github/ISSUE_TEMPLATE/bug.yml

@@ -5,11 +5,12 @@ body:
   - type: markdown
     attributes:
       value: |
-        ## This issue tracker is only for technical issues related to Bitcoin Core.
+        ## This issue tracker is only for technical issues related to Bitcoin Knots.
 
         * General bitcoin questions and/or support requests should use Bitcoin StackExchange at https://bitcoin.stackexchange.com.
-        * For reporting security issues, please read instructions at https://bitcoincore.org/en/contact/.
+        * For reporting security issues, please read instructions at https://bitcoinknots.org/contact/
         * If the node is "stuck" during sync or giving "block checksum mismatch" errors, please ensure your hardware is stable by running `memtest` and observe CPU temperature with a load-test tool such as `linpack` before creating an issue.
+        * If your issue also affects Bitcoin Core, report it at https://github.com/bitcoin/bitcoin/issues/new?labels=bug&template=bug.yml
 
         ----
   - type: checkboxes
@@ -57,7 +58,7 @@ body:
       required: false
   - type: dropdown
     attributes:
-      label: How did you obtain Bitcoin Core
+      label: How did you obtain Bitcoin Knots
       multiple: false
       options:
         - Compiled from source
@@ -67,10 +68,10 @@ body:
     validations:
       required: true
   - type: input
-    id: core-version
+    id: knots-version
     attributes:
-      label: What version of Bitcoin Core are you using?
-      description: Run `bitcoind --version` or in Bitcoin-QT use `Help > About Bitcoin Core`
+      label: What version of Bitcoin Knots are you using?
+      description: Run `bitcoind --version` or in Bitcoin-QT use `Help > About Bitcoin Knots`
       placeholder: e.g. v24.0.1 or master@e1bf547
     validations:
       required: true

.github/ISSUE_TEMPLATE/config.yml

@@ -1,8 +1,8 @@
 blank_issues_enabled: true
 contact_links:
-  - name: Bitcoin Core Security Policy
-    url: https://github.com/bitcoin/bitcoin/blob/master/SECURITY.md
+  - name: Bitcoin Knots Security Policy
+    url: https://bitcoinknots.org/contact/
     about: View security policy
-  - name: Bitcoin Core Developers
-    url: https://bitcoincore.org
-    about: Bitcoin Core homepage
+  - name: Bitcoin Knots Website
+    url: https://bitcoinknots.org
+    about: User-oriented information

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,17 +1,17 @@
 <!--
 *** Please remove the following help text before submitting: ***
 
-Pull requests without a rationale and clear improvement may be closed
-immediately.
+Before opening a pull request to Bitcoin Knots, please first consider if it
+is appropriate for Bitcoin Core and, if so, rebase it and [open a pull request](https://github.com/bitcoin/bitcoin/compare)
+there first! Bitcoin Core has a strict and slow review process, but since
+Knots is more relaxed, feel free to request a merge of your Core PR into
+Knots even while it's waiting on Core.
 
-GUI-related pull requests should be opened against
-https://github.com/bitcoin-core/gui
-first. See CONTRIBUTING.md
 -->
 
 <!--
 Please provide clear motivation for your patch and explain how it improves
-Bitcoin Core user experience or Bitcoin Core developer experience
+Bitcoin Knots user experience or Bitcoin Knots developer experience
 significantly:
 
 * Any test improvements or new tests that improve coverage are always welcome.
@@ -22,22 +22,7 @@ significantly:
 * Bug fixes are most welcome when they come with steps to reproduce or an
   explanation of the potential issue as well as reasoning for the way the bug
   was fixed.
-* Features are welcome, but might be rejected due to design or scope issues.
-  If a feature is based on a lot of dependencies, contributors should first
-  consider building the system outside of Bitcoin Core, if possible.
-* Refactoring changes are only accepted if they are required for a feature or
-  bug fix or otherwise improve developer experience significantly. For example,
-  most "code style" refactoring changes require a thorough explanation why they
-  are useful, what downsides they have and why they *significantly* improve
-  developer experience or avoid serious programming bugs. Note that code style
-  is often a subjective matter. Unless they are explicitly mentioned to be
-  preferred in the [developer notes](/doc/developer-notes.md), stylistic code
-  changes are usually rejected.
--->
-
-<!--
-Bitcoin Core has a thorough review process and even the most trivial change
-needs to pass a lot of eyes and requires non-zero or even substantial time
-effort to review. There is a huge lack of active reviewers on the project, so
-patches often sit for a long time.
+* Features are typically welcome.
+* Refactoring changes are never accepted in Knots, and must be performed in
+  Bitcoin Core.
 -->