sushipooo
Member
 Offline
Activity: 84
Merit: 10
|
 |
August 14, 2014, 12:39:56 AM |
|
"version" : 1010101,
"protocolversion" : 1001,
"walletversion" : 300,
"balance" : 2.50000000,
"blocks" : 391,
"timeoffset" : -1,
"connections" : 12,
"proxy" : "",
"pow_algo_id" : 2,
"pow_algo" : "x13",
"difficulty" : 0.15833305,
"difficulty_sha" : 2385.81132495,
"difficulty_x11" : 4.01287318,
"difficulty_x13" : 0.15833305,
"difficulty_x15" : 0.02978161,
"difficulty_scrypt" : 0.01562477,
"difficulty_nist5" : 0.20509619,
"difficulty_groestle" : 8.95962472,
"difficulty_pentablake" : 0.38569512,
"difficulty_whirlpool" : 0.84984568,
"difficulty_luffa" : 0.79904166,
"difficulty_keccak" : 0.34481761,
"difficulty_quark" : 0.02626831,
"difficulty_bastion" : 0.49461871,
"testnet" : false,
"keypoololdest" : 1407970251,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"errors" : ""
@Dev: To give you a clue.. Check Diff and nBits ... (for the X algos)
Working quickly to fix this issue with the x algos before normal block rewards come in to play. Will have updated wallet and github asap. Good... Next time contact a pool admin for the code review and TEST it before (every algo, not just SHA)   We tested it and they all worked but this was at diffs we could produce, sha was not the only algo we tested and if you believe that then I am sorry for your misconception. Fix pushed to Github, compiling windows wallet now. I can easily get diff > 3 or 4 with a single 280x @ x11/x13/x15 ... I'll be standing clear from now on. Sorry guys - you'll be fine. +1 Maybe an apology in is in order to Ocminer, dude has run top notch pools for months and you crucify him trying for actually trying to tell people to do some due diligence? This coin's team should actually tap into his talent or people like him to find a simple flaw he found in the code in a very short amount of time. You cheerleaders amaze me at times. I gave him a +1 after the apology. |
|
|
|
MickGhee
Legendary
Offline
Activity: 1428
Merit: 1001
Fucker of "the system"
|
|
August 14, 2014, 12:52:32 AM |
|
I NEED A NODE TO CONNECT MY WALLET !!!!!!!
nodes
nodes
nodes
nodes
|
Last night, while you were sleeping. I fucked the system!
|
|
|
|
Reese212
|
|
August 14, 2014, 12:52:48 AM |
|
cool, i can call myself a market Manipulator with my 0.1btc buy @ 1800sat. i'm much more powerful than i thought, thanks for reminding me! |
Dear Lord, please grant me the ability...
|
|
|
|
AltcoinRambo
|
|
August 14, 2014, 12:54:36 AM |
|
"version" : 1010101,
"protocolversion" : 1001,
"walletversion" : 300,
"balance" : 2.50000000,
"blocks" : 391,
"timeoffset" : -1,
"connections" : 12,
"proxy" : "",
"pow_algo_id" : 2,
"pow_algo" : "x13",
"difficulty" : 0.15833305,
"difficulty_sha" : 2385.81132495,
"difficulty_x11" : 4.01287318,
"difficulty_x13" : 0.15833305,
"difficulty_x15" : 0.02978161,
"difficulty_scrypt" : 0.01562477,
"difficulty_nist5" : 0.20509619,
"difficulty_groestle" : 8.95962472,
"difficulty_pentablake" : 0.38569512,
"difficulty_whirlpool" : 0.84984568,
"difficulty_luffa" : 0.79904166,
"difficulty_keccak" : 0.34481761,
"difficulty_quark" : 0.02626831,
"difficulty_bastion" : 0.49461871,
"testnet" : false,
"keypoololdest" : 1407970251,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"errors" : ""
@Dev: To give you a clue.. Check Diff and nBits ... (for the X algos)
Working quickly to fix this issue with the x algos before normal block rewards come in to play. Will have updated wallet and github asap. Good... Next time contact a pool admin for the code review and TEST it before (every algo, not just SHA) We tested it and they all worked but this was at diffs we could produce, sha was not the only algo we tested and if you believe that then I am sorry for your misconception. Fix pushed to Github, compiling windows wallet now. I can easily get diff > 3 or 4 with a single 280x @ x11/x13/x15 ... I'll be standing clear from now on. Sorry guys - you'll be fine. +1 Maybe an apology in is in order to Ocminer, dude has run top notch pools for months and you crucify him trying for actually trying to tell people to do some due diligence? This coin's team should actually tap into his talent or people like him to find a simple flaw he found in the code in a very short amount of time. You cheerleaders amaze me at times. I don't think anybody has an issue with him pointing out that people should do their due diligence or pointing out legitimate flaws in the code. The issue was that his original posting was a bit FUDdy and threw around some wild accusations. All of this happened before the current wallet flaw was known. As for him finding the problem in the code: great job, there's nothing else to say about that part. |
|
|
|
|
|
AltcoinRambo
|
|
August 14, 2014, 12:55:15 AM |
|
Ehi guys, DEV will work on the code. Where is the problem? Stay calm and BUY LOW!
+1 |
|
|
|
|
billotronic
Legendary
Offline
Activity: 1610
Merit: 1000
Crackpot Idealist
|
|
August 14, 2014, 12:55:57 AM |
|
I might be stupid, but I cannot seem to get the qt to build on Linux Mint... I'm pretty sure this .pro file is garbage.
Anyone have any luck?
[edit] yes, the daemon built fine.
|
|
|
|
Love_of_Algo (OP)
Newbie
Offline
Activity: 25
Merit: 0
|
|
August 14, 2014, 01:01:15 AM |
|
Yes this is completely our mistake, when Pride at C-CEX looked over our code he wasn't looking for mining difficulty issues, was looking for malicious code. Ocminer we appreciate you pointing this out quickly so we could resolve it. Trying to say that C-CEX didn't do their due diligence is completely wrong though, this will be fixed and algorithms will all be working when we have contact with the main dev at C-CEx to update wallet. Again our apologies, this is not anyone's fault but a mistake on our part that was fixed in 5 minutes, we just cannot release the new github commit and wallet until C-CEX does to prevent a potential fork.
|
|
|
|
|
|
Cesare1985
|
|
August 14, 2014, 01:02:43 AM |
|
I'm boring. Too FUD on this thread.
The only thing I can say is: a big whale bought all the pre-sale and he'll sell his bag to 10K-15K.
Buy buy and good night!
|
|
|
|
|
infernoman
Legendary
Offline
Activity: 964
Merit: 1000
|
|
August 14, 2014, 01:04:51 AM
Last edit: August 14, 2014, 01:22:28 AM by infernoman |
|
having trouble finding some things in the source for the p2pool. the address_version and the p2p prefix or secret code for p2p https://github.com/joincoin/joincoin/blob/master/src/chainparams.cpp i am trying to use the values from here. address_version=43, p2p_prefix='f1b4dc9e'.decode('hex'), |
|
|
|
|
sushipooo
Member
Offline
Activity: 84
Merit: 10
|
|
August 14, 2014, 01:36:49 AM |
|
I'm not sure but I think there is an issue with mining until C-CEX main dude comes back and updates the wallet at CCEX. |
|
|
|
infernoman
Legendary
Offline
Activity: 964
Merit: 1000
|
|
August 14, 2014, 01:38:46 AM |
|
okay understandable. can anyone tell me if i have the values correct then?
|
|
|
|
|
sushipooo
Member
Offline
Activity: 84
Merit: 10
|
|
August 14, 2014, 02:01:50 AM |
|
okay understandable. can anyone tell me if i have the values correct then?
wish I could help bro, But I think everyone is waiting to see what info comes out from the devs and CCEX admins. |
|
|
|
|
|
billotronic
Legendary
Offline
Activity: 1610
Merit: 1000
Crackpot Idealist
|
|
August 14, 2014, 02:17:32 AM |
|
need nodes.
not sure if this will help since my client is dead at block 416 but here ya go 21:16:43

[
{
"addr" : "3o2mhw35ksxoo6pq.onion:17941",
"services" : "00000001",
"lastsend" : 1407982492,
"lastrecv" : 1407982493,
"bytessent" : 947,
"bytesrecv" : 582,
"conntime" : 1407982492,
"version" : 1001,
"subver" : "/Joincoin:1.1.1.1/",
"inbound" : false,
"startingheight" : 416,
"banscore" : 0,
"syncnode" : true
},
{
"addr" : "ja3v33azywzgxtju.onion:17941",
"services" : "00000001",
"lastsend" : 1407982497,
"lastrecv" : 1407982499,
"bytessent" : 246,
"bytesrecv" : 582,
"conntime" : 1407982496,
"version" : 1001,
"subver" : "/Joincoin:1.1.1.1/",
"inbound" : false,
"startingheight" : 416,
"banscore" : 0
},
{
"addr" : "vfuj3avleabbnsgt.onion:17941",
"services" : "00000001",
"lastsend" : 1407982500,
"lastrecv" : 1407982501,
"bytessent" : 246,
"bytesrecv" : 582,
"conntime" : 1407982500,
"version" : 1001,
"subver" : "/Joincoin:1.1.1.1/",
"inbound" : false,
"startingheight" : 416,
"banscore" : 0
},
{
"addr" : "fwhy5hy2ljmeeul2.onion:17941",
"services" : "00000001",
"lastsend" : 1407982509,
"lastrecv" : 1407982510,
"bytessent" : 246,
"bytesrecv" : 582,
"conntime" : 1407982508,
"version" : 1001,
"subver" : "/Joincoin:1.1.1.1/",
"inbound" : false,
"startingheight" : 416,
"banscore" : 0
},
{
"addr" : "m3l7qwq5ziadyj55.onion:17941",
"services" : "00000001",
"lastsend" : 1407982512,
"lastrecv" : 1407982513,
"bytessent" : 246,
"bytesrecv" : 582,
"conntime" : 1407982512,
"version" : 1001,
"subver" : "/Joincoin:1.1.1.1/",
"inbound" : false,
"startingheight" : 416,
"banscore" : 0
},
{
"addr" : "4yyak3dyhg2hh66w.onion:17941",
"services" : "00000001",
"lastsend" : 1407982520,
"lastrecv" : 1407982522,
"bytessent" : 246,
"bytesrecv" : 552,
"conntime" : 1407982519,
"version" : 1001,
"subver" : "/Joincoin:1.1.1.1/",
"inbound" : false,
"startingheight" : 416,
"banscore" : 0
},
{
"addr" : "ywh5ouwnhagz5sa2.onion:17941",
"services" : "00000001",
"lastsend" : 1407982525,
"lastrecv" : 1407982534,
"bytessent" : 246,
"bytesrecv" : 487,
"conntime" : 1407982524,
"version" : 1001,
"subver" : "/Joincoin:1.1.1.1/",
"inbound" : false,
"startingheight" : 416,
"banscore" : 0
},
{
"addr" : "127.0.0.1:59624",
"services" : "00000001",
"lastsend" : 1407982534,
"lastrecv" : 1407982529,
"bytessent" : 547,
"bytesrecv" : 191,
"conntime" : 1407982528,
"version" : 1001,
"subver" : "/Joincoin:1.1.1.1/",
"inbound" : true,
"startingheight" : 416,
"banscore" : 0
},
{
"addr" : "p46we3plowvljfqt.onion:17941",
"services" : "00000001",
"lastsend" : 1407982531,
"lastrecv" : 1407982532,
"bytessent" : 246,
"bytesrecv" : 582,
"conntime" : 1407982530,
"version" : 1001,
"subver" : "/Joincoin:1.1.1.1/",
"inbound" : false,
"startingheight" : 416,
"banscore" : 0
}
]
|
|
|
|
MickGhee
Legendary
Offline
Activity: 1428
Merit: 1001
Fucker of "the system"
|
|
August 14, 2014, 02:20:15 AM |
|
so we are all stuck on 416
|
Last night, while you were sleeping. I fucked the system!
|
|
|
billotronic
Legendary
Offline
Activity: 1610
Merit: 1000
Crackpot Idealist
|
|
August 14, 2014, 02:21:04 AM
Last edit: August 14, 2014, 12:23:50 PM by billotronic |
|
_
|
|
|
|
|
anhpt192
|
|
August 14, 2014, 02:24:06 AM |
|
current price is not worth for mining  |
|
|
|
|
BTMan
Full Member
Offline
Activity: 126
Merit: 100
BTMan
|
|
August 14, 2014, 02:59:28 AM |
|
very good
|
|
|
|
|
InitialDat
|
|
August 14, 2014, 02:59:59 AM |
|
Yes this is completely our mistake, when Pride at C-CEX looked over our code he wasn't looking for mining difficulty issues, was looking for malicious code. Ocminer we appreciate you pointing this out quickly so we could resolve it. Trying to say that C-CEX didn't do their due diligence is completely wrong though, this will be fixed and algorithms will all be working when we have contact with the main dev at C-CEx to update wallet. Again our apologies, this is not anyone's fault but a mistake on our part that was fixed in 5 minutes, we just cannot release the new github commit and wallet until C-CEX does to prevent a potential fork.
New wallet will be out soon. |
|
|
|
|
portice
Legendary
Offline
Activity: 999
Merit: 1000
|
|
August 14, 2014, 03:05:15 AM |
|
Yes this is completely our mistake, when Pride at C-CEX looked over our code he wasn't looking for mining difficulty issues, was looking for malicious code. Ocminer we appreciate you pointing this out quickly so we could resolve it. Trying to say that C-CEX didn't do their due diligence is completely wrong though, this will be fixed and algorithms will all be working when we have contact with the main dev at C-CEx to update wallet. Again our apologies, this is not anyone's fault but a mistake on our part that was fixed in 5 minutes, we just cannot release the new github commit and wallet until C-CEX does to prevent a potential fork.
New wallet will be out soon. Timeline for soon? |
|
|
|
|
|
