-
```
curl "https://stacks-node-api.testnet.stacks.co/extended/v1/block/by_height/94100"
```
```
"microblocks_streamed": [
"0x5b5e4236a7496571b56c4765570b9c263f5b529c9b1fa060abf4b6cd50e16c3c"…
-
**Describe the bug**
The endpoint https://stacks-node-api.mainnet.stacks.co/v1/names/ape.mega shows SPC0KWNBJ61BDZRPF3W2GHGK3G3GKS8WZ7ND33PS as owner. However, the nft is owned by SPV48Q8E5WP4TCQ63E9…
-
Currently expands to: `(map sequence sequence)`
Should be: `(map func sequence)`
-
### Progress:
* [x] MVP support for PoX-2 / parity with current PoX-1 support
* [x] Support constructing & reading Stacking ops using the new segwit/taproot/bech32 address formats introduced in PoX-…
-
If you are running the script with a any flag (lets use proxy flag an an example) and restart the service with:
`./manage.sh -n testnet -a restart -f proxy` everything is restarted as expected.
…
-
https://github.com/Trust-Machines/stacks-blockchain/pull/5/files
TODO: Include methods
-
The hero section and the rest of the texts should be edited.
-
**Describe the bug**
Looks like there is a regression in the API for the name endpoint. Calling the API https://stacks-node-api.mainnet.stacks.co/v1/names/usernameTest endpoint returns a `400` HTTP…
-
The API currently uses the Stacks 2.0 `stx_lock_event` event to store and retrieve "locked" and "unlock_height" data when responding to account balance requests. This was implemented in https://github…
-
*We prefer clear, concrete, and concise applications. If an application is incomplete or unclear, we will request an update to the application.*
## Background
> What problems do you aim to solve…