[snip]
I agree.
I suggest to use recommended fee instead if change amount as fee and as this is advanced software, please allow users to edit transaction fee. You can send change back to origin address like xDan told.
The problem is not everyone would be happy with the funds being sent back to their original address, also its possible to populate the "inputs" on a new transaction with funds from multiple addresses. There is a few things to think about, because I don't want to force users to do anything they don't want to. But a confirmation notice sounds ok.. Ok. As it is aimed on advanced users, shouldn't we be able to set custom fee? Currently, I can't do it. Please change it. The transaction fee can be manipulated by adding another address, this can either be the address you populated the unspent funds from, or an entirely new address if you have privacy concerns. Am I miss understanding something? |
|
|
|
[snip]
I agree.
I suggest to use recommended fee instead if change amount as fee and as this is advanced software, please allow users to edit transaction fee. You can send change back to origin address like xDan told.
The problem is not everyone would be happy with the funds being sent back to their original address, also its possible to populate the "inputs" on a new transaction with funds from multiple addresses. There is a few things to think about, because I don't want to force users to do anything they don't want to. But a confirmation notice sounds ok.. |
|
|
|
Hey xDan! Before I start responding to your points individually, I just want to remind you that coinb.in is aimed at the "advanced" bitcoin user and offers the "tools" required for them to understand how things work. Also the code is also remarkably simple and easy to follow compared to say bitcoinjs. I haven't used the service, so I don't know if such a transaction would go through... But the fact it is even implied that it might is a very very scary thing and will keep me from using what otherwise looks like an excellent piece of software. Default to 100% of the value going to the transaction fee (if I don't put anything in the "amount" box) is crazy and might one day lose somebody all their coins.
A sane option might be giving a large red warning if the tx fee is larger than say 0.1% of the total value. Or not allowing it at all if it's over $1 worth or something.
The transaction would indeed go through if you signed it. The question is, who am I to prevent someone from choosing their transaction fee, regardless of how high or low it might be. It would be an unfortunate mistake to accidentally set a large fee so I will take into consideration what you've said and perhaps throw up a confirmation notice if the fee is too large. But please keep in mind this is the first time someone has mentioned this and made such a big issue about it. If a change address is required, the user should be asked for it also with big warnings that it should be a safe, permanent address, not in a virtual machine or livecd etc (where people have lost large amounts in the past). A conservative approach to handling change is to send it right bank to the original address. Not quite as private, but better than losing money. (and still needs warnings to the user that the address/private keys they are sending from must be kept!)
Yes a change address is required, again who am I to send automatically send it back to them. My philosophy is its your money, you can do with it as you like. If you dont want to use the tools to manually build a transaction, and want the comfort of your funds being returned to you, try the wallet instead https://coinb.in/#wallet you dont get same functionality as building the transaction yourself, and signing it etc, but if the transaction fee is your issue, you can be sure it will return it to your address. Check it out  Thanks again for the feedback and suggestions. Very great full! |
|
|
|
Nice work with this project. Looks cool. And thanks for supporting https://coinb.in |
|
|
|
|
HD support (bip32) has been added to coinb.in - enjoy everyone!
|
|
|
|
I can be a beta tester and for tutorials, need more info. Please PM me.
Thanks, will be in touch shortly. |
|
|
|
A few new features coming soon to coinb.in, such as: - HD Wallet Support (bip32)
- Use of Bitcoins Testnet
- Retrieve Unspent inputs from alternative blockchain explorers, such as blockr
- Broadcast to different blockchain explorers
- Build transactions for other Altcoins
I'm looking for beta testers and for someone to make a few video tutorials on using various aspects of Coinb.in - if anyone is interested, please get in touch by email OutCast3k<at>gmail.com |
|
|
|
Have you tried what I wrote yourself? I am still using 0.8.6 as I like the most. In 0.8.6 it is addmultisigaddress <nrequired> <'["key","key"]'> [account]
Add a nrequired-to-sign multisignature address to the wallet"
each key is a Bitcoin address or hex-encoded public key
If [account] is specified, assign address to [account]. It might differ in the new qt releases 0.9.x (I doubt it) but at least in 0.8.6 if you type what I typed above it will work.For example I generated 3MuDqC9b3cFtWmVs6rJpD4oJ79CPVJMGzE this way(it is 4-4 and it is non-standard) Try to type addmultisigaddress 2 '["1AKCGRnjWqwwSj7dUpBmY89QbjUivCo278","1HHMyRDBpG5Kfbgc1XZNnjorWTd5GaLA6Q","1CrxaQV5DGbSi7SPKNQNZa7LUXadTs25rd"]' in 0.9.x and you'll see that it works just fine.If I would be wrong qt would have not corresponded to 3CTqt1ryMJ7HU5PDgxHoJK3ThifLjqKYXQ Well ofcourse you could use pubkeys but do you want to do the extra work to get the pubkeys? Hey, You can only provide an address IF the client you are making the multisig address on has access to the public keys of the address you specified! Your client will make a multisig address using your addresses, because it has your public keys for them, but you can't generate someone else's public keys from their address alone. This is because an address is a hash of a public key, it is one way and can no be reversed, therefore it is impossible for your client to generate someone elses public key from their (unspent) address. You can read more about how multisig works on a protocol level here https://bitcoin.org/en/developer-guide#multisigSo unfortunetly in the real world your example is useless, because other peoples addresses will not be in your wallet! |
|
|
|
multi sig or bip38 addresses start with 3. u can use. http://coinb.in/multisig/ to create one, or learn more about it so u can create one yourself For me it is way easier to generate the multi-sig address on bitcoind(or bitcoinqt debug window) and it will be easier for beginners too. Why? Because you don't need to convert your compressed keys to uncompressed ones. Simply go to bitcoinqt press help press debug window press console and then type addmultisigaddress <number of how much priv keys out of addresses after this number it would need to make a transaction> <'[and now 3 addresses]'>.Correctly standard multisig addresses are 2-2 2-3 3-3 I recommend to use 2 as a number of required keys and use 3 addresses. A simple example would be: addmultisigaddress 2 '["1AKCGRnjWqwwSj7dUpBmY89QbjUivCo278","1HHMyRDBpG5Kfbgc1XZNnjorWTd5GaLA6Q","1CrxaQV5DGbSi7SPKNQNZa7LUXadTs25rd"]' Which corresponds to 3CTqt1ryMJ7HU5PDgxHoJK3ThifLjqKYXQ Hey, The new version of https://coinb.in supports compressed and uncompressed keys - check it out Also your bitcoin-qt example is slightly wrong because you need to use the public keys not an address to make a multisig address. |
|
|
|
Fixed a few bugs and added loads of little features, you can even set the "lock time" of transactions now. Feedback and suggestions are welcome |
|
|
|
Are there any sites that can compress and uncompress private keys? Or any open source code i can borrow? Bitcoind is giving me pub key compressed. http://coinb.in/multisig/ takes uncompressed. The new version at: http://coinb.in supports compressed keys. |
|
|
|
The new version is live here: http://coinb.in  will be published to github shortly. Major changes: - Multisig address generation now supports compressed public keys.
- Transactions and redeem scripts will return more information when they're decoded, including the N-of-M number and the amount of times they've been signed.
- Better transaction builder. You can build transactions from regular addresses as well as multisig addresses.
- Improved signing function. Regular transactions as well as multisig transactions can be signed.
- You can generate compressed and uncompressed public keys.
- Private keys are given a password field by default with option to show them later.
- You can generate addresses from Brain wallets.
- A built in browser based wallet, with access to your own private keys!
If you want to see more, please support the project by donating Enjoy! |
|
|
|
How can we email you? What's your email?
Its listed on my profile, but its: <my><user><name>@gmail.com |
|
|
|
Vanity Multi-Signature Addresses? Compressed? Is this possible? Or is it too much hard work? Or it's no longer multi-sig because you have one computer generating all the private keys? How about, in theory? Like, 3DabsAddress instead of 3randomlooking. Also, can multi-sig addresses be compressed? I found this, and it requires uncompressed public keys: http://coinb.in/multisig/*edit* then I found this thread, so I'm posting here instead. Sorry for the late reply, i've been so busy lately! The project is still alive and well! There is actually going to be an entirely new version released in the next week or so that will support compressed public keys and offer a few other new features! but not vanity addresses. If anyone would like to beta test for me, please get in touch via email and i'll give you access.Thanks everyone for your support, if you like this project please donate - *Edit* To everyone who has PM'd me asking if they can use the source code, yes you can its totally free to use, edit and redistribute. Enjoy! |
|
|
|
It's down  Will be back up soon, sorry about this. Some jerk is ddosing the server, and demanding he's paid X amount of bitcoins before he stops. As if! |
|
|
|
The same thing is happening to me - the 3-of-5 isn't working. I had a 2-of-3 work just fine this morning, but this afternoon, there is no way to get the 3-of-5 to work. Is coinbin not coding the transactions correctly? (Tried with blockchain.info to push too) Is my money lost for ever??? (  Thanks coinb.in...) I hope that is not the case... Thanks, -Luc The hex encoded transaction you have given me via email appears to use non existent transaction IDs, as I've explained back to you. I don't think your money is lost, but if you could try again and note down each step you take, and the output and then contact me if it fails. I finally could test succesfuly with real money.
answering my own questions: the redeem script is given when you create the multisig address.
It's quite simple!!
Have made a tutorial in french.
Will translate it in english and post here.
Thanks, glad you liked it. Great work on this! I've tried the service and a 2of3 worked great. however, I tried something that I actually need right now in the form of a 6-of-10 and... no go Getting a tx rejected -22 and log error says "nonstandard transaction: scriptsig-size" which I assume relates to the 500b limit mentioned earlier in the thread. Is there a way to make this work? Reading around in some other discussions I saw being mentioned that even a 15 of 15 should work, so I'm a bit confused as to why 6 of 10 doesn't. Also OutCast, on a side note, it would be really great if you could provide the non-minified bitcoinjs code (either as a download here or in the git repo) as part of the opensource approach. Thanks! Can you drop me a email with the details, and i'll take a look. I'm not sure right now. |
|
|
|
Quick question.! Do I have to run my own bitcoind client on the server to be able to run this script.?
No, its not required. |
|
|
|
Awesome, cheers.
I tried it again on Chrome. Trying to sign the partially signed transaction just yields a transaction with one different signature.
I tried with the unsigned transaction, and that failed too.
One thing that could be causing trouble is that I'm using one compressed keys, I notice it asks for them to be uncompressed when you're entering them? But, then again, the key I'm having trouble signed with came from Coinb.in.
Have you tried signing the transaction I pasted? I've used Coinbin before, and been telling a lot of people about it.
As I'm sure you are aware; signatures must be added to the 'scriptSig' in the same order the 'public keys' are found in the 'redeem script', because of this signatures aren't simply inserted to the scriptSig, they are rebuilt. The code for this is here: var pubkeyList = scriptListPubkey(redeemScript);
var sigsList = scriptListSigs(o.script);
sigsList[countObject(sigsList)+1] = signature;
for(x in pubkeyList){
for(y in sigsList){
if(Bitcoin.ECDSA.verify(sighash, sigsList[y], pubkeyList[x])){
s.writeBytes(sigsList[y]);
}
}
}
So, I suspect when the Bitcoin.ECDSA.verify() function is called it fails to validate your signature against a public key because its the wrong kind. (i.e. its compressed when it should be uncompressed) This means its not re-added. I'm not sure how you'd fix this exactly, but I will have a think. |
|
|
|
|
Show Posts
