Offical launch of PhenixCoin.com

[MaGNeT]

Want to buy:

5700 PXC for 1.111568 BTC
Transaction ID: 51C09F71-63A3-D109-6CE9
LINK

[weav]

Could any body do the maths and tell us that how much time will it take to reach the retarget block. At the current hash rate.

At the current difficulty of 10.3909 and current average hashrate of approximately 21 MH/s it takes about (10.3909 * 2^32 H) / (21 MH/s) = 2125 seconds - or 35 minutes - to solve a block.

That's approximately 35 minutes * 812 = 38 days for the remaining 2400 - (46412 mod 2400) = 1588 blocks until the next difficulty change.

[Nolo]

Could any body do the maths and tell us that how much time will it take to reach the retarget block. At the current hash rate.

At the current difficulty of 10.3909 and current average hashrate of approximately 21 MH/s it takes about (10.3909 * 2^32 H) / (21 MH/s) = 2125 seconds - or 35 minutes - to solve a block.

That's approximately 35 minutes * 812 = 20 days for the remaining (46412 mod 2400) = 812 blocks until the next difficulty change.

No, don't forget the new client changes this.  We are only 88 blocks from a difficulty change. 

[weav]

No, don't forget the new client changes this.  We are only 88 blocks from a difficulty change.  

Oops, of course, it applies immediately, sorry.

So at the current difficulty of 10.3909 and current average hashrate of approximately 21 MH/s it takes about (10.3909 * 2^32 H) / (21 MH/s) = 2125 seconds - or 35 minutes - to solve a block

That's approximately 148 * 35 minutes = 3 days and 15 hours for the remaining 480 - (46412 mod 480) = 148 blocks until the next difficulty change.

[torzsy]

Could any body do the maths and tell us that how much time will it take to reach the retarget block. At the current hash rate.

At the current difficulty of 10.3909 and current average hashrate of approximately 21 MH/s it takes about (10.3909 * 2^32 H) / (21 MH/s) = 2125 seconds - or 35 minutes - to solve a block.

That's approximately 35 minutes * 812 = 38 days for the remaining 2400 - (46412 mod 2400) = 1588 blocks until the next difficulty change.

Wrong imho. Only 96 blocks until next diff change.

46412 mod 480 = 96
96 * 35 minutes = 56 hours, so 3 days max at current hashrate. 

"Changes that have been implemented are: Difficultly changes every 480 blocks max change is 80%. We have also added checkpoints as well."

[weav]

Could any body do the maths and tell us that how much time will it take to reach the retarget block. At the current hash rate.

At the current difficulty of 10.3909 and current average hashrate of approximately 21 MH/s it takes about (10.3909 * 2^32 H) / (21 MH/s) = 2125 seconds - or 35 minutes - to solve a block.

That's approximately 35 minutes * 812 = 38 days for the remaining 2400 - (46412 mod 2400) = 1588 blocks until the next difficulty change.

Wrong imho. Only 96 blocks until next diff change.

46412 mod 480 = 96
96 * 35 minutes = 56 hours, so 3 days max at current hashrate.  

"Changes that have been implemented are: Difficultly changes every 480 blocks max change is 80%. We have also added checkpoints as well."

Yes, sorry for that. See my correction above. 46412 mod 480 = 332 though, but those are the blocks already mined after the last difficulty change. So only 480 - 332 = 148 blocks remaining until the next difficulty change

[lucazane]

you can add 630 kh/s ... adding a 7950

[nawazish1]

I am gonna make a thread to spread the word.

[HuuHachu]

I am gonna make a thread to spread the word.

You can't be as fast as magnet ^^

[nawazish1]

I am gonna make a thread to spread the word.

You can't be as fast as magnet ^^

Where is his thread

[weav]

We are only 88 blocks from a difficulty change. 

How did you arrive at this number?

[torzsy]

Could any body do the maths and tell us that how much time will it take to reach the retarget block. At the current hash rate.

At the current difficulty of 10.3909 and current average hashrate of approximately 21 MH/s it takes about (10.3909 * 2^32 H) / (21 MH/s) = 2125 seconds - or 35 minutes - to solve a block.

That's approximately 35 minutes * 812 = 38 days for the remaining 2400 - (46412 mod 2400) = 1588 blocks until the next difficulty change.

Wrong imho. Only 96 blocks until next diff change.

46412 mod 480 = 96
96 * 35 minutes = 56 hours, so 3 days max at current hashrate.  

"Changes that have been implemented are: Difficultly changes every 480 blocks max change is 80%. We have also added checkpoints as well."

Yes, sorry for that. See my correction above. 46412 mod 480 = 332 though, but those are the blocks already mined after the last difficulty change. So only 480 - 332 = 148 blocks remaining until the next difficulty change

Yeah, nevermind, I made a mistake too. Next retarget is not 30th of June at least.

[CoinEntropy]

Where's the open beta that was supposed to be here yesterday?

[ToxicDartFrog]

Where's the open beta that was supposed to be here yesterday?

If you're talking about the exchange it's pretty much ready but there's a few adjustments to be made before it can go live. Will be very soon. Patience

[barwizi]

any fix for the linux users?

[HuuHachu]

any fix for the linux users?

you still have your problem syncing ?
I'm using linux myself and have no problem with the updated client.
(lubuntu inside a virtualbox)

... well except now as it tries to download the litecoin chain ^^  (but restrating the client clear the problem for some time)

[HuuHachu]

Mmh ... to original post announces a 2.5 minutes blocktime.
As http://phenixcoin.com/ states a 1.5 minutes blocktime, I was suspecting a typo.

But looking at the code, the target blocktime is indeed 1.5 minutes (which means 2.5 days with 2400 blocks for retarget).
The values in the comments in the code are unmodified from litecoin and thus misleading ^^

With the update, the blocktime is still 1.5 minutes, and 480 blocks to retarget corresponds to 12 hours (ideally).
Would be nice to correct the original post
(and also many sites / pools announcing the 2.5 minutes blocks)

[weav]

Regarding the "Wallet won't sync if compiled from source in Linux" issue:

I started phenixcoin-qt with the following lines added in ~/.phenixcoin/phenixcoin.conf as well as in ~/.config/Phenixcoin/Phenixcoin-Qt.conf:

addnode=37.140.234.240
addnode=199.201.107.145
addnode=199.201.106.33
addnode=98.143.37.245

It's been running for several hours now and sync is still stuck at block 2400.

(Strangely enough, after a while it shows "370796 blocks remaining" and "Downloaded block 2399 of 373195" although there are only 46418 blocks in total by now, which it showed correctly earlier)

barwizi is experiencing the same problem and 2400 is the old difficulty retarget, so probably not a coincidence.

[Taxidermista]

Mmh ... to original post announces a 2.5 minutes blocktime.
As http://phenixcoin.com/ states a 1.5 minutes blocktime, I was suspecting a typo.

But looking at the code, the target blocktime is indeed 1.5 minutes (which means 2.5 days with 2400 blocks for retarget).
The values in the comments in the code are unmodified from litecoin and thus misleading ^^

With the update, the blocktime is still 1.5 minutes, and 480 blocks to retarget corresponds to 12 hours (ideally).
Would be nice to correct the original post
(and also many sites / pools announcing the 2.5 minutes blocks)

Is it 1.5 or 2.5 minutes per block?

[RAMZA]

Someone is having troubles with withdrawals of PCX on CRYPTSY???