Hi,

mining there myself. It seems to have a very short PPLNS warmup time (I'd guess 5min or below), yet still quite high of a share difficulty, i.e. the difficulty you must reach before there is a payout at all. There seem to be few shares in the chain, so already having one share in the chain leads to relatively high payouts.
In other words, depending on your hash rate, if you would get an average of 10kASC/h, you might end up with 55mins of nothing and then 5 mins in which you make those 10kASC.
Share diff seems to be around 300-450, so only after you have submitted a share like that, will you be "qualified" for payouts. As luck will have it, you may have multiple in a straight row, or none at all for a while.
If you use bfgminer, finding a share looks roughly like this:
 [2013-09-12 20:06:43] Stratum from pool 3 requested work update
 [2013-09-12 20:06:43] Accepted 0023c472 MMQ 5c pool 3 Diff 576/16

A "Requested work update" usually means that _someone_ on the pool found a share. If it's in the same second as one high-diff share found by you, you can be quite confident that you were the one with the qualified share, and can expect payouts within the next 2 blocks found by the pool.

Good luck :-)
Mike270

Dear Spoetnik,

in my opinion it's rather total disrespect for the netiquette that I consider "ban-worthy", but I'm no admin here.
It's not like you were attacked in any manner, so you just come into a threat and for no apparent reason start throwing out obscenities.
If you have a point to make about this coin, make it, and make it factual. If there's a point to your critique, that's a much better way to get it across.
No one has attacked you here, so there is absolutely no reason for this behaviour.

Kind regards
Mike270

You do not honestly expect anybody to reply honestly to that question, do you ? ;-)

Coin was actually announced earlier on, not sure if he's even the developer behind it.
https://cryptocointalk.com/topic/1092-pre-ann-butterflycoin-bfc-pre-announcement/

I think the term premine is used inflationary and it should be differentiated between "premining" for the own wallet, or "premining" for the purpose of paying out bounties.
Also: Are we so communist that we think that the creator of the coin deserves nothing for the effort put into it?
Do we expect people to put effort into a coin and a good diff adjustment algo (I think BOC has one) to do it for pure joy and for free?

Kind regards
Mike

Totally agree.

Great coin, I love how smooth yet responsive the diff adjusts to varying hashpower.

Ok, I must admit having been wrong, having crawled through the block explorer that doesn't offer the nice listings I'm used to (only one block at a time). Phew! ;-)
I took a look at block 58329, which is 10 minutes in the future from its surrounding blocks, and at 58332 a retarget occured from 742->704.
Blocks considered at retarget were 58252 and 58331, which had time stamps 19:28:58 and 20:11:07, so 42:09mins, where 40mins would have meant no retarget and >40mins meaning diff lowering.
So everything fine here.

Sorry for false alarm

Well I've been monitoring it live on my miner, and you could see more than 3 blocks per minute and the occasional block 15 minutes in the future and diff going straight down.
I've seen it with terracoin and those future-blocks are a very good indication when combined with a higher-than-aimed-for block generation rate.
Right now he seems to have stopped for the time being.

Looks like some Terracoining is going on - someone rides the diff down by manipulating his system clock into the future making the client think blocks took extra long, thus lowering diff.
Developers to the rescue!

Just open the wallet and unlock it (using "walletpassphrase" command in command line windows from BitBar).
I guess if you were mining your POS wouldn't really make you happy as it gets rounded to zero.
In my case I consolidated funds by moving money from multiple smaller transactions (i.e. mining) to myself in one transaction to have a larger POS.

Yep

No, they were using the halving code all along, I was monitoring it and you can see it by the fluctuations in the timestamps (+/- 20 mins).
Whenever a block was >5mins old, they'd make their client think it's actually 15 mins in the future ( so the client thinks the block is >20 mins old) to trigger the diff halving). It's difficult to see in the block explorers since they don't have the timestamp when they actually received the blocks, but when you see something like

block 1      10:10h       Diff 10000
block 2      10:30h       Diff 5000
block 3      10:11h       Diff 6000

then you can be pretty sure that the timewarp magic was used for block 2 whereas blocks 1+3 might be from regular miners.

Another scenario was when they found a block that was not yet 5 mins old (so they couldn't use their magic yet) they dated it 5 mins into the past, that way being able to mine the next block at half diff right from the beginning.

Something along

block 1    10:10h     Diff 10000
block 2    10:05h     Diff 12000
block 3    10:25h     Diff 5000
block 4    10:11h     Diff 6000

But they did it way better than the attacker from the last few days because they didn't take a 100% of the cake.
And also everybody else was profitting of the generally-low-difficulty as well, whereas last days' attacker was so fast almost everybody else was filling the orphanages.
But there were quite a few situations where we probably had been stuck for quite a while hadn't someone used the halve-diff trick for getting diff back down sooner than otherwise.

Kind regards
Mike

That's nice but I guess that's gonna happen frequently from now on and afaik this was why they introduced the diff halving (that was now abused) in the first place... what's gonna save us when for example at one exchange prices rice dramatically, hash power increases accordingly, then prices drop & miners leave and we are stuck who-knows-where?
Does anybody know where such kind of discussions by the devs can be followed? On terracointalk.org there seems to be not much going on :-(

You are being over-protective - your children need fresh air and freedom!
Well I would define an orphan as a block that made it onto the network, but looks like it didn't even make it onto the network.
Is your client connected? Are you perhaps on your on offline fork?

I like the infinitely unknown network hash rate :-)

I guess you should do --disable-opencl and do a build only for cpu mining...
Testing my own optimizations right now, so there won't be further findings from me for a while :-)

You need to pass it a --scan-time 1, that way it will register new blocks faster (necessary for those short intervals we have)
It seems to pass whatever it finds, though, no proof-of-work check implemented yet as it seems.
So far all my block candidates it found on testnet were rejected(by primecoind). No block candidates on production yet.

Just happened to be that way....
neverhappy...

WAIT!
There just was an update to the repository!
He also did some more updates, like making some mining printf's configurable, it seems.