Coinomi TX Signing Issues

[jackg]

I tried to make a transaction with coinomi and sign it, the signed hex is

Code:

0100000001d9c9f7d12419848477506c8ca09b47f55d6dd4ce8442a467b3cc78596405af211c0000006b483045022100e4feb502f883057194cb0f3dff802177036b52714c94852b6e6f0656a2adbe830220381b45ef1cf7c4937981c3a534364f7b0e7fa7e70de9cae2bc35b62104833043012102d2f573c371c17ae32225044fe2f7582a5ed5ae5835fe0408228f0149ee9a6a12ffffffff01a0860100000000001600146ca8c500e1894e369350c9b0f4f436adf007869500000000

My electrum says it's signed but my core says there's something wrong with the crtiptpubkey, I need to broadcast it in core as I don't wnat to pay a fee with it and it's affordable to just leave it as is until the bitcoin developers realise they don't have to enforce adding a fee to transactions any more...

[LoyceV]

As far as I know, it can't be broadcasted and will be rejected by any node.

Relevant information:

Default fees are proposed to be lowered in Bitcoin 0.18.0

Basically, the minimum will drop from 1sat/vbyte to 0.2sat/vbyte.

0.18.0 is scheduled for release in March 2019, which assumes nothing delays the release. And it may take time for the full effects be felt on the network, as miners may still refuse transactions less than 1sat/vbyte for a while (until a large enough backlog of < 1sat/vbyte transactions develops, I should imagine). Maybe this time next year we could be celebrating even cheaper fees

[Coding Enthusiast]

It is so easy to broadcast your transaction, you don't even need a client
Just connect to a seed node IP and ask for a list of node IP addresses.
Take one of the addresses and open a socket over port 8333 and use that IP to connect to and say "hi" like this (you may want to change the IP in it but it doesn't matter because it is flexible):

Code:

f9beb4d976657273696f6e0000000000660000008a94bbe97f1101000d00000000000000131b805900000000010000000000000000000000000000000000ffff05ef60c22acf0d0000000000000000000000000000000000ffff23a7f609208df65ca61c4a15f201102f5361746f7368693a302e31342e312f374d070001

Then wait to hear "hi" and a "handshake" back. Then "shake" the hand like this:

Code:

f9beb4d976657261636b000000000000000000005df6e0e2

Now that the greeting is over you can start talking with that node. In your case you just wanna tell them about your transaction, so just do that:

Code:

f9beb4d9747800000000000000000000bd000000eae844bb0100000001d9c9f7d12419848477506c8ca09b47f55d6dd4ce8442a467b3cc78596405af211c0000006b483045022100e4feb502f883057194cb0f3dff802177036b52714c94852b6e6f0656a2adbe830220381b45ef1cf7c4937981c3a534364f7b0e7fa7e70de9cae2bc35b62104833043012102d2f573c371c17ae32225044fe2f7582a5ed5ae5835fe0408228f0149ee9a6a12ffffffff01a0860100000000001600146ca8c500e1894e369350c9b0f4f436adf007869500000000

Rejected? Try another IP.

This, although being correct steps, was posted just for fun. I may have made mistakes since I didn't use a code, I just made them by hand. If you are interested I can explain with more details.

[jackg]

It is so easy to broadcast your transaction, you don't even need a client
Just connect to a seed node IP and ask for a list of node IP addresses.
Take one of the addresses and open a socket over port 8333 and use that IP to connect to and say "hi" like this (you may want to change the IP in it but it doesn't matter because it is flexible):

Code:

f9beb4d976657273696f6e0000000000660000008a94bbe97f1101000d00000000000000131b805900000000010000000000000000000000000000000000ffff05ef60c22acf0d0000000000000000000000000000000000ffff23a7f609208df65ca61c4a15f201102f5361746f7368693a302e31342e312f374d070001

Then wait to hear "hi" and a "handshake" back. Then "shake" the hand like this:

Code:

f9beb4d976657261636b000000000000000000005df6e0e2

Now that the greeting is over you can start talking with that node. In your case you just wanna tell them about your transaction, so just do that:

Code:

f9beb4d9747800000000000000000000bd000000eae844bb0100000001d9c9f7d12419848477506c8ca09b47f55d6dd4ce8442a467b3cc78596405af211c0000006b483045022100e4feb502f883057194cb0f3dff802177036b52714c94852b6e6f0656a2adbe830220381b45ef1cf7c4937981c3a534364f7b0e7fa7e70de9cae2bc35b62104833043012102d2f573c371c17ae32225044fe2f7582a5ed5ae5835fe0408228f0149ee9a6a12ffffffff01a0860100000000001600146ca8c500e1894e369350c9b0f4f436adf007869500000000

Rejected? Try another IP.

This, although being correct steps, was posted just for fun. I may have made mistakes since I didn't use a code, I just made them by hand. If you are interested I can explain with more details.

I do have a node already running (not synced but still). It's an issue with broadcasting somewhow.
I used sendrawtransaction Hex_Signed_TX and it said there was a scriptpubkey error.
I'm not entirely sure if that code actually works but it looks quite funny anyway .

[Coding Enthusiast]

I'm not entirely sure if that code actually works but it looks quite funny anyway .

These are just bytes, think of it as another language between two computers talking to each other. This is what your bitcoin core node is doing in the background. It is sending and receiving thee messages to "communicate".
f9beb4d9 says start here.
76657273696f6e0000000000 says the type of message I am sending you is "version"
766572616b00000000000000 says the type of message I am sending you is "verak"
The rest is other information such as IP addresses, ports, latest block height you have,...
That's the "greeting" part.
747800000000000000000000 says the type of message I am sending you is a "tx"
The rest is the transaction itself.
https://bitcoin.org/en/developer-reference#p2p-network

[simo25]

I'm not entirely sure if that code actually works but it looks quite funny anyway .

These are just bytes, think of it as another language between two computers talking to each other. This is what your bitcoin core node is doing in the background. It is sending and receiving thee messages to "communicate".
f9beb4d9 says start here.
76657273696f6e0000000000 says the type of message I am sending you is "version"
766572616b00000000000000 says the type of message I am sending you is "verak"
The rest is other information such as IP addresses, ports, latest block height you have,...
That's the "greeting" part.
747800000000000000000000 says the type of message I am sending you is a "tx"
The rest is the transaction itself.
https://bitcoin.org/en/developer-reference#p2p-network

sorry but I did not find a new message button
https://coinomi.com/

guys I know I'm a little late, but if we want there was not 1 key-extraction terrestrial, then 1 part of the private keys pulled it out
automatically xapo from his wallet, instead the other I had on electrum, I have the doubt of having lost it, when I did also there late the extraction of private bitcoin cash keys, because once exported from bitcoin, the private keys to collect cash Btc, I did not trust and I created 1 other wallet on electrum, where I moved the traditional btc, about 2 months after the postfork bitcoin gold .. do you think I played there to redeem the bitcoin gold?
I have already tried to export the private keys from the old wallet almost empty with the bitcoins prefork, and tells me exporting it on app coinom that there are no funds : - \, do you think it went like this?