RPC rawtransaction calls cannot decode rawtx about bitcoindiamond HOT 10 CLOSED

The info returned from insight-api/rawtx is not correct.

from bitcoindiamond.

That explains why I can't broadcast my TX because I use it to crosscheck the format. I guess you have some docs (or code) describing the difference? Could you give me a pointer so I can do it? We need to build and sign Tx offline for our cold wallets.
Thanks @heyconnor.

from bitcoindiamond.

@lix2ng TX version is 12, and there is a preblockhash followed version.

from bitcoindiamond.

@heyconnor Version 12 was set. I'll look into the preblockhash part.
If you could provide a legal tx string (which RPC will decode) as an example, that would be very useful to me.
Thanks!

from bitcoindiamond.

@lix2ng You can get raw tx by "bitcoindiamond-cli getrawtransaction [txid]".

from bitcoindiamond.

@heyconnor Confirmed. the rawtx from RPC getrawtransaction() has the previous block hash between the version word and input count.
Interesting. Does it mean I have to query the blkhash of current tip when making a Tx? What happens if I made it 1min before next block, and if user spent 1m1s to finish the signature I'll miss the window and the whole thing must restart? This train-catching game will frustrate user for sure.

from bitcoindiamond.

@lix2ng The preblockhash is not strictly checked currently. Just make sure it's not zero.

from bitcoindiamond.

OK, thanks. do you have a BCD-specific JS lib to handle the local building and signing of Tx?

from bitcoindiamond.

No.

from bitcoindiamond.

@heyconnor Thank you for being so patient to clarify my questions.
Now it's all clear to me. I'm closing now.

from bitcoindiamond.