Got one hour left! One final push for some funds!!! I anticipate that even though I didn't make $12k, I will be able to take a substantial amount of time off to work for Armory! And I'm really looking forward to it!
I will maintain a donation address (and there's a donate button in Armory) for after crowdfunding is over, but RocketHub was my way to collect donations from credit cards too. I may keep some kind of rewards thing for people who continue to donate in BTC, as I feel like it's a really good idea to make donors feel like their money isn't just hitting a black hole.
Topic: Armory Crowdfunding Finished! [UPDATE - *BETA*] - page 3. (Read 25502 times)
Two hours left.......
Ya, don't worry about the BitLotto request. We've since changed how it operates so it's not needed anymore. You can now make any size payment you want.
BTW, I really like your program!! Keep up the good work. My machine is a little on the low end for the requirements but I'm watching your progress closely. Thanks!
BTW, I really like your program!! Keep up the good work. My machine is a little on the low end for the requirements but I'm watching your progress closely. Thanks!
Has no one tried the new wallet migration tool (0.60-alpha-RC1)!?! I know there has been a low SNR on this thread sometimes, but there was a lot of people requesting it! Even if no one wants it right now ... I have no idea if the interface makes sense, whether it works on all systems, whether there's any problems with decrypting wallets associated with certain versions of the Satoshi client, etc. Please help test it so that I can release it as a final version!
I don't really want to enable folks to send hundreds of tiny transactions. That bloats the blockchain for everyone else. For instance... if you send 40 transactions like this, it's likely to add 10 kB to the blockchain, but if you send using multiple outputs, it will take about 1.5 kB...
It sounds like the BitLotto guys have decided that each transaction is one ticket. It should be pretty easy to change it to each transaction output is/can be a ticket. So instead of having a pool of tickets like:
They might have the following:
many thanks, each of say the 40 tx needs to be sent as a distinct tx on the blockchain because the tx is the lotto ticket, well it's hash is, so all need to be different & not bundled even though they're all going to the same address, so looking for a way to do this with a wallet that wasn't just manually entering 40 different tx, you'll get better feedback on this once the Bitlotto peeps have replied
edit: each tx is for 0.25 BTC with 0.0005 added as miners fee
edit 2: & it would be nice if it was easy to repeat each month to that month's lotto receiving address once that had been manually entered in to the wallet as recipient for another 40 times 0.25 BTC tx
edit: each tx is for 0.25 BTC with 0.0005 added as miners fee
edit 2: & it would be nice if it was easy to repeat each month to that month's lotto receiving address once that had been manually entered in to the wallet as recipient for another 40 times 0.25 BTC tx
I don't really want to enable folks to send hundreds of tiny transactions. That bloats the blockchain for everyone else. For instance... if you send 40 transactions like this, it's likely to add 10 kB to the blockchain, but if you send using multiple outputs, it will take about 1.5 kB...
It sounds like the BitLotto guys have decided that each transaction is one ticket. It should be pretty easy to change it to each transaction output is/can be a ticket. So instead of having a pool of tickets like:
Code:
TransactionA
TransactionB
TransactionC
TransactionD
They might have the following:
Code:
TransactionA:0
TransactionB:0
TransactionB:1
TransactionB:3
many thanks, each of say the 40 tx needs to be sent as a distinct tx on the blockchain because the tx is the lotto ticket, well it's hash is, so all need to be different & not bundled even though they're all going to the same address, so looking for a way to do this with a wallet that wasn't just manually entering 40 different tx, you'll get better feedback on this once the Bitlotto peeps have replied
edit: each tx is for 0.25 BTC with 0.0005 added as miners fee
edit 2: & it would be nice if it was easy to repeat each month to that month's lotto receiving address once that had been manually entered in to the wallet as recipient for another 40 times 0.25 BTC tx
edit: each tx is for 0.25 BTC with 0.0005 added as miners fee
edit 2: & it would be nice if it was easy to repeat each month to that month's lotto receiving address once that had been manually entered in to the wallet as recipient for another 40 times 0.25 BTC tx
I've pledged a 5 BTC bounty for someone to write an open source script for making large wagers on Bitlotto (atm the bets are for 0.25 BTC each so to wage 10 BTC takes 40 tx which is a pain to do manually), if a wallet service enables a 'repeat transaction n times feature ie same amount, from same address (or different ones if that's more practical) to be sent to just 1 receiving address (that month's Bitlotto address) then I would award the bounty to who ever made this first
https://bitcointalksearch.org/topic/m.803814
https://bitcointalksearch.org/topic/m.803814
So, one transaction: one input of 10 BTC from 1 address, and 40 outputs, each 0.25 BTC each to the exact same address? That can be done manually in Armory, as you can just add 39 recipients and manually copy&paste the data between the fields. It will put everything into the same transaction. Clearly it's not preferable, but it's better than creating 40 different transactions.
I am working on an example script for other reasons, that will also serve your purpose, too:
Input:
Wallet file
List of addresses in that wallet (or just one addr)
List of (recip, amt) pairs
Output:
Signed Transaction
It will search the blockchain, construct the transaction, calculate the fee, add the appropriate change output and sign it. It could send it too, if you want (I can add a confirmation message, along with a password prompt in case the wallet is encrypted).
I'll let you know when it's done -- it's part of my effort get developers a jumpstart on leveraging armoryengine since there is no JSON interface yet, and sounds like it would get me 5 BTC from you
Just be aware that the more outputs you use, the more the tx will cost. Each input is about 150 bytes, and each output is about 35 bytes. Above 3-4 kB, a tx can no longer be free.
I've pledged a 5 BTC bounty for someone to write an open source script for making large wagers on Bitlotto (atm the bets are for 0.25 BTC each so to wage 10 BTC takes 40 tx which is a pain to do manually), if a wallet service enables a 'repeat transaction n times feature ie same amount, from same address (or different ones if that's more practical) to be sent to just 1 receiving address (that month's Bitlotto address) then I would award the bounty to who ever made this first
https://bitcointalksearch.org/topic/m.803814
https://bitcointalksearch.org/topic/m.803814
I also must wait for the ram-reduction overhaul before I can enjoy Armory, as I still use WinXP 32bit. Once I get my hands on a fully functional (not just testnet) Armory, I'll probably be impressed enough to donate. 
A lot of you have been waiting for this feature, so please help test it! Gimme feedback!------------|
-------------------VVVVVVVVVVV--------------------------------------------------------------------------------------|
I wish I'd gotten RAM-reduction going by now, but instead I was listening to you and implementing features that I were in high demand (and not major overhauls of the application). Plus, the RAM-reduction is half-done, and hopefully be implemented in the next couple weeks!
Choosing not to do this upfront limits the amount of people that can trial the software. People by nature like to feel it, touch it, taste it prior to making commitments and this factor could have caused some missed donations. From reading user comments and your write ups I was filled with anticipation willing to give it a try when I discovered this fact. O.o My daily user only has 2GB so I couldn't play with Armory. SOAB :sigh: -------------------VVVVVVVVVVV--------------------------------------------------------------------------------------|
I wish I'd gotten RAM-reduction going by now, but instead I was listening to you and implementing features that I were in high demand (and not major overhauls of the application). Plus, the RAM-reduction is half-done, and hopefully be implemented in the next couple weeks!
I pledge $49.99+ in btc when it hits beta. I have been on the losing side of up front costs too many times - while this seems like a slam dunk, it is a personal issue for me. I check the armory thread all the time.
OT question about deterministic wallet: If someone were to get a few private keys from a deterministic wallet, can he extrapolate the data to retrieve all the keys?
OT question about deterministic wallet: If someone were to get a few private keys from a deterministic wallet, can he extrapolate the data to retrieve all the keys?
There is one chain code and an infinite series of private keys. If an attacker gets one private key and nothing else, that's all he gets. If he gets PrivKey(i) and the chaincode, then he can calculate PrivKey[i+1], PrivKey[i+2], ..., but not any of the ones before it (i-1, i-2, ...)
I pledge $49.99+ in btc when it hits beta. I have been on the losing side of up front costs too many times - while this seems like a slam dunk, it is a personal issue for me. I check the armory thread all the time.
OT question about deterministic wallet: If someone were to get a few private keys from a deterministic wallet, can he extrapolate the data to retrieve all the keys?
OT question about deterministic wallet: If someone were to get a few private keys from a deterministic wallet, can he extrapolate the data to retrieve all the keys?
A lot of you have been waiting for this feature, so please help test it! Gimme feedback!
Version 0.60-alpha-RC1: Satoshi Wallet Migrate/Import!
Finally got a migration tool integrated, and it works with encrypted wallet.dat files! Import from encrypted or unencrypted Satoshi wallets, with or without the address pool, including address labels, into an encrypted, unencrypted, or new Armory wallet.
A special thanks to Joric for providing me such excellent reference code to get the wallet-decryption working. I donated 5 BTC to Joric for his help! Now, if all you want to do is pull your private keys out of your wallet.dat, you can use Armory to dump them into a new wallet, and then use "Backup Individual Keys" to create a text file you can print out.
48 hours left in the crowdfunding!
It doesn't look like I'll make the $12k, but I will still be able to take a pretty significant chunk of unpaid leave. If I make it to $6k, I will cut a full day off my job! I wish I'd gotten RAM-reduction going by now, but instead I was listening to you and implementing features that I were in high demand (and not major overhauls of the application). Plus, the RAM-reduction is half-done, and hopefully be implemented in the next couple weeks!
Version 0.60-alpha-RC1: Satoshi Wallet Migrate/Import!
Finally got a migration tool integrated, and it works with encrypted wallet.dat files! Import from encrypted or unencrypted Satoshi wallets, with or without the address pool, including address labels, into an encrypted, unencrypted, or new Armory wallet.
A special thanks to Joric for providing me such excellent reference code to get the wallet-decryption working. I donated 5 BTC to Joric for his help! Now, if all you want to do is pull your private keys out of your wallet.dat, you can use Armory to dump them into a new wallet, and then use "Backup Individual Keys" to create a text file you can print out.
48 hours left in the crowdfunding!
It doesn't look like I'll make the $12k, but I will still be able to take a pretty significant chunk of unpaid leave. If I make it to $6k, I will cut a full day off my job! I wish I'd gotten RAM-reduction going by now, but instead I was listening to you and implementing features that I were in high demand (and not major overhauls of the application). Plus, the RAM-reduction is half-done, and hopefully be implemented in the next couple weeks!
PM Sent! Weekend is coming up. I think a cryptography lecture is in order. LOL
Just donated! Don't worry about sending me any trinkets. I want you to save all that time and extra resource for your project. What you are doing is tremendous.
The price of BTC is going higher these days as well. Good omen!
The price of BTC is going higher these days as well. Good omen!
Thanks! Well at least PM me your email address, and I'll send you the encryption seminar. There's no reason for any of the donors not to get that
Just donated! Don't worry about sending me any trinkets. I want you to save all that time and extra resource for your project. What you are doing is tremendous.
The price of BTC is going higher these days as well. Good omen!
The price of BTC is going higher these days as well. Good omen!
Nice Work.
I like the heading on the Bitcoin Media. Armory, it's THE PEOPLE'S VAULT! (I'm the capitalist to the core, no, not a communist, just love the sounding of the name).
Bumped (with another donation). Any one else ready to do something to get bitcoin mainstream ready?
I got an article in BitcoinMedia! I think that should help
http://bitcoinmedia.com/the-peoples-vault-armory-client/
Bumped (with another donation). Any one else ready to do something to get bitcoin mainstream ready?
Home from vacation and a bug-fix release!
I had introduced a nasty bug into Armory just before leaving for a week, probably causing all sorts of confidence issues for first time users. Those issues have been fixed!
--Sending transactions work as expected (ledger updates immediately with number of confirmations)
--Signing offline transactions no longer fails if there is a blockchain file on the offline system (weird problem, but fixed now)
Thanks for your patience!
Download the updated version 0.56-alpha at: http://bitcoinarmory.com/index.php/get-armory
I had introduced a nasty bug into Armory just before leaving for a week, probably causing all sorts of confidence issues for first time users. Those issues have been fixed!
--Sending transactions work as expected (ledger updates immediately with number of confirmations)
--Signing offline transactions no longer fails if there is a blockchain file on the offline system (weird problem, but fixed now)
Thanks for your patience!
Download the updated version 0.56-alpha at: http://bitcoinarmory.com/index.php/get-armory
Jump to: