Open owenkellogg opened 1 year ago
Thank you for making this issue!
Please get it some attention by boosting it here https://powco.dev/github/pow-co/pow.co/issues/69
Bounties may be sent to this address https://whatsonchain.com/address/1MqzySpwC9oHLpApEtpFp2AWuFLuzcwZ1L and will be paid to the worker who completes your issue.
Thank you for making this issue!
Please get it some attention by boosting it here https://powco.dev/github/pow-co/pow.co/issues/69
Bounties may be sent to this address https://whatsonchain.com/address/1MqzySpwC9oHLpApEtpFp2AWuFLuzcwZ1L and will be paid to the worker who completes your issue.
Thank you for making this issue!
Please get it some attention by boosting it here https://powco.dev/github/pow-co/pow.co/issues/69
Bounties may be sent to this address https://whatsonchain.com/address/1MqzySpwC9oHLpApEtpFp2AWuFLuzcwZ1L and will be paid to the worker who completes your issue.
Example: https://api.whatsonchain.com/v1/bsv/main/tx/f6c503d1f56cb937a074feb942f9c67f1696a79f6a7e27c61125a5f3deeba29e/hex
While in the mempool this is returning 404 and no content whatsoever.
However its counterpart without the
/hex
at the end gives the transaction but not the entire transaction.https://api.whatsonchain.com/v1/bsv/main/tx/f6c503d1f56cb937a074feb942f9c67f1696a79f6a7e27c61125a5f3deeba29e
One solution is to update the function that imports jobs/proofs by txid to instead get the latter endpoint and then go through each output script hex and attempt to parse a job or a proof.
All that said it might be most effective to go with posting the entire transaction hex rather than posting the txid itself, that way we can always import it first or broadcast it then import it. Ultimately the existing method to import jobs by txid was a convenience function and can be better re-enforced.