[ANN][JPC]MAKE JACKPOTCOIN GREAT AGAIN!

[ocminer]

A pool is not the problem, but there seems to be no miner supporting stratum correct here..

[Mikellev]

A pool is not the problem, but there seems to be no miner supporting stratum correct here..

Are these the same as in the ltc source ?

https://github.com/Crypto-Expert/stratum-mining/blob/master/lib/template_registry.py#L151-L158

@ocminer sgminer is running and supporting stratum afaik ?!

[TinyBBC]

so basically one just need to run any of the 8 algo or the fastest?

[ocminer]

A pool is not the problem, but there seems to be no miner supporting stratum correct here..

Are these the same as in the ltc source ?

https://github.com/Crypto-Expert/stratum-mining/blob/master/lib/template_registry.py#L151-L158

@ocminer sgminer is running and supporting stratum afaik ?!

No, sgminer is running with 80 bytes header from what i can see, this coin has 88 block header.

diff1 is wurst at first time, try to get valid shares with the hashing module & sgminer at first.

[Mikellev]

A pool is not the problem, but there seems to be no miner supporting stratum correct here..

Are these the same as in the ltc source ?

https://github.com/Crypto-Expert/stratum-mining/blob/master/lib/template_registry.py#L151-L158

@ocminer sgminer is running and supporting stratum afaik ?!

No, sgminer is running with 80 bytes header from what i can see, this coin has 88 block header.

diff1 is wurst at first time, try to get valid shares with the hashing module & sgminer at first.

Wurst ! Det het ju aber nice jetalked

[dga]

Just a note in case others encounter this - there's a bit of an oddity with the PoS mining:

If you're holding a bock and it mints more PoS, the block (with extra coins) gets tied up in "immature" until the entire thing confirms.  Which means your balance may temporarily drop -- I had 10 blocks confirmed, and now have 9 confirmed + 1 in immature for another 20 minutes (with extra coins) until that PoS block gets confirmed.

I assume this isn't a bug and is just how the PoS mining works, but it was new to me - hope I can save others the "wha?" response.

[ocminer]

A pool is not the problem, but there seems to be no miner supporting stratum correct here..

Are these the same as in the ltc source ?

https://github.com/Crypto-Expert/stratum-mining/blob/master/lib/template_registry.py#L151-L158

@ocminer sgminer is running and supporting stratum afaik ?!

No, sgminer is running with 80 bytes header from what i can see, this coin has 88 block header.

diff1 is wurst at first time, try to get valid shares with the hashing module & sgminer at first.

Wurst ! Det het ju aber nice jetalked

 

I only get rejects with latest sgminer + jackpotcoin_hash.. but maybe i am missing something...

[nomad1109]

Maybe I missed the explanation somewhere, but what are these small jackpot deposits I see arriving in my wallet?

I am not at my wallet machine, but I think they were for 100 coins (maybe 1,000), and I had three of them arrive sometime overnight.

Just thought it was odd, so figured I would ask.

Thanks for any info or pointing me in the right direction to the explanation.

[valley365]

Maybe I missed the explanation somewhere, but what are these small jackpot deposits I see arriving in my wallet?

I am not at my wallet machine, but I think they were for 100 coins (maybe 1,000), and I had three of them arrive sometime overnight.

Just thought it was odd, so figured I would ask.

Thanks for any info or pointing me in the right direction to the explanation.

These should be your PoS blocks (daily interest you earned on your holdings).

[valley365]

Just a note in case others encounter this - there's a bit of an oddity with the PoS mining:

If you're holding a bock and it mints more PoS, the block (with extra coins) gets tied up in "immature" until the entire thing confirms.  Which means your balance may temporarily drop -- I had 10 blocks confirmed, and now have 9 confirmed + 1 in immature for another 20 minutes (with extra coins) until that PoS block gets confirmed.

I assume this isn't a bug and is just how the PoS mining works, but it was new to me - hope I can save others the "wha?" response.

This is just normal way PoS works, the whole "base" + "interests" goes to "immature", and after 70 confirmations it will "mature" and the whole will be added back to "balance".

[jpcsupport]

A pool is not the problem, but there seems to be no miner supporting stratum correct here..

Are these the same as in the ltc source ?

https://github.com/Crypto-Expert/stratum-mining/blob/master/lib/template_registry.py#L151-L158

@ocminer sgminer is running and supporting stratum afaik ?!

     # 4. Reverse header and compare it with target of the user
        if settings.COINDAEMON_ALGO == 'scrypt':
            hash_bin = ltc_scrypt.getPoWHash(''.join([ header_bin[i*4:i*4+4][::-1] for i in range(0, 20) ]))
        elif settings.COINDAEMON_ALGO == 'scrypt-jane':
         if settings.SCRYPTJANE_NAME == 'vtc_scrypt':
             hash_bin = scryptjane.getPoWHash(''.join([ header_bin[i*4:i*4+4][::-1] for i in range(0, 20) ]))
       else:
       hash_bin = scryptjane.getPoWHash(''.join([ header_bin[i*4:i*4+4][::-1] for i in range(0, 20) ]), int(ntime, 16))
        elif settings.COINDAEMON_ALGO == 'quark':
            hash_bin = quark_hash.getPoWHash(''.join([ header_bin[i*4:i*4+4][::-1] for i in range(0, 20) ]))
elif settings.COINDAEMON_ALGO == 'skeinhash':
            hash_bin = skeinhash.skeinhash(''.join([ header_bin[i*4:i*4+4][::-1] for i in range(0, 20) ]))
        else:
            hash_bin = util.doublesha(''.join([ header_bin[i*4:i*4+4][::-1] for i in range(0, 20) ]))

        hash_int = util.uint256_from_str(hash_bin)
        scrypt_hash_hex = "%064x" % hash_int
        header_hex = binascii.hexlify(header_bin)
        if settings.COINDAEMON_ALGO == 'scrypt' or settings.COINDAEMON_ALGO == 'scrypt-jane':
            header_hex = header_hex+"0000008000000000000000000000000000000000000000000000000000000000000000000000000 00000000080020000"
        elif settings.COINDAEMON_ALGO == 'quark':
            header_hex = header_hex+"0000008000000000000000000000000000000000000000000000000000000000000000000000000 00000000080020000"
        else: pass       

Default code is took 80 bytes from the received works from miner, and
submit with the standard followed header

{
"data" : "00000004b84d4e22e93740d5d9e37eb38eaa40e46c55550c8759dbb430293bc4f4fff9697ba3666 4dc154dc975f3098fde4285313e9bc7f03414e0ed9093e0401a438d6b535e89031c055e9a 00000000 00000000 00000007 000000800000000000000000000000000000000000000000000000000000000000000000c002000 0",
"target" : "000000000000000000000000000000000000000000000000009a5e0500000000"
}

* more bytes are added on packet, actually,

Suggest for quick fix

elif settings.COINDAEMON_ALGO == 'jackpotcoin':
     header_hex = header_hex + "0000000000000007000000800000000000000000000000000000000000000000000000000000000 000000000c0020000"

[Spoetnik]

A pool is not the problem, but there seems to be no miner supporting stratum correct here..

wallets don't support stratum.. none of them ever have as far as i know..
pools do and we need a pool for that.

[Spoetnik]

rofl my 7950 is doing 81.75mh/s  

{
"pools" : [
   {
      "url" : "localhost:15372",
      "user" : "user",
      "pass" : "pass"
   }
]
,
"intensity" : "22",
"vectors" : "1",
"worksize" : "256",
"lookup-gap" : "2",
"thread-concurrency" : "44801",
"shaders" : "1792",
"gpu-engine" : "1060",
"gpu-fan" : "75",
"gpu-memclock" : "1575",
"gpu-memdiff" : "0",
"gpu-powertune" : "0",
"gpu-vddc" : "0.000",
"temp-cutoff" : "95",
"temp-overheat" : "85",
"temp-target" : "75",
"api-mcast-port" : "4028",
"api-port" : "4028",
"no-submit-stale" : false,
"expiry" : "120",
"gpu-dyninterval" : "7",
"gpu-platform" : "0",
"gpu-threads" : "2",
"hotplug" : "5",
"log" : "5",
"no-pool-disable" : true,
"queue" : "2",
"scan-time" : "60",
"temp-hysteresis" : "3",
"shares" : "0",
"kernel-path" : "/usr/local/bin"
}

How come you set the thread-concurrency so high?It seems even 290x can go that far for other algos.

generally on other algo's the more you turn it up the more dedicated gpu ram will get used while hashing.. this is what happens on scypt and scypt-n
most guys have no clue what their doing with tweaking advice on cgminer etc.. they shout random value for no apparent reason lol
and maybe i don't know what i am doing either BUT i have a method to my madness lol

my gpu has 3gb's of ram and i tweak cgminer / sgminer etc with a higher TC until i see the ram usage goes slightly over 3gb's and then cgminer will not run.
..then turn it back down a bit.. and either i use calculator to multiply shader count by a whole number or i do that adn add +1
..i head about plus from a guy here but don't know if that +1 is good though i thought it should always be an even multiple based scrypt cgminer docs.

and that is tuning for ONE gpu-thread.. what i just said will usually screw you bad if you go with two threads lol
So what happens is a lot of other misc algo's can be pushed a lot further so on Jackpot i maxed it on one one thread and then added a second thread
and since the hashing algo is so simple the miner can easily handle it no problem.. that config i posted for scrypt would not even try and load.. it would an error for sure lol
tweaking for two threads is another way of setting up the miner for one card.. both should ways (1 or 2 threads) give the same result if you know what your doing..

i could go on and on about this but you can find plenty of people to give you config settings tweaking advice.. i just do what i do
How did i know my ram usage ? i loaded up GPU-Z then loaded the miner and watched it as i kept starting and stopping my miner..
also read the doc's that come with cgminer

so to answer your question i used windows-calculator and i multiplied like 1792 my shader count (the gpu's technical hardware stream processor count)
so like 1792 x say a random number like 32 which gives me 57344 for thread concurrency and that is too high and the miner won't run..
so i just deducted by multiples of 1792 until the miner would start and run.. which is what i posted in my config
then after that monitor HW and WU and Hash rate and fine tune the Intensity for best performance and adjust scan time etc to match the pool / block speed etc..
that is the gist of it lol

if i was tweaking for two gpu-threads i'd prob do like half that TC normally.. 2 thread will never handle the full TC you can do with one gpu thread
i got away with it though in that config because this miner is running a super easy hashing algo ..which is usually not the case around here lol

edit:
that config i posted is doing about 81.5 MH/s on my one Radeon 7950 all night long solo mining pointed at my wallet.

[valley365]

jackpot grows to 4.6 mil now...

[Mikellev]

jackpot grows to 4.6 mil now...

Just found normal blocks until now.... sad....

[valley365]

jackpot grows to 4.6 mil now...

Just found normal blocks until now.... sad....

same here... it is super rare the jackpot

[mountainview]

interesting coin... I like jackpot!

[valley365]

I think we really need a pool to get this coin going, any pool dev there, being a first pool will be very profitable

[marseille]

this coin has some good and funny features

[JackpotCoin]

New exchange! https://www.coinopend.com/trading/JPC_BTC