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.
Topic: [ANN]Joincoin (J) ToR Anonymous All Algorithm mining! *1.3 WALLET UPDATE!* - page 36. (Read 118644 times)
August 13, 2014, 07:55:57 PM
August 13, 2014, 07:55:15 PM
Ehi guys, DEV will work on the code. Where is the problem? Stay calm and BUY LOW!
+1
August 13, 2014, 07:54:36 PM
"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)
"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.
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.
August 13, 2014, 07:52:48 PM
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!
August 13, 2014, 07:52:32 PM
I NEED A NODE TO CONNECT MY WALLET !!!!!!!
nodes
nodes
nodes
nodes
nodes
nodes
nodes
nodes
August 13, 2014, 07:39:56 PM
"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)
"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.
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.
August 13, 2014, 07:38:56 PM
Any nodes
August 13, 2014, 07:37:10 PM
"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)
"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.
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.
August 13, 2014, 07:33:41 PM
buy buy buy buy buy buy buy buy buy
August 13, 2014, 07:33:32 PM
I need nodes
Any nodes? Wallet has no block source
Any nodes? Wallet has no block source
August 13, 2014, 07:29:51 PM
Copychicken from C-Cex said:
"Copychicken: can someone post in the Jcoin thread that the scrypt Jcoin from poolsofhonor is down until the update???"
"Copychicken: can someone post in the Jcoin thread that the scrypt Jcoin from poolsofhonor is down until the update???"
August 13, 2014, 07:29:32 PM
Ehi guys, DEV will work on the code. Where is the problem? Stay calm and BUY LOW!
August 13, 2014, 07:26:22 PM
Ok everyone to explain the situation, the issue was once a certain algo's diff goes over a certain point other algo's wont find blocks. We have a fix for this but cannot implement it until C-CEX is able to update their wallet otherwise we would create a fork. So for now use sha algo and we have contacted C-CEX to be ready to update to the updated wallet that fixes this issue. My team and I are terribly sorry for the inconvenience and it will be rectified as soon as possible. Once we have support's attention at C-CEX this should be a smooth transition.
many people have dumped into you wall at 1800 what will happen to those coins. will they be given back to those that dumped or destroyed
Trade at your own risk.
/ 
lol right? I didn't dump so we'll see tomorrow if I made a good deal or not lol.
August 13, 2014, 07:24:07 PM
Ok everyone to explain the situation, the issue was once a certain algo's diff goes over a certain point other algo's wont find blocks. We have a fix for this but cannot implement it until C-CEX is able to update their wallet otherwise we would create a fork. So for now use sha algo and we have contacted C-CEX to be ready to update to the updated wallet that fixes this issue. My team and I are terribly sorry for the inconvenience and it will be rectified as soon as possible. Once we have support's attention at C-CEX this should be a smooth transition.
many people have dumped into you wall at 1800 what will happen to those coins. will they be given back to those that dumped or destroyed
Trade at your own risk.
/ August 13, 2014, 07:19:01 PM
Ok everyone to explain the situation, the issue was once a certain algo's diff goes over a certain point other algo's wont find blocks. We have a fix for this but cannot implement it until C-CEX is able to update their wallet otherwise we would create a fork. So for now use sha algo and we have contacted C-CEX to be ready to update to the updated wallet that fixes this issue. My team and I are terribly sorry for the inconvenience and it will be rectified as soon as possible. Once we have support's attention at C-CEX this should be a smooth transition.
many people have dumped into you wall at 1800 what will happen to those coins. will they be given back to those that dumped or destroyed
did you just ask that?lol
i want them destroyed but considering the code is messed up it doesnt matter
August 13, 2014, 07:16:04 PM
Ok everyone to explain the situation, the issue was once a certain algo's diff goes over a certain point other algo's wont find blocks. We have a fix for this but cannot implement it until C-CEX is able to update their wallet otherwise we would create a fork. So for now use sha algo and we have contacted C-CEX to be ready to update to the updated wallet that fixes this issue. My team and I are terribly sorry for the inconvenience and it will be rectified as soon as possible. Once we have support's attention at C-CEX this should be a smooth transition.
many people have dumped into you wall at 1800 what will happen to those coins. will they be given back to those that dumped or destroyed
did you just ask that?lol
August 13, 2014, 07:12:39 PM
Well.. At least the code has been reviewed
SCNR
SCNR
August 13, 2014, 07:12:12 PM
Ok everyone to explain the situation, the issue was once a certain algo's diff goes over a certain point other algo's wont find blocks. We have a fix for this but cannot implement it until C-CEX is able to update their wallet otherwise we would create a fork. So for now use sha algo and we have contacted C-CEX to be ready to update to the updated wallet that fixes this issue. My team and I are terribly sorry for the inconvenience and it will be rectified as soon as possible. Once we have support's attention at C-CEX this should be a smooth transition.
+1 August 13, 2014, 07:08:21 PM
Ok everyone to explain the situation, the issue was once a certain algo's diff goes over a certain point other algo's wont find blocks. We have a fix for this but cannot implement it until C-CEX is able to update their wallet otherwise we would create a fork. So for now use sha algo and we have contacted C-CEX to be ready to update to the updated wallet that fixes this issue. My team and I are terribly sorry for the inconvenience and it will be rectified as soon as possible. Once we have support's attention at C-CEX this should be a smooth transition.
many people have dumped into you wall at 1800 what will happen to those coins. will they be given back to those that dumped or destroyed
August 13, 2014, 07:07:32 PM
Ok everyone to explain the situation, the issue was once a certain algo's diff goes over a certain point other algo's wont find blocks. We have a fix for this but cannot implement it until C-CEX is able to update their wallet otherwise we would create a fork. So for now use sha algo and we have contacted C-CEX to be ready to update to the updated wallet that fixes this issue. My team and I are terribly sorry for the inconvenience and it will be rectified as soon as possible. Once we have support's attention at C-CEX this should be a smooth transition.
Yeah, when you cloned Myriadcoin you left out that important bug fix
Jump to: