[ANN] Slimcoin : Proof of Burn NEW BLOCK GEN, Mineable by low power computer!

[TheRealSteve]

Do you have approximately the amount of POB / day ?

range (datetime)	range (height)	PoW	PoB	PoS	total
2014/06/22 18:00:00 UTC 2014/06/23 18:00:00 UTC	17,417 18,527	200	62	849	1,111
2014/06/23 18:00:00 UTC 2014/06/24 18:00:00 UTC	18,528 19,693	192	68	906	1,166

As there was also some question as to the pool, I had an old tab with the found blocks open and amended it with later data.  Between 2014/06/24 10:00:00 UTC and 2014/06/24 18:00:00 UTC, the pool found 20 blocks.  The total number of PoW blocks in that timeframe was 48.  Given that the pool's hash rate has been slightly below 1Mhash/s for much of that time (according to the pool's own graphs, hash rate dropped abruptly a few hours ago), and an approximate 2Mhash/s network hash rate, that seems reasonable, even without keeping in mind the variability issue that sandor111 already mentioned.

[1715536801]

1715536801

[1715536801]

1715536801

[1715536801]

1715536801

[TheRealSteve]

You acting stupid too ? There were no PoS blocks before the last fork, it was broken.

You asked where the figures were coming from, I pointed out that it's in the code, you said that "this was implemented in the last fork".  The only logical interpretation is that "this" referred to the code cited - not any potential issues with regard to any PoS dealings.

As far as PoS blocks "before the last fork" goes - that depends on which fork you're referring to with "last fork".  They do appear to have occurred before the most recent fork:

Example blocks: 15158 (first one, afaict), 15305, 15436, 15468, 15474

If you meant the fork before that, then sure.

[primer-]

You acting stupid too ? There were no PoS blocks before the last fork, it was broken.

You asked where the figures were coming from, I pointed out that it's in the code, you said that "this was implemented in the last fork".  The only logical interpretation is that "this" referred to the code cited - not any potential issues with regard to any PoS dealings.

As far as PoS blocks "before the last fork" goes - that depends on which fork you're referring to with "last fork".  They do appear to have occurred before the most recent fork:

Example blocks: 15158 (first one, afaict), 15305, 15436, 15468, 15474

If you meant the fork before that, then sure.

Count ALL PoS blocks from height 0-15935 and 15935-19790 and you'll see what i am talking about...

Anyway, PoW creation time now is around 7-8 minutes. I cant wait for more PoS blocks, that should lower PoW blocks further BROKEN, dev better fix it in the next update.

[TheRealSteve]

Example blocks: 15158 (first one, afaict), 15305, 15436, 15468, 15474

Count ALL PoS blocks from height 0-15935 and 15935-19790 and you'll see what i am talking about...

Now why would I count them when I already stated that, as far as I can tell, 15158 was the first one, and the graph clearly shows there were many more after the most recent fork?

Besides, I still fail to see how that relates to "there were no PoS blocks before the last fork" (which is either false or true depending on which fork you were referring to), and moreover what the "this" in your post was.

Anyway, as mentioned, PoW could go up to a 15 minute interval as far as the code seems to be concerned - so rather than broken, I'd suspect it's by design.

[primer-]

Example blocks: 15158 (first one, afaict), 15305, 15436, 15468, 15474

Count ALL PoS blocks from height 0-15935 and 15935-19790 and you'll see what i am talking about...

Now why would I count them when I already stated that, as far as I can tell, 15158 was the first one, and the graph clearly shows there were many more after the most recent fork?

Besides, I still fail to see how that relates to "there were no PoS blocks before the last fork" (which is either false or true depending on which fork you were referring to), and moreover what the "this" in your post was.

Anyway, as mentioned, PoW could go up to a 15 minute interval as far as the code seems to be concerned - so rather than broken, I'd suspect it's by design.

There were several updates from 15000 - 15935. There were no PoS blocks when the network was healthy and when block propagation worked (up to block 15158). Then came the PoS update which killed block propagation/coin.

PoW blocks were created every 90 secs up to block 15158.

Quoting retard dev again : "A PoB block is found every 1-3 PoW blocks, (every 90-270 seconds). " (https://bitcointalk.org/index.php?topic=613213.msg7019069;topicseen#msg7019069)

EDIT : Specification says 250 million total coins will be created in 15 years. At the current rate 3000 coins are created per day. This number will be significantly lower every day due to higher difficulty/nEffectiveBurnCoins. 250 million in 15 years ? Not possible.

[jadefalke]

the Reward for a POW Block i got recently was 5.x SLM should that really that low?

[primer-]

the Reward for a POW Block i got recently was 5.x SLM should that really that low?

No, thats another GUI bug.

[primer-]

We need more hash power at slm.blockquarry.com - we are getting more blocks than slimcoinpool with LESS hash (blocks 19816, 19826, 19845, 19852 VS slimcoinpools 19823 and 19846)
https://slm.blockquarry.com/index.php?page=statistics&action=pool

[hashmaster3000]

If I understand the code correctly, the total target block time is 90s, not the PoW target block time.

The PoW target block time is determined by this formula:
(main.cpp:1045)

Code:

int64 nTargetSpacing = fProofOfStake ? STAKE_TARGET_SPACING : 
    min(nTargetSpacingWorkMax, (int64) STAKE_TARGET_SPACING * (1 + pindexLast->nHeight - pindexPrev->nHeight));

STAKE_TARGET_SPACING is 90 (1.5 minutes) and nTargetSpacingWorkMax is 900 (15 minutes).
Thus, for POS blocks, the target spacing is always set to 90 seconds (because fProofOfStake is true for POS blocks).
For POW blocks, the target spacing is min(nTargetSpacingWorkMax, (int64) STAKE_TARGET_SPACING * (1 + pindexLast->nHeight - pindexPrev->nHeight)).
In other words, the target spacing gets set to 90s * (2 + number_of_non_pow_blocks_since_the_last_pow_block).
If this value exceeds 15 minutes, the target spacing is set to 15 minutes.

=> When there are many PoS blocks, the PoW block spacing gets increased in order to achieve the total average block time of 90 seconds.
This feature seems to be inherited from Peercoin.

[primer-]

If I understand the code correctly, the total target block time is 90s, not the PoW target block time.

The PoW target block time is determined by this formula:
(main.cpp:1045)

Code:

int64 nTargetSpacing = fProofOfStake ? STAKE_TARGET_SPACING : 
    min(nTargetSpacingWorkMax, (int64) STAKE_TARGET_SPACING * (1 + pindexLast->nHeight - pindexPrev->nHeight));

STAKE_TARGET_SPACING is 90 (1.5 minutes) and nTargetSpacingWorkMax is 900 (15 minutes).
Thus, for POS blocks, the target spacing is always set to 90 seconds (because fProofOfStake is true for POS blocks).
For POW blocks, the target spacing is min(nTargetSpacingWorkMax, (int64) STAKE_TARGET_SPACING * (1 + pindexLast->nHeight - pindexPrev->nHeight)).
In other words, the target spacing gets set to 90s * (2 + number_of_non_pow_blocks_since_the_last_pow_block).
If this value exceeds 15 minutes, the target spacing is set to 15 minutes.

=> When there are many PoS blocks, the PoW block spacing gets increased in order to achieve the total average block time of 90 seconds.
This feature seems to be inherited from Peercoin.

Thanks for your detailed explanation. Any thoughts on total coin supply ? 250 million ? really ?
PoS blocks are increasing at a very fast rate, are we to expect 15 minute PoW blocks soon ?

[primer-]

UPDATE :  slm.blockquarry.com is now in front of slimcoinpool by 3 blocks - with only 470KH compared to 650KH
(blocks 19816, 19826, 19845, 19852, 19878 VS slimcoinpools 19823 and 19846)
How many coin flips is that ? 

https://slm.blockquarry.com/index.php?page=statistics&action=pool

[kbs1]

how many confirms does it take for slimcoinpool to payout? My first earnings were at block 19511 - 0.00834640 SLM, and now 200+ blocks later, still not a dime in the wallet and status of all blocks is "immature". How long before they mature?

[sandor111]

how many confirms does it take for slimcoinpool to payout? My first earnings were at block 19511 - 0.00834640 SLM, and now 200+ blocks later, still not a dime in the wallet and status of all blocks is "immature". How long before they mature?

at least 510 confirms are needed.

[hashmaster3000]

I didn't look at the total coin supply yet.

(...) are we to expect 15 minute PoW blocks soon ?

I might be wrong (seriously, I'm not an altcoin expert), but I think so.
When PoS blocks come in every 90 seconds, the POW target spacing should increase until it hits the 15min max limit.
Example calculation without PoB blocks, assuming that PoS "hashrate" (more accurately: the total eligible coin age in all PoS-enableed wallets) is fairly uniform:

PoW spacing_____	Expected non-PoW blocks since last PoW block_____	New PoW spacing
2*90	2	4*90
4*90	4	6*90
6*90	6	8*90
8*90	8	10*90
10*90	10	10*90 (max)

When there is a PoB block, the "non-PoW blocks since last PoW block" number gets increased by one, accelerating this process.
Thus, the PoW target spacing should indeed tend towards 900 seconds (15 minutes).

However, since sometimes (or maybe even quite often?) there will be less than 8 non-POW blocks during a 15-minute interval - causing the next PoW spacing to go down slightly.
Due to those temporary deviations, I expect that the average PoW target spacing will be slightly below 15 minutes.

If we drop the assumption that the PoS "hashrate" is fairly uniform (for example because some people don't stake 24/7 but just during a couple hours when their PC is powered on), the average PoW target spacing should drop another bit lower because the actual PoS block spacing will temporarily rise above 90s, increasing the probability of getting less than 8 non-PoW blocks during a 15min interval.

[glop]

   At this rate,  10 SLM / 15 minute  it will take 700 year to reach the target of 250Millions !!!!!!!! 


   or 7 year to reach 2.5 Millions     

[freigeist]

  At this rate,  10 SLM / 15 minute  it will take 700 year to reach the target of 250Millions !!!!!!!! 


   or 7 year to reach 2.5 Millions     

This is a long term project and coin and the developer
was thinking about the next generations of miners that will come in future.

If everything would be mined in few years what will the next generations do?!

[glop]

  At this rate,  10 SLM / 15 minute  it will take 700 year to reach the target of 250Millions !!!!!!!!  


   or 7 year to reach 2.5 Millions    

This is a long term project and coin and the developer
was thinking about the next generations of miners that will come in future.

If everything would be mined in few years what will the next generations do?!

   Think about your coin in 700 year, or instead if you cannot project you, think about this coin in the year 1314 !!!  almost 100 year before America has been discovered

[yang5034]

now it's hard to find pob now .Currency becomes pointless to burn coins.  all  the supply one day reduced to about 4000 coins , too much time to find pob to get the coins back.

I have found many PoB today, make sure you are :
1. Synced
2. Minting (unlocked wallet)
3. Running the latest client

how much pob a day，and how many coins you have burned ,when can you get the bruned coins back.

[kbs1]

Do I have to keep my wallet open in order to calculate PoB? I've burnt some coins, and I'd like to execute this on a raspberry Pi. Is it enough if I compile and run slimcoind there? Or how does this work? Is this work wallet - dependent? (I presume yes). Thanks.

Okay, it seems that just running slimcoind -daemon with the correct wallet.dat file is enough to produce PoB hashes

[idad01]

I have found many PoB today, make sure you are :
1. Synced
2. Minting (unlocked wallet)
3. Running the latest client

'Minting (unlocked wallet)' What does this mean?
Use 'setgenerate true' command?