--Nfmin 4 --Nfmax 30 --StartT 1377557867
Still all rejects... and getinfo shows this... thought that would be it... "keypoololdest" : 1378127041, |
|
|
|
|
So no pool for 24 hours?
What about the CPUMiner dream was working on... will he at least get what he needs to put that into use?
|
|
|
|
|
So much for launching today... has anyone heard anything from scifi?
EDIT: OMG scooby your GIF made me spit out my soda!
|
|
|
|
By last minute tuning you mean finding the --Nfmin --Nfmax and --StartT parameters... if they have even been changed from the original source?
Pretty much. It is a simple thing for those familiar with development (such as yourself), but much more difficult for the average person to find every spot these parameters are buried. I certainly hope at least the Nfactor4 cut-off date estimate is reset, or there will be some big issues. I hope releasing these miners will help a little bit, because the bigger hassle is matching SDK versions to Yacminer(cgminer) version and card model used. The yacoin miners seem to be very picky about the combination. Well... thanks for compiling an easy to use version for the masses... I should be set with what I currently have in hand minus checking these values... I will post back my early results. Is there another thread I should be watching for the client release of GPL? EDIT: Also... how to get invited to the pool? I see it is in maintenance mode but figured I could at least pre register... |
|
|
|
Just a little update from my end on GPL. I have a CPU miner and GPU miner ready to go, pending some last minute tuning when the code is released. The www.gplcoin.com mine will be open shortly after the new code is released. This will be a LP pool like KED. I will release the CPU miner first (Both releases will be strictly github source, I have modified current Yacoin miners to work with GPL. ) I will release the GPU miner later, after the difficulty has risen. The pool will not be able to handle the share load with GPU miners at the starting difficulty. It is going to have a hard time with CPU miners at the start. The changes only involve changing couple of parameters, so I am suggesting going to the main threads (I will publish) for help with installing and troubleshooting. I am providing these to help the Star Trek coin community, they are not my projects, and I am not going to make them my projects.  By order of the Grand Nagus, Network Hashrate is confidential.(In reality, the daemon has no network hash rate rpc command...  ) By last minute tuning you mean finding the --Nfmin --Nfmax and --StartT parameters... if they have even been changed from the original source? |
|
|
|
GoldPressedLatinum - Forked - Relaunch today or tomorrow.
I want to make sure enough people are aware that to old coin is dead before we relaunch!
Please help us spread the word ! Relaunch may be tomorrow not today to allow miners time to time to grieve and stop mining to old coin. Not a single Ferengi was harmed in the death of the old coin!
Please make sure this is posted to Github so the pool Ops can make a pool once this gets rolling. EDIT: FYI in the last 10 hours, only 116 blocks have been found... i think it is safe to say this has been abandoned... launch when ready lol. |
|
|
|
I really hate to do this but: I think I should send a word of caution about GPL. As a point of reference block 5: "hash" : "000004f7534468485df32db4e7732660f46eceabb7c80820638d686cbcd8e3a7",
"confirmations" : 65610,
"size" : 263,
"height" : 5,
"version" : 3,
"merkleroot" : "af29f173061f3d5f47dced344560e25bbe5e874d25c93f73e2b0459d3c5d4be1",
"mint" : 0.20000000,
"time" : 1377633845,
"nonce" : 3949,
"bits" : "1e0fffb2",
"difficulty" : 0.00024416,
"previousblockhash" : "00000b586ada34977216af662b5a181edb196172b96e4fff201133d2ff9fd1a9",
"nextblockhash" : "00000a7d36363f0fa11c6aa016c74d4e19250a987b3b9bde43b2009ec2112aaf",
"flags" : "proof-of-work",
"proofhash" : "000004f7534468485df32db4e7732660f46eceabb7c80820638d686cbcd8e3a7",
"entropybit" : 1,
"modifier" : "0000000000000001",
"modifierchecksum" : "cb8cf84c",
"tx" : [
"af29f173061f3d5f47dced344560e25bbe5e874d25c93f73e2b0459d3c5d4be1"
],
"signature" : "3046022100b02fa3a120e09cc44caf9876647156b9003da461bf8e4966bce4c6fc71f254e3022100a611fc002ed63bd345a36595822874ebeed355405cdce742a29cb8d0cfa1cc70"
} That date code is: Tue Aug 27 2013 15:04:05 GMT-0500 (CDT) Current GPL getinfo: "version" : "v1.0.0.0-gunit-beta",
"protocolversion" : 60005,
"walletversion" : 60000,
"balance" : 0.00000000,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"blocks" : 66754,
"moneysupply" : 13350.20820000,
"connections" : 7,
"proxy" : "",
"ip" : "107.xxx.xxx.xxx",
"difficulty" : 0.11081089,
"testnet" : false,
"keypoololdest" : 1377783844,
"keypoolsize" : 102,
"paytxfee" : 0.00000000,
"errors" : ""
} 65754 blocks in 3 days. Equates to around 15 blocks per SECOND over three days. I would hold off mining GPL and instead mine UFC or KED until the situation is fixed. I have already contacted the developer with some issues I have found in the code. The issues are easy to fix but will require a block chain restart.  I hope I am mistaken, but at the very least caution is in order. ~58 hours actually since that block... avg 6960 blocks should have been found... we are at 10 times that so... the difficulty adjustment is off somewhere. |
|
|
|
|
Thanks for the addnodes I am synced and solo mining with the GPU miner.
|
|
|
|
|
The GPL blockchain downloads so slowly...
anyone mind listing some addnodes please?
|
|
|
|
Yeaah a lot going wrong here... last found block was a FTC block 4 hours and 45 minutes ago... nothing since then has shown or credited...
The multiport hasn't been on FTC for about that amount of time.. Yes i fugured.... i checked all the other coins when i posted and they were all much longer... 5 hours to 12 hours... since that block nothing had been found according to stats. |
|
|
|
|
Yeaah a lot going wrong here... last found block was a FTC block 4 hours and 45 minutes ago... nothing since then has shown or credited...
|
|
|
|
|
Is something worng... or are the pools being EXTREMELY unlucky... when was the last time a block was found? On any coin?
|
|
|
|
|
Hours later... double payouts STILL happening... what gives?
Now im negative MNC and LKY... with a recent MNC payout being sent as a double payout over 2 hours AFTER the first payout credited... so... yeah...
|
|
|
|
One question to devs.
Where are transaction fees come for now.
As i see on my pool wallet and blockchain explorer, every "generate" block are extactly 5.00 HBN, even if block not empty and included some transations with fees.
These fees simply disappears somewhere. On other coins transaction fees is included into generate transaction.
Its by design or there are some bug in the code?
This is a legitimate question... blundertoe, shakezula and maybe mullick... this deserves an answer. |
|
|
|
I will give you PHS to take the time to make a MEGA account and use that... RapidShare is just so slow and lame... DONE: you can get the BETA Version of 1.2 Philosopherstone-qt.exe in RAR format at the following link: https://mega.co.nz/#!2BcElLza!DvzqCDg0NXSNfRZQ5TIa6y_ssBAslUjk3fF4WO8em1k (the Bang that mega uses usually busts the link, so copy and paste into browser is best) digeros, post addy ill send some PHS your way... but I really wanted PalmDetroit to start using Mega. Also... to fix the Mega link issue... instead of leaving the whole URL in between the tags... change the opening tag to have it as url=THIS IS THE FULLADDRES inside the brackets and then type a name for the link to be displayed... like the below... This is the same as the URL posted above |
|
|
|
I will give you PHS to take the time to make a MEGA account and use that... RapidShare is just so slow and lame... |
|
|
|
|
This needs to die... so tat diff will drop and ppl will stop having issues syncing.
When can these bad nodes be blocked?
18:03:21

getpeerinfo
18:03:21

[
{
"addr" : "198.50.233.22:16281",
"services" : "00000001",
"lastsend" : 1376517798,
"lastrecv" : 1376517798,
"conntime" : 1376515359,
"version" : 60006,
"subver" : "/Satoshi:0.7.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 9346,
"banscore" : 0
},
{
"addr" : "174.129.1.17:16281",
"services" : "00000001",
"lastsend" : 1376517465,
"lastrecv" : 1376517465,
"conntime" : 1376515378,
"version" : 60006,
"subver" : "/Satoshi:0.7.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 8500,
"banscore" : 0
},
{
"addr" : "64.120.17.149:38262",
"services" : "00000001",
"lastsend" : 1376517465,
"lastrecv" : 1376516840,
"conntime" : 1376515399,
"version" : 60006,
"subver" : "/Satoshi:0.7.2/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 9346,
"banscore" : 0
},
{
"addr" : "188.252.16.109:46477",
"services" : "00000001",
"lastsend" : 1376517605,
"lastrecv" : 1376517605,
"conntime" : 1376515876,
"version" : 60006,
"subver" : "/Satoshi:0.7.2/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 8632,
"banscore" : 0
},
{
"addr" : "74.71.187.106:49455",
"services" : "00000001",
"lastsend" : 1376517801,
"lastrecv" : 1376517801,
"conntime" : 1376515966,
"version" : 60006,
"subver" : "/Satoshi:0.7.2/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 9346,
"banscore" : 0
},
{
"addr" : "62.43.138.9:62145",
"services" : "00000001",
"lastsend" : 1376517673,
"lastrecv" : 1376517673,
"conntime" : 1376516984,
"version" : 60006,
"subver" : "/Satoshi:0.7.2/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 852,
"banscore" : 0
},
{
"addr" : "94.69.229.191:16281",
"services" : "00000001",
"lastsend" : 1376517659,
"lastrecv" : 1376517658,
"conntime" : 1376517028,
"version" : 60006,
"subver" : "/Satoshi:0.7.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 436,
"banscore" : 0
},
]
|
|
|
|
|
BitJohn you MUST save the Elephants!
|
|
|
|
Actually I ran this several times in a few different combinations just to see... and it is clear... there are peers at three different points of the chain sharing with everyone. So, to clear this up once and for all... I followed the steps again, but this time I set all addnodes to connect= and added all the ones that showed they were on block 11200+ and then started with 1.0 and chaged to 1.2. Flawless. Fast. Done. To help out anyone who does not want to go through this, I made a zip of the 1.0 and 1.2 versions of PHS and included a conf file with the connect entries... once synced you should be able to change them to addnodes and be fine. This also includes block0001.dat with blkindex.dat synced to block 11225 and my peers.dat at the time of me closing the client. Use at your own risk, I have no reason to have tampered with these but you should not just trust anyone who uploads anything and posts here. Do your due diligence, scan it etc. I take ZERO responsibility for loss of coins or anything else that might happen. PHS8-13-13.zip |
|
|
|
|
so what block is this supposed to be on now? Pool and client show 11200+ but even the method above I cant break 7900s...
|
|
|
|
|
Show Posts
