stacks-blockchain-api icon indicating copy to clipboard operation
stacks-blockchain-api copied to clipboard

API for the Stacks blockchain

Results 311 stacks-blockchain-api issues
Sort by recently updated
recently updated
newest added

Currently, the Rosetta endpoints only support creating transactions for two contract calls: `stack-stx` and `delegate-stx`. In order to fully use the Stacks blockchain's capabilities, we should add support for arbitrary...

rosetta

**Describe the bug** Calling `connectWebSocketClient(..).subscribeBlocks()` results in the following error: ```js JsonRpcError { message: 'Invalid params', code: -32602, data: 'subscription request must use a valid event name' } ``` **Expected...

good first issue
sockets

Let's figure out how to add the client library to the stacks.js monorepo. This goal should ideally include both an integration into the monorepo but also the being released in...

enhancement

The codebase generally has pretty good error capturing and logging for unexpected conditions. Typically any external bug report will have associated logs with `level: error` hours or days before the...

P2
Epic

There's a handful of cases where it would be useful for the search endpoint to be able to return results for partial text matches. Some examples: a contract name, token...

Hello, I could not find, in this repository, the documentation that is supposed to be ported from the Stacks blockchain repository. https://github.com/blockstack/stacks-blockchain/issues/2353

It would be great if there would be an API endpoint that would take an STX address (of a delegator) and return what accounts delegated how much (and until what...

enhancement

What's our take on updating the API routes and go with something more REST compliant? `/new_mempool_tx` -> `/mempool_tx/new` `/new_block`-> `/block/new` `/new_burn_block` -> -> `/burn_block/new` I was also thinking about maybe...

icebox

Currently, the client requires contract call arguments to be manually serialized: ```js await smartContracts.callReadOnlyFunction({ contractAddress, contractName, functionName, readOnlyFunctionArgs: { sender: stxAddress, arguments: [ `0x${serializeCV( tupleCV({ hashbytes, version, }) ).toString("hex")}`, `0x${serializeCV(uintCV(microSTXoLockup)).toString("hex")}`,...

enhancement
help wanted

Ref https://github.com/blockstack/stacks-blockchain-api/pull/193#issue-470994650 Multisig transactions have a few additional fields that can be returned. @aulneau @hstove any input on what might be useful?

enhancement
good first issue
help wanted
icebox