 Show Posts
|
|
Pages: [1] 2 3 4 5 6 »
|
So many fiat currencies out there....can't we just create a universal one to use globally?  thought thats what the US was doing with the USD.....well they're certainly printing enough of them for everyone  You got that right!  |
|
|
|
No. 7970's cannot obtain stable settings at intensities above 13. I don't know why, but I haven't heard of one case where anyone was able to attain a stable configuration with an -I 13+ Set -g to 2, -I to 13, and --thread-concurrency to 8192 Anyone who says intensities above 13 are stable for 7970s don't know what they are talking about. btw, did anyone receive your 15LTC reward yet?  ^^^ What he said. |
|
|
|
So many fiat currencies out there....can't we just create a universal one to use globally? |
|
|
|
|
I was actually on the forum when a coin was released! That's a first for me!
|
|
|
|
Orphaned Chocobos found = 27
Gil found = 0
Read op. Block reward is 0, until block 1000 OOPS! I didn't realize we were still that low on blocks...duh. |
|
|
|
|
Orphaned Chocobos found = 27
Gil found = 0
|
|
|
|
|
I haven't participated in a launch for the last 15 or so coins...kinda miss the chaos...so I might give this one a whirl for some kicks.
Would be nice to have a launch time (even if it is approximate).
|
|
|
|
|
WTF is with all the DDOS attacks on crypto sites?? In my over 15 years on the internet, I've never seen a community attacked so regularly.
|
|
|
|
|
Uh oh...number one on coinchoose right now...
There goes the neighborhood...
|
|
|
|
|
Hey D.I., you put some turtle wax on your avatar? Lookin shiny man! (Sorry, I just saw it...haven't been around much lately...super busy in RL).
|
|
|
|
no idea... i found the problem with that .... it wants that in linux .conf file ipcallowip=127.0.0.1 not rpcconnect=127.0.0.1 now i am getting a huge nubmer or errors that i can't find... i make everything like i do to most coin pools. that means: i find the address for PUBLIC ADDRESS from base58.h i find height or something like that from nSubsidy >>= (nHeight / 8400000); from main.cpp i change the port and rpc port at networks.py i change the worker port and the other port that connect the pools. i delete the IDENTIFY AND PREFIX i leave them like that (don't couse me any problems for solo pools) IDENTIFIER=''.decode('hex'),
PREFIX=''.decode('hex'),i change the helper.py with or 'netowrkname' like this if 'lite' in net.NAME or 'feather' in net.NAME or 'chn' in net.NAME or 'franko' in net.NAME or 'digital' in net.NAME or 'worldcoin' in net.NAME:
what else. and i run with python. (i create the screen first) but then let's say for fastcoin i get like 2 pages errors ..... i also hav no idea what this is CHAIN_LENGTH=24*60*60//10, # shares
REAL_CHAIN_LENGTH=24*60*60//10, # shares
SHARE_PERIOD=10, # seconds
and on the other networks.py this one and how i can translate it P2P_PREFIX='f9beb4d9'.decode('hex'),The P2P_PREFIX was explained by Kyune here: I think I may have figured this out. I had been bumping into the same problem (stalling at the P2P connection) on some coins but not others. I finally realized I was wrong in an initial assumption...the P2P_PREFIX setting in bitcoin/networks.py is in fact a coin-specific setting -- which is logical, as the other settings in that file are coin-specific as well. In fact, it looks like it is basically the "magic value" or "magic number" referred to in https://en.bitcoin.it/wiki/Protocol_specification, and after poking around in the code I think you can find it in main.cpp at pchMessageStart[4]=... Using this specific value as the P2P_PREFIX fixed the problem for me. So, for example, I haven't ever installed Dragoncoin myself, but looking quickly at the relevant line in main.cpp: unsigned char pchMessageStart[4] = { 0xfc, 0xd9, 0xb7, 0xdd };
Thus, for Dragoncoin, try setting P2P_PREFIX='fcd9b7dd'.decode('hex'),
and let us know if that gets you past stalling at the P2P connection. Hope this is helpful. I can't really help with the chain length as it is confusing to me too. |
|
|
|
|
No hard drive mining but there is a new coin getting released later today called HertzCoin (HZC) that mines using your monitor's refresh rate. Multiple monitor setups will mine faster.
Make sure you get in early...I hear a major rental car company is going to accept them at launch. I also heard there is going to be a HZC fontas pump in 24 hours. Oh and they'll be coming to Gox next week, CONFIRMED!
|
|
|
|
For future reference, you can find the P2P_PORT in the coin's source code in the protocol.h file, it's the 2nd value after GetDefaultPort.
You can find RPC_PORT in the source code in the bitcoinrpc.cpp file, look for GetArg (-rpcport, xxxx), where xxxx is the port.
I'm talking about the values you would specify in the bnetworks.py file.
Just to confirm what I *think* I know.... These values can be specified in the *.conf file as well can't they? (To match bnetwrks.py) |
|
|
|
|
Goldcoin should have been named Cultcoin....or KoolAidcoin.
|
|
|
|
@whitedragon
Yeah I have no problems with them. You just need to wait that the nibbled server syncs with the network.
Ok maybe I'll try it again now that it looks like I can actually stay in sync! |
|
|
|
Added average profitability last 24. Working on net hash rates and total market depth.
This is good...but hopefully we can get longer range too? At least 14 days worth.... I know you have been busy so don't think I'm nagging...whenever you have time. Good to see you "back in business". Another thank you for the work you are doing. |
|
|
|
And one of your gpus is off ! You rock ! turned off because it is built into the processor 7660D, I run the other config ))) @whitedragon You need to add this to the nible.conf file. addnode=99.132.231.140
addnode=72.11.149.185
addnode=207.12.89.2
addnode=46.39.246.24
addnode=54.244.198.104
addnode=72.78.100.3
addnode=106.187.94.209
maxconnections=5 This is to prevent that your connection is made with rogue or misbehaving peers, most of them trying to process into the nibble network blockchains that were mined offline, creting that problem. This list avoids that problem. I had the same problem that you had and now it's fixed. then delete the file pers.dat in the folder %appdata%/nibbleShit... I forgot I made a new nibble.conf file when I was messing with p2pool that didn't have the nodes in it...and I forgot to switch back to the other one when I installed fresh. I've switched back now and I'll turf my peers file and see how she goes. tyrion70 or basslike around? Did you guys get your p2pools to work with the addnode addresses in your conf file? Mine didn't seem to like it. |
|
|
|
|
Man I still can't keep my damn client from going out of sync. It happens all the time and just gets stuck there, never goes back in sync no matter how long I leave it running. I wiped all my nibble stuff clean, redownloaded and reinstalled client, redownloaded blockchain, added the nodes from first post on this thread, but STILL goes out of sync and gets stuck on some block number that shouldn't exist.
|
|
|
|
|
Hmm I didn't notice at first but setting PERSIST to true gives me a bunch of errors when I launch my miner. It mentions not being connected to peers...but my miner doesn't get work. Change it back to false and I can mine no problem.
Too tired now...almost 1am here in Taiwan. Will fool around more tomorrow.
|
|
|
|
|
Sorry guys...forget what I just said.
My client is still having problems going out of sync...and every time it happens it throws p2pool out of whack. Have there been any updates to the client lately that I missed? I just installed a new one like a week ago.
|
|
|
|
|
