I wrote the code to partially signal the PSBT. Briefly the server sends me a PSBT in Base64 format and N inputs to be signed. I encode the PSBT, signal the inputs with PK utilizing Schnorr technique. I replace it again to Base64 and ship it to the server (not finalised PSBT with unsigned enter 0).
That is the way it ought to appear to be after processing (right):
{
{ ‘outcome’: {
{ ‘inputs’: [
{
‘has_utxo": true,
‘is_final": false,
{ ‘next’: { ‘updater’.
},
{
‘has_utxo": true,
‘is_final": false,
{ ‘next’: ‘finalizer’.
},
{
‘has_utxo": true,
‘is_final": false,
{ ‘next’: ‘finalizer’.
}
],
‘payment": 1.328e-5,
‘subsequent": { ‘updater’
},
‘error": null,
‘id": null
}
That is what it seems like after being processed by my script. The Updater standing ought to change to finaliser for these inputs I signed, however it does not (incorrect) :
{
"outcome": {
"inputs": [
{
"has_utxo": true,
"is_final": false,
"next": "updater"
},
{
"has_utxo": true,
"is_final": false,
"next": "updater"
}
],
"estimated_vsize": 286,
"estimated_feerate": 7.0e-5,
"payment": 2.002e-5,
"subsequent": "updater"
},
"error": null,
"id": null
}
I checked signatures (they’re right), in contrast right partially signed PSBT and my very own (no variations besides txid, which will probably be distinctive each time), even tried to finalise PSBT (though it’s completely not want), however I nonetheless could not perceive why the standing of inputs stays Updater, when it’s despatched with finilize when signed through any pockets extension.I do not even perceive the place the error may very well be, since I do the logs BEFORE signing and AFTER signing, and their standing within the logs is up to date. Additionally, should you take the PSBT after my code has processed it and decoded it, it does replace and isn’t any totally different from the proper one apart from the TXid.
I am a whole beginner at coding, sorry if I stated something flawed
I wrote the code to partially signal the PSBT. Briefly the server sends me a PSBT in Base64 format and N inputs to be signed. I encode the PSBT, signal the inputs with PK utilizing Schnorr technique. I replace it again to Base64 and ship it to the server (not finalised PSBT with unsigned enter 0).
That is the way it ought to appear to be after processing (right):
{
{ ‘outcome’: {
{ ‘inputs’: [
{
‘has_utxo": true,
‘is_final": false,
{ ‘next’: { ‘updater’.
},
{
‘has_utxo": true,
‘is_final": false,
{ ‘next’: ‘finalizer’.
},
{
‘has_utxo": true,
‘is_final": false,
{ ‘next’: ‘finalizer’.
}
],
‘payment": 1.328e-5,
‘subsequent": { ‘updater’
},
‘error": null,
‘id": null
}
That is what it seems like after being processed by my script. The Updater standing ought to change to finaliser for these inputs I signed, however it does not (incorrect) :
{
"outcome": {
"inputs": [
{
"has_utxo": true,
"is_final": false,
"next": "updater"
},
{
"has_utxo": true,
"is_final": false,
"next": "updater"
}
],
"estimated_vsize": 286,
"estimated_feerate": 7.0e-5,
"payment": 2.002e-5,
"subsequent": "updater"
},
"error": null,
"id": null
}
I checked signatures (they’re right), in contrast right partially signed PSBT and my very own (no variations besides txid, which will probably be distinctive each time), even tried to finalise PSBT (though it’s completely not want), however I nonetheless could not perceive why the standing of inputs stays Updater, when it’s despatched with finilize when signed through any pockets extension.I do not even perceive the place the error may very well be, since I do the logs BEFORE signing and AFTER signing, and their standing within the logs is up to date. Additionally, should you take the PSBT after my code has processed it and decoded it, it does replace and isn’t any totally different from the proper one apart from the TXid.
I am a whole beginner at coding, sorry if I stated something flawed
