Problem with nLocktime?

[yakuza699]

Hello all, so i recently tried to do a delayed (locked) transaction and here is what i got

Code:

{
    "hash": "eb8f2e3bbdf9a16f1dcc863aae6d2cbdbc1024d44ba1420627036e699b9a4c6f",
    "ver": 1,
    "vin_sz": 2,
    "vout_sz": 2,
    "lock_time": 302900,
    "size": 375,
    "in": [
        {
            "prev_out": {
                "hash": "1b4d46059f20525baa9d8880a82f5e27d4d77de788faa713a362caf07ab9636d",
                "n": "1"
            },
            "scriptSig": "3046022100dad23a57bb5419d25331e6a7fd9297408e490edb0044e4d2807e0f49b3a0d94d022100d9d20788ce70388e96fc8c74fabcb6b6f711d3a783674757726a73bf3b31bcab01 0204cd1c526d46d34e7869211cf857541a94b026028fd571a6bd3004e66ee75696",
            "sequence": 302900
        },
        {
            "prev_out": {
                "hash": "dc4cfb20407046982cdbb305f746f685f85e7341d8ff7fbf15193ffbb5084c6d",
                "n": "1"
            },
            "scriptSig": "30450221009deb7676c1ba3c504349d404bc5143ad338bbd84d393f22b8db7bc5e276e5e2c02207a97f752cf4656e1286101b2ec3006a10c3df526290f1ecf96a25e187360b2a501 0204cd1c526d46d34e7869211cf857541a94b026028fd571a6bd3004e66ee75696",
            "sequence": 4294967295
        }
    ],
    "out": [
        {
            "value": "0.01000000",
            "scriptPubKey": "OP_DUP OP_HASH160 e0e8fbb1befe6c0a5b1ce82f613f171bbfbc4651 OP_EQUALVERIFY OP_CHECKSIG"
        },
        {
            "value": "0.04821340",
            "scriptPubKey": "OP_DUP OP_HASH160 01103eaf645bcec3ed2ee2fb61a56ca406c10334 OP_EQUALVERIFY OP_CHECKSIG"
        }
    ]

But then i tried to push it on blockchain.info/pushtx it said ''Invalid Sequence Number302900'' what should i do to get around this or am i doing something wrong? What else should i do for my coins getting in the chain but being locked till the xx block?

Best regards,
yakuza699

[1538088559]

1538088559

[1538088559]

1538088559

[1538088559]

1538088559

[1538088559]

1538088559

[DeathAndTaxes]

Transactions are not standard if the nlocktime is a block height in the future.  The tx is valid but not standard node will accept or relay it.  This is DDOS prevention mechanism.  You will need to wait until after the nlocktime has passed before you can broadcast the transaction.

[yakuza699]

Transactions are not standard if the nlocktime is a block height in the future.  The tx is valid but not standard node will accept or relay it.  This is DDOS prevention mechanism.  You will need to wait until after the nlocktime has passed before you can broadcast the transaction.

Then there is no use of nLocktime it would be the same as sending the simple transaction.

[DeathAndTaxes]

Transactions are not standard if the nlocktime is a block height in the future.  The tx is valid but not standard node will accept or relay it.  This is DDOS prevention mechanism.  You will need to wait until after the nlocktime has passed before you can broadcast the transaction.

Then there is no use of nLocktime it would be the same as sending the simple transaction.

Of course there is you can create the tx just not broadcast it.  Nothing requires you to broadcast the tx on the network early.  You could send the signed tx to the recipient directly and they could broadcast it once the lock time has past.

[yakuza699]

Transactions are not standard if the nlocktime is a block height in the future.  The tx is valid but not standard node will accept or relay it.  This is DDOS prevention mechanism.  You will need to wait until after the nlocktime has passed before you can broadcast the transaction.

Then there is no use of nLocktime it would be the same as sending the simple transaction.

Of course there is you can create the tx just not broadcast it.  Nothing requires you to broadcast the tx on the network early.  You could send the signed tx to the recipient directly and they could broadcast it once the lock time has past.

Hey DeathAndTaxes why you don't respond to my pm's?