|
Delete your databases folder and try from scratch.
|
|
|
|
|
That's how BTC transactions work.
|
|
|
|
I'm 100% positive I bought and transfered BTC then
Someothing else came to my mind, initially I ahd some trouble getting armory setup and when generating the adress, I had a "Node Offline" error in the bottom right corner. Don't know if that matters though.
As long the address you sent your coins to appears in the wallet, you are good. Would you mind sending me your watching only root so that I can double check on my end? PM me the string if you ok with that. |
|
|
|
|
Bcash uses the same address format as Bitcoin. Bcash supporter make a point of conflating the 2, and aggressive pro Bcash services will peddle you BCH where you thought you were getting actual Bitcoins. The issue you describe is symptomatic of such fuckery, so I'm asking you to double check.
|
|
|
|
when its finished ill start armoryqt with this target: "C:\Program Files (x86)\Armory\ArmoryQt.exe" --satoshi-datadir="g:\bitcoin"
Not sure if bitcoinqt should be running? I think once its indexed and sync'd ill try closing it and running the armoryqt target. If that doesn't handle Bitcoinqt in the background then i'll shut it down and run bitcoinqt (without reindex) and open armory with the target. Just not sure which to do when otherwise.
If you have autobitcoind on (default setting), Armory will try to run bitcoind for you if it can't find an exsiting instance, otherwise it will just use the current instance. |
|
|
|
|
Yes, but make sure to remove the -reindex after the first run.
|
|
|
|
Further I was under the impression the WITNESS service flag is enabled by default in 0.14.2. Is that incorrect?
Has been since 0.13.1. Maybe you want to double check your node is actually advertising the WITNESS flag. |
|
|
|
from the 0.96.2 changelog ( https://github.com/goatpig/BitcoinArmory/blob/master/changelog.txt#L29) - Enabled SegWit on the mainnet. Running against a node with WITNESS service bit flagged will allow you to create SegWit addresses.
Armory has to be online, i.e. both DB and node have to be running, and your node has to advertise the NODE_WITNESS flag in its version packet. Most likely you are doing this with your node turned off? |
|
|
|
|
You are missing about 3 months worth of block data. Start BitcoinQt manually, let it catch up then run Armory as usual again.
|
|
|
|
|
You're asking for the offline or the online machine?
|
|
|
|
|
Are you sure these are actual Bitcoins you sent to your wallet and not Bcash?
|
|
|
|
|
Update to 0.96.3.99 and post dbLog.txt as well. Don't paste that stuff here, use pastebin instead.
|
|
|
|
|
Copy the raw tx instead of broadcasting. Paste that in whatever service. There is no guarantee this will work, as you are obviously grabbing the utxos from Core node.
|
|
|
|
Under file > settings > Bitcoin home Dir: I have it pointing at c:\Bitcoin. Do I need to do anything else?
That should do the trick, otherwise read this guide. https://btcarmory.com/docs/pathingYou will have to delete your databases folder first though. |
|
|
|
blkfile dir: Z:\Users\ryssk\AppData\Roaming\Bitcoin\blocks
It's looking for blocks in this folder, where is did Core download blockchain data to? Chances are, somewhere else. |
|
|
|
|
1) Yes
2) It won't pick SegWit unless the tx you are spending from is SegWit. Otherwise it will pick P2SH-P2K. You would have to manually set your change address to nested P2WPKH to get it to create SegWit change when spending from a legacy outputs.
3) Doesn't matter for Core as long as it's a SegWit compliant version (13.1 and later iirc). For new address types, you want to keep the signer and online instance in lock step until the code congeals.
4) The fee is computed on the basis of full sat/byte for the non SW part, and discounted sat/weight for the witness data. Here's an example to illustrate:
You are setting the fee at 200 sat/B in the GUI for a 400 bytes tx that is half tx data, half witness. That gives you:
- 200 bytes at full 200 s/B (the 200 bytes of the plain tx data)
- 200 bytes at 50 s/B (discounted 200 bytes of witness data)
Your total fee is 50000 satoshis, your tx weighs 250 units, you effective fee is 200 s/wu.
If you choose the enforce a flat fee manually on a SW tx, the code will display the estimated s/wu of your tx.
All values in the GUI for unsigned tx are estimates, as signatures can vary by 1-2 bytes from the high end value Armory uses.
|
|
|
|
|
Je dis ca juste pour aider, la recompense ne m'interesse pas et j'ai pas le temps de lire l'OP pour voir les details. On m'a envoye un lien pour ce thread, je lis pas le forum FR d'habitude. Ce que je vais dire a peut etre deja etait couvert ailleurs.
En gros pour faire simple, Core a 2 type de wallet:
1) Les originales qui n'utilisent pas de chaines determinees. Dans ce cas la, tu l'a dans le baba, dsl. Les cles de ces wallets sont generees aleatoirement et il n'y a pas moyen de les recrees. Le "brute force" n'est pas une solution. Il n'y a pas assez d'energie sur la planete pour creer une collision sur un champ aussi large que 256 bit.
2) La version courante, qui est reglementaire BIP32. Dans ce cas, les cles privees sont generees de maniere determinee, et tout particulierement en utilisant la derivation "legere" de BIP32 a partir du noeud qui te concerne. Ainsi, simplement avec la chaine de cles publiques et une seule cle privee, tu peux recreer le xpriv du noeud et le restaurer dans n'importe quel programme qui supporte BIP32.
|
|
|
|
|
Show Posts
