The new version will enter beta test next week. A lot of improvements are expected! Stay tuned!
Good to hear!
Topic: [ANN][JPC]MAKE JACKPOTCOIN GREAT AGAIN! - page 41. (Read 470275 times)
Good to hear!
Hello, i have little problem qith wallet. The wallet not sync...
Log:
Can anyone help me? Dogecoin ad Bitcoin wallet working perfectly on the same computer...
HelloHello and and thanks
Log:
Code:
JackpotCoin version v1.5.0.0 (Aug 18 2014, 17:02:30)
Using OpenSSL version OpenSSL 1.0.1h 5 Jun 2014
Startup time: 09/06/14 05:07:35
Default data directory C:\Users\min\AppData\Roaming\JackpotCoin
Used data directory C:\Users\min\AppData\Roaming\JackpotCoin
dbenv.open LogDir=C:\Users\min\AppData\Roaming\JackpotCoin\database ErrorFile=C:\Users\min\AppData\Roaming\JackpotCoin\db.log
Final lk_max_locks is 1048576, sufficient for (worst case) 21 blocks in a single transaction (up to a 10-deep reorganization)
Bound to 0.0.0.0:15371
Loading block index...
SetBestChain: new best=8b6d9062479865e08c9d1218a3b9dfbd2ecf42e9b5d710e909b6ecb7e3ac1175 height=0 trust=1 date=04/24/14 16:36:17
ResetSyncCheckpoint: pending for sync-checkpoint acd60c624540af2e1b03c98b021cbd7ec1802b3fffe25a349130a7b95fb09ed6
ResetSyncCheckpoint: sync-checkpoint reset to 8b6d9062479865e08c9d1218a3b9dfbd2ecf42e9b5d710e909b6ecb7e3ac1175
block index loading time : 419ms
Loading wallet...
nFileVersion = 1050000
Performing wallet upgrade to 60000
RandAddSeed() 224088 bytes
keypool added key 1, size=1
keypool added key 2, size=2
keypool added key 3, size=3
keypool added key 4, size=4
keypool added key 5, size=5
keypool added key 6, size=6
keypool added key 7, size=7
keypool added key 8, size=8
keypool added key 9, size=9
keypool added key 10, size=10
keypool added key 11, size=11
keypool added key 12, size=12
keypool added key 13, size=13
keypool added key 14, size=14
keypool added key 15, size=15
keypool added key 16, size=16
keypool added key 17, size=17
keypool added key 18, size=18
keypool added key 19, size=19
keypool added key 20, size=20
keypool added key 21, size=21
keypool added key 22, size=22
keypool added key 23, size=23
keypool added key 24, size=24
keypool added key 25, size=25
keypool added key 26, size=26
keypool added key 27, size=27
keypool added key 28, size=28
keypool added key 29, size=29
keypool added key 30, size=30
keypool added key 31, size=31
keypool added key 32, size=32
keypool added key 33, size=33
keypool added key 34, size=34
keypool added key 35, size=35
keypool added key 36, size=36
keypool added key 37, size=37
keypool added key 38, size=38
keypool added key 39, size=39
keypool added key 40, size=40
keypool added key 41, size=41
keypool added key 42, size=42
keypool added key 43, size=43
keypool added key 44, size=44
keypool added key 45, size=45
keypool added key 46, size=46
keypool added key 47, size=47
keypool added key 48, size=48
keypool added key 49, size=49
keypool added key 50, size=50
keypool added key 51, size=51
keypool added key 52, size=52
keypool added key 53, size=53
keypool added key 54, size=54
keypool added key 55, size=55
keypool added key 56, size=56
keypool added key 57, size=57
keypool added key 58, size=58
keypool added key 59, size=59
keypool added key 60, size=60
keypool added key 61, size=61
keypool added key 62, size=62
keypool added key 63, size=63
keypool added key 64, size=64
keypool added key 65, size=65
keypool added key 66, size=66
keypool added key 67, size=67
keypool added key 68, size=68
keypool added key 69, size=69
keypool added key 70, size=70
keypool added key 71, size=71
keypool added key 72, size=72
keypool added key 73, size=73
keypool added key 74, size=74
keypool added key 75, size=75
keypool added key 76, size=76
keypool added key 77, size=77
keypool added key 78, size=78
keypool added key 79, size=79
keypool added key 80, size=80
keypool added key 81, size=81
keypool added key 82, size=82
keypool added key 83, size=83
keypool added key 84, size=84
keypool added key 85, size=85
keypool added key 86, size=86
keypool added key 87, size=87
keypool added key 88, size=88
keypool added key 89, size=89
keypool added key 90, size=90
keypool added key 91, size=91
keypool added key 92, size=92
keypool added key 93, size=93
keypool added key 94, size=94
keypool added key 95, size=95
keypool added key 96, size=96
keypool added key 97, size=97
keypool added key 98, size=98
keypool added key 99, size=99
keypool added key 100, size=100
keypool added key 101, size=101
error while loading wallet : ()
wallet loading time : 11958ms
Loading addresses...
ERROR: CAddrman::Read() : open failed
Invalid or missing peers.dat; recreating
Loaded 0 addresses from peers.dat 1ms
mapBlockIndex.size() = 1
nBestHeight = 0
setKeyPool.size() = 100
mapWallet.size() = 0
mapAddressBook.size() = 1
Done loading
refreshWallet
DNS seeding disabled
ThreadMapPort started
ThreadSocketHandler started
ThreadOpenAddedConnections started
ThreadOpenAddedConnections exited
ThreadMessageHandler started
ThreadOpenConnections started
ThreadIRCSeed exited
ThreadStakeMinter started
CPU Miner started for proof-of-stake
Flushed 0 addresses to peers.dat 40ms
ipcThread started
GetMyExternalIP() received [...MyIp...] ...MyIp...:0
GetMyExternalIP() returned ...MyIp...
AddLocal(...MyIp...:15371,5)
Flushing wallet.dat
Flushed wallet.dat 127ms
UPnP: ExternalIPAddress = ...MyIp...
UPnP Port Mapping successful.
Flush(false)
blkindex.dat refcount=0
blkindex.dat checkpoint
blkindex.dat closed
DBFlush(false) ended 31ms
StopNode()
ThreadSocketHandler exited
ThreadMessageHandler exited
ipcThread exited
UPNP_DeletePortMapping() returned : 0
ThreadMapPort exited
ThreadOpenConnections exited
ThreadStakeMinter exiting, 0 threads remaining
Flushed 0 addresses to peers.dat 18ms
Flush(true)
DBFlush(true) ended 0ms
JackpotCoin exited
Can anyone help me? Dogecoin ad Bitcoin wallet working perfectly on the same computer...
HelloHello and and thanks
702580 2014-09-04 15:47:10 14994454.064472 JPC dwarfpool JdaWQx5PCseQUB96FUZ4vALkfPYFUzVG6U
Anyone know what's going on with Miningpoolhub? It's been stuck for 8.5 hours. Showed as high as 14800% done 30 minutes ago, now showing 12015.75% done.
No payouts or new confirmed/unconfirmed shares for 9+ hours here. Stats show no new blocks found in over 9 hours. 
This is my last payout,
ID Date TX Type Status Payment Address TX # Block # Amount
6370693 2014-09-03 16:46:07 (UTC) Credit Confirmed Auto Exc... 5878523 n/a 7,874.06430241
It seems working now.
I'm not so sure. Current UTC time is 22:47 so that's almost 6 hours ago. Oddly, your last payout was many hours beyond mine and nanoprobe's. My last confirmed is:
6370294 2014-09-03 11:16:55 (UTC) Credit Confirmed 694690 122.21877594
I hope this is just a front end issue as this is a terrible time to have problems while a 15 mil max jackpot is waiting to be triggered.
6402373 2014-09-04 13:46:27 (UTC) Credit Unconfirmed 701092 952.46224533
6402242 2014-09-04 13:46:21 (UTC) Credit Unconfirmed 701061 1,013.72365140
6402120 2014-09-04 13:46:12 (UTC) Credit Unconfirmed 701058 1,024.71677161
6401985 2014-09-04 13:31:09 (UTC) Credit Unconfirmed 701036 971.55793174
These are current pending credits.
The last one is about 15 minutes ago.
LAST 20 BLOCKS FOUND
Block Validity Finder Time Difficulty Amount Expected Shares PPLNS Shares Actual Shares Percentage
701131 56 left anonymous 04/09 13:57:06 (UTC) 100.76 15,009.46 412,716 1,020,053 506,007 122.60
701114 39 left anonymous 04/09 13:52:30 (UTC) 103.11 15,009.46 422,334 992,618 914,380 216.51
701092 17 left creatune 04/09 13:45:47 (UTC) 113.72 15,009.46 465,796 930,818 1,184,071 254.20
701061 Confirmed anonymous 04/09 13:36:21 (UTC) 118.48 15,009.46 485,300 856,130 90,494 18.65
701058 Confirmed anonymous 04/09 13:35:41 (UTC) 115.68 15,009.46 473,819 1,097,230 670,844 141.58
Everything seems working.
Anyone know what's going on with Miningpoolhub? It's been stuck for 8.5 hours. Showed as high as 14800% done 30 minutes ago, now showing 12015.75% done.
No payouts or new confirmed/unconfirmed shares for 9+ hours here. Stats show no new blocks found in over 9 hours. This is my last payout,
ID Date TX Type Status Payment Address TX # Block # Amount
6370693 2014-09-03 16:46:07 (UTC) Credit Confirmed Auto Exc... 5878523 n/a 7,874.06430241
It seems working now.
I'm not so sure. Current UTC time is 22:47 so that's almost 6 hours ago. Oddly, your last payout was many hours beyond mine and nanoprobe's. My last confirmed is:
6370294 2014-09-03 11:16:55 (UTC) Credit Confirmed 694690 122.21877594
I hope this is just a front end issue as this is a terrible time to have problems while a 15 mil max jackpot is waiting to be triggered.
Anyone know what's going on with Miningpoolhub? It's been stuck for 8.5 hours. Showed as high as 14800% done 30 minutes ago, now showing 12015.75% done.
No payouts or new confirmed/unconfirmed shares for 9+ hours here. Stats show no new blocks found in over 9 hours. This is my last payout,
ID Date TX Type Status Payment Address TX # Block # Amount
6370693 2014-09-03 16:46:07 (UTC) Credit Confirmed Auto Exc... 5878523 n/a 7,874.06430241
It seems working now.
Sounds like the old MPOS cron-jobs weren't running meaning the stats weren't being updated.
Of course, we are more than happy to have miners
Anyone know what's going on with Miningpoolhub? It's been stuck for 8.5 hours. Showed as high as 14800% done 30 minutes ago, now showing 12015.75% done.
No payouts or new confirmed/unconfirmed shares for 9+ hours here. Stats show no new blocks found in over 9 hours. This is my last payout,
ID Date TX Type Status Payment Address TX # Block # Amount
6370693 2014-09-03 16:46:07 (UTC) Credit Confirmed Auto Exc... 5878523 n/a 7,874.06430241
It seems working now.
Anyone know what's going on with Miningpoolhub? It's been stuck for 8.5 hours. Showed as high as 14800% done 30 minutes ago, now showing 12015.75% done.
No payouts or new confirmed/unconfirmed shares for 9+ hours here. Stats show no new blocks found in over 9 hours.
Anyone know what's going on with Miningpoolhub? It's been stuck for 8.5 hours. Showed as high as 14800% done 30 minutes ago, now showing 12015.75% done.
The new version will enter beta test next week. A lot of improvements are expected! Stay tuned!
right on nice to hear.. i don't know if you seen previous pages but some other guy mentioned CPU usage
and i think it might be higher.. figured you may want to look at that etc.
i don't have any major requests ..just do what you do
The new version will enter beta test next week. A lot of improvements are expected! Stay tuned!
Possibly, it is a local fork.
Please, turn-off QT, and waiting an hour
and than, run again,
it will refresh the database,
Please, turn-off QT, and waiting an hour
and than, run again,
it will refresh the database,
As for the less frequent staking, it's normal, the staking rules have been slightly changed in order to reduce dust, and thus avoid blockchain bloat.
Thanks to both of you. I will leave the wallet off for a while and clean out the pc and do something constructive, like finally install the new water block and radiator that has sat here for 3 months...
Any updates about when the 1.6 wallet with be coming out?
As for the less frequent staking, it's normal, the staking rules have been slightly changed in order to reduce dust, and thus avoid blockchain bloat.
holy crap you got that much ?
i am getting about the same roughly ..hard to say i don't pay much attention to the totals etc
but what were you getting total stake per 24hrs or per week etc ? does that much up to close to now ?
i thought the dev's intention was to stop the smaller amounts from staking kind of..
so i am guessing you would get less but more bigger ones ? so it evens out ?
i am getting about the same roughly ..hard to say i don't pay much attention to the totals etc
but what were you getting total stake per 24hrs or per week etc ? does that much up to close to now ?
i thought the dev's intention was to stop the smaller amounts from staking kind of..
so i am guessing you would get less but more bigger ones ? so it evens out ?
Actually I went back a bit and 30/hour is unrealistic. I think it used to be 20 or so on average back when there was more daily trading activity, but I think these last 2 weeks people are just holding more in their wallets and that's why I have been getting less. This was from a week ago and it was on the new updated wallet, so I don't think that has been the issue the last few days where i've been getting far less. I should have made a note of how many I had before per hour and what the difficulty was at the time so I had something to compare it to.
Possibly, it is a local fork.
Please, turn-off QT, and waiting an hour
and than, run again,
it will refresh the database,
hopefully the dev can chime in and give you a response.
and i had used a Securcoin block explorer way back that listed difficulty besides each block found
i wonder if a JPC one does that too then you could that info from there..
sometimes i get no stake at all for a day or two with about 350k coins
but i don't usually get stake as small as 20 coins
and i sometimes have just counted it up for the period.. say 24 hrs
same as i have always done on pools.
the devs response on the update was cryptic a few pages back though
he really did not go into very much detail about it at all..
and i had used a Securcoin block explorer way back that listed difficulty besides each block found
i wonder if a JPC one does that too then you could that info from there..
sometimes i get no stake at all for a day or two with about 350k coins
but i don't usually get stake as small as 20 coins
and i sometimes have just counted it up for the period.. say 24 hrs
same as i have always done on pools.
the devs response on the update was cryptic a few pages back though
he really did not go into very much detail about it at all..
holy crap you got that much ?
i am getting about the same roughly ..hard to say i don't pay much attention to the totals etc
but what were you getting total stake per 24hrs or per week etc ? does that much up to close to now ?
i thought the dev's intention was to stop the smaller amounts from staking kind of..
so i am guessing you would get less but more bigger ones ? so it evens out ?
i am getting about the same roughly ..hard to say i don't pay much attention to the totals etc
but what were you getting total stake per 24hrs or per week etc ? does that much up to close to now ?
i thought the dev's intention was to stop the smaller amounts from staking kind of..
so i am guessing you would get less but more bigger ones ? so it evens out ?
Actually I went back a bit and 30/hour is unrealistic. I think it used to be 20 or so on average back when there was more daily trading activity, but I think these last 2 weeks people are just holding more in their wallets and that's why I have been getting less. This was from a week ago and it was on the new updated wallet, so I don't think that has been the issue the last few days where i've been getting far less. I should have made a note of how many I had before per hour and what the difficulty was at the time so I had something to compare it to.
holy crap you got that much ?
i am getting about the same roughly ..hard to say i don't pay much attention to the totals etc
but what were you getting total stake per 24hrs or per week etc ? does that much up to close to now ?
i thought the dev's intention was to stop the smaller amounts from staking kind of..
so i am guessing you would get less but more bigger ones ? so it evens out ?
i am getting about the same roughly ..hard to say i don't pay much attention to the totals etc
but what were you getting total stake per 24hrs or per week etc ? does that much up to close to now ?
i thought the dev's intention was to stop the smaller amounts from staking kind of..
so i am guessing you would get less but more bigger ones ? so it evens out ?
Anyone else with a decent amount of JPC in their wallet not getting many stakes anymore? It seems after I updated to the last wallet and resynced the blockchain that I'm only getting maybe 2-4 stakes an hour instead of the 20-30 I used to get. It still says I should expect 1 in 4min, but it seems like my coins aren't being allocated for staking as often as before. I'm thinking there might be something else up with my computer or wallet. I suppose I can restart the pc since I haven't in forever, just curious if anyone else had something similar happen.
Dev, if you're lurking here, does that have something to do with the reconfiguration you talked about in the 1.5 wallet update?
Dev, if you're lurking here, does that have something to do with the reconfiguration you talked about in the 1.5 wallet update?
I got a lot of replies to my questions, so I didn't want to quote everyone. But thank you to all that helped answer them! If anyone has any more information regarding any of them, please let me know.
Thanks!
Thanks!
Bigredmachine:
To answer your question about 20 second block times producing more orphans than 60 second blocks:
The main cause of orphans is when two miners find the solution at the same time. Both miners then proceed to the next block, but one is now on a fork. This happens even if the block time is 20 minutes. The more numerous the blocks, the more numerous the orphans.
If there was only one pool mining a coin, and all the miners were on that pool, there would not be any orphans at all. But since there are several pools, and many solo miners, the chance of simultaneous solutions increases geometrically.
The reason for the short block times here, is to get more coins out there. There is no limit to the number of JPC coins.
JPC has a 120 second block time
To answer your question about 20 second block times producing more orphans than 60 second blocks:
The main cause of orphans is when two miners find the solution at the same time. Both miners then proceed to the next block, but one is now on a fork. This happens even if the block time is 20 minutes. The more numerous the blocks, the more numerous the orphans.
If there was only one pool mining a coin, and all the miners were on that pool, there would not be any orphans at all. But since there are several pools, and many solo miners, the chance of simultaneous solutions increases geometrically.
The reason for the short block times here, is to get more coins out there. There is no limit to the number of JPC coins.
JPC has a 120 second block time
Thanks for the reply!
To clarify about orphans, what I meant by shorter times causing more orphans is this:
- After a block is found, a non-negligible amount of time is spent propagating that block to all the nodes in the network.
- Assuming that this takes 5 seconds (my understanding is that it is closer to 10-12 seconds), 25% of a 20 second block time is spent without knowledge that the previous block has been found. If a block with the same height as the not-yet-known block is found during this small time, it will be orphaned (and rightfully so).
- This small time spent syncing the network is roughly the same regardless of block times.
- Again assuming 5 seconds to sync the network, a 60 second block time would have ~8% of the time spent searching by nodes occur during this sync-up time, and 92% of the time spent searching be useful time spent. A 2.5 minute block time would mean ~3% is wasted.
- In essence, as block time is decreased, the number of Orphans/Share is increased.
My questions then I suppose were really these (again, I am genuinely interested in an asnwer, and not trying to FUD):
- What are the repercussions of the much higher rate of orphans? Are there repercussions?
- Can this result in more transactions being voided?
- And finally, since all PoS implementations rely on centralized checkpointing, this means that the operator of the central checkpoint and those nodes closest to that central checkpoint are able to sync much faster than other nodes. What advantages does this give to those nodes in terms of # of Orphans compared to slower-to-sync nodes farther away?
I think you are combining orphans and rejected shares in your reasoning here. Orphans are formed when two miners of different pools find a solution nearly the same time, where as what you are describing with the lag time above, is the increased amount of rejected shares due to the miners still working on a block that has already been solved.
Jump to: