davec
Newbie
Offline
Activity: 39
Merit: 0
|
|
September 18, 2014, 03:13:00 AM |
|
What is going on here? Is this a BUG? There was a bug in the upstream leveldb that could rarely lead to what you're seeing and was fixed a while back. There hasn't been a new Windows msi released yet. You can build from source quite easily with Go on Windows if you want to build with the latest code. There will be another msi release soon which includes that fix along with several other enhancements.
|
|
|
|
T-rage_11
Member
Offline
Activity: 74
Merit: 10
www.btcaudio.eu || LIVE-AUDIO-TICKER
|
|
September 18, 2014, 12:08:30 PM |
|
What is going on here? Is this a BUG? There was a bug in the upstream leveldb that could rarely lead to what you're seeing and was fixed a while back. There hasn't been a new Windows msi released yet. You can build from source quite easily with Go on Windows if you want to build with the latest code. There will be another msi release soon which includes that fix along with several other enhancements. I just built on Windows XP x86 AND Windows 8.1 x64 .. BUT the bug is STILL HERE !? Is it normal that my new .exe builds are smaller than the "original" ones? they are just 12 MB (x86) and 15MB (x64) big! original x64 = 18MB
|
|
|
|
davec
Newbie
Offline
Activity: 39
Merit: 0
|
|
September 18, 2014, 02:54:34 PM Last edit: September 18, 2014, 03:32:06 PM by davec |
|
I just built on Windows XP x86 AND Windows 8.1 x64 .. BUT the bug is STILL HERE !?
Is it normal that my new .exe builds are smaller than the "original" ones? they are just 12 MB (x86) and 15MB (x64) big! original x64 = 18MB
You'll need to delete your database from "%LOCALAPPDATA%\Btcd\data\mainnet", so the chain download starts over. The issue is your existing database is corrupt (hence why you're seeing the issue looking up a specific transaction), so only upgrading the code alone won't fix it. However, the root cause that led to the corruption to begin with is what updating the code resolves. I should have mentioned that in my original response. As far as the size, the last released msi was built with the Go 1.2 runtime, and I'm guessing you built the latest with the most recent Go 1.3.1 run-time, so a difference in size is expected. 12MB (x86) and 15MB (x64) is what I have as well with the go 1.3 runtime. EDIT: I just rebuilt to verify: x6409/18/2014 10:13 AM 15,415,296 btcd.exe x8609/18/2014 10:15 AM 12,524,544 btcd.exe
|
|
|
|
T-rage_11
Member
Offline
Activity: 74
Merit: 10
www.btcaudio.eu || LIVE-AUDIO-TICKER
|
|
September 18, 2014, 03:23:40 PM Last edit: September 19, 2014, 11:03:59 AM by T-rage_11 |
|
I just built on Windows XP x86 AND Windows 8.1 x64 .. BUT the bug is STILL HERE !?
Is it normal that my new .exe builds are smaller than the "original" ones? they are just 12 MB (x86) and 15MB (x64) big! original x64 = 18MB
You'll need to delete your database from "%LOCALAPPDATA%\Btcd\data\mainnet", so the chain download starts over. The issue is your existing database is corrupt (hence why you're seeing the issue looking up a specific transaction), so only upgrading the code alone won't fix it. However, the root cause that led to the corruption to begin with is what updating the code resolves. I should have mentioned that in my original response. As far as the size, the last released msi was built with the Go 1.2 runtime, and I'm guessing you built the latest with the most recent Go 1.3.1 run-time, so a difference in size is expected. 12MB (x86) and 15MB (x64) is what I have as well with the go 1.3 runtime. EDIT: I just rebuilt to verify: x6409/18/2014 10:13 AM 15,415,296 btcd.exe x8609/18/2014 10:15 AM 12,524,544 btcd.exe thanks my x64 buildEDIT: AFTER SOME HOURS I GET THE "Adding orphan blocks"-BUG AGAIN
|
|
|
|
pmorris
Newbie
Offline
Activity: 21
Merit: 0
|
|
September 18, 2014, 05:59:08 PM |
|
I recently switched from running bitcoind to btcd on linux.
Once golang was installed it’s pretty much an automated installation process – 1 command to auto download and install the btcd package. A well-documented sample config file is provided that was easy to tailor. Launched it and done.
Full network sync from scratch took 26 hours. Memory usage is in the 200MB range. Couple of days in it’s been rock solid and seems to be working great.
I’m hugely impressed with what the devs have achieved. Their code appears to be clean, modular, well documented and comprehensively covered by tests. So a great base to build on.
|
|
|
|
T-rage_11
Member
Offline
Activity: 74
Merit: 10
www.btcaudio.eu || LIVE-AUDIO-TICKER
|
|
September 20, 2014, 11:23:52 PM Last edit: September 25, 2014, 10:28:16 PM by T-rage_11 |
|
I am trying the new btcd v0.9.0-beta now .. https://github.com/conformal/btcd/releasesEDIT: x64 version v0.9.0-beta EDIT2: PROBLEM SOLVED ! NO BUG ! JUST A BAD HARD DISK !
|
|
|
|
davec
Newbie
Offline
Activity: 39
Merit: 0
|
|
September 21, 2014, 07:04:19 PM |
|
Would you please file an issue on the btcd issue tracker? We'll need to get your database logs to track down your issue.
|
|
|
|
zznbey
Member
Offline
Activity: 112
Merit: 10
|
|
September 21, 2014, 07:09:05 PM |
|
as if dependence on a bunch of profiteers would be a good thing.
|
Bitnet. Vx8pzeLKG3FNV9CKikh6RXp7gDRKnH1Pea
|
|
|
davec
Newbie
Offline
Activity: 39
Merit: 0
|
|
September 21, 2014, 08:23:58 PM Last edit: September 21, 2014, 09:58:33 PM by davec |
|
zznbey:
I'm not sure what point you're trying to make, but I think perhaps you are confused. The btcd code is ISC licensed and freely available for all to fork and modify as they see fit. It is no different than Bitcoin Core in that respect.
|
|
|
|
johnnyrocket
|
|
September 21, 2014, 09:57:54 PM |
|
I recently switched from running bitcoind to btcd on linux.
Once golang was installed it’s pretty much an automated installation process – 1 command to auto download and install the btcd package. A well-documented sample config file is provided that was easy to tailor. Launched it and done.
Full network sync from scratch took 26 hours. Memory usage is in the 200MB range. Couple of days in it’s been rock solid and seems to be working great.
I’m hugely impressed with what the devs have achieved. Their code appears to be clean, modular, well documented and comprehensively covered by tests. So a great base to build on.
I've also recently tested btcd out, and the code looks clean + tests are present. I do see better performance than bitcoind, as well. Keep up the good work!
|
|
|
|
T-rage_11
Member
Offline
Activity: 74
Merit: 10
www.btcaudio.eu || LIVE-AUDIO-TICKER
|
|
September 26, 2014, 02:12:30 PM |
|
Can you subscribe to new unconfirmed transactions with btcd ?like the blockchain API: https://blockchain.info/de/api/api_websocketI currently use the blockchain API for my site: btcaudio.tk/livebut I want to use my own bitcoin node for this .. can I do this with btcd?
|
|
|
|
|
Sanquin
Newbie
Offline
Activity: 35
Merit: 0
|
|
September 26, 2014, 11:49:20 PM |
|
Always been interested in GO, Looks a very promising project, block safari looks good also. Il drop by and see you on IRC
|
|
|
|
T-rage_11
Member
Offline
Activity: 74
Merit: 10
www.btcaudio.eu || LIVE-AUDIO-TICKER
|
|
October 30, 2014, 02:06:59 AM |
|
I want to connect to my btcd-server with javascript <!DOCTYPE html>
<meta charset="utf-8" />
<title>WebSocket Test</title>
<script language="javascript" type="text/javascript">
var wsUri = "ws://echo.websocket.org/"; var output;
function init() { output = document.getElementById("output"); testWebSocket(); }
function testWebSocket() { websocket = new WebSocket(wsUri); websocket.onopen = function(evt) { onOpen(evt) }; websocket.onclose = function(evt) { onClose(evt) }; websocket.onmessage = function(evt) { onMessage(evt) }; websocket.onerror = function(evt) { onError(evt) }; }
function onOpen(evt) { writeToScreen("CONNECTED"); doSend("WebSocket rocks"); }
function onClose(evt) { writeToScreen("DISCONNECTED"); }
function onMessage(evt) { writeToScreen('<span style="color: blue;">RESPONSE: ' + evt.data+'</span>'); websocket.close(); }
function onError(evt) { writeToScreen('<span style="color: red;">ERROR:</span> ' + evt.data); }
function doSend(message) { writeToScreen("SENT: " + message); websocket.send(message); }
function writeToScreen(message) { var pre = document.createElement("p"); pre.style.wordWrap = "break-word"; pre.innerHTML = message; output.appendChild(pre); }
window.addEventListener("load", init, false);
</script>
<h2>WebSocket Test</h2>
<div id="output"></div> http://www.websocket.org/echo.htmlCan I disable the RPC-CERTIFICATES or how can I connect with Javascript over TLS?
|
|
|
|
work2heat
Newbie
Offline
Activity: 21
Merit: 0
|
|
November 01, 2014, 01:58:20 AM |
|
Started playing with this today. Great work conformal team!
|
|
|
|
davec
Newbie
Offline
Activity: 39
Merit: 0
|
|
November 06, 2014, 05:30:34 PM Last edit: November 06, 2014, 06:31:15 PM by davec |
|
I want to connect to my btcd-server with javascript
Can I disable the RPC-CERTIFICATES or how can I connect with Javascript over TLS?
I just saw this. You can't disable TLS, but I have a gist up on my github which demonstrates how to connect via TLS that I've tested with firefox and chrome: https://gist.github.com/davecgh/8a16b1048fe0fb406d29Make sure you modify the username and password near the top of the file in the javascript to the correct values or you'll get an undefined error since btcd will immediately disconnect you upon receiving invalid credentials.
|
|
|
|
T-rage_11
Member
Offline
Activity: 74
Merit: 10
www.btcaudio.eu || LIVE-AUDIO-TICKER
|
|
November 06, 2014, 09:34:20 PM |
|
I want to connect to my btcd-server with javascript
Can I disable the RPC-CERTIFICATES or how can I connect with Javascript over TLS?
I just saw this. You can't disable TLS, but I have a gist up on my github which demonstrates how to connect via TLS that I've tested with firefox and chrome: https://gist.github.com/davecgh/8a16b1048fe0fb406d29Make sure you modify the username and password near the top of the file in the javascript to the correct values or you'll get an undefined error since btcd will immediately disconnect you upon receiving invalid credentials. Awesome! Thank you!
|
|
|
|
micax1
|
|
November 18, 2014, 01:44:28 PM |
|
Hi. first of all Thank you for great software! I`m using it and fully satisfied! Want to ask a question: Is there any guide on how to convert BTCD or complete solution for litecoin and dogecoin based on BTCD??
Thank you!
|
|
|
|
allgoodthings1
|
|
November 19, 2014, 03:11:54 PM |
|
Is this normal?
I am installing btcd on a Widows 7 (64-bit) machine with the .msi istaller. On the initial sync, I'm up to block 324k -- and the HDD is reading/writing constantly! The green light on my box hardly even flashes. It's much more ON than OFF.
I tried stopping the program, rebooting the computer and starting the program again. But the behaviour continues, and this has gone on like this for several hours now.
Will this go away or get better when the blockchain is fully synced, or is this normal behaviour for btcd?
|
|
|
|
davec
Newbie
Offline
Activity: 39
Merit: 0
|
|
November 19, 2014, 07:46:11 PM |
|
Hi. first of all Thank you for great software! I`m using it and fully satisfied! Want to ask a question: Is there any guide on how to convert BTCD or complete solution for litecoin and dogecoin based on BTCD??
Thank you!
I don't know of any guides on converting the code base for LTC/DOGE. I know there has been some work to create ppcd which is for peercoin, so that is probably a pretty good place to see some conversion work that has been done. Is this normal?
I am installing btcd on a Widows 7 (64-bit) machine with the .msi istaller. On the initial sync, I'm up to block 324k -- and the HDD is reading/writing constantly! The green light on my box hardly even flashes. It's much more ON than OFF.
I tried stopping the program, rebooting the computer and starting the program again. But the behaviour continues, and this has gone on like this for several hours now.
Will this go away or get better when the blockchain is fully synced, or is this normal behaviour for btcd?
After the final checkpoint (currently at 319400), it starts to do full verification on the blocks, which is why you see the heavy HDD usage (it's loading every single input transaction to every transaction in every new block). This is also true of all full nodes that must do verification and is normal until you're fully synced at which point the usage drops significantly.
|
|
|
|
|