Skip to content

docs: overhaul stacking.md (remove outdated data, update branding, an…#557

Open
0xward wants to merge 1 commit into
stacks-network:masterfrom
0xward:fix/stacking-overhaul
Open

docs: overhaul stacking.md (remove outdated data, update branding, an…#557
0xward wants to merge 1 commit into
stacks-network:masterfrom
0xward:fix/stacking-overhaul

Conversation

@0xward

@0xward 0xward commented Jun 15, 2026

Copy link
Copy Markdown

Description

As a Stacks documentation contributor, I would like to update the stacking.md file to reflect the current post-Nakamoto network state. This is needed because the existing documentation contains stale 2021 data, deprecated "Stacks 2.0" branding, and broken links, which are misleading for current developers.

  1. Motivation for change: The stacking.md file contained outdated 2021 Stacking thresholds, used deprecated "Stacks 2.0" branding, and included a dead link to a legacy blog.
  2. What was changed:
    • Removed obsolete 2021 Stacking threshold figures.
    • Replaced hardcoded values with a reference to the official Stacking documentation.
    • Updated "Stacks 2.0 blockchain" branding to "Stacks blockchain".
    • Removed the broken link to blog.blockstack.org.
  3. How does this impact application developers: Improves documentation reliability and ensures developers are guided to the most current resources.
  4. Link to relevant issues and documentation: N/A
  5. Provide examples of use cases with code samples and applicable acceptance criteria: N/A

Type of Change

  • API reference/documentation update

Does this introduce a breaking change?

No.

Are documentation updates required?

  • Link to documentation updates: N/A (This PR is the documentation update)

Testing information

  1. Is testing required for this change? No.
  2. If it’s a bug fix, list steps to reproduce the bug: N/A
  3. Briefly mention affected code paths: N/A
  4. List other affected projects if possible: N/A
  5. Things to watch out for when testing: Verified links redirect to expected pages.

Checklist

  • Code is commented where needed
  • Unit test coverage for new or modified code paths
  • npm run test passes
  • Changelog is updated
  • Tag 1 of @person1 or @Person2

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.

1 participant