|
Today is "El Salvador day," so there's lots of news and lots of trading.
According to blockchain.info, block 699509 was timestamped 17:00 UTC and 699510 was timestamped 18:06 UTC -- a 66-minute interval. Isn't that quite unusual? If so, what might have been the cause?
|
|
|
|
You replied to a topic which was inactive for more than 4 years. Your post was probably reported by someone and deleted because it was considered as spam or due to necro-bumping (making a useless post on a thread which has been inactive for a very long time.) Nice monitor! However, it doesn't display peers having .onion (Tor) addresses. I made that post because I thought it would be quite useful to someone like ... me! The topic subject is a remote GUI monitor for bitcoind (or -qt). Evidently this freeware open-source software got little attention and use, but it looked like exactly what I needed so I spent non-trivial time installing it. For users who don't care about the deficiency I noted it's a "nice monitor!" For those, like me, who do, it's disappointing. I have no connection with the author. Thanks for the explanation, although in this instance I'm not persuaded by the rationales. If the thread is too old to take replies, I'm not sure why the OP isn't deleted. There's no need to get into the weeds on this, but my suggestion stands.
|
|
|
|
A reply of yours, quoted below, was deleted by a Bitcoin Forum moderator. Posts are most frequently deleted because they are off-topic, though they can also be deleted for other reasons. In the future, please avoid posting things that need to be deleted. May I suggest that, when the reasons are "other" that some guidance be provided so that I may "avoid posting things that need to be deleted"? The quoted email reports on a reply which was definitely on-topic, and I have no idea why it was deleted. I understand that mods don't want to get into discussions of, i.e., arguments about, such decisions but might some variations of the boilerplate be assembled to provide a clue?
|
|
|
|
Indeed... assumption is the mother of all fuck ups  May I ask what lead to you assuming that Bitcoin Core would just use Tor by default? I'm curious to know if there is a learning opportunity here for everyone.  It was a stupid misreading, out of context, of some phrase like "Bitcoin Core v0.12 and later automatically tries to connect to Tor" [following context omitted; in https://en.bitcoin.it/wiki/Setting_up_a_Tor_hidden_service], but I'm not sure that precisely was the source.
|
|
|
|
You're not using Tor. Bitcoin Core cannot connect to the Tor instance, are you running Tor at all?
You have to use -onlynet=onion and -bind=127.0.0.1 to force Bitcoin Core to only connect to onion nodes and for incoming connections to go through Tor. If done correctly, bitcoin-cli getnetworkinfo should return reachable for onion and have a network score. [...]
I'm sure tor is running. E.g., it shows in ps output and I can get Firefox to use tor by setting it to use tor's Socks proxy. As mentioned in the OP I presumed Core uses tor by default even with no (relevant) changes to bitcoin.conf or to tor's configuration (torrc). I now know, with the prodding of your and other responses here, that presumption was incorrect. Thanks!
|
|
|
|
|
Installed Bitcoin Core 0.21.1 on a Ubuntu system, copied over the contents of the .bitcoin directory (including blockchain data) from another system on which I'd been running Core for years. Installed Tor, with which I've no prior experience. Started bitcoin-qt having only these parameters in ~/.bitcoin/bitcoin.conf: dbcache=1024 datadir=[path to .bitcoin data directory on volume different from /home volume] debug=tor
I presumed that Core defaults to using Tor for its output.
There were a sizeable number of connections, both in and out, and my blockchain was brought up to date. The only evidence I see of Tor in debug.log is numerous periodic instances of: tor: Error connecting to Tor control socket tor: Not connected to Tor control port 127.0.0.1:9051, trying to reconnect
--until I closed bitcoin-qt, which generated: tor: Thread interrupt Shutdown: In progress... addcon thread exit torcontrol thread exit
In neither the "New outbound peer connected" entries in debug.log nor in the Peers window did I see anything that specifically indicated Tor to me, but then I don't know what I'm looking for. I retained the debug.log and screenshots of the Peers window for review. I can issue CLI commands if helpful.
|
|
|
|
I was able to import this one, thanks! (And I was able to independently verify that it's ThomasV's key). Then, however... In that procedure, at this step... Download the Electrum image file and the associated signature file. Open a Finder window, navigate to the location where you saved the Electrum .dmg file and the .asc signature file, and double click the signature file. ...all that happened was that it imported the key (again, with no apparent harm). What did not happen was what the procedure said would happen: Mac GPG will launch the verification tool, and compare the .dmg file to the signature file. Once the verification tool has completed its diagnostic it'll pop up a [results window].
Update: gpg --verify Downloads/electrum-4.1.5.dmg.ThomasV.asc Downloads/electrum-4.1.5.dmg gpg: Signature made Mon Jul 19 11:22:27 2021 PDT gpg: using RSA key 6694D8DE7BE8EE5631BED9502BD5824B7F9470E6 gpg: Good signature from "Thomas Voegtlin ( https://electrum.org) < thomasv@electrum.org>" [unknown] gpg: aka "ThomasV < thomasv1@gmx.de>" [unknown] gpg: aka "Thomas Voegtlin < thomasv1@gmx.de>" [unknown] gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. The .asc (PGP signature) file for that command was the one downloaded from the Electrum site -- the one that I cannot import into GPG. But if I try to use the one @NeuroticFish kindly provided, which I can import, I get: gpg --verify Downloads/ThomasV.asc Downloads/electrum-4.1.5.dmg gpg: verify signatures failed: Unexpected error [moderator's note: consecutive posts merged]
|
|
|
|
Thanks, but the first thing I did was try to follow that procedure, which is linked to on the Electrum download page. At this step... The Electrum site reports his key ID as 0x2bd5824b7f9470e6. Use this value to look up Voegtlin’s public key. Click the GPG Keychain “Lookup Key” button and enter the developer key ID. The[n] click Search. ...I get the result "No keys found."
|
|
|
|
MacOS 11.5.1 I have PGPTools installed, but I thought showing CLI results would be useful here. In case it's not obvious, I'm not sophisticated w/r PGP. ~ % gpg --verify Downloads/electrum-4.1.5.dmg.ThomasV.asc Downloads/electrum-4.1.5.dmg gpg: Signature made Mon Jul 19 11:22:27 2021 PDT gpg: using RSA key 6694D8DE7BE8EE5631BED9502BD5824B7F9470E6 gpg: key 2BD5824B7F9470E6: new key but contains no user ID - skipped gpg: Total number processed: 1 gpg: w/o user IDs: 1 gpg: Can't check signature: No public key
~ % gpg --import Downloads/electrum-4.1.5.dmg.ThomasV.asc gpg: no valid OpenPGP data found. gpg: Total number processed: 0
% cat Downloads/electrum-4.1.5.dmg.ThomasV.asc -----BEGIN PGP SIGNATURE-----
iQIzBAABCgAdFiEEZpTY3nvo7lYxvtlQK9WCS3+UcOYFAmD1wuMACgkQK9WCS3+U [... omitted for brevity ...] 7CDdNAheFpE+xz2F3JSeXrWBHnnYP3k/bVMJwSmSgrvxVRzPpfM= =K00C -----END PGP SIGNATURE-----
|
|
|
|
Hi, just thinking here, when we first setup the nano it gives us a recovery seed right. Then we add our wallets via the app manager. Wouldn't that mean every wallet install I would get a different private key (ie bitcoin and neo couldn't have the same private key). ... TL;DR: The recovery seed is used to (re)generate a master seed, from all the private seeds for one or more coin types are derived in a deterministic fashion. Ledger Nano S is a Hierarchical Deterministic (HD) wallet.
|
|
|
|
In the end you still need internet connection to use your bitcoin.
So what? With a hardware wallet your private keys are never exposed to an internet connection. This is not true of a smartphone wallet.
|
|
|
|
To use bitcoin then an internet connection is a must, don't you know that basic? Bitcoin is a digital currency in the first place.
To send and receive requires internet. Hardware wallets do not connect to the internet, but they can connect to a computer via USB and the computer can connect to the internet. The user's private keys never leave the hardware wallet; the hardware wallet can generate receiving addresses and sign send transactions. With a smartphone, the device storing private keys is directly connected to the internet, even if only temporarily.
|
|
|
|
Yes, that statement is inaccurate. That is there because that dialog usually only appears for the first run of the software, but we recycled it for when you reset the gui settings as well.
Thanks; all is now well. One last (I hope!) question: should I use -resetguisettings on subsequent runs of 0.15.0?
|
|
|
|
Mac OS 10.10.5 (Yosemite) After getting the crash discussed in this thread, I tried the suggested remedy: Applications $ Bitcoin-Qt.app/Contents/MacOS/Bitcoin-QT -resetguisettings ...which brings up a "Welcome to Bitcoin Core" dialog box that says since this is the first time the program's been launched the entire blockchain will be downloaded. I guess I can do that, but <whine>do I have to</whine>? Did I misapply the remedy by trying it only after running 0.15.0 without it and getting the crash, instead of on the first run? If you had chose a custom your data directory the first time you ran Bitcoin Core, this behavior is expected. It is to ensure that you choose the same data directory again so that you don't have to download the blockchain again. If you do use the same datadir, then it won't download the blockchain again. I can't recall what I did the first time I ran Core years ago, but the current dialog box has the "Use the default..." radio button pre-selected, the "Use a custom data directory..." button not selected, and "/Users/[me]/Library/Application Support/Bitcoin" in the field in which a custom directory can be specified. (Entry in that field is disabled unless the custom directory button is clicked.) That is in fact where the data is, and indeed the dialog box says under that field, "Directory already exists. Add /name if you intend to create a new directory here." Then outdented underneath that, "When you click OK, Bitcoin Core will begin to download and process the full Bitcoin block chain..." Is the latter statement inaccurate in my case?
|
|
|
|
Mac OS 10.10.5 (Yosemite) After getting the crash discussed in this thread, I tried the suggested remedy: Applications $ Bitcoin-Qt.app/Contents/MacOS/Bitcoin-QT -resetguisettings ...which brings up a "Welcome to Bitcoin Core" dialog box that says since this is the first time the program's been launched the entire blockchain will be downloaded. I guess I can do that, but <whine>do I have to</whine>? Did I misapply the remedy by trying it only after running 0.15.0 without it and getting the crash, instead of on the first run?
|
|
|
|
EDIT: However... proofer@prooferminer:~/miners/cgminer$ DISPLAY=:0 fglrxinfo X Error of failed request: BadRequest (invalid request code or no such operation) Major opcode of failed request: 153 (GLX) Minor opcode of failed request: 19 (X_GLXQueryServerString) Serial number of failed request: 12 Current serial number in output stream: 12 SOLVED  Problem summary: Upgraded Ubuntu to 12.04; found that AMD Catalyst 11.12 driver (a.k.a. fglrx 8.92) is incompatible with Xorg X server 1.13.0, which is in 12.04.2, which is the current release of 12.04 LTS (Precise Pangolin). There was also an issue of 12.04.2 having kernel 3.5, which is incompatible with Catalyst 11.12's installer; it wants kernel 3.2. Solution: install 12.04.1, which has xserver 1.11.3 and kernel 3.2. Even after running Software Updater, which updates to 12.04.2, xserver stays at 1.11.3 and the kernel stays at 3.2. 12.04.1 is available here.
|
|
|
|
? sudo aticonfig --initial -f --adapter=all Yes, I had done that prior to the results I showed. I was following the procedure from the Unofficial Wiki for the AMD Linux Driver. I used the commands to create fglrx .deb packages from the AMD Catalyst 11.12 download and install the packages, plus aticonfig etc. and of course the usual (which I put in here a few days ago) To see that your display is correct: export DISPLAY=:0 xlsfonts
That returns a long list of fonts. EDIT: However... proofer@prooferminer:~/miners/cgminer$ DISPLAY=:0 fglrxinfo X Error of failed request: BadRequest (invalid request code or no such operation) Major opcode of failed request: 153 (GLX) Minor opcode of failed request: 19 (X_GLXQueryServerString) Serial number of failed request: 12 Current serial number in output stream: 12
|
|
|
|
I was mining OK with Ubuntu 11.04 and Catalyst 11.06. After upgrading to Ubuntu 12.04 and Catalyst 11.12, I built the current cgminer from source, which has been my usual practice. Two problems: 1. The system is not detecting my display monitor's characteristics and is using a generic "laptop" monitor config with the wrong resolution. This is not a big problem, but I'm mentioning it here in case it's a clue. 2. cgminer 2.11.3 is not seeing my three 5970 GPUs: proofer@prooferminer:~/miners/cgminer$ aticonfig --lsa * 0. 13:00.0 ATI Radeon HD 5900 Series 1. 12:00.0 ATI Radeon HD 5900 Series 2. 0b:00.0 ATI Radeon HD 5900 Series 3. 0a:00.0 ATI Radeon HD 5900 Series 4. 07:00.0 ATI Radeon HD 5900 Series 5. 06:00.0 ATI Radeon HD 5900 Series
* - Default adapter proofer@prooferminer:~/miners/cgminer$ xhost + &> /dev/null proofer@prooferminer:~/miners/cgminer$ DISPLAY=:0 cgminer -n [2013-03-22 20:29:53] CL Platform 0 vendor: Advanced Micro Devices, Inc. [2013-03-22 20:29:53] CL Platform 0 name: AMD Accelerated Parallel Processing [2013-03-22 20:29:53] CL Platform 0 version: OpenCL 1.1 AMD-APP (831.4) [2013-03-22 20:29:53] Error -1: Getting Device IDs (num) [2013-03-22 20:29:53] clDevicesNum returned error, no GPUs usable [2013-03-22 20:29:53] 0 GPU devices max detected I'm stumped. 
|
|
|
|
I use Catalyst 11.12 and SDK 2.5 on Ubuntu 12.04 (phatk kernel). It took me a long time to figure out how to install both of them properly. Unless you're using 7000 series cards, I'd recommend this combo.
I just upgraded from 11.04 to 12.04 and am in the throes of trying to figure out what you figured out. After about 24 hours of messing around I'm just about to re-install 12.04 to get a clean slate. Do any memories/hints/notes come to mind?
|
|
|
|
|
I just upgraded p2pool from 11.1 to 11.2, and am informed that I need to update twisted. I'm running Ubuntu 11.04. Synaptic shows that I have python-twisted 10.2.1 installed and also indicates that is the latest version. Does this mean I must upgrade Ubuntu or ... ?
|
|
|
|
|