Skip to content

Comments

docs(tutorial): Config - Stacks Node Follower vs Miner Modes#1775

Closed
jadonamite wants to merge 1 commit intostacks-network:masterfrom
jadonamite:patch-11
Closed

docs(tutorial): Config - Stacks Node Follower vs Miner Modes#1775
jadonamite wants to merge 1 commit intostacks-network:masterfrom
jadonamite:patch-11

Conversation

@jadonamite
Copy link

Description

This PR adds Module 10: Node Configuration by @jadonamite. It provides an elaborate comparison and setup guide for running Stacks Nodes in distinct operational modes.

Content Overview

  • Architecture: The distinction between State Validators (Followers) and Consensus Participants (Miners).
  • Configuration: Side-by-side Config.toml breakdowns for [node], [burnchain], and [miner] sections.
  • VRF Explanation: Demystifying the vrf_secret vs seed requirements for miners.

Checklist

  • Config.toml parameters validated against Stacks Node v2.4 (Nakamoto).
  • Security warnings regarding Hot Wallets (Miner mode) included.
  • Formatting follows the repository's style guide.

adds **Module 10: Node Configuration** by @jadonamite. It provides an elaborate comparison and setup guide for running Stacks Nodes in distinct operational modes.
@jadonamite jadonamite requested a review from a team as a code owner January 21, 2026 15:34
@eric-stacks
Copy link
Collaborator

@jadonamite alot of your PRs were just repurposing content from other sections into the Tutorials section. This is redundant and not needed.

PRs need to have a value add not a redundancy of content.

@jadonamite
Copy link
Author

you closed all my PR saying every single thing was repurposed from other section ...?
wow , thats wild

@eric-stacks
Copy link
Collaborator

you closed all my PR saying every single thing was repurposed from other section ...? wow , thats wild

it was deemed that all of your PRs were related to existing guides that are already available in the docs.

Redundancy and duplication of content is what we want to avoid. if you have a guide or tutorial that covers new content, then this would be more acceptable.

@jadonamite
Copy link
Author

@eric-stacks everything i made , every single PR i made was from issues i personally had encountered working with stacks over the months and a research of issues faced by users too on stacks-overflow or on reddit and online generally , i actually felt hurt to see that every single PR i made was closed with this comment , I have no words , i simply love stacks too much to do other wise i would still contribute my content i see and try to do my due research if it exist

@eric-stacks
Copy link
Collaborator

eric-stacks commented Jan 27, 2026

@jadonamite let's chat more about this on Discord, what's your Discord handle?

Firstly, many of the PRs you made didn't constitute as Tutorials in the definition we define for Tutorials. Tutorials are longer form lesson-based tutorials. You're PRs were more so one-page How-To guides.

Perhaps we can find some place other place in our docs for them. And some/many of the PRs i've noticed are already somewhat covered in other areas of the docs. In addition, some of your guides were using outdated or incorrect stacks.js/Hiro API syntax defintiions. I would suggest you to verify that everything written in your guide is accurate before making a PR.

But nonetheless, i'm happy to talk more on Discord about this and let's find a better way for your guides to fit in.

@jadonamite
Copy link
Author

jadonamite commented Jan 28, 2026

_jadonamite @discord @eric-stacks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants