There was a limited amount of "pre-mining" for testing but be aware all funds from that are being used for bountys. And no its not like we mined 5 million coins genisis blocks
No one would have been mad about this if you had told so from the beginning. Just saying. |
|
|
|
6vS3UsTu4QCfEZULeDaY6F3ZTVzaLyoXwp Thanks!  |
|
|
|
17 blocks 3 orphans since 20:30 GMT. Try forwarding the listening port etc.
And 1379 blocks before 20:30 GMT. Yes i looked it up. Anything to say about that?  edit: http://www62.zippyshare.com/v/13419047/file.htmlThat's the debug.log for anyone interested. |
|
|
|
1. had to pop out so instead of releasing it late and have you moaning i released 5 mins early..
2. Source will be updated in a bit.
Who was mining this 2 hours, 15 13 minutes and 4 seconds before public release? |
|
|
|
Disclaimer: Times are GMT -1 First blocks: received block b72991e577191701a912
ProcessBlock: ORPHAN BLOCK, prev=2819820a89faeae87c54
received block 1bac648d050ddc94c70b
SetBestChain: new best=1bac648d050ddc94c70b height=1 work=2097184 date=06/26/13 17:16:56
ProcessBlock: ACCEPTED
received block 492905d0fdecfe0aa768
SetBestChain: new best=492905d0fdecfe0aa768 height=2 work=3145776 date=06/26/13 17:17:11
ProcessBlock: ACCEPTED
received block e1f98ab97e56005eb905
SetBestChain: new best=e1f98ab97e56005eb905 height=3 work=4194368 date=06/26/13 17:17:51
ProcessBlock: ACCEPTED
received block f23a5e22aa2951bcfa57
SetBestChain: new best=f23a5e22aa2951bcfa57 height=4 work=5242960 date=06/26/13 17:18:57
ProcessBlock: ACCEPTED
received block 0f268c4415eb1e62add8
SetBestChain: new best=0f268c4415eb1e62add8 height=5 work=6291552 date=06/26/13 17:19:51
ProcessBlock: ACCEPTED
received block e8794f936b0305228714
SetBestChain: new best=e8794f936b0305228714 height=6 work=7340144 date=06/26/13 17:20:00
ProcessBlock: ACCEPTED up to block 1000 received block 9189180670e77315acab
SetBestChain: new best=9189180670e77315acab height=995 work=1346380770 date=06/26/13 19:10:01
ProcessBlock: ACCEPTED
received block d5ae10913e35f9a3279e
SetBestChain: new best=d5ae10913e35f9a3279e height=996 work=1350575090 date=06/26/13 19:10:12
ProcessBlock: ACCEPTED
received block 9f030fdf711ad5ea1e14
SetBestChain: new best=9f030fdf711ad5ea1e14 height=997 work=1354769410 date=06/26/13 19:10:20
ProcessBlock: ACCEPTED
received block 5a96ff35dee35aa26d2e
SetBestChain: new best=5a96ff35dee35aa26d2e height=998 work=1358963730 date=06/26/13 19:10:52
ProcessBlock: ACCEPTED
received block 72eafd57fc61a350f569
SetBestChain: new best=72eafd57fc61a350f569 height=999 work=1363158050 date=06/26/13 19:11:00
ProcessBlock: ACCEPTED
received block 4af57f35d5eaf09fad34
SetBestChain: new best=4af57f35d5eaf09fad34 height=1000 work=1367352370 date=06/26/13 19:11:11
ProcessBlock: ACCEPTED current last block: received block d405c0112d991de7d7d6
SetBestChain: new best=d405c0112d991de7d7d6 height=1828 work=12327219202 date=06/26/13 19:46:21
ProcessBlock: ACCEPTED Look it up yourself in the debug.log: http://www62.zippyshare.com/v/13419047/file.html |
|
|
|
|
That'd be 100k coins. OK, block reward will rise by factor 5 after 5k blocks, making the launch a bit fairer. Still sucks and gives the impression of a dishonest dev(team member), not a good thing for a fresh coin.
|
|
|
|
21:37:15 getblockcount 21:37:15 1553 This coin was mined at least a half hour before release. Notice what the client tells you when the last recieved block was generated while syncing. Meh. If you say 0% premine, don't premine, not that hard. edit: GMT+1 btw |
|
|
|
F19hxiVLdfeV2pYEfANaRRZ1Z7azS2ynqt Thx if this is still going. |
|
|
|
The maintenance message indeed makes a better impression than the 404s on bter, guess they went to bed.  Results are the same though, so no big difference. |
|
|
|
MeD14xLwyKARD6BYvfS2MBkwiYf3y3dMW5 sure, why not  |
|
|
|
Also, YAC will be unminable by GPUs after the next N change.
Not really correct, I'm not sure why people have continued repeating that assumption. It was mtrlt's modified (and unreleased) Reaper kernel that had a problem with N >= 8192. That's not the kernel everyone else is mining with and has no connection with hanzac's OpenCL kernel. Oh well, that statement was repeated so often i thought it was confirmed.  So, will YAC eventually become unminable by GPU, e.g. when the miner needs too much memory? Or was that an unfounded rumour? |
|
|
|
Wow @ all the hate. At least it's not scrypt.  He litterally took the YAC source code, did a find and replace for YAC to YBC, and changed 1 line of code, to lower the block reward. Not that different from the coins you "support". Also, YAC will be unminable by GPUs after the next N change. |
|
|
|
Wow @ all the hate. At least it's not scrypt. |
|
|
|
Gotta love this coin, it just wants to punch you in the face then chew on it for good measure. Thanks for the clue with the first version of the miner, my 5770 got no accepted shares with v5 but v1 gets me a whopping 25kH. |
|
|
|
|
If you get HW errors, that's probably because of the N increase a few hours ago. Almost no one is able to mine with GPU anymore.
|
|
|
|
It's interesting that vircurex and bter are down at the same time. |
|
|
|
Diff and reward change slowly.  |
|
|
|
|
Show Posts
