Quote from: abadon666999 on Today at 02:17:29 PM

i have read that poolin pool have broadcast in the past...non standard tx with hight fees as compensation

Yours is actually standard in the current protocol but your nLocktime isn't less than the LOCKTIME_THRESHOLD which made it "lock-by-blockheight".
So you'll have to wait for block height 7140000 or the Bitcoins locked in that script cannot be spent.

It's a different scenario this time since they do not have to change anything in Bitcoin to include the "uncompressed SegWit" transaction in their block.
All they had to do is accept that said transaction to their mempool to be mined.

Only miners with nodes before BIP-65 implementation may consider your transaction non-standard but valid;
But AFAIK (CMIIAW), the block will be rejected by new nodes.

Quote from: LoyceV on Today at 03:02:45 PM

Option 1: whoever has access to 39QWbnkbcPFcrJFEB6yvVDc12eX5zqVt3y can create a new transaction.

Unfortunately, the 7140000 locktime isn't the transaction's locktime but the locking script's.

For reference, here's the input's Redeem Script:

Code:

7140000 OP_CHECKLOCKTIMEVERIFY OP_DROP <PubKey> OP_CHECKSIG