You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- disingenuous to think default policy is the factor that changes this, approach should be more like OCEAN
77
77
- Core isn't* bitcoin, Knots isn't dangerous
78
78
79
79
* Call to Action
80
-
- First time node runner -- Run Core
81
-
- Non-technical -- Run Knots
82
-
- Role of a node runner
80
+
- First time node runner -- Run Core. Why you should run a node
81
+
- Non-technical, still learning -- Run Knots
82
+
- Role of a node runner
83
83
- Study, compile your own, give back
84
84
85
85
* Resources links
@@ -91,9 +91,10 @@ Recently there has been a lot of drama concerning OP_Return at Bitcoin Core (pr
91
91
- I'm unwilling to defend Core's actions because I don't agree with them and have no need to (i don't receive funding from chaincode labs or spiral)
92
92
- heart of the issue was "fix or remove" datacarrier
93
93
- Core dragged their feet -- did nothing, then removed datacarrier without acknowledging their initial inaction
94
+
- Core argues and communicates in bad faith
94
95
- Unified mempools / Policy should equal consensus is the wrong approach
95
-
- I don't advocate for Knots, but I respect what Luke-jr is doing and have no problem recommending long-standing Bitcoin implementations
96
-
- Core should have left it alone - unclear why push for a change that lacks technical merit with poor arguments -- questionable motivations in funding
96
+
- I don't advocate for Knots, but I respect what Luke-jr is doing and encourage others to look into it
97
+
- Core should have left it alone - unclear what need is there to push for a change that lacks technical merit with poor arguments -- questionable motivations in funding
0 commit comments