Author

Topic: Redeem coins from Time-locked address (Read 297 times)

legendary
Activity: 3682
Merit: 1580
July 05, 2018, 10:15:51 AM
#12
Salmen did you know coinb.in has testnet support: https://coinb.in/#settings

You can test hodl addresses on testnet instead. Electrum has testnet support so you can use that as well.
For Bitcoin testnet vast of the functions on Coinb.in are constrained and Electrum does not support redeeming time-locked address.

hodl addresses work on testnet. i speak from experience using coinb.in

as for electrum i mention it because in order to generate a hodl address you'll need to supply the public key of one of your legacy addresses, acquire testnet bitcoins from a faucet and then send those to the hodl address. for all that you can use an electrum testnet wallet. you're still going to have to use coinb.in to sign the transaction spending from the hodl address.
legendary
Activity: 1059
Merit: 1020
July 05, 2018, 10:14:15 AM
#11
Salmen did you know coinb.in has testnet support: https://coinb.in/#settings

You can test hodl addresses on testnet instead. Electrum has testnet support so you can use that as well.
For Bitcoin testnet vast of the functions on Coinb.in are constrained and Electrum does not support redeeming time-locked address.



The problem is this, your timestamp is 1745893229 which is equal to Tuesday 29th April 2025 02:20:29 AM UTC but saying that your transaction looks a bit broken in general.
can you tell me how you figure out the unlock time from the rawtx?
I only know by plugging the redeem script on verify page I can tell its unlock time

To be sure can I see the redeem script you have.
@OP if you are reluctant about telling us the redeem script, you can try it yourself
on coinb.in page, click Verify tab, input your redeem script, click submit
it will returns: Hodl Address, Required Signature, and its Unlock Time
Yes, I just added on the above, but here again: https://coinb.in/?verify=046079345bb17541046d37106834e29cc16fb64a6fed20a5ce9b7b4be9d64f2da69c2bedb3d9b103bda4be4a9fde5b3af85d61db74976c4cf01610e84279300f5f2071a8eb05ea808bac#verify

It looks like I was wrong about the timestamp I extracted. Thanks for confirming with the redeem script.

I think there is a bug in generating the transaction from your redeem script, not the signing procedure as such.

I'm looking into it and should it fixed in the next update which I'll push our in 24hrs or less.
I am glad to hear that. Yesterday, I was desperate with making the transaction through tools.
hero member
Activity: 714
Merit: 601
July 05, 2018, 10:02:50 AM
#10
Salmen did you know coinb.in has testnet support: https://coinb.in/#settings

You can test hodl addresses on testnet instead. Electrum has testnet support so you can use that as well.
For Bitcoin testnet vast of the functions on Coinb.in are constrained and Electrum does not support redeeming time-locked address.



The problem is this, your timestamp is 1745893229 which is equal to Tuesday 29th April 2025 02:20:29 AM UTC but saying that your transaction looks a bit broken in general.
can you tell me how you figure out the unlock time from the rawtx?
I only know by plugging the redeem script on verify page I can tell its unlock time

To be sure can I see the redeem script you have.
@OP if you are reluctant about telling us the redeem script, you can try it yourself
on coinb.in page, click Verify tab, input your redeem script, click submit
it will returns: Hodl Address, Required Signature, and its Unlock Time
Yes, I just added on the above, but here again: https://coinb.in/?verify=046079345bb17541046d37106834e29cc16fb64a6fed20a5ce9b7b4be9d64f2da69c2bedb3d9b103bda4be4a9fde5b3af85d61db74976c4cf01610e84279300f5f2071a8eb05ea808bac#verify

It looks like I was wrong about the timestamp I extracted. Thanks for confirming with the redeem script.

I think there is a bug in generating the transaction from your redeem script, not the signing procedure as such.

I'm looking into it and should it fixed in the next update which I'll push our in 24hrs or less.
legendary
Activity: 1059
Merit: 1020
July 05, 2018, 07:40:05 AM
#9
Salmen did you know coinb.in has testnet support: https://coinb.in/#settings

You can test hodl addresses on testnet instead. Electrum has testnet support so you can use that as well.
For Bitcoin testnet vast of the functions on Coinb.in are constrained and Electrum does not support redeeming time-locked address.



The problem is this, your timestamp is 1745893229 which is equal to Tuesday 29th April 2025 02:20:29 AM UTC but saying that your transaction looks a bit broken in general.
can you tell me how you figure out the unlock time from the rawtx?
I only know by plugging the redeem script on verify page I can tell its unlock time

To be sure can I see the redeem script you have.
@OP if you are reluctant about telling us the redeem script, you can try it yourself
on coinb.in page, click Verify tab, input your redeem script, click submit
it will returns: Hodl Address, Required Signature, and its Unlock Time
Yes, I just added on the above, but here again: https://coinb.in/?verify=046079345bb17541046d37106834e29cc16fb64a6fed20a5ce9b7b4be9d64f2da69c2bedb3d9b103bda4be4a9fde5b3af85d61db74976c4cf01610e84279300f5f2071a8eb05ea808bac#verify
hero member
Activity: 1232
Merit: 738
Mixing reinvented for your privacy | chipmixer.com
July 04, 2018, 06:27:27 PM
#8
The problem is this, your timestamp is 1745893229 which is equal to Tuesday 29th April 2025 02:20:29 AM UTC but saying that your transaction looks a bit broken in general.
can you tell me how you figure out the unlock time from the rawtx?
I only know by plugging the redeem script on verify page I can tell its unlock time

To be sure can I see the redeem script you have.
@OP if you are reluctant about telling us the redeem script, you can try it yourself
on coinb.in page, click Verify tab, input your redeem script, click submit
it will returns: Hodl Address, Required Signature, and its Unlock Time
legendary
Activity: 3682
Merit: 1580
July 04, 2018, 04:27:10 PM
#7
Salmen did you know coinb.in has testnet support: https://coinb.in/#settings

You can test hodl addresses on testnet instead. Electrum has testnet support so you can use that as well.
legendary
Activity: 1059
Merit: 1020
July 04, 2018, 11:30:31 AM
#6
I have been experiencing problems when I try to spend the outputs of this time-locked address: 36v4jJ8A3xCDteSrh7C2b5godwgMCsvqns.


First of all, I entered the redeem script of this time-locked address on Coinb.in and generated the unsigned transaction which I signed in the following.
I then broadcasted the signed transaction and received the following error: 16: mandatory-script-verify-flag-failed (Script evaluated without error but finished with a false/empty top stack element).


I am not fairly sure whether I missed something or there is an issue on coinb.in's side.

The transaction raw code is:
Code:
0100000001bbd220981879eeab38042b0630a04f99f54a37ad2d303e90f13eb76bd6886f51000000008b483045022100d4ba35ee2cbe1d24c82a88fc0eaeed8f13012c0b4febef4a32ffd042a12743150220187018b59741363d33fa3ca0f86daa3e9d14c0e75ab644a3c9e474cfc7ca96d70141046d37106834e29cc16fb64a6fed20a5ce9b7b4be9d64f2da69c2bedb3d9b103bda4be4a9fde5b3af85d61db74976c4cf01610e84279300f5f2071a8eb05ea808bffffffff0180bb00000000000017a914837b578229e3e15172f819dc4a43ecdb46a87e308700000000

It would be great if someone figures the problem.

The problem is this, your timestamp is 1745893229 which is equal to Tuesday 29th April 2025 02:20:29 AM UTC but saying that your transaction looks a bit broken in general.

Looks like you'll be got a bit of a hodl ahead.

To be sure can I see the redeem script you have.
Weird. I set the date for the 28th June 2018 at 8 o'clock as it can be seen here.
I tried half of the day with spending them.
hero member
Activity: 714
Merit: 601
July 04, 2018, 10:30:40 AM
#5
I have been experiencing problems when I try to spend the outputs of this time-locked address: 36v4jJ8A3xCDteSrh7C2b5godwgMCsvqns.


First of all, I entered the redeem script of this time-locked address on Coinb.in and generated the unsigned transaction which I signed in the following.
I then broadcasted the signed transaction and received the following error: 16: mandatory-script-verify-flag-failed (Script evaluated without error but finished with a false/empty top stack element).


I am not fairly sure whether I missed something or there is an issue on coinb.in's side.

The transaction raw code is:
Code:
0100000001bbd220981879eeab38042b0630a04f99f54a37ad2d303e90f13eb76bd6886f51000000008b483045022100d4ba35ee2cbe1d24c82a88fc0eaeed8f13012c0b4febef4a32ffd042a12743150220187018b59741363d33fa3ca0f86daa3e9d14c0e75ab644a3c9e474cfc7ca96d70141046d37106834e29cc16fb64a6fed20a5ce9b7b4be9d64f2da69c2bedb3d9b103bda4be4a9fde5b3af85d61db74976c4cf01610e84279300f5f2071a8eb05ea808bffffffff0180bb00000000000017a914837b578229e3e15172f819dc4a43ecdb46a87e308700000000

It would be great if someone figures the problem.

The problem is this, your timestamp is 1745893229 which is equal to Tuesday 29th April 2025 02:20:29 AM UTC but saying that your transaction looks a bit broken in general.

Looks like you'll be got a bit of a hodl ahead.

To be sure can I see the redeem script you have.
hero member
Activity: 714
Merit: 601
July 04, 2018, 10:22:35 AM
#4
That error means that the signature is invalid. coinb.in has, for quite a while now, been known to have issues with their signer which results in invalid signatures.

Looking at the transaction, it is actually incomplete. It is completely missing the redeemScript.

Excuse me, but I'm the lead developer of coinbin and I'm unaware of any issues. Please provide proof of claim. Thanks.
legendary
Activity: 1059
Merit: 1020
July 04, 2018, 06:00:12 AM
#3
That error means that the signature is invalid. coinb.in has, for quite a while now, been known to have issues with their signer which results in invalid signatures.

Looking at the transaction, it is actually incomplete. It is completely missing the redeemScript.
I thought so. I have tried using Bitcoin Core to build the transaction.
First, I created the unsigned transaction using this command.

Code:
createrawtransaction '[{"txid":"516f88d66bb73ef1903e302dad374af5994fa030062b0438abee79189820d2bb", "vout":0}]' '{"3DgECca9xyBAvEcwrtF5QnS5HkEGxxa81y":0.00048}' 1530172800

Then I signed it with the private key using this:

Code:
signrawtransaction "0200000001bbd220981879eeab38042b0630a04f99f54a37ad2d303e90f13eb76bd6886f510000000000feffffff0180bb00000000000017a914837b578229e3e15172f819dc4a43ecdb46a87e30878095345b" '[{"txid":"516f88d66bb73ef1903e302dad374af5994fa030062b0438abee79189820d2bb","vout":0,"scriptPubKey":"a914395060fa01753cb19684415f6720d7bdb9b689e487","redeemScript":"046079345bb17541046d37106834e29cc16fb64a6fed20a5ce9b7b4be9d64f2da69c2bedb3d9b103bda4be4a9fde5b3af85d61db74976c4cf01610e84279300f5f2071a8eb05ea808bac", "amount": 0.00048}]' [...]

And received the following error: Unable to sign input, invalid stack size (possibly missing key)
staff
Activity: 3458
Merit: 6793
Just writing some code
July 03, 2018, 07:10:33 PM
#2
That error means that the signature is invalid. coinb.in has, for quite a while now, been known to have issues with their signer which results in invalid signatures.

Looking at the transaction, it is actually incomplete. It is completely missing the redeemScript.
legendary
Activity: 1059
Merit: 1020
July 03, 2018, 04:52:08 PM
#1
I have been experiencing problems when I try to spend the outputs of this time-locked address: 36v4jJ8A3xCDteSrh7C2b5godwgMCsvqns.


First of all, I entered the redeem script of this time-locked address on Coinb.in and generated the unsigned transaction which I signed in the following.
I then broadcasted the signed transaction and received the following error: 16: mandatory-script-verify-flag-failed (Script evaluated without error but finished with a false/empty top stack element).


I am not fairly sure whether I missed something or there is an issue on coinb.in's side.

The transaction raw code is:
Code:
0100000001bbd220981879eeab38042b0630a04f99f54a37ad2d303e90f13eb76bd6886f51000000008b483045022100d4ba35ee2cbe1d24c82a88fc0eaeed8f13012c0b4febef4a32ffd042a12743150220187018b59741363d33fa3ca0f86daa3e9d14c0e75ab644a3c9e474cfc7ca96d70141046d37106834e29cc16fb64a6fed20a5ce9b7b4be9d64f2da69c2bedb3d9b103bda4be4a9fde5b3af85d61db74976c4cf01610e84279300f5f2071a8eb05ea808bffffffff0180bb00000000000017a914837b578229e3e15172f819dc4a43ecdb46a87e308700000000

It would be great if someone figures the problem.
Jump to: