[XPM] [ANN] Primecoin Release - First Scientific Computing Cryptocurrency

[Sunny King]

Nice chart but doesn't look correct though. There were a significant period over the weekend that block spacing dropped under 10 seconds.

[1715234641]

1715234641

[1715234641]

1715234641

[1715234641]

1715234641

[1715234641]

1715234641

[1715234641]

1715234641

[1715234641]

1715234641

[rethaw]

Nice chart but doesn't look correct though. There were a significant period over the weekend that block spacing dropped under 10 seconds.

I think you're right... I'll take a closer look at what went wrong.

[stas]

Hi, all!
my client is not synchronizing. I meat it attempts to , but would not succeed.
Until today everything was OK.
Id there anything could be done?

thank you.

[Impaler]

If the initial code had been properly optimized then starting difficulty could have been nearly 9 and we wouldn't be seeing such a short block time.  This is a lesson, if your going to release a new algorithm for CPU mining, optimize the CPU code or else you've get quasi-ASIC like behavior in which hash rates explode and the coins may end up monopolized by people who have access to the high potency mining ability even if this is by software rather then hardware.

Starting difficulty would have still been where Sunny set it, 7. I don't know what the distribution looks like, but I am still finding blocks on 5 micro instances and a laptop running while I am sleeping. If difficulty adjustments took two weeks, I would agree with you, but it's dynamic.

If his starting difficulty was in any way chosen to reflect the mining rate of some target number of PCs (the method Satoshi used) then optimized code would certainly have lead him to choose a higher difficulty, do you think 7 was just a number he pulled out of his ass with no regard to the target block time?

So not only does he have to code and promote the coin, now he has to divine the future? I imagine that he set it where it to wouldn't be jammed up with orphan chains initially when utilizing CPU mining and then allowed it to self regulate. There is no way to predict adoption or hashing power or optimization. You are just some tool upset about the first WEEK of mining. Entitlement is an ugly thing. Didn't get enough of those 200k coins, or what?

Fuckin' a...some people will bitch about anything.

Oh get off it you twit, I'm pointing out how Sunny King could have had a better initial release that meet HIS goals.  From what I've read on the optimization threads the original client was doing really obviously un-optimized stuff like calling malloc repeatedly which any first year programmer knows is a performance killer.  Optimization CAN be predicted and the factor of 100x we have seen so far would be considered quite easy and 'low hanging fruit' to most programmers.

SK was clearly trying to avoid overly fast blocks per his own pre-release thread that advertised "Reasonably high starting difficulty to limit instamining" but that effort was defeated by lack of optimization to the mining code under which the initial difficulty was chosen.  Its a lesson anyone working on a new hash algorithm in the future should take to heart, it is meant as a constructive postmortem of this coins release.

Your statements are simply knee-jerk defensiveness and seem to be ignorant of SK stated intentions as well, I assure you he is capable of taking constructive criticism and learning from mistakes, I recommend you do likewise.

[airtreb]

how can i make primecoind works? when i want to see my primespersec using command primecoind getprimespersec geives me this error: you must set rpcpassword=<password> in the configuration file:
if the file doesn't exist, create it  with owner-readable-only file permission

this is my config file

rpcuser=x
rpcpassword=x
gen=2


can someone help me with this? thanks

[Schleicher]

Nice chart but doesn't look correct though. There were a significant period over the weekend that block spacing dropped under 10 seconds.

Orphaned blocks are not included in the graph, I think.

[paulthetafy]

how can i make primecoind works? when i want to see my primespersec using command primecoind getprimespersec geives me this error: you must set rpcpassword=<password> in the configuration file:
if the file doesn't exist, create it  with owner-readable-only file permission

this is my config file

rpcuser=x
rpcpassword=x
gen=2


can someone help me with this? thanks

Set the pass different to the user and gen=1

[rethaw]

Nice chart but doesn't look correct though. There were a significant period over the weekend that block spacing dropped under 10 seconds.

I fixed this chart... Sorry about that!

[mr_random]

If the initial code had been properly optimized then starting difficulty could have been nearly 9 and we wouldn't be seeing such a short block time.  This is a lesson, if your going to release a new algorithm for CPU mining, optimize the CPU code or else you've get quasi-ASIC like behavior in which hash rates explode and the coins may end up monopolized by people who have access to the high potency mining ability even if this is by software rather then hardware.

Starting difficulty would have still been where Sunny set it, 7. I don't know what the distribution looks like, but I am still finding blocks on 5 micro instances and a laptop running while I am sleeping. If difficulty adjustments took two weeks, I would agree with you, but it's dynamic.

If his starting difficulty was in any way chosen to reflect the mining rate of some target number of PCs (the method Satoshi used) then optimized code would certainly have lead him to choose a higher difficulty, do you think 7 was just a number he pulled out of his ass with no regard to the target block time?

So not only does he have to code and promote the coin, now he has to divine the future? I imagine that he set it where it to wouldn't be jammed up with orphan chains initially when utilizing CPU mining and then allowed it to self regulate. There is no way to predict adoption or hashing power or optimization. You are just some tool upset about the first WEEK of mining. Entitlement is an ugly thing. Didn't get enough of those 200k coins, or what?

Fuckin' a...some people will bitch about anything.

Oh get off it you twit, I'm pointing out how Sunny King could have had a better initial release that meet HIS goals.  From what I've read on the optimization threads the original client was doing really obviously un-optimized stuff like calling malloc repeatedly which any first year programmer knows is a performance killer.  Optimization CAN be predicted and the factor of 100x we have seen so far would be considered quite easy and 'low hanging fruit' to most programmers.

SK was clearly trying to avoid overly fast blocks per his own pre-release thread that advertised "Reasonably high starting difficulty to limit instamining" but that effort was defeated by lack of optimization to the mining code under which the initial difficulty was chosen.  Its a lesson anyone working on a new hash algorithm in the future should take to heart, it is meant as a constructive postmortem of this coins release.

Your statements are simply knee-jerk defensiveness and seem to be ignorant of SK stated intentions as well, I assure you he is capable of taking constructive criticism and learning from mistakes, I recommend you do likewise.

Hindsight is 20-20.

Further point - do you know what the word insta stands for in instamine?  The opportunities for this coin have been fairly equal and better than most other coins. On day 1 people were sharing guides on how to mine it on cloud servers... I followed a guide 3 days later and mined a good amount of coins on amazon. On day 1 and 2 I got a few blocks on my spare computers in my house.

The coin distribution of this new release has been comparatively excellent. It makes coins like Feathercoin which produced 3 million in the first day look like a joke.

[itod]

I just posted this idea in another thread, but I'm posting it again to reach more XPM miners.

I've started 'banking' single mined blocks in encrypted wallets with each block I find by making a back-up and creating a new wallet each time (where possible).

I figured that if / when someone happens to find a block with an exeptionally long chain, then at least it will be a mined block on a single wallet.

This could give the block a higher value in the future as the coins will also be unspent.

Primecoin is a Scientific Computing Cryptocurrency afterall.

Sounds like a tedious task, if you ask me.
You could just mine into one wallet and dump those private keys into separate wallets later on.

Amazing how creative people are at wasting their time when they don't understand how something works. He obviously didn't get that blocks are linked to private keys inside the wallet, instead he thought they are linked to the particular instance of the wallet used during the mining.

[reb0rn21]

My client also not connecting after i deleted block chain, any addnode to help?

[mikaelh]

My client also not connecting after i deleted block chain, any addnode to help?

Here's a list of outgoing connections from my primecoind:

Code:

        "addr" : "192.241.143.207:9911",
        "addr" : "198.211.105.211:9911",
        "addr" : "50.112.196.19:9911",
        "addr" : "88.190.56.58:9911",
        "addr" : "46.249.52.141:9911",
        "addr" : "54.232.230.20:9911",
        "addr" : "54.215.168.106:9911",
        "addr" : "198.199.108.176:9911",

[zax983]

OK, but I have so bad luck or it's most suck coin ever?!

I mine over 70 hours and I found 10 blocks (all immature...). Today all was changed to orphan and was delete from my wallet... It's really not nice and completly demotivated...

You can try to break my badluck with any donation to XPM: AYt9xqb8vCDEQoL6W1hKxJmLwwQ6BvjFA6

can you explain?

[refer_2_me]

Nice chart but doesn't look correct though. There were a significant period over the weekend that block spacing dropped under 10 seconds.

I fixed this chart... Sorry about that!

https://i.imgur.com/XgvFoU4.png

https://i.imgur.com/WhShzqc.gif

Cool charts, but IMO you should scale the y axis the same in all of them. It looks like you are using matplotlib, so you can set that with 'ylim(ymax =160)'.

[jubalix]

strange....no blocks for ages now...

wonder if the upstart inteferes with primecoind?

[BitcoinFX]

I just posted this idea in another thread, but I'm posting it again to reach more XPM miners.

I've started 'banking' single mined blocks in encrypted wallets with each block I find by making a back-up and creating a new wallet each time (where possible).

I figured that if / when someone happens to find a block with an exeptionally long chain, then at least it will be a mined block on a single wallet.

This could give the block a higher value in the future as the coins will also be unspent.

Primecoin is a Scientific Computing Cryptocurrency afterall.

Sounds like a tedious task, if you ask me.
You could just mine into one wallet and dump those private keys into separate wallets later on.

Amazing how creative people are at wasting their time when they don't understand how something works. He obviously didn't get that blocks are linked to private keys inside the wallet, instead he thought they are linked to the particular instance of the wallet used during the mining.

Actually I do very much understand, although some maybe do not or would not know how to do this easily.

With the gap increasing between finding a block its not really time consuming at all. Even less so in fact if you automate the process.

Perhaps there are other reasons why this is also a good idea ?  

[paulthetafy]

Quite a few people have posted now saying that they seem to find blocks in quick succession.  I've noticed the same thing, but even to the point where different VPS's (same provider) have all found blocks within a minute of each other but nothing for hours either side.  In the last 4 hours I found 9 blocks all at the same time across 6 VPS's (around 30 mins ago), and then nothing for the 3 hours before that.  I have seen the same kind of patterns over the last few days too (though no normally 9 at the same time!).  Has anyone got any theories as to why this might be?

[jubalix]

Quite a few people have posted now saying that they seem to find blocks in quick succession.  I've noticed the same thing, but even to the point where different VPS's (same provider) have all found blocks within a minute of each other but nothing for hours either side.  In the last 4 hours I found 9 blocks all at the same time across 6 VPS's (around 30 mins ago), and then nothing for the 3 hours before that.  I have seen the same kind of patterns over the last few days too (though no normally 9 at the same time!).  Has anyone got any theories as to why this might be?

I have seen exactly this

once one block was found, on one instance....then a whole load more were found quickly by that isnatnce

another that found none never found any

I think findinf say 12 blocks with one instance an zero with an identical instance is very unlikely.....


somethings going on...

I have a few theories
and one is really out there....

[paulthetafy]

What do I need to search debug.log for in order to locate where I have found a block?

[pgbit]

Quite a few people have posted now saying that they seem to find blocks in quick succession.  I've noticed the same thing, but even to the point where different VPS's (same provider) have all found blocks within a minute of each other but nothing for hours either side.  In the last 4 hours I found 9 blocks all at the same time across 6 VPS's (around 30 mins ago), and then nothing for the 3 hours before that.  I have seen the same kind of patterns over the last few days too (though no normally 9 at the same time!).  Has anyone got any theories as to why this might be?

I have seen exactly this

once one block was found, on one instance....then a whole load more were found quickly by that isnatnce

another that found none never found any

I think findinf say 12 blocks with one instance an zero with an identical instance is very unlikely.....


somethings going on...

I have a few theories
and one is really out there....

I get this too. All arrive at once. Go on then, tell us...