Pages:
Author

Topic: [coinb.in] Open Source, Multi Signature, HD Wallet, SegWit/Bech32 and more! - page 6. (Read 74837 times)

hero member
Activity: 528
Merit: 527
So, does that mean that we can't recover our BCH from time-locked addresses funded before the fork? I got one that will be available next saturday and I woudn't mind a few extra Bitcoins. Is there is any ETA?

We can recover BCH, but apparently we will have to sign the transaction while online, so not 100% secure.

It would be possible to rewrite the code to allow offline signing, but I don't think anyone will be motivated enough to do that.
legendary
Activity: 2758
Merit: 6830
So, does that mean that we can't recover our BCH from time-locked addresses funded before the fork? I got one that will be available next saturday and I woudn't mind a few extra Bitcoins. Is there is any ETA?
hero member
Activity: 714
Merit: 601
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):

Code:
} else if (utxo_script['type'] == 'multisig') {

to this

Code:
} else if ( (utxo_script['type'] == 'multisig') || (utxo_script['type'] == 'hodl')) {

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'm going from memory here and I've not paid tooo much attention to bitcoin cash, but I believe their new routine to generate a transaction hash includes the value of each input where as the legacy version doesn't.
hero member
Activity: 528
Merit: 527
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):

Code:
} else if (utxo_script['type'] == 'multisig') {

to this

Code:
} else if ( (utxo_script['type'] == 'multisig') || (utxo_script['type'] == 'hodl')) {

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) 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.

hero member
Activity: 714
Merit: 601
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

Bitcoin cash and bitcoin do not use the same sighashes as a method of replay protection. This means transactions built for the bitcoin network can't be broadcasted to the bcash network with out an update to the signing procedure.

There is a bitcoin cash pull request on the github repo, which I've not accepted but it does work (I choose to support segwit right now over bcash) You can download it and use it to create transactions for the bcash network.
hero member
Activity: 714
Merit: 601
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?  Tongue

It's an open source project, nobody here has paid anything, we are not a company, if there is a delay in responding it's because we are not heavily funded and there is 1 developer responding to multiple enquiries.

Firstly, I will point out the obvious. We do not have access to your private keys. If for some unfortunate reason our API is struggling to return the correct balance you can import your API key into another wallet.

Secondly, you have provided no information to go on. No email address, no github ticket, no bitcoin address to check a balance.

Finally I don't like helping people who call this project a scam. It's rude, you've contributed nothing, paid nothing and have the audacity to post that.


Edit to add: coinb.in's wallet feature works by generating a set of keys from the login details you give it. Please pay close attention to the login notice in yellow. It states different login combinations will open up different addresses. For example, I could login with the email address [email protected] and the password 1111111111 and receive one address, log back out and log back in the with same email address but a different password 222222222 and get an entirely different address. If the address has changed and your balance is zero, it's because you are not entering in the same details as before. Please don't come here and publicly call this project a scam when you clearly have no idea.
newbie
Activity: 1
Merit: 0
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?  Tongue
hero member
Activity: 528
Merit: 527
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
sr. member
Activity: 860
Merit: 423

As much as I personally do not support the bitcoin cash hard fork, allowing users to dump it is probably a good thing.

I am reviewing and testing this pull request, but I am also aware that there are a few very minor issues in this pull request, which leaves me wondering if they should be fixed before or after.

Faster it is done, better it is.
hero member
Activity: 714
Merit: 601
Hey there!

I think you should look again, of course coinb.in allows custom fees, it just appears you don't understand how fees work.

As you stated, what is not sent is used as a fee, this is how the Bitcoin protocol works, what is not spent is used as a transaction fee - it's simple. To avoid this, you create a second "change" address where you spend the change back to your own address, thus lowering fees.

For more information on fees and "change addresses"  please see https://en.bitcoin.it/wiki/Change and https://en.bitcoin.it/wiki/Transaction_fees

Please remember coinb.in is meant for advanced users who understand the bitcoin protocol and whilst I don't want to discourage you or anyone else from experimenting with this project and increasing your understanding, you should be extra careful as you clearly aren't fimilar with the protocol as you have shown by your lack of understanding and complaining.

All the best.
You are right and electrum wallet automatically add my address to the tx as change address and in coinb.in we need to do it manually now i understand.It would be great option to have this in coinbin wallet too so we don't have to manually enter the change address our own sending address should be set by default to change address but i understand you if it's meant for advanced users.

Unfortunately it is not possible to easily predict the users change address with total accuracy in this wallet due to the way it's designed, the best method in this scenario is to let the user choose.
member
Activity: 108
Merit: 10
Hey there!

I think you should look again, of course coinb.in allows custom fees, it just appears you don't understand how fees work.

As you stated, what is not sent is used as a fee, this is how the Bitcoin protocol works, what is not spent is used as a transaction fee - it's simple. To avoid this, you create a second "change" address where you spend the change back to your own address, thus lowering fees.

For more information on fees and "change addresses"  please see https://en.bitcoin.it/wiki/Change and https://en.bitcoin.it/wiki/Transaction_fees

Please remember coinb.in is meant for advanced users who understand the bitcoin protocol and whilst I don't want to discourage you or anyone else from experimenting with this project and increasing your understanding, you should be extra careful as you clearly aren't fimilar with the protocol as you have shown by your lack of understanding and complaining.

All the best.
You are right and electrum wallet automatically add my address to the tx as change address and in coinb.in we need to do it manually now i understand.It would be great option to have this in coinbin wallet too so we don't have to manually enter the change address our own sending address should be set by default to change address but i understand you if it's meant for advanced users.
hero member
Activity: 714
Merit: 601
OP deleted my post i don't know why he did this to may be prevent the truth Op you don't believe in open communication?
this wallet has some problems i signed tx offline using my private key and it said signed but showed the same unsigned tx in the box.weird.unisgned tx was of electrum wallet and it was RBF tx.I hope this time you reply me and don't delete this post.

Sorry it was an accidental delete and was in the process of messaging you about this. You can go through this thread and github and see I don't delete bad feedback.

In truth your complaint is about electrum, its is an issue that's been know about for a while, it likely won't be fixed because we handle data within the transaction in a slightly different way, although I am making presumptions here and will happily inspect your transactions to be sure. What I suggest is; instead of building a transaction using electrum and complaining that this software doesn't sign it properly, you try building and signing a transaction using only coinb.in.

Please keep us updated. Thanks.

*Edited to clarify*
I tried with coinb.in wallet first but the thing is your wallet does not allow to set custom fees.It stated what is not sent will be used as transaction fees and i had to set custom fees so i created an unsigned tx with electrum wallet RBF enabled and then wrote the unsigned hash in coinb.in offline wallet and used my private key to sign it and it stated signed but showed the same unsigned tx in box.why coinb.in wallet does not allow custom fees?

Hey there!

I think you should look again, of course coinb.in allows custom fees, it just appears you don't understand how fees work.

As you stated, what is not sent is used as a fee, this is how the Bitcoin protocol works, what is not spent is used as a transaction fee - it's simple. To avoid this, you create a second "change" address where you spend the change back to your own address, thus lowering fees.

For more information on fees and "change addresses"  please see https://en.bitcoin.it/wiki/Change and https://en.bitcoin.it/wiki/Transaction_fees

Please remember coinb.in is meant for advanced users who understand the bitcoin protocol and whilst I don't want to discourage you or anyone else from experimenting with this project and increasing your understanding, you should be extra careful as you clearly aren't fimilar with the protocol as you have shown by your lack of understanding and complaining.

All the best.
member
Activity: 108
Merit: 10
OP deleted my post i don't know why he did this to may be prevent the truth Op you don't believe in open communication?
this wallet has some problems i signed tx offline using my private key and it said signed but showed the same unsigned tx in the box.weird.unisgned tx was of electrum wallet and it was RBF tx.I hope this time you reply me and don't delete this post.

Sorry it was an accidental delete and was in the process of messaging you about this. You can go through this thread and github and see I don't delete bad feedback.

In truth your complaint is about electrum, its is an issue that's been know about for a while, it likely won't be fixed because we handle data within the transaction in a slightly different way, although I am making presumptions here and will happily inspect your transactions to be sure. What I suggest is; instead of building a transaction using electrum and complaining that this software doesn't sign it properly, you try building and signing a transaction using only coinb.in.

Please keep us updated. Thanks.

*Edited to clarify*
I tried with coinb.in wallet first but the thing is your wallet does not allow to set custom fees.It stated what is not sent will be used as transaction fees and i had to set custom fees so i created an unsigned tx with electrum wallet RBF enabled and then wrote the unsigned hash in coinb.in offline wallet and used my private key to sign it and it stated signed but showed the same unsigned tx in box.why coinb.in wallet does not allow custom fees?
hero member
Activity: 714
Merit: 601
OP deleted my post i don't know why he did this to may be prevent the truth Op you don't believe in open communication?
this wallet has some problems i signed tx offline using my private key and it said signed but showed the same unsigned tx in the box.weird.unisgned tx was of electrum wallet and it was RBF tx.I hope this time you reply me and don't delete this post.

Sorry it was an accidental delete and was in the process of messaging you about this. You can go through this thread and github and see I don't delete bad feedback.

In truth your complaint is about electrum, its is an issue that's been know about for a while, it likely won't be fixed because we handle data within the transaction in a slightly different way, although I am making presumptions here and will happily inspect your transactions to be sure. What I suggest is; instead of building a transaction using electrum and complaining that this software doesn't sign it properly, you try building and signing a transaction using only coinb.in.

Please keep us updated. Thanks.

*Edited to clarify*
member
Activity: 108
Merit: 10
OP deleted my post i don't know why he did this to may be prevent the truth Op you don't believe in open communication?
this wallet has some problems i signed tx offline using my private key and it said signed but showed the same unsigned tx in the box.weird.unisgned tx was of electrum wallet and it was RBF tx.I hope this time you reply me and don't delete this post.
hero member
Activity: 714
Merit: 601
Segwit will be enabled within the next week.
hero member
Activity: 714
Merit: 601
hero member
Activity: 714
Merit: 601

As much as I personally do not support the bitcoin cash hard fork, allowing users to dump it is probably a good thing.

I am reviewing and testing this pull request, but I am also aware that there are a few very minor issues in this pull request, which leaves me wondering if they should be fixed before or after.
staff
Activity: 4270
Merit: 1209
I support freedom of choice
legendary
Activity: 2436
Merit: 1187
still nobody knows how to broadcast transaction to bcc network?

BCC has one block explorer called blockdozer which has a broadcast option. check it here: http://blockdozer.com/insight/tx/send

there is also electron cash which is risky to use but is an option because it is SPV and fast.

oh! big thanks my friend
Pages:
Jump to: