Subscribing... Cuz ill need this soon
same
Topic: Vanitygen: Vanity bitcoin address generator/miner [v0.22] - page 164. (Read 1153757 times)
ok, never mind previous post. I think I found the answer (didnt show up in search) but I see that it doesnt matter if you stop and start it.
so this means that I can seach for an expression, then quit vgen, start it again later and it will not repeat the work it has already done?
ok, never mind previous post. I think I found the answer (didnt show up in search) but I see that it doesnt matter if you stop and start it.
so this means that I can seach for an expression, then quit vgen, start it again later and it will not repeat the work it has already done?
ok, never mind previous post. I think I found the answer (didnt show up in search) but I see that it doesnt matter if you stop and start it.
Theoretically, does it matter if I start and stop vanitygen when trying to find a regular expression vanity match?
Am I better to "pause" it after it's been running for a few days (which I really can't do)
The reason I ask is because I need to reboot but I've been trying to find a match for a couple of days and if I start and stop, do I basically have to start brute force at the beginning, or is it like mining where stopping and starting theoretically doesnt matter.
thanks for any advice,
-gBIT
Am I better to "pause" it after it's been running for a few days (which I really can't do)
The reason I ask is because I need to reboot but I've been trying to find a match for a couple of days and if I start and stop, do I basically have to start brute force at the beginning, or is it like mining where stopping and starting theoretically doesnt matter.
thanks for any advice,
-gBIT
Account to Account Transfers in the bitcoind (or bitcoin-qt?) application:
https://en.bitcoin.it/wiki/Accounts_explained#Account_-.3E_Account_Transfers
This is the functionality to which I refer. The documentation is not clear whether the bitcoin-qt GUI application uses true Bitcoin transactions or will fall back on this move behavior when requesting to send bitcoin value to another address within your wallet.
In my opinion, the Account concept (read the full wiki page above) is a very useful feature, but has no place in the defacto/reference software from bitcoin.org. They should provide a reference implementation that does not have such features and release the more feature-full edition separately. Anyway, that's getting rather off topic.
Can anyone clarify the behavior of bitcoin-qt when sending values intra-wallet?
https://en.bitcoin.it/wiki/Accounts_explained#Account_-.3E_Account_Transfers
Quote
Use the move method to transfer balances from one account to another. Moves from the default account to any other account always succeed; moves from any other account will fail if the account has insufficient funds. Moves are not broadcast to the network, and never incur transaction fees; they just adjust account balances in the wallet.
This is the functionality to which I refer. The documentation is not clear whether the bitcoin-qt GUI application uses true Bitcoin transactions or will fall back on this move behavior when requesting to send bitcoin value to another address within your wallet.
In my opinion, the Account concept (read the full wiki page above) is a very useful feature, but has no place in the defacto/reference software from bitcoin.org. They should provide a reference implementation that does not have such features and release the more feature-full edition separately. Anyway, that's getting rather off topic.
Can anyone clarify the behavior of bitcoin-qt when sending values intra-wallet?
Accounts aren't addresses. Accounts are groups of addresses. It was designed to be an accounting system for wallets but honestly it is next to worthless (for a variety of reasons).
If you want to send 1 BTC from address A to address B the only way possible to create a tx and submit it to the network. It doesn't matter if address A & B are in the same wallet or on other sides of the globe. There are no exceptions.
If you think about it obviously this has to always be the case. If you could move funds between addresses without making a tx how would the network verify their balances?
I understand exactly what you mean. Here's how I interpreted the Account feature: The wallet balance doesn't represent which private keys own which transactions. You can move value within your wallet for your own bookkeeping. When you send funds, you cannot choose from which Input transactions (or associated private keys) are chosen, and the wallet takes the balance from the "default" account. Accounts can even go negative, which also supports this behavior. Thus, an "account balance" is just high-level bookkeeping, and the actual funds are a mix of transactions. So, the client silently just changes intra-wallet account values without sending transactions (because the wallet doesn't care to actually perform those transactions).
I have enough cryptographic experience to understand what is going on, and the bitcoin.org documentation still tripped me up. Thanks for your clarifications. Sorry to have taken this off-topic. I'll do some further research/testing.
Account to Account Transfers in the bitcoind (or bitcoin-qt?) application:
https://en.bitcoin.it/wiki/Accounts_explained#Account_-.3E_Account_Transfers
This is the functionality to which I refer. The documentation is not clear whether the bitcoin-qt GUI application uses true Bitcoin transactions or will fall back on this move behavior when requesting to send bitcoin value to another address within your wallet.
In my opinion, the Account concept (read the full wiki page above) is a very useful feature, but has no place in the defacto/reference software from bitcoin.org. They should provide a reference implementation that does not have such features and release the more feature-full edition separately. Anyway, that's getting rather off topic.
Can anyone clarify the behavior of bitcoin-qt when sending values intra-wallet?
https://en.bitcoin.it/wiki/Accounts_explained#Account_-.3E_Account_Transfers
Quote
Use the move method to transfer balances from one account to another. Moves from the default account to any other account always succeed; moves from any other account will fail if the account has insufficient funds. Moves are not broadcast to the network, and never incur transaction fees; they just adjust account balances in the wallet.
This is the functionality to which I refer. The documentation is not clear whether the bitcoin-qt GUI application uses true Bitcoin transactions or will fall back on this move behavior when requesting to send bitcoin value to another address within your wallet.
In my opinion, the Account concept (read the full wiki page above) is a very useful feature, but has no place in the defacto/reference software from bitcoin.org. They should provide a reference implementation that does not have such features and release the more feature-full edition separately. Anyway, that's getting rather off topic.
Can anyone clarify the behavior of bitcoin-qt when sending values intra-wallet?
Accounts aren't addresses. Accounts are groups of addresses. It was designed to be an accounting system for wallets but honestly it is next to worthless (for a variety of reasons).
If you want to send 1 BTC from address A to address B the only way possible to create a tx and submit it to the network. It doesn't matter if address A & B are in the same wallet or on other sides of the globe. There are no exceptions.
If you think about it obviously this has to always be the case. If you could move funds between addresses without making a tx how would the network verify their balances?
Account to Account Transfers in the bitcoind (or bitcoin-qt?) application:
https://en.bitcoin.it/wiki/Accounts_explained#Account_-.3E_Account_Transfers
This is the functionality to which I refer. The documentation is not clear whether the bitcoin-qt GUI application uses true Bitcoin transactions or will fall back on this move behavior when requesting to send bitcoin value to another address within your wallet.
In my opinion, the Account concept (read the full wiki page above) is a very useful feature, but has no place in the defacto/reference software from bitcoin.org. They should provide a reference implementation that does not have such features and release the more feature-full edition separately. Anyway, that's getting rather off topic.
Can anyone clarify the behavior of bitcoin-qt when sending values intra-wallet?
both. https://en.bitcoin.it/wiki/Accounts_explained#Account_-.3E_Account_Transfers
Quote
Use the move method to transfer balances from one account to another. Moves from the default account to any other account always succeed; moves from any other account will fail if the account has insufficient funds. Moves are not broadcast to the network, and never incur transaction fees; they just adjust account balances in the wallet.
This is the functionality to which I refer. The documentation is not clear whether the bitcoin-qt GUI application uses true Bitcoin transactions or will fall back on this move behavior when requesting to send bitcoin value to another address within your wallet.
In my opinion, the Account concept (read the full wiki page above) is a very useful feature, but has no place in the defacto/reference software from bitcoin.org. They should provide a reference implementation that does not have such features and release the more feature-full edition separately. Anyway, that's getting rather off topic.
Can anyone clarify the behavior of bitcoin-qt when sending values intra-wallet?
Account to Account Transfers in the bitcoind (or bitcoin-qt?) application:
https://en.bitcoin.it/wiki/Accounts_explained#Account_-.3E_Account_Transfers
This is the functionality to which I refer. The documentation is not clear whether the bitcoin-qt GUI application uses true Bitcoin transactions or will fall back on this move behavior when requesting to send bitcoin value to another address within your wallet.
In my opinion, the Account concept (read the full wiki page above) is a very useful feature, but has no place in the defacto/reference software from bitcoin.org. They should provide a reference implementation that does not have such features and release the more feature-full edition separately. Anyway, that's getting rather off topic.
Can anyone clarify the behavior of bitcoin-qt when sending values intra-wallet?
https://en.bitcoin.it/wiki/Accounts_explained#Account_-.3E_Account_Transfers
Quote
Use the move method to transfer balances from one account to another. Moves from the default account to any other account always succeed; moves from any other account will fail if the account has insufficient funds. Moves are not broadcast to the network, and never incur transaction fees; they just adjust account balances in the wallet.
This is the functionality to which I refer. The documentation is not clear whether the bitcoin-qt GUI application uses true Bitcoin transactions or will fall back on this move behavior when requesting to send bitcoin value to another address within your wallet.
In my opinion, the Account concept (read the full wiki page above) is a very useful feature, but has no place in the defacto/reference software from bitcoin.org. They should provide a reference implementation that does not have such features and release the more feature-full edition separately. Anyway, that's getting rather off topic.
Can anyone clarify the behavior of bitcoin-qt when sending values intra-wallet?
If you're using the bitcoin-qt wallet (from bitcoin.org), moving bitcoins between "accounts" in your wallet might be done locally (not on the block chain). Can anyone else confirm whether this is always the behavior when moving values within the wallet? Is there any way to tell bitcoin-qt to send the transaction to the network, even if you own the destination address (the wallet has the private key)?
this dosnt hapen, if you send something to yourself one of your "hidden" adress is used to recieve the BTC and the amount of BTC isnt decrease. Thats because if you send something to yourself, u already know u will get that amount of BTC. you cant transfer anything locally because only transactions with valid inputs are getting accepted, if you just change the input who dosnt have enough BTC then it will fail. You have to tell the network that u send BTC to another adress otherwise the money is lost (you can recover it by undoing the transaction in your wallet since the transaction never got send to the network (assuming u modified bitcoin to not send the transaction)).greetings
I'm pretty sure the transaction has to go to the network, otherwise there wouldn't be confirmations and the transaction wouldn't really have happened. That having been said, I had coins go from one wallet to another and the address wasn't showing on firstbits.com several days later (this was a few months ago). I think it is way behind. Is the firstbits info on blockchain.info calculated the same way and accurate?
If you're using the bitcoin-qt wallet (from bitcoin.org), moving bitcoins between "accounts" in your wallet might be done locally (not on the block chain). Can anyone else confirm whether this is always the behavior when moving values within the wallet? Is there any way to tell bitcoin-qt to send the transaction to the network, even if you own the destination address (the wallet has the private key)?
its saying that all 4 of mine are not in the chain... I have moved a few coins to and from them last night. o well!
I think it is worth mentioning to everyone you need to use your generated address in order to claim the firstbits location.
I love my new address (Check sig) 
Hello, just a note that I made a vanity address generator applet (see topic here). It's ridiculously slow compared to the likes of Vanitygen. Just an experiment, as I'm starting to tinker with Bitcoin.
stupid question, stupid answer:
develop OpenCL driver for ur FPGA then u can!
develop OpenCL driver for ur FPGA then u can!
Will VanityADress gen be workable with FPGA`s like BFL?
Jump to: