Rafael Cárdenas
Rafael Cárdenas
if a transaction fails for each of those DBs, the other write should not go through and viceversa
...so we can have its genesis and all of its future transfers. This will be very useful if we need to backfill missing inscriptions on the Ordinals API.
**Describe the bug** I'm experiencing very strange behavior with my local mainnet Stacks node (2.4.0.0.0)... it's been stuck at block 107054 for days now, and when looking at the logs...
The following is a list of issues that must be tackled in order to bring the subdomain registrar to a much better operating condition than it has today. The current...
There are newer request libraries such as [undici](https://github.com/nodejs/undici) that are much more easy to work with when it comes to JSON parsing, request/response schema validation, status code and headers handling,...
The registrar still contains request logic that assumes the target nodes are from Blockstack v1, including [custom load balancer logic](https://github.com/stacks-network/subdomain-registrar/blob/master/src/operations.js#L306-L318) that is no longer relevant. It should be updated to...
The registrar can receive 404 status codes from the Stacks Blockchain API if a transaction ID is not found for any reason (missing from mempool, etc.). It should try again...
The registrar currently runs on node 12, which is outdated and no longer maintained. It should be upgraded to at least node 18 which is the current LTS version.