Search content
Sort by
Showing 17 of 17 results by x_static
Those running KGW might want to take a look and my commit for BOB's Wormhole, and possibly adapt it to their own coin, if they still plan to keep it KGW. That is if no one finds its flaws are worse than stock.
BOB's Wormh0le - Kimoto Gravity Well Customization
BOB's Wormh0le - Kimoto Gravity Well Customization
This glorious patch has changed 2 lines of the actual code to make it fit your very slow coin and 1 more line to narrow event horizons. Now, it's surely the greatest thing since tinned beer. Or not? It's still KGW and it's still broken, time warping not fixed, but you don't get it anyway because you haven't cared to read this thread from the start before posting your advertising spam.
Nice, you confirm some of my previous statements, but you obviously are guilty of what you assume I've done. Which is not read this thread. It's time to stop talking and backup your claims. TimeWarp BOB. I DARE YEW!!!
So, lets have a gander at Auroracoin Block Explorer to prove a point I made in my post right above this, about how default KGW sucks and is a coin fountain.
Lets look at the two most recent groups, of 100 blocks. With a 5 minute block target, we should average 12 blocks per hour, taking about 8 hours & 20 minutes to generate 100 blocks.
14532 2014-04-29 08:34:53 10 diff 122.244
to
14631 2014-04-29 19:26:02 4 diff 109.553
Just shy of 11 hours to generate the above 100 blocks. Over a 100 block period, I'd really hope that I'd be reasonably close to being on target time wise. 2.5 hours off is significant. But lets look at the last 100.
14632 2014-04-29 19:36:12 7 diff 109.722
to
14731 2014-04-29 23:38:07 7 diff 134.433
100 blocks in 4 hours. That is a huge swing, and what I like to call "clumping". Which what default KGW is prone to, because its looking at a huge window, and not reacting fast enough to whats going on "right now". But look at the block 14731, right before the diff hit 134.433.
14730 2014-04-29 23:29:39 2 diff 118.773
So, 99 blocks to go from a difficulty of 109 to 118, then bam. Finally it decides enough is enough. But wait... I just notice this...
14590 2014-04-29 15:34:26 22 diff 117.466
14591 2014-04-29 15:40:09 5 diff 114.095
14592 2014-04-29 18:18:58 33 diff 114.132
14593 2014-04-29 18:19:41 1 diff 71.654
With difficulty dropping, 14592 was a 2 hour and 40 minute block. 14593, difficulty dropped to 71! Here is where the coin fountain kicked in. In a matter of 5 hours and 20 minutes, 139 blocks were generated. Remarkably close to the 144 block minimum window standard KGW looks at.
14592 2014-04-29 18:18:58 33 diff 114.132
14617 2014-04-29 18:23:37 1 diff 107.076
The first 25 block of this fast period were stripped off in 5 minutes!!! 25 blocks in the period that only 1 was supposed to be generated. Crazy stuff... KGW sucks... Was this an attack, or just bad luck that prompted this crazy swing? I think you can just chock it up to KGW sucking badly in stock form with that 144 block minimum window. Yes, if you add up all the blocks over time since KGW has kicked in, you might be near your block generation target. But no matter how bad of luck you run into, 25 blocks in 5 minutes is unacceptable. Bad luck is bad luck, no one should be rewarded like that for it. Those blocks should just be lost is it was that bad. This scares me more than time warp, because it will happen under just normal operating conditions.
Those running KGW might want to take a look and my commit for BOB's Wormhole, and possibly adapt it to their own coin, if they still plan to keep it KGW. That is if no one finds its flaws are worse than stock.
BOB's Wormh0le - Kimoto Gravity Well Customization
Lets look at the two most recent groups, of 100 blocks. With a 5 minute block target, we should average 12 blocks per hour, taking about 8 hours & 20 minutes to generate 100 blocks.
14532 2014-04-29 08:34:53 10 diff 122.244
to
14631 2014-04-29 19:26:02 4 diff 109.553
Just shy of 11 hours to generate the above 100 blocks. Over a 100 block period, I'd really hope that I'd be reasonably close to being on target time wise. 2.5 hours off is significant. But lets look at the last 100.
14632 2014-04-29 19:36:12 7 diff 109.722
to
14731 2014-04-29 23:38:07 7 diff 134.433
100 blocks in 4 hours. That is a huge swing, and what I like to call "clumping". Which what default KGW is prone to, because its looking at a huge window, and not reacting fast enough to whats going on "right now". But look at the block 14731, right before the diff hit 134.433.
14730 2014-04-29 23:29:39 2 diff 118.773
So, 99 blocks to go from a difficulty of 109 to 118, then bam. Finally it decides enough is enough. But wait... I just notice this...
14590 2014-04-29 15:34:26 22 diff 117.466
14591 2014-04-29 15:40:09 5 diff 114.095
14592 2014-04-29 18:18:58 33 diff 114.132
14593 2014-04-29 18:19:41 1 diff 71.654
With difficulty dropping, 14592 was a 2 hour and 40 minute block. 14593, difficulty dropped to 71! Here is where the coin fountain kicked in. In a matter of 5 hours and 20 minutes, 139 blocks were generated. Remarkably close to the 144 block minimum window standard KGW looks at.
14592 2014-04-29 18:18:58 33 diff 114.132
14617 2014-04-29 18:23:37 1 diff 107.076
The first 25 block of this fast period were stripped off in 5 minutes!!! 25 blocks in the period that only 1 was supposed to be generated. Crazy stuff... KGW sucks... Was this an attack, or just bad luck that prompted this crazy swing? I think you can just chock it up to KGW sucking badly in stock form with that 144 block minimum window. Yes, if you add up all the blocks over time since KGW has kicked in, you might be near your block generation target. But no matter how bad of luck you run into, 25 blocks in 5 minutes is unacceptable. Bad luck is bad luck, no one should be rewarded like that for it. Those blocks should just be lost is it was that bad. This scares me more than time warp, because it will happen under just normal operating conditions.
Those running KGW might want to take a look and my commit for BOB's Wormhole, and possibly adapt it to their own coin, if they still plan to keep it KGW. That is if no one finds its flaws are worse than stock.
BOB's Wormh0le - Kimoto Gravity Well Customization
This was actually a quite informative, leading edge thread on the subject of difficulty retargeting algorithms until you popped in and sullied it with your stench.
Yes, and ghostlander has a number of quality contribution to the thread.
How about you doing the same?
My first post doesn't count? Default KGW is a coin fountain. You don't even need to exploit it. Just throw hash at the coin, and it starts spitting blocks out. Grab about 40 - 50 blocks in a couple minutes, then take your hash elsewhere. Simple as that. BOB's Wormhole addresses that issue. Does it create more problems than it addresses? That's why I posted here for review. Did I choose KGW for Dobbscoin? No. Another member of the Dobbscoin crew approached Shakezula on the subject of difficulty retarget algorithms, and he put together this commit, which with settings like "PastSecondsMin = TimeDaySeconds * 2.5;" was sure to turn Dobbscoin into a coin fountain. Not to mention that he failed to address the fact that Dobbscoin has a working testnet. BOB's Wormhole is KGW tuned to a 10 minute block target, with a much smaller event horizon window. Settings like no one else is running. Put forth in this thread to be scrutinized. I personally think KGW sucks. The Wormhole IMO being the best implementation out. I'll take clamping over coin fountain, any day. Especially with a 10 minute block target, on a coin that isn't meant for speculators. Maybe look at my commit history for Dobbscoin, and learn how to make a Coingen coin better than most of whats out right now.
I invite you all to smack around Dobbscoin a.k.a. BOB, some. It also uses KGW, has the fix in the OP applied, but it's running some settings we like to call BOB's Wormh0le, with a much smaller event horizon window. Not intended to be the be all end all answer... It's still KGW. But putting something a little different out there, that we might be able to learn from. Yeah, there is practically no hash on the coin, so it won't take much to hammer it, so try not to hit it too hard and just it. Though, at the end of the day, we're not trippin. Checkpoint, increment versions, rebuild, release... It'd be nicer if you didn't try to completely ruin the fun for everyone. I'm thinking we're most susceptible to a difficulty walkup. Haven't really tested it. Figure some of you all might be better equipped to accomplish the task of exposing flaws with excellence. BTCBob will probably get mad at me for posting this. But hey... Anyone down to hammer the h0le? Heh heh... Them other Bobbies will probably freak out if they see some huge diff spikes... LOL
Dobbscoin Homepage
Latest Dobbscoin Release
Dobbscoin Source
Dobbscoin Block Explorer (might be interesting to compare to Auroracoin block explorer)
Dobbscoin Home Pool
Dobbscoin SMF
#dobbscoin on FreeNode
P.S. Though BOB has Coingen roots, Testnet does work. So that's always an option. Though the seed node can be wonky at times.
Dobbscoin Homepage
Latest Dobbscoin Release
Dobbscoin Source
Dobbscoin Block Explorer (might be interesting to compare to Auroracoin block explorer)
Dobbscoin Home Pool
Dobbscoin SMF
#dobbscoin on FreeNode
P.S. Though BOB has Coingen roots, Testnet does work. So that's always an option. Though the seed node can be wonky at times.
libstdc++ and libgcc_s_dw2 are regular 32-bit MinGW runtimes, no real need to compile them in. In fact, this executable has even these two compiled in after a project file update. All other non-system dependencies are also built in. A cheap insult, piss off.
Actually, those are the MinGW Versions of standard GNU C & C++ runtime libraries. 32-bit, 64 bit, I don't know... Your wallet ran on a neither my Windows XP or 64-bit Windows 7 VM's. Fail! Rather than adapting the project file to conform to your non-compliant build system(breaking the build for others in the process), you should be editing your command lines used to invoke qmake & make, to accomplish the task of statically compiling binaries. Valid criticism is not a cheap insult. It would seem you started the insults, so maybe you should piss off.
Quote
Blah-blah-blah. If no one in the community needs Mac or Linux or Plan 9 or whatever binaries, why am I supposed to deliver these? Come back to the real world where over 90% are Windows users and most Linux users can build Qt clients & daemons themselves. Feel proud of being a Mac user? Most of the others don't give a shit.
You need to come back to the real world, where people like options. Stop making excuses for why you can't build to Bitcoin standards.
Quote
Really? Feel free to tell me more about coin generation, make my day.
Failed comeback. Vague response. You sound like a little child. Game over. This was actually a quite informative, leading edge thread on the subject of difficulty retargeting algorithms until you popped in and sullied it with your stench. If you want to continue taking it on the head, we hash this out over on CCT. No more cluttering this thread with your BS.
Been looking for a decent replacement to the PPC every block retarget algorithm. KGW, DGW, DigiShield, whatever else does no good. Have got the job done myself finally.
https://github.com/ghostlander/Orbitcoin/blob/1e417b40a65dc316037855b1d3db3b32165c80db/src/main.cpp#L1157
Re-targets every block with separate fixed targets for PoW and PoS. Two averaging windows (short of 5 blocks and long of 20 blocks), both are limited against time warping. Interwindow averaging and 0.25 damping with the final +1% / -2% difficulty limiting. Runs fine so far.
OMFG, this Bobcoin spam is now here at Bitcointalk. This annoying Coingen nonsense will get killed some day. The sooner is the better.
https://github.com/ghostlander/Orbitcoin/blob/1e417b40a65dc316037855b1d3db3b32165c80db/src/main.cpp#L1157
Re-targets every block with separate fixed targets for PoW and PoS. Two averaging windows (short of 5 blocks and long of 20 blocks), both are limited against time warping. Interwindow averaging and 0.25 damping with the final +1% / -2% difficulty limiting. Runs fine so far.
Quote
P.S. Though BOB has Coingen roots, Testnet does work. So that's always an option. Though the seed node can be wonky at times.
OMFG, this Bobcoin spam is now here at Bitcointalk. This annoying Coingen nonsense will get killed some day. The sooner is the better.
LOL, this from the guy who can't even compile a release quality wallet. DLL's included in the Zip for your pleasure, right? LOL
Over at Dobbscoin, we release a full compliment of Wallets with each update. Built to Bitcoin standards. Not this frankenstein build system built, windows wallet only garbage that you and Shakezula seem to have pioneered. You and your cult of crapcoin are the ones who will be dying off soon.
After a quick look at your Orbitcoin block explorer, it would appear your coin generation is all over the place. Nowhere in the realm of where they should be for what you claim the targets are. For PoS or PoW.
P.S. To BCX and other "testers"... Orbitcoin is most definitely worthy of annihilation... Feel free to hit Dobbscoin just as hard...
I invite you all to smack around Dobbscoin a.k.a. BOB, some. It also uses KGW, has the fix in the OP applied, but it's running some settings we like to call BOB's Wormh0le, with a much smaller event horizon window. Not intended to be the be all end all answer... It's still KGW. But putting something a little different out there, that we might be able to learn from. Yeah, there is practically no hash on the coin, so it won't take much to hammer it, so try not to hit it too hard and just shatter it. Though, at the end of the day, we're not trippin. Checkpoint, increment versions, rebuild, release... It'd be nicer if you didn't try to completely ruin the fun for everyone. I'm thinking we're most susceptible to a difficulty walkup. Haven't really tested it. Figure some of you all might be better equipped to accomplish the task of exposing flaws with excellence. BTCBob will probably get mad at me for posting this. But hey... Anyone down to hammer the h0le? Heh heh... Them other Bobbies will probably freak out if they see some huge diff spikes... LOL
Dobbscoin Homepage
Latest Dobbscoin Release
Dobbscoin Source
Dobbscoin Block Explorer (might be interesting to compare to Auroracoin block explorer)
Dobbscoin Home Pool
Dobbscoin SMF
#dobbscoin on FreeNode
P.S. Though BOB has Coingen roots, Testnet does work. So that's always an option. Though the seed node can be wonky at times.
Dobbscoin Homepage
Latest Dobbscoin Release
Dobbscoin Source
Dobbscoin Block Explorer (might be interesting to compare to Auroracoin block explorer)
Dobbscoin Home Pool
Dobbscoin SMF
#dobbscoin on FreeNode
P.S. Though BOB has Coingen roots, Testnet does work. So that's always an option. Though the seed node can be wonky at times.
No other pool for this coin, and the pool doesn't allow for picking difficulty.
I have 4 leased rigs on this coin right now.
xxxxxxxxx (Scrypt 1.33 MH/s) 1.50 3 hours and 56 minutes xxxxxxxxx
SPIDERRIG5 (Scrypt 3.10 MH/s) 2.53 21 hours and 40 minutes spiderdk
xxxxxxxxx (Scrypt 1.40 MH/s) 1.45 47 hours and 38 minutes xxxxxxxxx
xxxxxxxxx (Scrypt 0.35 MH/s) 0.36 47 hours and 18 minutes xxxxxxxxx
I have 4 leased rigs on this coin right now.
xxxxxxxxx (Scrypt 1.33 MH/s) 1.50 3 hours and 56 minutes xxxxxxxxx
SPIDERRIG5 (Scrypt 3.10 MH/s) 2.53 21 hours and 40 minutes spiderdk
xxxxxxxxx (Scrypt 1.40 MH/s) 1.45 47 hours and 38 minutes xxxxxxxxx
xxxxxxxxx (Scrypt 0.35 MH/s) 0.36 47 hours and 18 minutes xxxxxxxxx
Your pool reject rate is quite high now, you will get lower hashrate on the average
http://i61.tinypic.com/20qm8u1.png
http://i61.tinypic.com/20qm8u1.png
Code:
sgminer 4.1.0-121-gd480 - Started: [2014-04-23 01:13:28]
--------------------------------------------------------------------------------
(5s):290.8K (avg):292.0Kh/s | A:194576.000 R:16.000 HW:0 WU:269.952/m
ST: 1 SS: 21 NB: 26 LW: 46545 GF: 1 RF: 0
Connected to pool.slackprojects.org (stratum) diff 16 as user M3d00d
Block: 7ea3a507... Diff:59.2K Started: [13:14:38] Best share: 659K
--------------------------------------------------------------------------------
[P]ool management [G]PU management [S]ettings [D]isplay options [Q]uit
GPU 0: | 292.1K/292.0Kh/s|A:194576.00 R:0.01% HW:0 WU:269.95/m I:1
GPU 1: | OFF / 0.000h/s|A: 0.00 R:0.00% HW:0 WU: 0.00/m I: 0
--------------------------------------------------------------------------------
[13:14:52] Accepted c42fa42f Diff 334/16 GPU 0 at pool.slackprojects.org
[13:14:55] Accepted f96c84ad Diff 262/16 GPU 0 at pool.slackprojects.org
[13:14:57] Accepted 0ac37b64 Diff 23/16 GPU 0 at pool.slackprojects.org
[13:14:58] Accepted 0ff533c4 Diff 16/16 GPU 0 at pool.slackprojects.org
[13:15:02] Accepted 081091ef Diff 31/16 GPU 0 at pool.slackprojects.org
[13:15:05] Accepted 0bf07577 Diff 21/16 GPU 0 at pool.slackprojects.org
[13:15:09] Accepted 02632fd2 Diff 107/16 GPU 0 at pool.slackprojects.org
[13:15:11] Accepted 0a91eafd Diff 24/16 GPU 0 at pool.slackprojects.org
[13:15:12] Accepted 065299ea Diff 40/16 GPU 0 at pool.slackprojects.org
[13:15:18] Accepted 0734cd3b Diff 35/16 GPU 0 at pool.slackprojects.org
[13:15:20] Accepted 0c1b56dd Diff 21/16 GPU 0 at pool.slackprojects.org
[13:15:21] Accepted 65df184e Diff 643/16 GPU 0 at pool.slackprojects.org
--------------------------------------------------------------------------------
(5s):290.8K (avg):292.0Kh/s | A:194576.000 R:16.000 HW:0 WU:269.952/m
ST: 1 SS: 21 NB: 26 LW: 46545 GF: 1 RF: 0
Connected to pool.slackprojects.org (stratum) diff 16 as user M3d00d
Block: 7ea3a507... Diff:59.2K Started: [13:14:38] Best share: 659K
--------------------------------------------------------------------------------
[P]ool management [G]PU management [S]ettings [D]isplay options [Q]uit
GPU 0: | 292.1K/292.0Kh/s|A:194576.00 R:0.01% HW:0 WU:269.95/m I:1
GPU 1: | OFF / 0.000h/s|A: 0.00 R:0.00% HW:0 WU: 0.00/m I: 0
--------------------------------------------------------------------------------
[13:14:52] Accepted c42fa42f Diff 334/16 GPU 0 at pool.slackprojects.org
[13:14:55] Accepted f96c84ad Diff 262/16 GPU 0 at pool.slackprojects.org
[13:14:57] Accepted 0ac37b64 Diff 23/16 GPU 0 at pool.slackprojects.org
[13:14:58] Accepted 0ff533c4 Diff 16/16 GPU 0 at pool.slackprojects.org
[13:15:02] Accepted 081091ef Diff 31/16 GPU 0 at pool.slackprojects.org
[13:15:05] Accepted 0bf07577 Diff 21/16 GPU 0 at pool.slackprojects.org
[13:15:09] Accepted 02632fd2 Diff 107/16 GPU 0 at pool.slackprojects.org
[13:15:11] Accepted 0a91eafd Diff 24/16 GPU 0 at pool.slackprojects.org
[13:15:12] Accepted 065299ea Diff 40/16 GPU 0 at pool.slackprojects.org
[13:15:18] Accepted 0734cd3b Diff 35/16 GPU 0 at pool.slackprojects.org
[13:15:20] Accepted 0c1b56dd Diff 21/16 GPU 0 at pool.slackprojects.org
[13:15:21] Accepted 65df184e Diff 643/16 GPU 0 at pool.slackprojects.org
Why am I only getting 2.35MH/s @ a quoted 3.10MH/s? Rig was at 4.95MH/s When I rented...
Re: [ANN] [888] [SCRYPT] OctoCoin ◦ The Power of Eight ◦ Don't Blink
ah well. might try p2pool soon
It's really the safest way to mine any new coin. I'm on freebtc.eu:8000 right now.. But 888.qemulab.com:8888 seems to have some good hashing going on too. The full list is here:
http://octoscanner.qemulab.com
Re: [ANN] [888] [SCRYPT] OctoCoin ◦ The Power of Eight ◦ Don't Blink
sent octocoinpool (dot) tk pool operator a message about gaps about an hour long where coins do not show up even though dashboard registers me mining. Not sure if it's faster to contact here or through pool's email.
Honestly, this seems to happen on every pool.
With every coin. Every time. Does anyone remember pre-christmas when the R9's came out, and 280X's were flying off the shelves, and impossible to get. Took the price from $300 a card to $400 a card. All that added hashing power took even the best pools down. The added flow of coin, had Cryptsy at its knees. MCXNow shut down temporarily(I think rightfully so), because RS knew his infrastructure, mainly on the support side wasn't ready to cope with the huge influx. Almost no one was able to cope with the growth... These 888 pools had no time to test things... Thankfully the P2Pool's appear to be running flawlessly. freebtc.eu:8888 just keeps spitting coin at me. And all quirks aside, xnigma.com is not a horrifying place to have start getting the 888 moving around. The sysops are actually quite present, and willing to listen to their userbase. Right now all coins are alpha. Even the Alpha(Bitcoin) is alpha. 888 Seems on par, with other coins being released in this day and age.
Re: [ANN] [888] [SCRYPT] OctoCoin ◦ The Power of Eight ◦ Don't Blink
?
Re: [ANN] [888] [SCRYPT] OctoCoin ◦ The Power of Eight ◦ Don't Blink
If a dev plans to launch a coin to be a real player in economic markets, the least they can do is compile the client for linux and windows. Since they did not, we can only speculate they are some fly-by-night hackjob crew.
Cross platform is important, and not having it at launch (or even hours after launch) is a huge problem. The devs have been nearly silent on launchday which is not a good sign.
Cross platform is important, and not having it at launch (or even hours after launch) is a huge problem. The devs have been nearly silent on launchday which is not a good sign.
I've yet to see anyone do this right... Good points. In my eyes, Mac support is a must as well at launch.
Re: [ANN] [888] [SCRYPT] OctoCoin ◦ The Power of Eight ◦ Don't Blink
when will the mac client be launched ?
Not sure about the official one. But I've compiled my own.
OSX Wallet, 10.6 - 10.9 / 32bit Compatible:
https://mega.co.nz/#!BRJmkYiK!_SUWxyy0yFCKwK-sRA4KZ-gNc9WQptpJhLxQOE94jPw
No BS. Just a working wallet. In the old days, this how we did it. If the coin ain't got a Mac client, you build it.
I'm not opposed to donations...
8LXEAESZN2BT5qUf9xEKp1nFixLjSST82w
Enjoy 888...
Edit: PS - I've let the dev know about this build.
Re: [ANN] [888] [SCRYPT] OctoCoin ◦ The Power of Eight ◦ Don't Blink
Re: [PRE-ANN] [888] [SCRYPT] OctoCoin ◦ The Power of Eight ◦ Don't Blink
I know, first post and uploading a wallet. I know that's usually a red flag. Just trying to make the launch a little more interesting.
Hopefully this gets appreciated in the end.
OSX Wallet, 10.6 - 10.9 / 32bit Compatible:
https://mega.co.nz/#!BRJmkYiK!_SUWxyy0yFCKwK-sRA4KZ-gNc9WQptpJhLxQOE94jPw
Accepting 888 donations as appreciation:
8LXEAESZN2BT5qUf9xEKp1nFixLjSST82w
P.S. Mining on freebtc.eu:8888 P2Pool, and getting coin deposited roughly ~5min....
Hopefully this gets appreciated in the end.
OSX Wallet, 10.6 - 10.9 / 32bit Compatible:
https://mega.co.nz/#!BRJmkYiK!_SUWxyy0yFCKwK-sRA4KZ-gNc9WQptpJhLxQOE94jPw
Accepting 888 donations as appreciation:
8LXEAESZN2BT5qUf9xEKp1nFixLjSST82w
P.S. Mining on freebtc.eu:8888 P2Pool, and getting coin deposited roughly ~5min....