Miko
Newbie
 Offline
Activity: 4
Merit: 0
|
 |
September 24, 2015, 04:05:39 PM |
|
Danke für deine Ausführungen Onkel Paul! Wenn ich es richtig verstanden habe brauche (muß) ich nur abzuwarten bis die Kette durch ist dann kommt auch das Geld. Ist das lange warten nur einmalig oder muss ich bei jeder Transaktion die ganze Kette abwarten? Miko Bitcoin core needs to store the whole blockchain on your hard disk. Downloading (and verifying) that amount of data takes quite some time, that's right.
Currently there's no easy way around this with bitcoin core, other wallets such as Electrum don't store the full blockchain but rely on external services for blockchain access. This is much faster for initial setup, but at the moment, this is not an option for you because you already sent funds from coinBase to an address within your bitcoin core wallet. So you'll definitely want to keep that running until you have full control over your funds.
It might be possible to export the private key for the address to which you sent your coinBase funds, and import this into another wallet which you can use sooner, but I don'd really have experience in this, so I won't advise you to do this. If you find someone who can explain this process and lead you through it, that might be an option, though.
Onkel Paul
|
|
|
|
|
shorena
Copper Member
Legendary
Offline
Activity: 1498
Merit: 1520
No I dont escrow anymore.
|
|
September 24, 2015, 04:47:25 PM |
|
Danke für deine Ausführungen Onkel Paul! Wenn ich es richtig verstanden habe brauche (muß) ich nur abzuwarten bis die Kette durch ist dann kommt auch das Geld. Ist das lange warten nur einmalig oder muss ich bei jeder Transaktion die ganze Kette abwarten? Miko Bitcoin core needs to store the whole blockchain on your hard disk. Downloading (and verifying) that amount of data takes quite some time, that's right.
Currently there's no easy way around this with bitcoin core, other wallets such as Electrum don't store the full blockchain but rely on external services for blockchain access. This is much faster for initial setup, but at the moment, this is not an option for you because you already sent funds from coinBase to an address within your bitcoin core wallet. So you'll definitely want to keep that running until you have full control over your funds.
It might be possible to export the private key for the address to which you sent your coinBase funds, and import this into another wallet which you can use sooner, but I don'd really have experience in this, so I won't advise you to do this. If you find someone who can explain this process and lead you through it, that might be an option, though.
Onkel Paul
Du musst jedes mal synchronisieren. Das kann am Anfang ein paar Tage dauern, aber danach muss nur noch synchronisiert werden was Du "verpasst" hast während bitcoin core geschlossen war. Wenn Du also jeden Tag einmal synchronisieren lässt ist das relativ übersichtlich und sollte nicht länger als 15 minuten dauern. Wie lange genau hängt von der Festplatte der CPU und deiner Internetverbindung ab. Für alles weitere auf Deutsch, bitte hier -> https://bitcointalk.org/index.php?board=16.0 im deutschen Bereich posten. --- English translation: The sync has to be done every time, but only the first sync tages up to a gew days. Every further sync only has to catch up to the latest blocks which is significantly faster. If you sync once a day it should not take longer than ~15 minutes, depending on disk, CPU and internet connection. |
Im not really here, its just your imagination.
|
|
|
|
wwwin
|
|
September 25, 2015, 04:43:02 AM |
|
Danke für deine Ausführungen Onkel Paul! Wenn ich es richtig verstanden habe brauche (muß) ich nur abzuwarten bis die Kette durch ist dann kommt auch das Geld. Ist das lange warten nur einmalig oder muss ich bei jeder Transaktion die ganze Kette abwarten? Miko Bitcoin core needs to store the whole blockchain on your hard disk. Downloading (and verifying) that amount of data takes quite some time, that's right.
Currently there's no easy way around this with bitcoin core, other wallets such as Electrum don't store the full blockchain but rely on external services for blockchain access. This is much faster for initial setup, but at the moment, this is not an option for you because you already sent funds from coinBase to an address within your bitcoin core wallet. So you'll definitely want to keep that running until you have full control over your funds.
It might be possible to export the private key for the address to which you sent your coinBase funds, and import this into another wallet which you can use sooner, but I don'd really have experience in this, so I won't advise you to do this. If you find someone who can explain this process and lead you through it, that might be an option, though.
Onkel Paul
Vielen Dank |
|
|
|
|
|
Andrelvogue
|
|
September 28, 2015, 07:18:58 AM |
|
This is kinda handy thank you for the update and sharing this. |
|
|
|
|
Mikestang
Legendary
Offline
Activity: 1274
Merit: 1000
|
|
October 05, 2015, 07:19:31 PM |
|
So while I was re-syncing the blockchain over the weekend (every time my computer loses power my local copy of the blockchain becomes corrupt, kind of annoying) and I noticed that my USB miners, specifically my U3, freak out while core is syncing. The U3 is a crazy machine to begin with, but I was really surprised to see it basically be unable to hash while the sync was taking place. It would have HW errors more than 20%, hash rate would gradually fall and fall and fall if I left it running, so I killed it until the sync was done and now it's back to running, well I hesitate to say good, but it's running as good as a U3 is expected to.
|
|
|
|
|
|
Icon
|
|
October 08, 2015, 06:52:20 PM |
|
So any reason why the windows 64 bit version is now eating up over 2 gb of system ram while running..?
All my other QT clients ltc/huc only use ~ 400 mb of ram while running
Icon
|
|
|
|
|
egghead123
Legendary
Offline
Activity: 1330
Merit: 1000
|
|
October 15, 2015, 12:29:16 PM |
|
Vulnerability in UPnP library used by Bitcoin Core.An exploitable buffer overflow vulnerability exists in the XML parser functionality of the MiniUPnP library. A specially crafted XML response can lead to a buffer overflow on the stack resulting in remote code execution. An attacker can set up a server on the local network to trigger this vulnerability.  |
|
|
|
|
Lauda
Legendary
Offline
Activity: 2674
Merit: 2965
Terminated.
|
|
October 15, 2015, 02:18:13 PM
Last edit: October 15, 2015, 02:28:38 PM by Lauda |
|
Vulnerability in UPnP library used by Bitcoin Core.An exploitable buffer overflow vulnerability exists in the XML parser functionality of the MiniUPnP library. A specially crafted XML response can lead to a buffer overflow on the stack resulting in remote code execution. An attacker can set up a server on the local network to trigger this vulnerability. It is not a big deal. You can't just easily access someones local network. Just upgrade to 0.11.1 and ignore it. Besides a quick workaround was posted as soon as that was discovered. |
"The Times 03/Jan/2009 Chancellor on brink of second bailout for banks" 😼 Bitcoin Core ( onion) |
|
|
Mikestang
Legendary
Offline
Activity: 1274
Merit: 1000
|
|
October 15, 2015, 04:56:32 PM |
|
Vulnerability in UPnP library used by Bitcoin Core.An exploitable buffer overflow vulnerability exists in the XML parser functionality of the MiniUPnP library. A specially crafted XML response can lead to a buffer overflow on the stack resulting in remote code execution. An attacker can set up a server on the local network to trigger this vulnerability. Upgrade to 0.11.1 and this is no concern. Or you can uncheck the upnp box in the config settings and the vulnerability is negated. |
|
|
|
|
|
Pyr3x
|
|
October 15, 2015, 11:03:30 PM |
|
Vulnerability in UPnP library used by Bitcoin Core.An exploitable buffer overflow vulnerability exists in the XML parser functionality of the MiniUPnP library. A specially crafted XML response can lead to a buffer overflow on the stack resulting in remote code execution. An attacker can set up a server on the local network to trigger this vulnerability. What versions does this affect? |
|
|
|
shorena
Copper Member
Legendary
Offline
Activity: 1498
Merit: 1520
No I dont escrow anymore.
|
|
October 16, 2015, 04:17:40 AM |
|
Vulnerability in UPnP library used by Bitcoin Core.An exploitable buffer overflow vulnerability exists in the XML parser functionality of the MiniUPnP library. A specially crafted XML response can lead to a buffer overflow on the stack resulting in remote code execution. An attacker can set up a server on the local network to trigger this vulnerability. What versions does this affect? all, but 0.11.1 and 0.10.3 |
Im not really here, its just your imagination.
|
|
|
Meuh6879
Legendary
Offline
Activity: 1512
Merit: 1011
|
|
October 21, 2015, 11:23:07 AM |
|
|
|
|
|
|
|
Pyr3x
|
|
October 21, 2015, 12:19:33 PM |
|
Vulnerability in UPnP library used by Bitcoin Core.An exploitable buffer overflow vulnerability exists in the XML parser functionality of the MiniUPnP library. A specially crafted XML response can lead to a buffer overflow on the stack resulting in remote code execution. An attacker can set up a server on the local network to trigger this vulnerability. What versions does this affect? all, but 0.11.1 and 0.10.3 Thanks, I will update all my nodes. |
|
|
|
|
