Thanks for pointing this out. Will have it fixed asap.

Coinb.in's fee estimation has stopped working. Look at the block height. It shows that #590168 is the latest block, but it was mined 12 days ago.

Tell me please, is this version obsolete? https://github.com/coinbin/coinbin
Does this version have a relationship to official repotory?

No commits since 2014, A beta version and it says it was made by OutCast3k.

It's possible that it was by OP and then he changed the repository because apparently, the first version released on the new repository is 1.1 while the link you're referring to is 1.0.

I don't see why you would use something unstable and that might have bugs though. So If you're planning to do that, make sure to check the source code and not just run it as well, just to be sure that it doesn't contain anything malicious.

My conclusion came based on two things:

1. The current repository has version 1.1 as the first release which means that 1.0 might have been somewhere else (in the link you gave).

2. Whoever posted that release wanted to give credit to OutCast3k. I don't this is likely because coinb.in was not famous back then, so someone hosting something for phishing people is unlikely.

Either way though, I wouldn't suggest using it even If it was from the original creator, because it might contain a lot of bugs.

For Bitcoin testnet vast of the functions on Coinb.in are constrained and Electrum does not support redeeming time-locked address.



Yes, I just added on the above, but here again: https://coinb.in/?verify=046079345bb17541046d37106834e29cc16fb64a6fed20a5ce9b7b4be9d64f2da69c2bedb3d9b103bda4be4a9fde5b3af85d61db74976c4cf01610e84279300f5f2071a8eb05ea808bac#verify

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:

It would be great if someone figures the problem.

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.

[Spam][Spam][Spam][Spam]

-- snip --

After some further research, I discovered that someone else other than coinb.in may have had access to a private key.
I will update here once I compile some proof and reveal the identity of the scam artist. Sorry if my original post implied that coinb.in was the perp as it doesn't seem very likely anymore.  

Ok, I finally got HODL txs to work using your link to https://github.com/globaltoken/coinbin/commit/88f5eee6ad9114feb70c523ca7c834d99c106476

I had to change one line of code in coin.js though (line 1024 in my notebook editor after running https://dirtymarkup.com on it):


to this


I also had to push the tx elsewhere as the broadcast function failed for me.

These are minor bugs compared to the next one though.

I decided to create a tx for a large amount of BCC. I set everything up. Then I went offline to get my private key to sign it and discovered I can't sign offline. So I canceled the tx, and did some experiments.

It seems that if I try to sign while offline, I get an error message due to our javascript trying to reload the inputs during the signing. Specifically in r.getinputvalues routine. It will sign fine if I then go back online though (changing nothing else).

I don't remember this being a problem when signing a Hodl tx with Bitcoin offline when I originally tested it.

This seems like a major security breach to me. I have gone over the code as much as I can and while I don't see the private key being stolen, I am not a professional programmer either (I panhandle for a living - make about $5/hour) so something could be hidden in an obscure area from me.

Unfortunately, I don't think this can be easily fixed without rewriting a lot of code. I know it would take me months. I will probably just sign the large transaction and immediately broadcast it. My coins are still locked up for another 3 years though. Plenty of time to think about it though.

I just hope they don't use replay protection again during the Seg1X|Seg2X fork. What a f*cking mess.

I locked a bunch of Bitcoins before the fork to BTC and BCC. So was wondering if the coins would be recoverable on the BCC fork. So decided to experiment.

Created a time locked address using address: 12Cp73Mbb4PEXmDjYitGcfgPDpRRvPPxpS,
Public Key: 04882490aac1fb4de17bcd7c70c72672d291d3cbce869834dee98452a98874766ef996adec88b74 98dfb3fd3141fb3af5fa020746ceb8f11d5ee4e35d26284f7e4
Time: 09/13/2017 01:00

Resulting Address: 3BQyYQS3vSdjYHNJK8ogyo5Z3NkmzxWrr3
Resulting Redeem Script:
04b00fb959b1754104882490aac1fb4de17bcd7c70c72672d291d3cbce869834dee98452a988747 66ef996adec88b7498dfb3fd3141fb3af5fa020746ceb8f11d5ee4e35d26284f7e4ac

Sent 0.001 BCC to that address, TX=
76f21028ebdeff0c2347ae00ada70d3c32cfdf8a38178b2a032f2a030ce420e4

To create a tx, I had to manually input everything, resulting in the following script:
0100000001e420e40c032a2f032a8b17388adfcf323c0da7ad00ae47230cffdeeb2810f27600000 0004a04b00fb959b1754104882490aac1fb4de17bcd7c70c72672d291d3cbce869834dee98452a9 8874766ef996adec88b7498dfb3fd3141fb3af5fa020746ceb8f11d5ee4e35d26284f7e4ac00000 00001905f0100000000001976a9140b0f1dc4fce32f2d38bdbf822c2222d1870b999a88acb00fb9 59

Signed with private key to 12Cp73Mbb4PEXmDjYitGcfgPDpRRvPPxpS:

0100000001e420e40c032a2f032a8b17388adfcf323c0da7ad00ae47230cffdeeb2810f27600000 00094483045022100fa78e56b7ec881f8bb2eb97ea9825856ecd06941dea3ac74092d663b721379 8b02207824e621b4ee21df7591a1e8f45a45b162e5ea39cd073b70bcabc6501f7683e3014a04b00 fb959b1754104882490aac1fb4de17bcd7c70c72672d291d3cbce869834dee98452a98874766ef9 96adec88b7498dfb3fd3141fb3af5fa020746ceb8f11d5ee4e35d26284f7e4ac0000000001905f0 100000000001976a9140b0f1dc4fce32f2d38bdbf822c2222d1870b999a88acb00fb959

Tried to push at http://blockdozer.com/insight/tx/send

Resulting in the following:

An error occured:
64: non-mandatory-script-verify-flag (Signature must use SIGHASH_FORKID). Code:-26

Having some problem with this wallet. Two weeks ago deposited coions to my wallet then later logged in and there was nothing, new btc address and zero funds. Contacted support via email and no response, sent a message here to OutCast3k(one of the developers as I see) and no response. Is this project just a scam right now or what? Any chance to get my coins back?  

Thanks! I was actually just now messing around with it before reading your comment and I got it figured out! Yay, took a min but I got it. lol. Thank you though!
Coinb.in is awesome!

Will still send ya a reward though if ya want