|
You need to elaborate on what's going on.
|
|
|
|
Hello,
I have the same error when trying to send btc from Armory v 0.95.1-beta-374672b751
Bitcoin Core wersja v0.13.2 (32-bit)
empty address is created: 1B6zDd41anwF4vMkLPCoSP7zWdtRpaCwCr but there is no transfer of btc
thank you for help
Grab the raw transaction from Armory and broadcast it directly with core for a better error message.
Same stuff applies. |
|
|
|
|
Start Bitcoin Core with -disablewallet and go the console tab. Then type "sendrawtransaction tx" where tx is your raw transaction in hexits (not line breaks, no spaces, no symbols)
|
|
|
|
|
Your tx didn't make to the mempool. You can just resend with a more appropriate fee.
|
|
|
|
|
Grab the raw transaction from Armory and broadcast it directly with core for a better error message.
|
|
|
|
That means I use same wallet to make a new transaction with enough fee to process, all unconfirmed transactions and double spending will be clear in the network. Am I right?
Doubt it. No CPFP in 0.95 wait for 0.96
I didn't imply I'll do CPFP for 0.96. |
|
|
|
Thank you for your advice . CPFP (Child Pays for Parent), don't know how to perform with armory 095.1.
No CPFP in 0.95 What is the minimum fee can get the confirmation of transaction?
Pick fee/byte option when sending, it will show you your nodes auto fee rate. I did clear all unconfirmed transaction in armory. Can I send the bitcoin normally?
That clears ZC from your DB, not the Bitcoin network. Nothing short of CPFP can help you. |
|
|
|
|
Has this transaction made it to the mempool?
|
|
|
|
At any point, do you go back to allowing Armory to run Bitcoin in the background again?
Upcoming version. |
|
|
|
|
You need to perform a CPFP, which Armory does not support atm.
|
|
|
|
Excellent. Could you make your signature a link?
I got no idea how to o.o And add a donation address if you ever feel like it.
Once the new wallets are out Ill feel comfortable doing that. |
|
|
|
Sorry for the late reply.
Unfortunately no, no developer here. I might identify simple typos after staring half an hour at the code, but that's about it.
I'll gladly paste extra-verbose output here.
I am running Armory on Debian 8, kernel 4.4.38-11, in a Qubes/Xen VM.
Ente
My test worked right away. I'm using a Win8 guest with a Ubuntu 16.04 guest through VBox. As soon as I managed to get nginx through, the client on the host found the server on the guest. For now I'm going to assume something is off in your configuration. For starters, run sanity checks on your server. Next, post your config file and let's go over it. |
|
|
|
|
This is a known Armory bug, fixed for 0.96.
|
|
|
|
I expect you're aware of this goatpig; Wallet Properties -> Receive Coins button produces Fixed Possibly this issue is known/WIP also.... - Click Receive Coins
- Click Address Type
- Select and apply Compressed nested P2SH key
QR code & text remains the P2PKH address. Instead of generating one P2PKH, 100 addresses are generated/displayed, and no compressed P2SH addresses at all. Edit(Edit): A 2nd attempt at creating a compressed nested P2SH worked The compressed P2SH nested keys only appear in Wallet Properties after closing and reopening it (Wallet Properties dialog) Fixed Update: The fee bug I mentioned earlier (ask for 0.0001 BTC fee, get 0.00011576 BTC) is gone. Still, the Coin Control bug is present. I have to explicitly choose UTXOs, otherwise no fee is selected and Armory warns me that I'm trying to send a Tx with no fees. Your transaction comes with a fee rate of 0.00 satoshi/Byte.
This is much lower than the median fee rate of 50 satoshi/Byte.
Are you absolutely sure that you want to send with this fee? If you do not want to proceed with this fee rate, click "No".
Nothing seems to be in the Python (armorylog.txt) or C++/DB (dbLog.txt) logs. If I futz around enough with the UTXO set, I can reset it to the entire set and get a fee. Can you give me a step by step of how you get to that? Okay, now that I've played around with it, the real bug is if the amount being sent is really low. If it's >= 0.1 BTC, you're good. If it's <0.1 BTC, the fee is calculated at times but not at others. Here are examples. I'm not sure there's a pattern to this. Some may work at times but not at others, especially once you start putting in values and then trying new values. 0.09 - No fee 0.001 - Fee 0.01 - No fee 0.011 - No fee 0.0111 - Fee 0.021 - Fee 0.02 - No fee 0.020 - Fee Can't reproduce. This has to do with your utxo mix. Try singling it out with coin selection. |
|
|
|
|
Delete your DB folder and try again.
|
|
|
|
- After ~7-8 blocks come in, Armory seems to stop picking up new blocks even though Core keeps chugging along. No messages on the command line. When I close, I have to force quit. The blocks seem to be picked up upon restart.
I've pushed some code that should fix this at least on the db side. Can you observe both client and db, and in particular if the client drops the connection with the db, is the db still fine? |
|
|
|
Sorry for the late reply.
Unfortunately no, no developer here. I might identify simple typos after staring half an hour at the code, but that's about it.
I'll gladly paste extra-verbose output here.
I am running Armory on Debian 8, kernel 4.4.38-11, in a Qubes/Xen VM.
Ente
I'll be looking into this soon, sit tight. |
|
|
|
I expect you're aware of this goatpig; Wallet Properties -> Receive Coins button produces (ERROR) Traceback (most recent call last):
File "/home/user/BitcoinArmory/qtdialogs.py", line 1550, in getNewAddress
if DlgNewAddressDisp(self.wlt, self, self.main, loading).exec_():
File "/home/user/BitcoinArmory/qtdialogs.py", line 2242, in __init__
addrStr = self.addr.getAddrStr()
File "/home/user/BitcoinArmory/armoryengine/PyBtcAddress.py", line 161, in getAddrStr
raise Exception("Deprecated, get address from mirror wallet instead")
Exception: Deprecated, get address from mirror wallet instead
Traceback (most recent call last):
File "/home/user/BitcoinArmory/qtdialogs.py", line 1550, in getNewAddress
if DlgNewAddressDisp(self.wlt, self, self.main, loading).exec_():
File "/home/user/BitcoinArmory/qtdialogs.py", line 2242, in __init__
addrStr = self.addr.getAddrStr()
File "/home/user/BitcoinArmory/armoryengine/PyBtcAddress.py", line 161, in getAddrStr
raise Exception("Deprecated, get address from mirror wallet instead")
Exception: Deprecated, get address from mirror wallet instead
Fixed |
|
|
|
Update: The fee bug I mentioned earlier (ask for 0.0001 BTC fee, get 0.00011576 BTC) is gone. Still, the Coin Control bug is present. I have to explicitly choose UTXOs, otherwise no fee is selected and Armory warns me that I'm trying to send a Tx with no fees. Your transaction comes with a fee rate of 0.00 satoshi/Byte.
This is much lower than the median fee rate of 50 satoshi/Byte.
Are you absolutely sure that you want to send with this fee? If you do not want to proceed with this fee rate, click "No".
Nothing seems to be in the Python (armorylog.txt) or C++/DB (dbLog.txt) logs. If I futz around enough with the UTXO set, I can reset it to the entire set and get a fee. Can you give me a step by step of how you get to that? |
|
|
|
|
You have something listening on port 9001 on localhost, that's stopping the db from setting up.
|
|
|
|
|
Show Posts
