try to synch without using those addnodes some of them seem to be bad, i am able to synch without using any addnodes at all
I did that yesterday...that's how I ended up on an invalid fork again. I'm currently importing the bootstrap file. |
|
|
|
 It's importing now. |
|
|
|
I'm having the same problem, and this was after updating to v2.2, wiping out the forked blockchain, and letting it download again. getinfo output: {
"version" : "v2.2.0.0-gf96a5a-noise23",
"protocolversion" : 60008,
"walletversion" : 60000,
"balance" : 0.00000000,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"split threshold" : 30.00000000,
"blocks" : 684620,
"moneysupply" : 3995123.58842300,
"connections" : 7,
"proxy" : "",
"ip" : "70.173.239.125",
"PoW difficulty" : 1040.48052646,
"PoS difficulty" : 0.00080916,
"testnet" : false,
"keypoololdest" : 1417625103,
"keypoolsize" : 101,
"paytxfee" : 0.00010000,
"unlocked_until" : 1504112287,
"errors" : "WARNING: Invalid checkpoint found! Displayed transactions may not be correct! You may need to upgrade, or notify developers."
}It seems like you are still on a fork - current blockheight is only 683362 - http://tek.blockchain.lt/ , yours is 684620. Unfortunately, you have to re-sync again. Delete blockchain files and peers.dat and add these nodes to tekcoin.conf - addnode=69.197.161.122
addnode=104.193.43.106
addnode=104.218.234.124
addnode=104.218.234.125
addnode=199.233.245.36  I previously had no addnode lines in there (well, I had some, but they were all commented out). I tried putting the lines above in as "connect=" instead, but wasn't able to get through to download blocks in a reasonable time. They're in now as addnodes and not connects. As I write this, getblockcount returns 15106 and getpeerinfo returns these addresses: 46.166.164.221 182.170.206.51 66.215.60.93 93.183.214.228 None are running Tekcoin 2.2. Here's the full getpeerinfo output: [
{
"addr" : "46.166.164.221:8514",
"services" : "00000001",
"lastsend" : 1417794375,
"lastrecv" : 1417794375,
"conntime" : 1417794051,
"version" : 60008,
"subver" : "/tekcoin:2.1.1.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 684741,
"banscore" : 0
},
{
"addr" : "182.170.206.51:8514",
"services" : "00000001",
"lastsend" : 1417794422,
"lastrecv" : 1417794422,
"conntime" : 1417794171,
"version" : 60008,
"subver" : "/tekcoin:2.1.1.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 93980,
"banscore" : 0
},
{
"addr" : "66.215.60.93:8514",
"services" : "00000001",
"lastsend" : 1417794412,
"lastrecv" : 1417794412,
"conntime" : 1417794227,
"version" : 60008,
"subver" : "/tekcoin:2.1.1.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 684745,
"banscore" : 0
},
{
"addr" : "93.183.214.228:8514",
"services" : "00000001",
"lastsend" : 1417794405,
"lastrecv" : 1417794405,
"conntime" : 1417794337,
"version" : 60008,
"subver" : "/tekcoin:2.1.1.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 368479,
"banscore" : 0
}
]
What are the odds I'll get a valid copy of the blockchain from these hosts? |
|
|
|
Invalid checkpoint problem.
I upgraded my wallet last night. Dumped the whole dir except my wallet.dat file and let the blockchain rebuild. I looked at my wallet this morning and I'm getting the notice at the bottom of the window about an invalid checkpoint. What's the deal with that?. I have had 6 payouts from the pool I use.. and none of them are showing up.
It seems like your wallet caught a bad block from an obsolete peer. Please re-sync with v2.2 I'm having the same problem, and this was after updating to v2.2, wiping out the forked blockchain, and letting it download again. getinfo output: {
"version" : "v2.2.0.0-gf96a5a-noise23",
"protocolversion" : 60008,
"walletversion" : 60000,
"balance" : 0.00000000,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"split threshold" : 30.00000000,
"blocks" : 684620,
"moneysupply" : 3995123.58842300,
"connections" : 7,
"proxy" : "",
"ip" : "70.173.239.125",
"PoW difficulty" : 1040.48052646,
"PoS difficulty" : 0.00080916,
"testnet" : false,
"keypoololdest" : 1417625103,
"keypoolsize" : 101,
"paytxfee" : 0.00010000,
"unlocked_until" : 1504112287,
"errors" : "WARNING: Invalid checkpoint found! Displayed transactions may not be correct! You may need to upgrade, or notify developers."
} |
|
|
|
The OP needs to be updated with the correct source-code location. I built tekcoind from the source at https://github.com/maxxine/TEK yesterday and let it download the blockchain. It ended up on what I'm guessing is an invalid fork, as a few hours' mining at iSpace yesterday never showed up in my wallet, but according to http://tek.blockchain.lt/address/BrRijfWVpWkR8WeJ4DeWmUwxQFc1qp2oMu, nearly 24 coins had been paid out. I've rebuilt tekcoind, this time with source from https://github.com/noise23/TEK, the link to which I found buried in this thread in some posts from mid-November. It looked like it was going to take an abnormally long time to fix the already-downloaded forked blockchain, so I just saved tekcoin.conf and wallet.dat and am downloading it again. (According to this post, the block explorer is on the correct chain, which means iSpace is also on the correct chain. As I write this, my copy of the blockchain is up to #109248; it still has a while to go.) |
|
|
|
Can you print out your raw http request?
I've put up screen captures from Wireshark here: http://imgur.com/a/Sh2jx#0Joulecoin:   Bitcoin:   |
|
|
|
In addition to that, I've tried sending RPC commands with curl as described in the Bitcoin wiki: curl --user user --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "getinfo", "params": [] }' -H 'content-type: text/plain;' http://127.0.0.1:8844/This fails with a 401 error. It should work the same as bitcoind. This is the relevant code in rpcserver.cpp. Do you get "ThreadRPCServer incorrect password attempt from ...." in your debug.log? Can you print out your raw http request? Yes...even though the password is correct. Throwing -v in to the options to curl, I get this: Enter host password for user 'salfter': [password pasted in here]
* Hostname was NOT found in DNS cache
* Trying 127.0.0.1...
* Connected to 127.0.0.1 (127.0.0.1) port 8844 (#0)
* Server auth using Basic with user 'salfter'
> POST / HTTP/1.1
> Authorization: Basic [base64 encoding of RPC password redacted]
> User-Agent: curl/7.35.0
> Host: 127.0.0.1:8844
> Accept: */*
> content-type: text/plain;
> Content-Length: 71
>
* upload completely sent off: 71 out of 71 bytes
* HTTP 1.0, assume close after body
< HTTP/1.0 401 Authorization Required
< Date: Wed, 03 Dec 2014 20:05:43 +0000
< Server: joulecoin-json-rpc/v0.9.2.2-beta
* Authentication problem. Ignoring this.
< WWW-Authenticate: Basic realm="jsonrpc"
< Content-Type: text/html
< Content-Length: 296
<
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/1999/REC-html401-19991224/loose.dtd">
<HTML>
<HEAD>
<TITLE>Error</TITLE>
<META HTTP-EQUIV='Content-Type' CONTENT='text/html; charset=ISO-8859-1'>
</HEAD>
<BODY><H1>401 Unauthorized.</H1></BODY>
</HTML>
* Closing connection 0
The same transaction against bitcoind, by comparison, looks like this: Enter host password for user 'salfter': [password pasted in here]
* Hostname was NOT found in DNS cache
* Trying 127.0.0.1...
* Connected to 127.0.0.1 (127.0.0.1) port 8332 (#0)
* Server auth using Basic with user 'salfter'
> POST / HTTP/1.1
> Authorization: Basic [base64 encoding of RPC password redacted]
> User-Agent: curl/7.35.0
> Host: 127.0.0.1:8332
> Accept: */*
> content-type: text/plain;
> Content-Length: 71
>
* upload completely sent off: 71 out of 71 bytes
< HTTP/1.1 200 OK
< Date: Wed, 03 Dec 2014 20:08:43 +0000
< Connection: keep-alive
< Content-Length: 456
< Content-Type: application/json
* Server bitcoin-json-rpc/v0.9.99.0-c1def0d is not blacklisted
< Server: bitcoin-json-rpc/v0.9.99.0-c1def0d
<
{"result":{"version":99900,"protocolversion":70002,"walletversion":60000,"balance":0.93079170,"blocks":332738,"timeoffset":0,"connections":8,"proxy":"","difficulty":40007470271.27126312,"testnet":false,"keypoololdest":1415387100,"keypoolsize":99,"unlocked_until":0,"paytxfee":0.00000000,"relayfee":0.00001000,"errors":"This is a pre-release test build - use at your own risk - do not use for mining or merchant applications"},"error":null,"id":"curltest"}
* Connection #0 to host 127.0.0.1 left intact
|
|
|
|
I'm looking at adding Joulecoin to my MinerSwitcher setup, but I've run into a snag: I can't get the block reward out of joulecoind. [...] It's hard to reach any other conclusion than that there's a bug somewhere in the Joulecoin codebase, given that I have 25 other coins configured and running properly with the same code. Are you sure you have the correct port, port is open, etc? Try telnet to the host/port and see if you can connect. The getblocktemplate command returns the information you are looking for: {
"coinbasevalue" : 1600000000,
}
In addition to that, I've tried sending RPC commands with curl as described in the Bitcoin wiki: curl --user user --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "getinfo", "params": [] }' -H 'content-type: text/plain;' http://127.0.0.1:8844/This fails with a 401 error. It works against bitcoind (and, presumably, the other coin daemons...also tested it against 42, for instance), but not joulecoind. I'm giving it the same password that's in .joulecoin/joulecoin.conf, so that isn't it. |
|
|
|
That's not a FUD address. This is a FUD address: FUDCo1NsCduuG1JK7rnR32ejQczu7ypH1c You, sir, have a badass FUD address. oclvanitygen FTW! 1000 FUD sent. Thanks! |
|
|
|
sweet!! ill hook u up with some fud when i get home!!
Just checked now after Thanksgiving weekend...looks like FUDcoin lets you embed notes in the blockchain, as the coins you kicked my way are identified as such. Neat!...and thanks! |
|
|
|
- Added an --enable-forcecombo option to allow building of driver combinations with drivers that are normally built standalone.
I'm rebuilding now...it's on a Raspberry Pi, so it'll be a while. ...and it's now rebuilt and running. |
|
|
|
I spend several hours getting oclvanitygen working with AMD Radeon 7xxx on 64-bit Linux - Ubuntu 12.04 and Ubuntu 14.04. In the end only the following is needed: - Ubuntu drivers
- vanitygen patch
- 1 userspace library file from AMD APP SDK v2.7
I created a minimal instruction text file. Maybe this will save someone some hours of searching the internet. https://nastyfans.org/download/oclvanitygen.txtI had been having trouble getting oclvanitygen running again since migrating from Gentoo to Ubuntu (and getting it running on Gentoo was a bit of a hassle). This got my 6870 back in the game. Thanks! |
|
|
|
so who here has a REAL FUD address? I know members of the #FUDsterMafia do, Emilio does, and so does moonchaser. Anyone else in the thread have one? Post it!! Lets see them FUDdresses!!
FRx91BrHsFWvXUpicw8ncdKo4AYWsEQFkr that is my real FUD address. Good Luck developers I wish you all the best in the future. That's not a FUD address. This is a FUD address: FUDCo1NsCduuG1JK7rnR32ejQczu7ypH1c |
|
|
|
I'm attempting to set up a Fudcoin explorer. (After that, I'll expand it to the other coins for which I have daemons running, but I'm starting with Fudcoin.) I already have a Bitgem explorer running (see link in my sig) with the CryptoManiac fork, so I started with that. It reads in the blockchain and starts the webserver, but when I try to access it, it fails with a division-by-zero error: Traceback (most recent call last):
File "/usr/lib/python2.7/wsgiref/handlers.py", line 85, in run
self.result = application(self.environ, self.start_response)
File "Abe/abe.py", line 209, in __call__
handler(page)
File "Abe/abe.py", line 307, in handle_chains
100.0 - (100.0 * (ss + more) / (total_ss + more)))
ZeroDivisionError: float division by zero
If I put the offending code in a try-except block, the homepage comes up...but it only shows the genesis block. I then tried the main branch. It won't even start up: Traceback (most recent call last):
File "Abe/abe.py", line 32, in <module>
import DataStore
File "/home/abe/bitcoin-abe/Abe/DataStore.py", line 31, in <module>
import Chain
File "/home/abe/bitcoin-abe/Abe/Chain/__init__.py", line 17, in <module>
from .. import deserialize, BCDataStream, util
ValueError: Attempted relative import beyond toplevel package
The last version tagged is 0.7.2, which is nearly two years old. The last commit in master is only a couple of months old, but it doesn't do any good if it won't run. Is there another fork that people are using nowadays? The coins I'm interested in monitoring are sha256d and scrypt coins. Proof-of-stake support is needed for some. |
|
|
|
|
The OP needs to be updated...it has RPC and P2P ports flipped around, which caused some issues when I wanted to add FFC to my MinerSwitcher setup and was trying to make RPC calls to the P2P port.
|
|
|
|
New release: Version 4.7.1, 4th November 2014
- Changed the configure build system to make it impossible to build more than one device in if the chosen driver was meant to be used standalone, along with more explicit tagging of standalone drivers in the configure help. This should make it easier to choose a more suitable configuration for distribution packaging.
Is there an option to override this new behavior? I have had a couple of BFL Jalapeņos running off the Raspberry Pi in my Bitfury rig for at least a year now. In recent months, I've been using the Black Arrow Bitfury driver in cgminer; its auto-tune support has been pretty nice, and it works like a champ with BFSB hardware. Now I'll have to build cgminer twice (once with --enable-bab and again with --enable-bflsc) and run two instances of cgminer, where before a single instance would suffice. |
|
|
|
Blockchain started syncing, then I encrypted the wallet...and now it won't connect to anything. addnode=67.212.70.89 is in fudcoin.conf. I built fudcoind from GitHub source on Ubuntu Server LTS 14.04. Are there more nodes that can be added to fudcoin.conf, or should I just let it keep running until it finally connects? It's not like Fudcoin will fit in with MinerSwitcher just yet as it isn't on any exchanges, but I have some of my hashpower dedicated to it for at least a little while...don't think I've gotten in this early on a coin ever. Edit: Never mind: salfter@files:~$ fudcoind getpeerinfo
[
{
"addr" : "67.212.70.89:54540",
"services" : "00000001",
"lastsend" : 1415922272,
"lastrecv" : 1415922273,
"conntime" : 1415920351,
"version" : 61000,
"subver" : "/Kaufman:1.0.0/",
"inbound" : false,
"startingheight" : 206,
"banscore" : 0
},
{
"addr" : "5.135.190.96:54540",
"services" : "00000001",
"lastsend" : 1415922237,
"lastrecv" : 1415922237,
"conntime" : 1415920436,
"version" : 61000,
"subver" : "/Kaufman:1.0.0/",
"inbound" : false,
"startingheight" : 206,
"banscore" : 0
}
]
|
|
|
|
I'm running the latest version, but I've had a transaction to an exchange stuck with zero confirmations for the better part of 24 hours now. Also, while a mining pool says it's sent me payments, they've not arrived. Is something still not right with the network?
You might need to reindex the blockchain to get back on the right fork, which you can do by starting the wallet with " -reindex" option. Did that, and now the coins received from the pool have shown up. Coins sent to Cryptsy for trading haven't shown up there; a support ticket has been opened. They might need to do the same. |
|
|
|
I'm running the latest version, but I've had a transaction to an exchange stuck with zero confirmations for the better part of 24 hours now. Also, while a mining pool says it's sent me payments, they've not arrived. Is something still not right with the network?
You might need to reindex the blockchain to get back on the right fork, which you can do by starting the wallet with " -reindex" option. Giving this a shot now...we'll see what happens when it's done. |
|
|
|
Is there some specific way I'm supposed to backup the wallet?
Usually I just copy the wallet file and put it on a flash drive right from the directory, but when I try to restore the wallet with XPM I get wallet data corrupt, can't restore.
The better way to go would be to dump out all of the private keys in your wallet, or at least the ones that have non-zero balances. To do this, you'll first need to dump all of your wallet addresses. This avoids issues with binary wallet incompatibility (as might happen when coin daemons are built with different bdb versions). Something like this should do the trick: (for i in `primecoind listtransactions "" 9999999 | grep addr | sort | uniq | sed "s/\",//;s/.*\"//"`; do echo -n $i" "; primecoind dumpprivkey $i; done ) 2>&1 | grep -v error
It finds all addresses associated with the transactions in your wallet. It then tries to retrieve private keys. This will fail for other people's addresses, but we filter those out. You should get a space-separated list of addresses and private keys as output. Verify that these addresses contain your wallet's entire balance before you get rid of it. |
|
|
|
|
Show Posts
