stacks-core
stacks-core copied to clipboard
stacks-network
The Stacks blockchain implementation
We should add a GH action that forces PRs to include `CHANGELOG.MD` changes.
ex: https://github.com/blockstack/stacks-blockchain/blob/master/testnet/stacks-node/conf/neon-follower-conf.toml#L8 I propose using standardized names in user-facing config files like `testnet`, `regtest`, or `mainnet` This would help users avoid confusion about what network they're configuring. One idea would...
Connecting to the Stacks testnets requires having the same initial balances configured for the genesis block as the rest of the network. Otherwise, the initialized node will operate as a...
**Describe the bug** The `tx_status` of https://stacks-node-api.mainnet.stacks.co/extended/v1/tx/0x38e2f50a4c410e2835a3497d0a7f68c2e81150a3f95956333c31d7b68beb647b?chain=mainnet is shown as `abort_by_post_condition`. However, the `tx result` is `(err u5)`. **Expected behavior** I'd expect the tx status as `abort_by_response` **Additional context** First...
At some point, we will want it to be possible for Stacks nodes to register themselves on home networks and serve blocks and transactions to not only local clients, but...
**Is your feature request related to a problem? Please describe.** In my smart contract, I would like to determine during which cycle a bitcoin transaction happened. This is to calculate...
There are a small number of places that uses burn_chain or burn chain instead of burnchain.
We need a more specific style guide for the `stacks-blockchain` repo. There has been some confusion about what should be in the comments.
It's currently fairly difficult to sign a multi-sig transaction unless using a single instance of `TransactionSigner`. This means that the transaction can't easily be signed by _multiple_ parties. This is...
This is a feature request for *benchmarking* of Clarity2 functions. We already have Issue #1165 for benchmarking Clarity functions. However, what might lost in the shuffle is the fact that...