|
Pool is being worked on. should be caught up soon
|
|
|
|
|
Just remember if he gets too many emails he will close the site for a few days, then give incorrect informations on what he will do next.
|
|
|
|
|
Just a reminder Pool is up using DPZ see Sig
|
|
|
|
Are there more users that have problems with the fireflycoin wallet, it can't find any connection. The wallet is now more than 48 hours online, but no connections???
Any one have a idea?
Thanks & Greetings
Try adding some of the ip address below to the fireflycoin.conf file 16:59:47

getpeerinfo
16:59:47

[
{
"addr" : "98.219.143.145:5534",
"services" : "00000001",
"lastsend" : 1390784323,
"lastrecv" : 1390784324,
"bytessent" : 5202,
"bytesrecv" : 56709,
"conntime" : 1390784322,
"version" : 70001,
"subver" : "/FireFlyCoin:0.9.1/",
"inbound" : false,
"startingheight" : 304489,
"banscore" : 0,
"syncnode" : true
},
{
"addr" : "162.243.43.190:5534",
"services" : "00000001",
"lastsend" : 1390784330,
"lastrecv" : 1390784337,
"bytessent" : 232,
"bytesrecv" : 10560,
"conntime" : 1390784329,
"version" : 70001,
"subver" : "/FireFlyCoin:0.9.0/",
"inbound" : false,
"startingheight" : 304489,
"banscore" : 0
},
{
"addr" : "198.199.100.216:5534",
"services" : "00000001",
"lastsend" : 1390784331,
"lastrecv" : 1390784331,
"bytessent" : 232,
"bytesrecv" : 10530,
"conntime" : 1390784330,
"version" : 70001,
"subver" : "/FireFlyCoin:0.9.1/",
"inbound" : false,
"startingheight" : 304489,
"banscore" : 0
},
{
"addr" : "24.205.183.65:5534",
"services" : "00000001",
"lastsend" : 1390784374,
"lastrecv" : 1390784378,
"bytessent" : 232,
"bytesrecv" : 10560,
"conntime" : 1390784373,
"version" : 70001,
"subver" : "/FireFlyCoin:0.9.1/",
"inbound" : false,
"startingheight" : 304489,
"banscore" : 0
},
{
"addr" : "134.119.3.131:5534",
"services" : "00000001",
"lastsend" : 1390784387,
"lastrecv" : 1390784387,
"bytessent" : 232,
"bytesrecv" : 153,
"conntime" : 1390784386,
"version" : 70001,
"subver" : "/FireFlyCoin:0.9.1/",
"inbound" : false,
"startingheight" : 304489,
"banscore" : 0
}
]
so put in addnode=189.199.100.216 addnode=198.199.100.216 addnode=134.119.3.131 and so on |
|
|
|
|
so for all the above that have not received QBT. please make sure it is a V3 wallet
I'm not the OP so I can't put a note there if you verify V3 wallet I'll send you coin.
This giveaway is closed after this message
|
|
|
|
|
right ok I'll check it again
|
|
|
|
|
because UFC has gone from scrypt to blake should I stop/change amount/push harder the current UFC giveaways
|
|
|
|
|
I use google auth on my android devices.
|
|
|
|
|
https:\\Scifi-ex.com is open QBT is trading
|
|
|
|
|
pool should be up in 90min
|
|
|
|
|
Working on getting pool up. no response from provider yet
|
|
|
|
From walletconvert.txt If one tries to use an old wallet with the new client without having run the wallet with the salvagewallet switch once, the client will lock/crash.
However, after running the client/daemon with the switch on the old wallet, conversion works great and the switch is no longer needed.
Linux users use a switch (--salvagewallet) ./federationcredit --daemon --salvagewallet or ./federationcredit-qt --salvagewallet
Windows users can use the convert.bat file to run the client with the salvagewallet switch. |
|
|
|
|
Trying to get a X6500 going starting with BTC will change bitsteam for something else once I have it working on BTC.
-S x6500:auto
did not find anything
-S x6500:serial=A5VNUHUE
-S x6500:A5VNUHUE
-S x6500:\\.\COM5
all give
[2014-01-24 20:55:40] Waiting for devices; press 'M+' to add, or 'Q' to quit
[2014-01-24 20:55:40] Waiting for devices; press 'M+' to add, or 'Q' to quit
did copy a bitstream into folder and renamed it to
fpgaminer_x6500-overclocker-0402.bit
|
|
|
|
|
Should be 12 noon PST 2000UTC 1/25/14
|
|
|
|
this also works goto console and type getmininginfo 19:57:00

getmininginfo
19:57:00

{
"blocks" : 443,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 550.80730191,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 33183330417,
"pooledtx" : 0,
"testnet" : false
}
"networkhashps" : 33,183,330,417, is hashrate about 50% more than last time I checked |
|
|
|
|
From getmininginfo on UFC
"networkhashps" : 22764047717,
22,764,047,717
So ~20GH/s Network Hash already not bad at all.
|
|
|
|
|
Show Posts
