Parse signed transaction error

[ddxx5317]

Ask a question

I use the serialization library to sign a transaction, and then use the construction/submit endpoint of rosetta-api to broadcast the hex signature data, but it returns "Parse signed transaction error"

eg：

// build tx
const txBody = txBuilder.build();
const txHash = CardanoWasm.hash_transaction(txBody);
const transaction = CardanoWasm.Transaction.new(txBody, witnesses, undefined);
const txHex = Buffer.from(transaction.to_bytes()).toString("hex");

// send txHex
curl -X POST 'localhost:8888/construction/submit'
-H "Content-Type: application/json"
-d '{"network_identifier": {"blockchain": "cardano","network": "mainnet"},"signed_transaction": txHex}'

return:
{
"code": 5003,
"message": "Parse signed transaction error",
"retriable": false
}

What's the problem ? Does Rosetta not support transactions signed with serialization libraries?

[sc-starman]

same here, I use wallet-core library to sign the transaction and broadcast it using rosseta

[zhanghuize-git]

Hi bro, are you solve it ？

[Godspeed-exe]

Rosetta expects a specific format, for that reason it’s advised to go through the entire process using Rosetta (query, construct , sign, submit).

Do you use any of the above functionalities of Rosetta? If not, you might as well submit it by connection a submit-api to your node socket,

Of course, you can reverse engineer the Rosetta format, you’ll you have to wrap your CBOR in the Rosetta JSON envelope and then CBOR encode it again.

@Kartiiyer12 @linconvidal I believe we have examples of this somewhere?

[Kartiiyer12]

Hi @zhanghuize-git

It would be easier to build submit api within the cardano-rosetta image and use that to submit transactions.

To add submit api within the existing Dockerfile -

• (Build the submit api) https://github.com/cardano-foundation/cardano-rosetta/blob/master/Dockerfile#L107 -> add
  && cabal build cardano-submit-api

• (copy the executable )https://github.com/cardano-foundation/cardano-rosetta/blob/master/Dockerfile#L111 -> add
  && cp -p "$(./scripts/bin-path.sh cardano-submit-api)" /root/.local/bin/

• (copy into cardano-rosetta-server) https://github.com/cardano-foundation/cardano-rosetta/blob/master/Dockerfile#L210 -> add
  /root/.local/bin/cardano-submit-api \
  -(add config to start submit api) https://github.com/cardano-foundation/cardano-rosetta/blob/master/ecosystem.config.js#L34 -> add

{
      name: 'cardano-submit-api',
      script: '/usr/local/bin/cardano-submit-api',
      args: [
        '--config', '/config/cardano-submit-api/config.json',
        '--socket-path', '/ipc/node.socket',
        '--port', '8090',
        '--listen-address', '0.0.0.0',
        '--mainnet'
      ],
      autorestart: true,
      exec_mode: 'fork_mode',
      kill_timeout : 30000,
      error_file: 'NULL',
      out_file: 'NULL'
    },

• At last when running the rosetta, make sure you run the docker to expose both the rosetta and the submit-api port.

docker run --name cardano-rosetta -d -p 8080:8080 -p 8090:8090 -v cardano-rosetta:/data \
  --shm-size=2g \
  cardanofoundation/cardano-rosetta:2.3.3

[zhanghuize-git]

Thanks for the replies guys, I'm using the cardano-rosetta api for the whole process, and after much exploration I realized that it's the signing that's the problem.

[Godspeed-exe]

Good to hear! Let us know how to help!

btw, if you are working with an exchange with can also support you directly through a dedicated channel. Let me know if that’s useful to you!

[zhanghuize-git]

I am a exchange wallet devloper, our product need support cardano chain.

[Godspeed-exe]

hello @zhanghuize-git

can you reach out to [email protected] ? We're happy to set up a dedicated channel to smoothen the support with your team.