Matthew Little

[Stacks 2.1] 500 response from `GET /v2/pox`

6

Running the latest `next` branch in mocknet mode, and the `GET /v2/pox` endpoint often returns an HTTP 500 error with the message: `Failed to query peer info`. On my machine,...

[Stacks 2.1] The `/v2/pox` endpoint never switches to PoX-2

2

When running with the latest `next` branch, the `GET /v2/pox` endpoint always returns `{"contract_id":"ST000000000000000000002AMW42H.pox"}` regardless of the epoch or cycle. The expected behavior is that this should return `{"contract_id":"ST000000000000000000002AMW42H.pox-2"}` when...

The `matured_miner_rewards` payload included in the `/new_block` event always specifies the coinbase tx leader's principal, and never specifies the alternate recipient. I've tested with both standard principals and contract principals....

* [x] https://github.com/hirosystems/stacks-blockchain-api/issues/1281 * [x] https://github.com/hirosystems/stacks-blockchain-api/issues/1274 * [x] https://github.com/hirosystems/stacks-blockchain-api/issues/1275 - Note: done on the API side, bug needs fixed in stacks-node, see issue details. * [x] https://github.com/hirosystems/stacks-blockchain-api/issues/1276 * [ ]...

[Stacks 2.1] Support PoX-2 in Rosetta stacking operations

3

See related issue https://github.com/hirosystems/stacks-blockchain-api/issues/1277 which goes over similar details and questions around PoX-2. The Rosetta implementation currently contains rosetta-operations for initiating a Stacking transaction. It also returns a synthetic "stx-unlocked"...

Context from https://github.com/hirosystems/stacks-blockchain-api/pull/1295 The Rosetta construction code still uses the legacy fee calculation method of essentially `fee = someConstant * tx.byteLength`. There's a new-ish RPC endpoint `/v2/fees/transaction` which can return...

[Stacks 2.1] Support `coinbase-pay-to-alt-recipient` transactions

1

Support `coinbase-pay-to-alt-recipient` transactions, see https://github.com/stacks-network/stacks-blockchain/pull/3164 **Blocked** by bug in the stacks-node, see https://github.com/stacks-network/stacks-blockchain/issues/3258

[Stacks 2.1] Support PoX-2 for account STX balance `locked` state

2

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.com/hirosystems/stacks-blockchain-api/pull/324 -- the...

Related to signer support in the API & Explorer https://github.com/hirosystems/explorer/issues/1248 The API and Explorer would like to show signer performance, e.g. a record of uptime and slot success rate. It...

Add `signer-key` to `*-increase` pox events

2

The `signer-key` has effectively become the “primary key” for all signer data. So if I’m trying to lookup information about stackers based on `signer-key`, it gets pretty difficult when important...