|
Yes, that is possible, and is a key part of cold storage setups.
|
|
|
|
|
It will be cheaper for you to do the transactions as one large transaction as that cuts out the overhead required for making multiple transactions. It also reduces the risk of having long unconfirmed transaction chains which can be very problematic for the people receiving the Bitcoin.
Regarding the size of the transaction, 500 Kb is quite large. If your transaction is going to be that big, you should probably split it up into multiple transactions.
|
|
|
|
Did you make the other one? If so, you can just do Repair Wallet again and make the same transaction but include a higher fee. |
|
|
|
"Transaction rejected by our node. Reason: Transaction was previously accepted but has been pruned from our database." can you translate please?  That message means that blockchain.info has removed the transaction from their node. This does not mean that it cannot confirm, nor does it mean that every other node on the network has also removed the transaction. When you did "Repair Wallet", did it remove the transaction from your wallet (it should have)? Did the transaction appear again after some time, or did it never leave your wallet? |
|
|
|
|
We have managed to get Armory fully translated into another language, German. Please help use test that the translations are working properly by switching to the other languages and by using the German translations to find any missing strings or bugs with displaying the strings or dialog boxes.
Note that some Usermode strings are not translated. That has been fixed and the translations will be applied once the translation resources are updated later.
|
|
|
|
Hey, just a short question:
Can I use the "recovery wallet" function and enter some lines of which i have created my self to create my own entropy and do not have to trust armory in that case?
I know, this is on my own risk then, if im stupid enough to enter some pseudo-entropy its my own fault. Just wanna know if this might be a possibility if i create them by dices or so...
No. IIRC the recovery stuff contains sanity checks and checksums so you can't just enter a bunch of random stuff, it will fail those checks. EDIT: just saw that in the menu of "create wallet" i can find a button "add manual entropy", but then again i have to trust armory that it actually use this "manual entropy". But if i just enter my own lines in the recovery function, it has to, right? So if i would not trust it, it would be the better option.... (just in case Im somewhat paranoid  ) The manual entropy option for creating a wallet uses a deck of cards. If you are concerned that it does not use your manual entropy, then look at the source code and compile from source yourself. |
|
|
|
|
Bitcoin Core must be running in order for Armory to work. Armory by default will run bitcoin core for you in the background, but recently that has not been working too well.
Go to File > Settings and uncheck the box "Let armory run bitcoind in the background". Then stop Armory, start Bitcoin Core, and start Armory again.
|
|
|
|
|
Your proof that the money was sent is the transaction id. The transaction has been confirmed, so it is already sent. If they say it was not, then they are lying to you or don't know what they are talking about.
|
|
|
|
|
Go to File > Settings and uncheck the box "Let Armory run Bitcoind in the background". Then stop Armory, start Bitcoin Core, and start Armory again.
|
|
|
|
I mean to generate some words in the beginning via brute force generating adresses. Is there a free programm which can do that ?
Such programs already exist and have existed for a long time. See Vanitygen: https://bitcointalk.org/index.php?topic=25804.0 |
|
|
|
if this can be done by anyone, then it can become a vulnerability?
No. There is no vulnerability. Rebroadcasting does not give anyone the ability to steal other people's Bitcoin. It does not risk anyone's Bitcoin nor does it cause issues for nodes. It only causes a problem for poorly written wallet software which does not have an option for removing the unconfirmed transactions. |
|
|
|
This result kind of makes me wonder why so many old blocks. once verified, need to be stored in the first place. Why shouldn't that pruning function be built into CORE main program code as a default standard? Is there perhaps some security advantage in storing all those old blocks. that I've missed?
When you prune, you lose some functionality. If the database becomes corrupted, it becomes very painful to fix that as it requires redownloading the entire blockchain. You can't rescan or import other addresses and private keys. Additionally, pruned nodes cannot sync a new node since it cannot provide the entire blockchain. Becaues of these shortcomings of pruning, it is not enabled by default. |
|
|
|
|
You should use dynamic fees instead of setting a fixed fee rate. Use Electrum's dynamic fees, and if such an option is not available, use the latest version of Electrum. When you go to send, there should be a slider that lets you choose a fee rate. Always use the dynamic fees.
Additionally, you can enable Opt-In RBF which allows you to easily replace the transaction with one that pays a higher fee. Electrum supports this feature, go to Tools > Preferences and check "Enable Opt-in RBF". When you go to send Bitcoin, you can check the "Replaceable" option in the send tab so that if the transaction gets stuck, you can increase its fee.
|
|
|
|
For some reason I can't get past the first window of your program. I paste in the raw hex of my transaction, but nothing happens when I click the next button. I think it is a valid raw transaction because if I alter it at all and then click next an error window pops up that says, "Please enter a valid transaction." But for some reason it won't advance to the next screen with the valid transaction.
It's probably failing to connect to the APIs it uses to calculate the fee and get info about the transaction. Restart it and try again. |
|
|
|
|
The automatic rebroadcasting is an "issue" that users here cannot help you with. If blockchain.info is rebroadcasting, contact their support to help you. If someone else on the network is rebroadcasting, there is nothing that anyone here can do. Anyone can rebroadcast any transaction.
|
|
|
|
|
A block does not take ten minutes to "hit" your wallet. It takes, on average 10 minutes to be found. The block does not exist until it is found, and then it only takes a couple hundred milliseconds to "hit" your wallet.
There is no way to predict what data will be in the block.
|
|
|
|
|
It's called change.
Imagine that each transaction you receive to your address is like a piece of paper money, like a dollar bill. When you want to spend part of that money, you need to receive change to only spend part of it. For example, I pay for a $15 item with a $20 and receive $5 in change.
The same thing happens in Bitcoin because you can only fully spend from an output; you cannot partially spend it. Whatever is leftover, i.e. the change, has to be sent back to your wallet, so the transaction has a change output. Most wallets will generate a new address for your change outputs, so this is what you are seeing.
|
|
|
|
|
Show Posts
