Author

Topic: CHECKLOCKTIMEVERIFY in P2SH (Read 1015 times)

jr. member
Activity: 41
Merit: 3
December 30, 2015, 12:49:37 AM
#8
Just curious... Why are you testing on mainnet instead of testnet?

I played with testnet before and it has the same problem of nodes not relaying nonstandard tx.

And you pay real BTC for testing on mainnet? Smiley

You should check and test everything on testnet first!


Yes I pay small amount of BTC in return of gained knowledge.
I found it harder to test on testnet anyway. or maybe I am just too lazy to retry....
legendary
Activity: 954
Merit: 1003
December 29, 2015, 06:02:53 PM
#7
Just curious... Why are you testing on mainnet instead of testnet?

I played with testnet before and it has the same problem of nodes not relaying nonstandard tx.

And you pay real BTC for testing on mainnet? Smiley

You should check and test everything on testnet first!
jr. member
Activity: 41
Merit: 3
December 23, 2015, 10:58:16 PM
#6
Just curious... Why are you testing on mainnet instead of testnet?

I played with testnet before and it has the same problem of nodes not relaying nonstandard tx.
legendary
Activity: 3472
Merit: 4801
December 23, 2015, 10:50:12 PM
#5
Just curious... Why are you testing on mainnet instead of testnet?
jr. member
Activity: 41
Merit: 3
December 23, 2015, 09:50:56 PM
#4
The nSequence field of the input looks like it is 0xffffffff. You will need to change that to something else otherwise the transaction will not be accepted. Resend the transaction but with the proper nSequence.

Hi knightdk, I have created another tx with different nsequence but I don't think it works https://blockchain.info/tx/b2bab79aeca10f2f65d28a83925ed06383850cf325adca0ef64602f6f824940e
It is still unconfirmed despite I locked it only until 389900
jr. member
Activity: 41
Merit: 3
December 23, 2015, 06:12:56 PM
#3
The nSequence field of the input looks like it is 0xffffffff. You will need to change that to something else otherwise the transaction will not be accepted. Resend the transaction but with the proper nSequence.

Do you mean nSequence field of the redeem tx?
staff
Activity: 3458
Merit: 6793
Just writing some code
December 23, 2015, 06:07:40 PM
#2
The nSequence field of the input looks like it is 0xffffffff. You will need to change that to something else otherwise the transaction will not be accepted. Resend the transaction but with the proper nSequence.
jr. member
Activity: 41
Merit: 3
December 23, 2015, 05:52:08 PM
#1
Hi all,

I tried to construct P2SH script utilizing CHECKLOCKTIMEVERIFY (BIP065) using the following skeleton
Quote
    IF
        SHA256 EQUALVERIFY
        CHECKSIG
    ELSE
        CHECKLOCKTIMEVERIFY DROP
        CHECKSIG
    ENDIF

The tx is here https://blockchain.info/tx/541ed46b7ec371524eeb08339fbf3b308ae4e6312beaceece884d6d2d8f7e702
And the redeem tx is here https://blockchain.info/tx/24a44ba982e4be2865c3c84fc408079871b49baa0d8a185ce45781228e8ae56e trying to redeem using the ELSE condition.
The problem is that the redeem tx has not been confirmed despite it has been around 10 hrs and it has a proper tx fee. I set the to 389820 whereas 389820 was the future block height, but it is now 389881 and the tx is not yet confirmed.

I wonder if there is something wrong with my txs. Thanks.
Jump to: