Topic: [ANN]Joincoin (J) ToR Anonymous All Algorithm mining! *1.3 WALLET UPDATE!* - page 35. (Read 118639 times)
August 14, 2014, 02:58:22 AM
anyhow the coin has had a bad start it may have danaged confidence investors maybe looking for a quick exit
August 14, 2014, 01:02:34 AM
Wel, this is just not another thing. This could be used to further secure the chains of all the coins, think on myriad.
August 14, 2014, 12:39:55 AM
any sha256 pools?
or we need to wait until the updated released?
or we need to wait until the updated released?
I think we just waiting on C-CEX admins to update the wallet. Need main guy who has access.
August 14, 2014, 12:34:20 AM
any sha256 pools?
or we need to wait until the updated released?
or we need to wait until the updated released?
August 13, 2014, 11:35:51 PM
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?
I'm not sure. I believe Pride mentioned something about only one person having access to part of the server to update the new wallet, so we would have to wait on him.
patience will pay off guys ! August 13, 2014, 11:09:38 PM
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?
I'm not sure. I believe Pride mentioned something about only one person having access to part of the server to update the new wallet, so we would have to wait on him.
August 13, 2014, 11:05:15 PM
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?
August 13, 2014, 10:59:59 PM
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.
August 13, 2014, 10:59:28 PM
very good
August 13, 2014, 10:24:06 PM
current price is not worth for mining 
August 13, 2014, 10:21:04 PM
_
August 13, 2014, 10:20:15 PM
so we are all stuck on 416
August 13, 2014, 10:17:32 PM
need nodes.
not sure if this will help since my client is dead at block 416 but here ya go
Code:
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
}
]
August 13, 2014, 10:16:02 PM
need nodes.
August 13, 2014, 10:01:50 PM
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.
August 13, 2014, 09:38:46 PM
okay understandable. can anyone tell me if i have the values correct then?
August 13, 2014, 09:36:49 PM
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'),
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'),
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.
August 13, 2014, 09:04:51 PM
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'),
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'),
August 13, 2014, 09:02:43 PM
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!
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!
August 13, 2014, 09:01:15 PM
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.
Jump to: