bitcoind – Bitcoin TX decoding failed while sending to a network (retest)

I have manually created a signature (referring to the signature output formats in Bitcoin CLI). But I tried to send the same thing to the network that I get

Error code: -22

Error message:

TX decoding failed

Below is the signed tx

signed tx:


Splitting the same signed transmitter:

02 00 00 00 // Version

01 // number of inputs (var_uint)

38 c0 59 ad fe 41 e8 0f b4 6e 14 d2 39 49 30 43 43 from c5 60 a6 fb ce f4 b2 e3

11 0f 82 41 81 6d // Enter transaction hash

00 00 00 00 00 // Enter index

2c // size of the script (var_uint)

2b // Data must be pushed The files under 43 bytes are pushed

07 // Press 7 bytes to stack

68 61 6e 75 6d 61 6e // Data must be pushed

a8 // OP_HASH256

Press 20 // 32 bytes

1c a3 58 97 54 0e c7 ae 72 94 a8 ca cd 11 ca f2 c0 9f 95 f0 26 c9 25 c6 ce 4e

4c 29 b2 0e 3c 41

87 // OP_EQUAL

ff ff ff // Sequence

02 // no vouts

80 50 74 01 00 00 00 00 // Amount

19 // Size of the script (var_uint)

76 // OP_DUP

a9 // OP_HAH160

14 // 20 bytes have to be pushed

6a 3f fa dd da e4 cc b4 22 3a 8c 72 15 d4 b4 81 da f6 96 77



00 d0 12 13 00 00 00 00 // Amount

17 // Size of the script (var_uint)

a9 // OP_HASH160

14 // 20 bytes have to be pushed

DE f3 47 cf 3b 01 bf 03 a3 0d 7e e9 f6 2d 86 ed 51 09 b5 47

87 // OP_EQUAL

00000000 // lock time

Can someone help me find out what I miss?

dlp – Solution to block the sending of emails to domains with typos

I am trying to find a solution to block the sending of emails to domains with typos, e.g. or

I work for an O365-based customer who wants to make sure the typo is appropriate for some specific domains for which he shares private information via email so he does not send any important information to a catchall mailbox on a parked domain.

Suggestions are welcome.


design – What is the purpose of event sourcing and asynchronous message queues for sending commands?

So what's the use of keeping events as a sequence if we're not sure about their order?

Well, we are sure about the order of events – they are sorted in the order in which they are writtenThis is determined by the order in which the instructions finish processing. (If you use a single command handler, this is the order in which the commands arrive at the handler.)

The asynchronous message queue can be used to transmit messages to a (currently) unavailable recipient. The queue itself is a plumber with higher availability because we do not need to constantly change it for business reasons.

Since commands may be out of service, the receiver's logic must cover this contingency (assuming it is important to the business). Basically, distributed messaging means that you never know if you have received all the messages that you will eventually receive. At some point you have to guess that you have all the news or are paralyzed forever in idleness.

Think of e-mail. You will receive an e-mail from Bob, you will act accordingly and later you will receive an e-mail from Alice, who has sent it earlier as Bob's mail, but hers was delayed somewhere. What now? Go as well as you can and continue.

See also Race Conditions Don & # 39; t Exist.

Are there cryptocurrencies that do not use Bitcoin source code and support sending to multiple addresses in a single transaction with a good market capitalization?

ether; nem; ripple; Eos; Omni; Stellar; Iota; While many of them bring features, Bitcoin will never support them. Neither of them support sending to multiple people within a single transaction, at least not without the use of Multisig or a Smart Contract.

Are there crypto-currencies or tokens that are not based on Bitcoin source code and that support multi-address sending in a single transaction that exists in the top 100 coinmarketcap?

Java – Error sending information to the server with retrofit

I'm developing an Android application that uses retrofit to send and receive data from the server. The problem is when sending user and password. It worked fine before the AES-GCM encryption was introduced in the app. Without the encryption of the user and the password, the retrofit sends and retrieves everything normally. If cryptography is used, the following exception is thrown: End of input in row 1, column 1, (Note: Base64 is also used with SafeURL.)

I initially thought that the problem is in the characters, I thought that a character confused the address of the URL and the server could not query the database correctly, but I saved the encrypted values ​​directly into the variables (without going through the encryption algorithm directly ) The retrofit usually worked like this.

Then I thought the problem might have been on the server. My web service is scheduled in PHP. I continue to check the characters of the encrypted string and paste them directly into the URL of the server. This works normally again. The json with the data is printed and displayed on the screen.

I do not know what to do, my intuition points to a mistake in the method Base64 I use:

userEncripted = Base64.encodeToString (UserEncriptedByte, Base64.URL_SAFE);
Encrypted password = Base64.encodeToString (PasswordEncriptByte, Base64.URL_SAFE);

Another suspicion I have is a limitation of retrofitting.

If you need the code, just talk. Thanks in advance.

Desktop application – users who forgot to regenerate PDF before sending

It sounds like you have a decision to make: Maintain a folder of PDF files that users can access directly or not?

If this is not the case, and this is an example of users discovering an inadvertent link to your planned workflow, I would suggest that you do not allow this to users. Use a different file format, save your PDF files in an archive, and change the extension so that they do not "look" like PDF files. Users can complain, but they'll get over it and their workflow will adjust.

If you do If you want to manage a folder of PDF files for these users, you should use a background thread that deletes the old PDF file and creates the new one as soon as an invoice is updated. That way, the app does not have to freeze for a few seconds if it changes anything. That way, you can get rid of the Show / Save button if you want, since the folder is now the authoritative source. If you want to keep the Show / Save button, you can also deploy the PDF directly from the * folder instead of having to create a new PDF file for an unchanged invoice every time the user clicks the button.

* (Note that you probably want some security that prevents users from modifying PDF files in the folder, for example, to save the MD5 hash of the file.)

NOTE: I assume that the PDF Files folder is part of your app, not just an example of a folder where your users may save downloaded documents. If that's it If this is the case, you have a classic document management problem … SharePoint and colleagues take care of it every day. You may want to investigate how they handle it, but I'm not aware of a good and unobtrusive solution.

Desktop application – users forget to regenerate PDF before sending

My company has developed ERP software for small businesses, and there are always problems.

The Invoices section of the app has a View / Print button that exports the invoice to a PDF file. The problem is that users more often than desired change a setting in the invoice, or add a product or actually change something, and then open the PDF Files folder and retrieve the invoice PDF file to send. Note that they did not click the Show / Print button, so the PDF file was not regenerated and therefore is not up to date.

We can not prevent the user from accessing the PDF Files folder because they may want to copy the PDF file to a USB flash drive. The only possible solution that we have considered is to regenerate the PDF file each time something is changed for the bill really slows the app down, as generating the PDF file can take up to 1 or 2 seconds can take if the bill contains many lines.

We have repeatedly tried to tell users that they are PDF files Not They are automatically generated and need to click on Show / Print to regenerate it. However, they always forget and then call over the phone that the PDF files are outdated.

What would be the best way to solve this problem?

Note: Invoice is a loose translation of French, according to Google Translate "Invoice" would work too. I am only talking about a document containing a list of the products ordered by the customer and the total amount to be paid

sending failed

Consider the following (does not mind if the registration is disabled …):

submit failed = inurl: Registration disabled
Sending attempt failed = registration is disabled <

1.SER visits the URL, in the log you can see:
registration failed (inurl: registration disabled)
2. SER is still trying to send 4 times due to "Resend Error".
registration failed (inurl: registration disabled)
registration failed (inurl: registration disabled)
registration failed (inurl: registration disabled)
registration failed (inurl: registration disabled)

Even if we told SER that the sending failed (what should be the priority and stop the sending?), Continue to post SER because it found "resend error".

What do you think?