[ANN][JPC]MAKE JACKPOTCOIN GREAT AGAIN!

[Spoetnik]

Jackpotcoin Mining Pool Hub
http://jackpotcoin.miningpoolhub.com

Just distributed 583163 block's Jackpot!

http://explorer.jpcpal.com/block.php?height=583163
- Distributed to miners who mined for 583162 block
- 50% to the finder, 50% to rest of miners.
- 20568524.094792 JPC!


Happy Mining!

figures after i switched pools lol
congrats to guys who won !

[wacko]

PoS:
- 20 sec block target
- diff retarget each block
- PoS daily interest payout initially at 0.1% per day (equivalent to 44% annual interest rate), gradually dropping down to 0.01% per day (equivalent to 3.7% annual rate), the decrease will be over a period of 5 years (rate adjusted each 3 months). Then it will stay at this rate.
- minimum holding time before the pos will be generated: 1 day.
- max accumulated coin-day is 30 days (after 30 days, only the 130-day coin-day will be counted).

So, you must calculate % yourself - guess nobody done this yet
[/quote]
Ok, so it started with 0.1% per day and is gradually dropping down to 0.01% per day over a period of 5 years. If it's adjusting once per 3 months, that's what, 20 adjustments in total? Considering that it all started on April 26, there's been one adjustment already, so the current interest should be somewhere around 0.095%, and it'll drop down to ~ 0.09% in October.  

And what does this mean: "max accumulated coin-day is 30 days (after 30 days, only the 130-day coin-day will be counted)"? I suppose "130-day" is a typo and it should be "30-day". But I don't get this "coin-day" thing. With 10mil in the wallet, 0.095% is just 9500 JPC per day, which is kinda low compared to PoW mining. I mean, to buy 10mil JPC, one needs to spend at least 1 BTC, so one loses 1 BTC to buy some alt. currency (that's been going down in price for quite some time now) and in return gets less than 10k JPC per day via staking. But with 1 BTC one can easily buy 3x 750 Ti, and each of those 750 Ti cards makes ~10k JPC a day, so it's ~30k JPC a day for the same 1 BTC spent, which even with expensive electricity is still at least twice more profitable than going to an exchange and buying those 10mil JPC for staking. Buying GPUs is also a lot safer investment than buying coins.

I'm curious though whether my math is right, cause someone in this topic previously said that they were making more money from staking JPC than from mining. Maybe it's not 9-10k a day with 10mil in the wallet, but more? This "coin-day" thing is a mystery for now. Anyway, sorry if it all sounds dumb, I'm totally new to PoS and reading introductory articles about it didn't help, still not clear on the subject. Can anyone that does staking give an example of how much they've got in their wallet and how much they make with PoS?

[bee7]

Guys, can anyone explain how to calculate staking profits? Say I buy 10 mil JPC and put them in my wallet, start staking.. how much will I make on average in a day/week?

You will get your profits according to the schedule:

- PoS daily interest payout initially at 0.1% per day (equivalent to 44% annual interest rate), gradually dropping down to 0.01% per day (equivalent to 3.7% annual rate), the decrease will be over a period of 5 years (rate adjusted each 3 months). Then it will stay at this rate.

You get it regardless of how often you find a stake block. The reward for stake block depends only on 'coin-age' of an input participated in the block creation and the input value. Literally, the age of an input expressed in days multiplied by the value of the input expressed in full coins. The coin-age then multiplied by the current reward rate which is 0.0955% ATM.


@Spoetnik:

JPC was hacked months ago for some many millions of coins via users (not exchanges) (it was an RPC exploit vulnerable on lots of coins)
and the hacker dumped them all on exchanges tanking the price and it never recovered !

Could you please elaborate what you meant. I am asking as an another coin dev to take countermeasures if this issue actually has place.

[TheCoinFinder]

JPC was hacked months ago for some many millions of coins via users (not exchanges) (it was an RPC exploit vulnerable on lots of coins)
and the hacker dumped them all on exchanges tanking the price and it never recovered !

Could you please elaborate what you meant. I am asking as an another coin dev to take countermeasures if this issue actually has place.

Apparently a lot of people had their rpclisten set to a publically accessible IP address (rather than the standard and default 127.0.0.1) - further, this address was not behind any sort of NAT or firewall - and had a guessable password (presumably some default one).

I can't really call it an exploit.

[bee7]

JPC was hacked months ago for some many millions of coins via users (not exchanges) (it was an RPC exploit vulnerable on lots of coins)
and the hacker dumped them all on exchanges tanking the price and it never recovered !

Could you please elaborate what you meant. I am asking as an another coin dev to take countermeasures if this issue actually has place.

Apparently a lot of people had their rpclisten set to a publically accessible IP address (rather than the standard and default 127.0.0.1) - further, this address was not behind any sort of NAT or firewall - and had a guessable password (presumably some default one).

I can't really call it an exploit.

Thank you
I was told already the same version of story, I just want to make sure that Spoetnik does not know something different

[jhed]

Hello All,

I'm new to JPC and I'm having trouble synchronizing my wallet past block 500000. I found the following information in my debug.log:

Code:

08/16/14 14:30:01 ERROR: CheckProofOfStake() : INFO: read txPrev failed
08/16/14 14:30:01 WARNING: ProcessBlock(): check proof-of-stake failed for block ac923d44cbeea785da2464fc5235f3aec6d046af9164e2dc33f700d91d7cc719
08/16/14 14:30:04 ERROR: AcceptBlock() : rejected by hardened checkpoint lock-in at 500001
08/16/14 14:30:04 ERROR: ProcessBlock() : AcceptBlock FAILED
08/16/14 14:30:04 Misbehaving: 67.8.38.82:15371 (0 -> 100) DISCONNECTING
08/16/14 14:30:04 disconnecting node 67.8.38.82:15371

I built my wallet from from the latest source on github (ece0c8abf7). Any help would be greatly appreciated.

fwiw, I've git reset my local repo to the PoS Bugfix commit (df207d524c), rebuilt, and I'm trying to sync the blockchain from scratch now. I wonder if I'll run into the same issue.

I was able to sync the whole chain from scratch from the PoS Bugfix commit (v1.4.1.0), but not from the latest commit (v1.5.0 Final Beta).

[Spoetnik]

JPC was hacked months ago for some many millions of coins via users (not exchanges) (it was an RPC exploit vulnerable on lots of coins)
and the hacker dumped them all on exchanges tanking the price and it never recovered !

Could you please elaborate what you meant. I am asking as an another coin dev to take countermeasures if this issue actually has place.

Apparently a lot of people had their rpclisten set to a publically accessible IP address (rather than the standard and default 127.0.0.1) - further, this address was not behind any sort of NAT or firewall - and had a guessable password (presumably some default one).

I can't really call it an exploit.

Thank you
I was told already the same version of story, I just want to make sure that Spoetnik does not know something different

ya what he said
and i am not sure a firewall would help ..that should be looked into !
you see we're going to be exempting the miner to go online on the internet inbound and outbound right ?

also some other guy posted a way for you to check if your vulnerable by using your browser..
you you check out this topic further pages back so we don't have to repeat it all from memory

and call it what you want but it must have been a big problem for so many coins to have been stolen. (i heard this affects other coins too)

[bee7]

JPC was hacked months ago for some many millions of coins via users (not exchanges) (it was an RPC exploit vulnerable on lots of coins)
and the hacker dumped them all on exchanges tanking the price and it never recovered !

Could you please elaborate what you meant. I am asking as an another coin dev to take countermeasures if this issue actually has place.

Apparently a lot of people had their rpclisten set to a publically accessible IP address (rather than the standard and default 127.0.0.1) - further, this address was not behind any sort of NAT or firewall - and had a guessable password (presumably some default one).

I can't really call it an exploit.

Thank you
I was told already the same version of story, I just want to make sure that Spoetnik does not know something different

ya what he said
and i am not sure a firewall would help ..that should be looked into !
you see we're going to be exempting the miner to go online on the internet inbound and outbound right ?

also some other guy posted a way for you to check if your vulnerable by using your browser..
you you check out this topic further pages back so we don't have to repeat it all from memory

and call it what you want but it must have been a big problem for so many coins to have been stolen. (i heard this affects other coins too)

Then this is not a vulnerability of a wallet software (the assumption I did as you mentioned "lots of coins"), but a question of a misconfiguration. With all due respect, could you please be more precise in the future.

Thank you.

[jhed]

Hello All,

I'm new to JPC and I'm having trouble synchronizing my wallet past block 500000. I found the following information in my debug.log:

Code:

08/16/14 14:30:01 ERROR: CheckProofOfStake() : INFO: read txPrev failed
08/16/14 14:30:01 WARNING: ProcessBlock(): check proof-of-stake failed for block ac923d44cbeea785da2464fc5235f3aec6d046af9164e2dc33f700d91d7cc719
08/16/14 14:30:04 ERROR: AcceptBlock() : rejected by hardened checkpoint lock-in at 500001
08/16/14 14:30:04 ERROR: ProcessBlock() : AcceptBlock FAILED
08/16/14 14:30:04 Misbehaving: 67.8.38.82:15371 (0 -> 100) DISCONNECTING
08/16/14 14:30:04 disconnecting node 67.8.38.82:15371

I built my wallet from from the latest source on github (ece0c8abf7). Any help would be greatly appreciated.

fwiw, I've git reset my local repo to the PoS Bugfix commit (df207d524c), rebuilt, and I'm trying to sync the blockchain from scratch now. I wonder if I'll run into the same issue.

I was able to sync the whole chain from scratch from the PoS Bugfix commit (v1.4.1.0), but not from the latest commit (v1.5.0 Final Beta).

Bug confirmed and fixed. I'm syncing past 500000 now. If you're here dev, thank you.
https://github.com/rtc29462/JackpotCoin/issues/2

[Spoetnik]

JPC was hacked months ago for some many millions of coins via users (not exchanges) (it was an RPC exploit vulnerable on lots of coins)
and the hacker dumped them all on exchanges tanking the price and it never recovered !

Could you please elaborate what you meant. I am asking as an another coin dev to take countermeasures if this issue actually has place.

Apparently a lot of people had their rpclisten set to a publically accessible IP address (rather than the standard and default 127.0.0.1) - further, this address was not behind any sort of NAT or firewall - and had a guessable password (presumably some default one).

I can't really call it an exploit.

Thank you
I was told already the same version of story, I just want to make sure that Spoetnik does not know something different

ya what he said
and i am not sure a firewall would help ..that should be looked into !
you see we're going to be exempting the miner to go online on the internet inbound and outbound right ?

also some other guy posted a way for you to check if your vulnerable by using your browser..
you you check out this topic further pages back so we don't have to repeat it all from memory

and call it what you want but it must have been a big problem for so many coins to have been stolen. (i heard this affects other coins too)

Then this is not a vulnerability of a wallet software (the assumption I did as you mentioned "lots of coins"), but a question of a misconfiguration. With all due respect, could you please be more precise in the future.

Thank you.

read the changlog buddy.. why does it say "fixed bug" and they changed the code why ? because of misconfiguration ??
..gimme a break with your argumentative fucking bulllshit
quit picking at my ass.. and next time stfu and do your own homework then harassing me to do it for you.
the first reply said it was on previous pages..
you could have just shit the fuck up and went and read them instead you kept harping on me like a mouthy fucking cunt nagging and nagging

[Spoetnik]

Hello All,

I'm new to JPC and I'm having trouble synchronizing my wallet past block 500000. I found the following information in my debug.log:

Code:

08/16/14 14:30:01 ERROR: CheckProofOfStake() : INFO: read txPrev failed
08/16/14 14:30:01 WARNING: ProcessBlock(): check proof-of-stake failed for block ac923d44cbeea785da2464fc5235f3aec6d046af9164e2dc33f700d91d7cc719
08/16/14 14:30:04 ERROR: AcceptBlock() : rejected by hardened checkpoint lock-in at 500001
08/16/14 14:30:04 ERROR: ProcessBlock() : AcceptBlock FAILED
08/16/14 14:30:04 Misbehaving: 67.8.38.82:15371 (0 -> 100) DISCONNECTING
08/16/14 14:30:04 disconnecting node 67.8.38.82:15371

I built my wallet from from the latest source on github (ece0c8abf7). Any help would be greatly appreciated.

fwiw, I've git reset my local repo to the PoS Bugfix commit (df207d524c), rebuilt, and I'm trying to sync the blockchain from scratch now. I wonder if I'll run into the same issue.

I was able to sync the whole chain from scratch from the PoS Bugfix commit (v1.4.1.0), but not from the latest commit (v1.5.0 Final Beta).

Bug confirmed and fixed. I'm syncing past 500000 now. If you're here dev, thank you.
https://github.com/rtc29462/JackpotCoin/issues/2

Awesome great work guys !! 
I take it we will get a wallet update soon then eh ?

[bee7]

JPC was hacked months ago for some many millions of coins via users (not exchanges) (it was an RPC exploit vulnerable on lots of coins)
and the hacker dumped them all on exchanges tanking the price and it never recovered !

Could you please elaborate what you meant. I am asking as an another coin dev to take countermeasures if this issue actually has place.

Apparently a lot of people had their rpclisten set to a publically accessible IP address (rather than the standard and default 127.0.0.1) - further, this address was not behind any sort of NAT or firewall - and had a guessable password (presumably some default one).

I can't really call it an exploit.

Thank you
I was told already the same version of story, I just want to make sure that Spoetnik does not know something different

ya what he said
and i am not sure a firewall would help ..that should be looked into !
you see we're going to be exempting the miner to go online on the internet inbound and outbound right ?

also some other guy posted a way for you to check if your vulnerable by using your browser..
you you check out this topic further pages back so we don't have to repeat it all from memory

and call it what you want but it must have been a big problem for so many coins to have been stolen. (i heard this affects other coins too)

Then this is not a vulnerability of a wallet software (the assumption I did as you mentioned "lots of coins"), but a question of a misconfiguration. With all due respect, could you please be more precise in the future.

Thank you.

read the changlog buddy.. why does it say "fixed bug" and they changed the code why ? because of misconfiguration ??
..gimme a break with your argumentative fucking bulllshit
quit picking at my ass.. and next time stfu and do your own homework then harassing me to do it for you.
the first reply said it was on previous pages..
you could have just shit the fuck up and went and read them instead you kept harping on me like a mouthy fucking cunt nagging and nagging

Relax a bit please. I just asked what you meant and you replied that it was misconf issue. Now you say, that some fixes to the code were done. It was so difficult to say it from the very begin?

Ok, let's look what you are talking about. The only relevant change I found is in commit https://github.com/rtc29462/JackpotCoin/commit/4e0eb23dec09eeac9943ea24f56ede0d678cb16d#diff-d41d8cd98f00b204e9800998ecf8427e, file bitcoinrpc:

Code:

@@ -531,9 +531,18 @@ bool ClientAllowed(const boost::asio::ip::address& address)
 
     const string strAddress = address.to_string();
     const vector<string>& vAllow = mapMultiArgs["-rpcallowip"];
-    BOOST_FOREACH(string strAllow, vAllow)
-        if (WildcardMatch(strAddress, strAllow))
-            return true;
+
+    //
+    // minimumn 8 characters for IP address, so, * or *.*.*.* will be ignored
+    // need to set more detail IP address with wile card
+    //
+    BOOST_FOREACH(string strAllow, vAllow) {
+        if (strAllow.length() > 7) {
+            if (WildcardMatch(strAddress, strAllow)) {
+                return true;
+            }
+        }
+    }
     return false;
 }

Is that a fix of a vulnerability??? It is a fix of stupidity of some representatives of the mankind.

The WildcardMatch function looks completely fine. Its implementation in JPC source tree is the same as the original bitcoin wallet has. Though, the bitcoin's version ClientAllowed has some ipv6 related fixes, but the rest of the code is the same as above without the "fix". So, is Gavin Andersen not aware of this "vulnerability" also?

I had no intention to offend you anyhow, I asked you to give the things their real names. Your reply was rude. Adults do not conduct themselves this way IMO.

[Dotcommie]

Relax a bit please. I just asked what you meant and you replied that it was misconf issue. Now you say, that some fixes to the code were done. It was so difficult to say it from the very begin?

Ok, let's look what you are talking about. The only relevant change I found is in commit https://github.com/rtc29462/JackpotCoin/commit/4e0eb23dec09eeac9943ea24f56ede0d678cb16d#diff-d41d8cd98f00b204e9800998ecf8427e, file bitcoinrpc:

Code:

@@ -531,9 +531,18 @@ bool ClientAllowed(const boost::asio::ip::address& address)
 
     const string strAddress = address.to_string();
     const vector<string>& vAllow = mapMultiArgs["-rpcallowip"];
-    BOOST_FOREACH(string strAllow, vAllow)
-        if (WildcardMatch(strAddress, strAllow))
-            return true;
+
+    //
+    // minimumn 8 characters for IP address, so, * or *.*.*.* will be ignored
+    // need to set more detail IP address with wile card
+    //
+    BOOST_FOREACH(string strAllow, vAllow) {
+        if (strAllow.length() > 7) {
+            if (WildcardMatch(strAddress, strAllow)) {
+                return true;
+            }
+        }
+    }
     return false;
 }

Is that a fix of a vulnerability??? It is a fix of stupidity of some representatives of the mankind.

The WildcardMatch function looks completely fine. Its implementation in JPC source tree is the same as the original bitcoin wallet has. Though, the bitcoin's version ClientAllowed has some ipv6 related fixes, but the rest of the code is the same as above without the "fix". So, is Gavin Andersen not aware of this "vulnerability" also?

I had no intention to offend you anyhow, I asked you to give the things their real names. Your reply was rude. Adults do not conduct themselves this way IMO.

Don't worry about it.  Any wallet that used just a * for the allowip in the conf file could be affected the same way.  I heard the difference is that since the coin was big in Korea and a lot may be running an outdated OS or not running a firewall, it was just easier to get in and initiate a command that sent the balance wherever they wanted.  Definitely not a code issue, more of a security issue.  I remember when the coin launched the example conf file had just the wildcard *.  Not sure if it was in the OP or right after it, but yeah, it won't allow you to just use that anymore so it would be a lot harder. Somebody could still get onto your network and if they know what ips you're allowing, they could do the same thing as far as i know.

[tc61]

Commie, how is hanging man..have not seen you around since the mineip days....you still think there is life left in JPC?

[Dotcommie]

Commie, how is hanging man..have not seen you around since the mineip days....you still think there is life left in JPC?

Hah, I'm still in here pretty regularly.  I still think there is plenty of life, but there were just too many holders of JPC before.  All alt coins are down and BTC is taking a dive of $10-20 per day it seems, so something should happen eventually.  I tried to trick people into selling JPC for cheap a while ago, but it didn't keep moving down.  Now it looks like buy support was pulled. Probably until the markets pick back up, but who knows.  It really just takes 1 or 2 committed people with a few extra BTC to get things moving again, so I'll just sit on it like I'm sitting on a couple other coins that took a dive.

We have a much more even distribution on the rich list as well, so I would assume there will be decent movement in the future, but nothing is certain.  I do know there hasn't been any major problems with the coin, wallet, or dev...which is a rare thing these days, so I think there are still good things to come for jpc.

[wacko]

Me again with noob PoS questions. So, I bought 1mil JPC and put them into my wallet, kept the wallet open. First 24 hours my "weight" was ~0 and "expected time to earn reward" was like a few years. Nothing changed after 24 hours, so I restarted the wallet. After restart, "weight" changed to 7131 and "expected time" changed to 249 days. I left the wallet open and checked it again ~ 8 hours later: nothing's changed. Exactly the same weight and time. So I restarted the wallet again, and after the restart the weight changed to 186003 and time changed to 14 days. The wallet is always synced, it always says "minting", yet these 2 values never update unless I restart the wallet. After ~ 3 hours with no change I restarted the wallet again and now it's 280777 & 7 days.

So, is it a normal behavior? Why don't those values update without manual restart?

[zuludrag]

Me again with noob PoS questions. So, I bought 1mil JPC and put them into my wallet, kept the wallet open. First 24 hours my "weight" was ~0 and "expected time to earn reward" was like a few years. Nothing changed after 24 hours, so I restarted the wallet. After restart, "weight" changed to 7131 and "expected time" changed to 249 days. I left the wallet open and checked it again ~ 8 hours later: nothing's changed. Exactly the same weight and time. So I restarted the wallet again, and after the restart the weight changed to 186003 and time changed to 14 days. The wallet is always synced, it always says "minting", yet these 2 values never update unless I restart the wallet. After ~ 3 hours with no change I restarted the wallet again and now it's 280777 & 7 days.

So, is it a normal behavior? Why don't those values update without manual restart?

I was writing about this before, but dev did not fixed it with last update. Stake weight does not update automatically.
And for the first stake usually (with today's network weight) it takes around 4-7 days for the first stake...

p.s.: values are updated too if you lock and unlock your wallet - no need to restart

[bee7]

Me again with noob PoS questions. So, I bought 1mil JPC and put them into my wallet, kept the wallet open. First 24 hours my "weight" was ~0 and "expected time to earn reward" was like a few years. Nothing changed after 24 hours, so I restarted the wallet. After restart, "weight" changed to 7131 and "expected time" changed to 249 days. I left the wallet open and checked it again ~ 8 hours later: nothing's changed. Exactly the same weight and time. So I restarted the wallet again, and after the restart the weight changed to 186003 and time changed to 14 days. The wallet is always synced, it always says "minting", yet these 2 values never update unless I restart the wallet. After ~ 3 hours with no change I restarted the wallet again and now it's 280777 & 7 days.

So, is it a normal behavior? Why don't those values update without manual restart?

It is a bug in representation layer. You need not to restart the wallet, as the stake searching function that is run in background persistently loops through all available inputs and recalculates their weights on every pass. Roughly, expected time is an estimation how long it would take to find a stake using that particular input provided the weight would not change and the PoS difficulty would be the same. As time goes the weight grows, so the probability to find a stake increases and the expected time to find a stake decreases. The behavior you observe is not a real picture, but a result of not updating the stats in the user interface. The figures you got restarting the wallet are showing how these parameters are changing with time. If there were no bug you would see the stats changing in the real time.


@Dev:

Code:

void BitcoinGUI::updateMintingWeights()
{
    // Only update if we have the network's current number of blocks, or weight(s) are zero (fixes lagging GUI)
    if ((clientModel && clientModel->getNumBlocks() == clientModel->getNumBlocksOfPeers()) || !nWeight || !nNetworkWeight)
    {
        nWeight = 0;

        if (pwalletMain)
            pwalletMain->GetStakeWeight(*pwalletMain, nMinMax, nMinMax, nWeight);

        nNetworkWeight = GetPoSKernelPS();
    }
}

::getNumBlocksOfPeers() may report a value different than its previous result only when a new node got connected between its successive calls. When the wallet could not accept inbound connections (e.g. it is behind a firewall and there is no port forwarding) and it reached the maximum number of outbound connections the code above would not trigger the UI update until the set of connected nodes is changed.

Edit: generally, the ::getNumBlocksOfPeers() value changes only when a new node connected.

[Tyr808]

Just got my 750ti back from MSI's repair today.  Feels good to be mining the JPC again

[tc61]

It would feel better if we were above 15 LOL welcome back