Pages:
Author

Topic: [ANN] Kryptohash | Brand new PoW algo | 320bit hash | ed25519 | PID algo for dif - page 62. (Read 149437 times)

legendary
Activity: 1400
Merit: 1000
I see.. then.. what ? This is the end for this coin ?  Cry



Not the end of the coin just the evolution of it.

I like that the dev is staying on top off things. I hope this coin has success for his efforts.

On a side note,  since the coin is going to be hard forked or rolled back does it make any sense to mine it right now until the wallet is released?

I am not sure how that works.
legendary
Activity: 1568
Merit: 1000
Twitter @Acimirov
I see.. then.. what ? This is the end for this coin ?  Cry

sr. member
Activity: 350
Merit: 250
The last wallet cannot fix this ??
OMG .. Smiley WTF !


The last wallet did not address the ultra high difficulty on new block generation, the next 100 blocks would have been brutal to solve without a pool and long-pole server to distribute work for new block generation so he is hard forking it at block 5098 to address this.  Mind you this would not have happened if everyone updated their wallet to 0.3.3 when asked to do so, and because of that he had to make the wallet deny connections to obsolete versions of the wallet, so if people don't keep up on new developments and actually read the thread, you won't be able to sync your wallet.  On the plus side those that fail to keep up and read will not be able to screw up the blockchain for everyone else...
legendary
Activity: 1568
Merit: 1000
Twitter @Acimirov
The last wallet cannot fix this ??
OMG .. Smiley WTF !
member
Activity: 86
Merit: 11
legendary
Activity: 1568
Merit: 1000
Twitter @Acimirov
How to sync guys ? I'm with last wallet 0.3.4 and loaded blockchain again but it is stuk on block 5104.

PLS Advise ?
member
Activity: 86
Merit: 11
thanks WORE, was just making sure im set and ready  Wink
sr. member
Activity: 350
Merit: 250
Compiled cgminer-khc from git repo but when i fire it up i get

No suitable long-poll found for http://127.0.0.1:38912




edit: same happens if i use the https://github.com/kryptohash/cgminer-khc/releases

Yes, whenever you mine solo there is no long-poll server found, this is usually only found on pools.  The reason you are awaiting work on pool 0 is found in previous posts.
member
Activity: 86
Merit: 11
Compiled cgminer-khc from git repo but when i fire it up i get

No suitable long-poll found for http://127.0.0.1:38912




edit: same happens if i use the https://github.com/kryptohash/cgminer-khc/releases
sr. member
Activity: 329
Merit: 250
Guys, at the current Diff, it is going to take days to reach Block 5200 where it is expected to retarget to a lower value.

I'm going to have to create a new wallet version with a hard fork at block 5098 and get a lower retarget value for a brand new block 5100.

You are doing a fantastic job at making adjustments. Thanks.

Just curious if cgminer is causing issues also with read outs. Wallet shows difficulty of 902.1813 while cgminer still shows over 1.86k.

Well, not as fantastic as I was expecting.  3 Wallet versions in 3 days isn't what I was hoping to see but, I'm learning a very good deal about how these coins operate in the real world and not to trust too much the simulations I was performing on my Testnet in the last few months.

cgminer-khc does have few serious problems.  But this Diff value problem you mention seems to be just a display issue, perhaps a mismatch in the algorithm to estimate the Network Diff.  I'll fix it as soon as I fix the extra GPU mining problem which is at the top of my to do list.
sr. member
Activity: 329
Merit: 250
Since I also have big dramas at the office, the ETA for next wallet is going to be, 12 hours from now (or Dec 6th, 2:00AM  GMT)

I'm going to try to get home early so, I can begin working on the hard fork at block 5098 and a new retarget value for block 5100

Thanks for your patience.
legendary
Activity: 1400
Merit: 1000
Guys, at the current Diff, it is going to take days to reach Block 5200 where it is expected to retarget to a lower value.

I'm going to have to create a new wallet version with a hard fork at block 5098 and get a lower retarget value for a brand new block 5100.

You are doing a fantastic job at making adjustments. Thanks.

Just curious if cgminer is causing issues also with read outs. Wallet shows difficulty of 902.1813 while cgminer still shows over 1.86k.
sr. member
Activity: 329
Merit: 250
Guys, at the current Diff, it is going to take days to reach Block 5200 where it is expected to retarget to a lower value.

I'm going to have to create a new wallet version with a hard fork at block 5098 and get a lower retarget value for a brand new block 5100.
legendary
Activity: 1610
Merit: 1008
Forget-about-it
i just loaded the client, had it off for 8 hrs. shows 5104..
legendary
Activity: 1400
Merit: 1000
Can anyone verify the correct block number we are on? I am showing 5104 and that I found 5103.

Something is definitely wrong with the cgminer. When it showed me finding block 5103 my accepted shares was 902 and rejected was 0.
legendary
Activity: 1568
Merit: 1000
Twitter @Acimirov
sr. member
Activity: 329
Merit: 250

Yay!

Client [schmoe] runs obsolete version 0.3.2, disconnecting

[2014-12-04 23:27:45] Waiting for work from Pool 0    Grin

My 129 coins for block 5100 are still there, the way it looked it would seem lotta folks solved that block.  I figured you would clip the blockchain at 5099, so maybe we should name the block?  Grin  How about 7th Ave, you dirty slut, forkin up the difficulty, halting the blockchain!

I added the checkpoint at block 5000 since that was the block where the fork began.  

My concern right now is that I've been trying to mine block 95ed9842d for 50 mins already.  



Difficulty is 1.86K in miner, same as 5100 for me, and 902.18130373 in console.  Running a 280x it took a while to get through 5100 for me, is it going to wait until 5199 to retarget diff?

We are going to have to wait till next retarget at block 5199.  


Oh boy, might want to release a manual retarget wallet, or maybe get that pool up.

I think there is a problem with the cgminer-khc getting the wrong diff.   But, I need to sleep now.  I'm very tired.

I'm running
cgminer.exe --debug --kryptohash -o 127.0.0.1:38912 -u user -p pass --shaders 2816 --shaders-mul 8 2>log.txt

newbie
Activity: 23
Merit: 0
update 0.34,but stop in 5103 block!
sr. member
Activity: 350
Merit: 250

Yay!

Client [schmoe] runs obsolete version 0.3.2, disconnecting

[2014-12-04 23:27:45] Waiting for work from Pool 0    Grin

My 129 coins for block 5100 are still there, the way it looked it would seem lotta folks solved that block.  I figured you would clip the blockchain at 5099, so maybe we should name the block?  Grin  How about 7th Ave, you dirty slut, forkin up the difficulty, halting the blockchain!

I added the checkpoint at block 5000 since that was the block where the fork began.   

My concern right now is that I've been trying to mine block 95ed9842d for 50 mins already. 



Difficulty is 1.86K in miner, same as 5100 for me, and 902.18130373 in console.  Running a 280x it took a while to get through 5100 for me, is it going to wait until 5199 to retarget diff?

We are going to have to wait till next retarget at block 5199. 


Oh boy, might want to release a manual retarget wallet, or maybe get that pool up.
legendary
Activity: 1400
Merit: 1000
now wallet block on 5103.no start new block .no look 5104 block ,dev why ?

If you have block 5103 and the hash is 0000000046017B173A6680B24C496C0D8CF21075E933D40048B1AE57443B6DF93F616A7D4298ED9 5, you are on the right tip of the blockchain

How do I find this out.

Now I am going to sleep.
Pages:
Jump to: