Quote from: amaclin on July 07, 2016, 04:54:30 AM

Quote from: Quickseller on July 07, 2016, 12:21:21 AM

I am fairly certain that you are playing stupid and that you know exactly why your transactions are not confirming.

1) What does 'stupid' means? (Sorry, google translate gives me very strange results)

You are pretending to not know the answer to your question.

Quote from: amaclin on July 07, 2016, 04:54:30 AM

2) Yes, I know.
But I have a right to ask about it.
And I want to give you some knowledge.
I am asking "What can I do to confirm them into blocks?"
I am not asking "Why these transactions are unconfirmed?"

Okay, give me some knowledge.

If my assumption that one (or more) of the parent transactions that sent btc to 14iDe9xhqYh76TRHRHiaWWPdniyaEHhYjj either is nonstandard or break consensus rules, and based on your history I think I this is a good assumption, then you will need to change the consensus rules

It looks like you might have "forgotten" to sign f65d87013d8965128e0b6f304cf87480694b7622947b9c3a1c08c834befb5b45 with your multisig addresses.

Quote from: amaclin on July 07, 2016, 04:54:30 AM

Quote

I am fairly certain that you intentionally created an invalid transaction that will never confirm
that some block explorers (including blockchain.info) treats as valid.

I am fairly certain that Satoshi Nakamoto intentionally created an 'financial system' that will never success
that some people treats as revolutionary technology.
Go on.

What is your point? Also this is off topic here.

Quote from: amaclin on July 07, 2016, 04:54:30 AM

Quote

The transaction in question that needs to get confirmed is 519a70ba4ac00303a97bedfd82bec31f288773a16603f57ced0f8b7522e5e32d, and no I will not get it confirmed for you.

It is confirmed. Go on.

Okay I was wrong about which transaction was invalid, and depending on how complex that p2sh inputs are, I may still be wrong.

The rawtx for f65d87013d8965128e0b6f304cf87480694b7622947b9c3a1c08c834befb5b45 is:

Code:

01000000068667fcbe3378dca9b5120485540d718d12ebf5a6851d83bfbde61d560ff01b9e0200000069463043022030c8007933d78b9fc7274f983de07325226dffc416fdb8f81b9561bdde1a8b9a021f73048fdaf0a43a27e12e5eb2ab90123ad05faadeb278722482f8b7c866d3cc0121033d8cb6f0e3c227a2c99eb86ef54fb3fcab33e68f5d9a427a1eb796d7bb6ac350ffffffff2de3e522758b0fed7cf50366a17387281fc3be82fded7ba90303c04aba709a5100000000035101b2ffffffff328685b0352c981d3d451b471ae3bfc78b82565dc2a54049a81af273f0a9fd9c010000000b0009630330472d5fae685bffffffff328685b0352c981d3d451b471ae3bfc78b82565dc2a54049a81af273f0a9fd9c020000000b0009630359646d5fae6858ffffffff328685b0352c981d3d451b471ae3bfc78b82565dc2a54049a81af273f0a9fd9c030000000b000963034bd4715fae6854ffffffff328685b0352c981d3d451b471ae3bfc78b82565dc2a54049a81af273f0a9fd9c040000000b000963036de8705fae6860ffffffff0220a10700000000001976a91428b3fbcea21c43586d2ba016881475f36be1f30f88ac4cac2702000000001976a9140a95414e29781511c4449a0b191a65aed0143c5f88ac00000000

and when I try to decode this with both electrum and coinb.in, I receive messages saying that the transaction is not signed (is partially signed)