So if you say I'm experiencing something no one has seen so far... interesting...
Rico
Indeed, you are experiencing an issue that no one else has before. Here, I made a PR fixing this: https://github.com/bitcoin/bitcoin/pull/8746. |
|
|
|
I'm not sure what I'm doing wrong, when i generate the hash it matches correct but then I tried verifying as below and got public key not found. I have imported the keys that were listed in OP, there were 5 i think
xxxxxxxxxxx$ gpg --verify SHA256SUMS.asc
gpg: Signature made Tue 23 Aug 2016 16:23:26 CEST using RSA key ID 36C2E964
gpg: Can't check signature: public key not found
I feel like it is safe to use the binary because the hashes did match, is that the case? why have i not go the right public key?
Double check that you have imported the key with fingerprint 01EA5486DE18A882D4C2684590C8019E36C2E964. That's the release signing key. Thanks for getting back to me, I must have done something wrong on importing the keys, I had missed that one somehow. Now I am getting this xxxxxxxxxxx$ gpg --verify SHA256SUMS.asc gpg: Signature made Tue 23 Aug 2016 16:23:26 CEST using RSA key ID 36C2E964 gpg: Good signature from "Wladimir J. van der Laan (Bitcoin Core binary release signing key) < laanwj@gmail.com>" gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: 01EA 5486 DE18 A882 D4C2 6845 90C8 019E 36C2 E964 I have a warning on the output now, is this something I should worry about? Or can I now safely assume I have correct binary ? You can assume you have the correct binary because the signature is good. However, the warning means that you personally have not trusted this key. Ideally you would meet up with Wladimir and he would show you his ID and his key fingerprint and prove to you that he is in control of the key. However, since that isn't likely to happen, you can check who else has signed his key, and if you trust them, you can set your own trust on his key. |
|
|
|
Really? That is quite strange. It works for me on multiple systems. The history is never written to the disk so it should not persist across instances of Bitcoin Core.
Not sure about being written to disk, but it definitely had to read it from the disk. My only explanation so far would be, that some old version of bitcoin core did write this. I have not yet restarted my server since I found out with the 0.13.0, I actually cannot claim id does write something to the disk. But as I have restarted Bitcoin core several times on the running server (uptime like 2 days), I can confirm that the history stored on disk - obviously, but maybe from earlier versions - 0.13.0 did read on every startup. Let me check again: Yup. My bitcoin-qt definitely stores history to disk, as even garbage I put in, like walletpassphrase "shitty passphrase" timeoutappears again after I shutdown and restart my bitcoin-qt and then simply press arrow up. Rico Huh. That should never happen. Can you make a video of it please? I am not able to reproduce this. |
|
|
|
It should clear the history every time you restart Bitcoin Core. It doesn't do that when you close the debug window though.
(i found the pale blue (x)) unfortunately, v0.13.0.0-ga402396 (64-bit) doesn't clear the history at all. Not if I restart Bitcoin Core, not if restart the computer. Really? That is quite strange. It works for me on multiple systems. The history is never written to the disk so it should not persist across instances of Bitcoin Core. You're a programmer. You should submit a PR to fix this, or at the very least, open an issue and suggest it. The developers don't frequent this forum anymore.
Ok, I'll submit a press release.  Rico Pull requests: https://github.com/bitcoin/bitcoin/pulls |
|
|
|
I don't understand anything about this Bitcoin core. Some one should please help out.
It's a Bitcoin wallet. It requires downloading and syncing the entire blockchain. To run, just download, install, and run. It does everything automatically. |
|
|
|
By clicking the Clear Console button (shortcut: Control-L), which has the added benefit that your passphrase is no longer displayed right there on the screen, so why on Earth would you not clear it anyway if other people have access to your machine?  There is no "Clear Console button", but Control-L works. Thanks. It's the x in the circle on the top left of the debug window. I did not write other people have access to my machine, I wrote "when someone gained access". Big difference - you're welcome.
I will use Control-L from now on, but I still fail to see why this isn't default after bitcoin-qt has been closed, at least cleanse history from all critical or potentially critical information (passphrase, private keys etc.).
It should clear the history every time you restart Bitcoin Core. It doesn't do that when you close the debug window though. Quite a security risk IMHO, especially as I cannot recall to have read that big fat warning to "not forget doing Ctrl-L" after entering some sensitive information. Actually the help states Ctrl-L is for clearing the screen - not screen and history.
Rico
You're a programmer. You should submit a PR to fix this, or at the very least, open an issue and suggest it. The developers don't frequent this forum anymore. |
|
|
|
Well unfortunately I am not familiar with the Mac build process. I suggest that you go to https://github.com/bitcoin/bitcoin/issues and see if anyone else has had the same issue. If not, submit a new issue. I also recommend that you go to the #bitcoin-core-dev channel and ask them about this. The developers do not frequent this forum anymore so you aren't likely to get any support related to build issues here. |
|
|
|
|
Are all the dependencies up to date? Did you do make clean first to clean up any old build stuff?
|
|
|
|
2016-09-15 21:40 (ERROR) -- Traceback (most recent call last):
File "/usr/bin/../lib/armory/ArmoryQt.py", line 6635, in method_signal
method()
File "/usr/bin/../lib/armory/ArmoryQt.py", line 6672, in completeBlockchainProcessingInitialization
gotDB = self.startArmoryDBIfNecessary()
File "/usr/bin/../lib/armory/ArmoryQt.py", line 2198, in startArmoryDBIfNecessary
spawnId = TheSDM.spawnDB(TheBDM.armoryDBDir)
File "/usr/lib/armory/SDM.py", line 513, in spawnDB
launchProcess(pargs, **kargs)
File "/usr/lib/armory/armoryengine/ArmoryUtils.py", line 642, in launchProcess
return Popen(cmd, stdin=PIPE, stdout=PIPE, stderr=PIPE, *args, **kwargs)
File "/usr/lib/python2.7/subprocess.py", line 710, in __init__
errread, errwrite)
File "/usr/lib/python2.7/subprocess.py", line 1327, in _execute_child
raise child_exception
OSError: [Errno 2] No such file or directory
2016-09-15 21:40 (INFO) -- ArmoryQt.py:5641 - Dashboard switched to "Scanning" mode Armory seems to hang on preparing the database. I'm not sure what it thinks is missing. All the files seem to be there. It looked like some of the files were missing when I was checking manually, but I've uninstalled/reinstalled using the deb files, reset the db and settings several times and everything seems to be there. Any ideas? It looks like it's unable to start ArmoryDB. Can you try running |
|
|
|
What's with the red warning stamped over all my PM to other fellow members?
Many new accounts in the past have been used to attempt to scam other people by impersonating high ranking members. The warning is to help prevent people from falling victim to such scams. While those users can be banned, it takes time for moderators to notice them and ban them. What about helping the people new yo cryptocurrencies instead of govong the "im senior so im well versed in this area of interest, i stick my nose and poke at every posts all day, comment for the sole purpose of commenting not aiming to help whatever the discission or subject matter is about, enjoys picking errors like typos to make the posters look as stupid as possible thus making myself a class above the ppl i belittled. I'm guessing these pointless non constructive posts not even helping with the subject matter earns u precious activity points which in turn aid with the promotion?
Use the ignore function. Then you don't have to read all that stuff. How about a full time job outside the forum., or screwing your girlfriends whenever youre bored? Now i bet youre not too familiar with what im saying.... [/b]
Most people here are a bunch of nerds... so what's a social life? Im here in this crappiest of forums only becauae i encountered some crypto related problems.
Looking through your post history, you have not encountered any crypto related problems. What you have encountered are scams, gambling websites, and shitty services. Not really crypto problems. Just trying to resolve problems. If i have a choice i rather not here, the replies ice gotten from my first forum participation onward i knew this place isnt my kind of place. I thought seniors are supposed to lend juniors a helping hand because of their experience? Here though i noticed most are just trying to prove they know more and they have to be better. A bunch of crap so full of yourselves probably your lifes evolves aroundbthis place as well. Lol
Most people who are posting are spamming anyways. I was wondering why my earlier attempt to look for my missing deposit is leading nowhere. Then i notice the big red warning stamped over my pm to enquire about the issues i wanted to resolve.
*Sigh* Im guessing some ppl are creating accounts and inpersonating some of you seniors from the looks of it? It sure is wrong and annoying for with impersonator running around pretending to becsomeone they are not. Not to mention they may also be crimes being commited by the imprrsonators.
But my question is, impersonators created accounts to disguise as as someone else what about the real newbies? Now newbies are all suspicious of being impersonators as well? That really proves my point just how much is in that forum head of yours.
How does that prove any point? Theymos added those because of impersonation issues with many accounts impersonating some very trusted members in order to scam people. The warning is removed after you stop being a newbie (because if you're an impersonator, you will never get that far; you'll be banned). Sigh...no wonder my emails to relevant parties regarding my issues nevervgotten any response. Thanks but no thanks....these seniors are so full of themselves are they doing or teaching anyone anything useful, crypto related?
If you actually want to have a discussion about something crypto or technical related (but I don't think you actually do), then post in the Development and Technical section because that's where there aren't spammers. |
|
|
|
Reason why I want to know, is because I want to work with 2 systems; 1 offline, and 1 online. On my offline system, I want to create the addresses I need. Through my online system, I want to send my coins to those addresses. But if I create an address on an offline system that never connects to the net, I'm not entirely sure that address will 100% be mine (because to my logic, that address never gets propagated to the network and thus maybe someone somewhere could generate the exact same address?).
It doesn't matter either way, wallets do not check whether a newly generated address has been used before, and there is nothing to "register" and address to. Wallets assume an address is new because they assume that the PRNG is not broken and that fact that the probability of an address collision is ridiculously low. Also, having to search through the entire blockchain for all of the known addresses would take a while and use up a lot of computing resources. |
|
|
|
|
You have to do work. Bitcoin isn't a magic internet money, you have to earn it the exact same way that you would earn any other money. Anyone claiming that you can double your Bitcoin with no work at all is lying and a scammer.
|
|
|
|
Hi
So I executed ArmoryDB, and I still get the same error, I think the problem might come from the _CppBlockUtil.so file,
which I can't view.
I also tried running armoryd.py and it gave me th same problem.
Now I am just stuck.
Try running ArmoryQt first. There's a good chance that Armoryd and the other example scripts don't work anymore due to large architectural changes that just happened. |
|
|
|
You only paid 0.00004195BTC fee for 373 bytes transaction, of course it'll take long. If you've sent many transactions like that and never got this problem then that's what's surprising.
As I said I typically pay whatever fee the core client suggests, and that is what I did here. So if you click the Choose... button next to Transaction Fee, you will get some more detailed selection about the transaction fee. The normal fee (which is probably what you have it set to), is actually an estimate to get a confirmation within the next 25 blocks. So if you actually want faster confirmations, you need to move the slider to the right towards "fast". Moreover blockchain.info describes expected confirmation for this transaction as "Very Soon (High Priority)"  - though I do not know on what basis it makes that assessment. Their assessment is highly inaccurate. I recommend that completely disregard it and never think of it again. Well yes I understand that thank you but given the number of full blocks we have seen in quick succession (there have now been 8 blocks exceeding 998 kB) I imagine the backlog of transactions must be quite large, and how much extra would one have to pay to actually make a difference?
You just need to pay more than the lowest paying transaction in the block. You would effectively bump that transaction out with yours. |
|
|
|
I remember there was what sounded like a sensible discussion on refactoring bitcoind into two distinct modular programs, namely one that does the network/verification logic (bitcoin_node) and another which is the reference wallet (bitcoin_wallet) that speaks to bitcoin_node.
Is this still the plan and/or is anyone already working on it?
AFAIK, no. |
|
|
|
|
Try starting Bitcoin Core with the -reindex option. If that doesn't work, go to the data directory and delete the chainstate and databases folders.
|
|
|
|
Hi everyone,
So I am busy testing v0.94.99 now and the first script I tried was the BDMbasics_watchBalance.py script, and I am getting this error
Traceback (most recent call last):
File "BDMbasics_watchBalance.py", line 60, in <module>
wlt.registerWallet(isNew=False)
File "../armoryengine/PyBtcWallet.py", line 284, in registerWallet
self.cppWallet = TheBDM.registerWallet(prefixedKeys, self.uniqueIDB58, isNew)
File "../armoryengine/BDM.py", line 116, in inner
return func(*newArgs, **kwargs)
File "../armoryengine/BDM.py", line 246, in registerWallet
return self.bdv().registerWallet(uniqueIDB58, prefixedKeys, isNew)
File "../CppBlockUtils.py", line 1393, in registerWallet
def registerWallet(self, *args): return _CppBlockUtils.BlockDataViewer_registerWallet(self, *args)
<class 'CppBlockUtils.DbErrorMsg'>: <CppBlockUtils.DbErrorMsg; proxy of <Swig Object of type 'DbErrorMsg *' at 0x7f455a913480> >
Anybody got a similar error and solved it?
Start ArmoryDB in another shell. Then try again. |
|
|
|
It's up again.
and it's down. And it's up again. My server must really hate me. |
|
|
|
Cannot update using the URL on Ubuntu 16.04 LTS. Please fix  How are you not able to update? Please elaborate. What happens? |
|
|
|
|
Show Posts
