stacks
Stacks blockchain node and mining — RPC API, testnet transactions, PoX mining, event observer, SIPs, property testing, release process, profiling, and service setup.
Works with
--- name: stacks description: Stacks blockchain node and mining — RPC API, testnet transactions, PoX mining, event observer, SIPs, property testing, release process, profiling, and service setup. license: MIT --- > Skill is based on Stacks blockchain (stacks-node v3.3.0.0.5), generated 2026-02-24. Docs: `sources/stacks/docs/`, [docs.stacks.co](https://docs.stacks.co/) Stacks is a layer-2 blockchain anchored to Bitcoin security, using Proof of Transfer (PoX) for mining and Clarity for smart contracts. This skill covers the reference node (stacks-node): RPC endpoints, testnet tx flow, mining config, event observer, SIPs, property testing, release/branching, profiling, init/service, and CI. ## Core References | Topic | Description | Reference | |-------|-------------|-----------| | RPC Endpoints | POST/GET for transactions, accounts, contracts, blocks, PoX, Nakamoto (v2/v3) | [core-rpc-endpoints](references/core-rpc-endpoints.md) | | Testnet and Transactions | Genesis balance, encode/sign, publish contract, contract-call via blockstack-cli and RPC | [core-testnet-transactions](references/core-testnet-transactions.md) | ## Features | Topic | Description | Reference | |-------|-------------|-----------| | Mining (PoX) | Miner config, burn commitment, RBF, fee/cost estimation | [features-mining](references/features-mining.md) | | Event Dispatcher | events_observer config, events_keys, POST endpoints and payloads | [features-event-dispatcher](references/features-event-dispatcher.md) | | SIPs | Stacks Improvement Proposals — where they live and how to use them | [features-sips](references/features-sips.md) | ## Best Practices | Topic | Description | Reference | |-------|-------------|-----------| | Property Testing | proptest-rs, strategies, assertions, CI (PROPTEST_CASES) | [best-practices-property-testing](references/best-practices-property-testing.md) | | Release and Branching | Version format, master/develop/release, release steps, hotfixes | [best-practices-release-branching](references/best-practices-release-branching.md) | ## Advanced | Topic | Description | Reference | |-------|-------------|-----------| | Profiling | Logging, mock miner, tip-mine, flamegraph, SQLite profiling | [advanced-profiling](references/advanced-profiling.md) | | Init and Service | systemd, SysVinit, macOS LaunchAgents, paths and user | [advanced-init-service](references/advanced-init-service.md) | | CI Workflow | Tests, partitions, release builds, Docker, adding tests | [advanced-ci-workflow](references/advanced-ci-workflow.md) | ## External Links - [Stacks docs](https://docs.stacks.co/) - [Stacks blockchain (GitHub)](https://github.com/stacks-network/stacks-blockchain) - [SIPs (stacksgov/sips)](https://github.com/stacksgov/sips)
More Debugging skills
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
explore-code
lllllllama/rigorpilot-skills
Rigor Improve implementation leaf skill for auditable candidate implementation in deep learning research repositories. Use when the researcher explicitly authorizes exploratory work on an isolated branch or worktree to transplant modules, adapt a backbone, add LoRA or adapter layers, replace a head, or stitch together meaningful low-risk migration ideas with rollback-aware records in `explore_outputs/`. Do not use for end-to-end exploration orchestration on top of `current_research`, trusted baseline reproduction, conservative debugging, environment setup, verified contribution claims, or default repository analysis.
safe-debug
lllllllama/rigorpilot-skills
Rigor Debug / Rigor Audit skill for deep learning research work. Use when the user pastes a traceback, terminal error, CUDA OOM, checkpoint load failure, shape mismatch, NaN loss symptom, or training failure and wants conservative diagnosis before any patching, with debug fixes clearly separated from research contributions. Do not use for broad refactoring, speculative adaptation, automatic exploratory patching, or general repository familiarization.
