bitme
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 14, 2013, 04:01:56 PM |
|
I pay 7DBL per block on my pool 54.214.242.109 with 0% fee. This wild giveaway of precious doubloons wont last forever so join now...
|
NXT makes the Difference My nxtforum account : bitme
|
|
|
|
qwep
Legendary
Offline
Activity: 1008
Merit: 1000
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 16, 2013, 11:25:45 AM |
|
I pay 7DBL per block on my pool 54.214.242.109 with 0% fee. This wild giveaway of precious doubloons wont last forever so join now... Registration does not work
|
|
|
|
Petr1fied
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 16, 2013, 11:48:27 AM |
|
I pay 7DBL per block on my pool 54.214.242.109 with 0% fee. This wild giveaway of precious doubloons wont last forever so join now... Registration does not work It worked perfectly well when I registered yesterday. Mac OSX 10.6+ Binary standby...rebuffering...
maxpower posted an updated Mac Client here for Mac OS X 10.7 Lion.
|
|
|
|
qwep
Legendary
Offline
Activity: 1008
Merit: 1000
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 16, 2013, 12:47:20 PM |
|
I pay 7DBL per block on my pool 54.214.242.109 with 0% fee. This wild giveaway of precious doubloons wont last forever so join now... Registration does not work It worked perfectly well when I registered yesterday. Checked in but the login and password does not accept
|
|
|
|
shakezula (OP)
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 16, 2013, 02:34:59 PM |
|
I pay 7DBL per block on my pool 54.214.242.109 with 0% fee. This wild giveaway of precious doubloons wont last forever so join now... Registration does not work It worked perfectly well when I registered yesterday. Mac OSX 10.6+ Binary standby...rebuffering...
maxpower posted an updated Mac Client here for Mac OS X 10.7 Lion. Very nice, added to the main thread. My Mac-Qt skills are lacking in getting them to run on anything but my own machine at the moment!
|
|
|
|
mhill12
Newbie
Offline
Activity: 54
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 17, 2013, 11:34:47 PM |
|
Sadly, because of the difficulty adjust to 1.13, it looks like we will take a few days until we readjust to a profitable level.
My estimate for the next block adjust is Saturday, based on the average block solve times at this difficulty.
|
|
|
|
Petr1fied
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 18, 2013, 10:55:08 AM Last edit: June 18, 2013, 11:11:21 AM by Petr1fied |
|
Coin devs really need to stop referring to diff retargets in terms of time when in reality it is by the number of blocks solved. (No offence to shakezula intended, all devs refer to retargets in terms of time rather than block intervals).
When the flash miners desert (usually at 1.0 or above) then even 720 blocks can be a very painful interval. This has happened to pretty much every coin recently. At least 720 blocks isn't as bad as the default 2016 blocks.
In my honest opinion, all coins really need to start using much smaller retarget intervals so the coin is better suited to adjust it's difficulty for the size of the network and the dedicated miners don't get screwed over for too long when the flash miners leave.
|
|
|
|
The_Catman
Full Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif) ![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 168
Merit: 100
Captain Jack Fenderson
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 18, 2013, 05:28:08 PM |
|
Coin devs really need to stop referring to diff retargets in terms of time when in reality it is by the number of blocks solved. (No offence to shakezula intended, all devs refer to retargets in terms of time rather than block intervals).
When the flash miners desert (usually at 1.0 or above) then even 720 blocks can be a very painful interval. This has happened to pretty much every coin recently. At least 720 blocks isn't as bad as the default 2016 blocks.
In my honest opinion, all coins really need to start using much smaller retarget intervals so the coin is better suited to adjust it's difficulty for the size of the network and the dedicated miners don't get screwed over for too long when the flash miners leave.
As i understand it, in the source code it's measured in time, so I'm not sure how the retarget interval is affected by how many blocks are actually mined.
|
|
|
|
Petr1fied
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 18, 2013, 05:48:33 PM |
|
As i understand it, in the source code it's measured in time, so I'm not sure how the retarget interval is affected by how many blocks are actually mined.
The idea is to try and keep transactions moving at a set rate by adjusting the difficulty up or down to try and reach an equilibrium for the size of the network. Taking doubloons as an example it's goal is to try and solve 1 block every minute and do difficulty retargets every 12 hours. This is where the 720 blocks for difficulty retargets comes from: 12 hours = 43200 seconds 1 minute = 60 seconds 43200 / 60 = 720 blocks This is all well and good when the network speed is consistent or at the very least doesn't fluctuate too much but in these days of flash miners you get a massive spike in mining which pushes the difficulty up and then just as fast as they came 4/5 (or more) of the miners abandon the coin. This leaves the coin stuck at too high a difficulty and there is no longer any possibility of getting anywhere near the next retarget block in a reasonable timeframe. Sure the difficulty is guaranteed to come down because of this but it'll take a week to get there and this pattern will happen to every coin that doesn't take into consideration the flash miner problem when deciding how many blocks there are between difficulty retargets.
|
|
|
|
The_Catman
Full Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif) ![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 168
Merit: 100
Captain Jack Fenderson
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 18, 2013, 06:04:58 PM |
|
As i understand it, in the source code it's measured in time, so I'm not sure how the retarget interval is affected by how many blocks are actually mined.
The idea is to try and keep transactions moving at a set rate by adjusting the difficulty up or down to try and reach an equilibrium for the size of the network. Taking doubloons as an example it's goal is to try and solve 1 block every minute and do difficulty retargets every 12 hours. This is where the 720 blocks for difficulty retargets comes from: 12 hours = 43200 seconds 1 minute = 60 seconds 43200 / 60 = 720 blocks This is all well and good when the network speed is consistent or at the very least doesn't fluctuate too much but in these days of flash miners you get a massive spike in mining which pushes the difficulty up and then just as fast as they came 4/5 (or more) of the miners abandon the coin. This leaves the coin stuck at too high a difficulty and there is no longer any possibility of getting anywhere near the next retarget block in a reasonable timeframe. Sure the difficulty is guaranteed to come down because of this but it'll take a week to get there and this pattern will happen to every coin that doesn't take into consideration the flash miner problem when deciding how many blocks there are between difficulty retargets. So you didn't read what I said at all. -_- In the source, retarget interval is literally set to 12hrs flat out, not "720 blocks". How many actual blocks are mined at that time shouldn't affect the retargeting happening exactly when it's supposed to.
|
|
|
|
mhill12
Newbie
Offline
Activity: 54
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 18, 2013, 08:33:01 PM |
|
Looking over historical difficulty, it seems to be 720 blocks, not 12 hours.
Also, difficulty would not still be 1.13 since it has been that way about 24 hrs.
|
|
|
|
mhill12
Newbie
Offline
Activity: 54
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 18, 2013, 11:31:20 PM |
|
Looking in the source code, it is 720 blocks: static const int64 nTargetTimespan = 0.5 * 24 * 60 * 60; static const int64 nTargetSpacing = 60; static const int64 nInterval = nTargetTimespan / nTargetSpacing; nInterval is number of blocks before difficulty retargets.
|
|
|
|
sal002
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 19, 2013, 12:51:25 AM |
|
|
|
|
|
The_Catman
Full Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif) ![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 168
Merit: 100
Captain Jack Fenderson
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 19, 2013, 12:55:31 AM |
|
Looking in the source code, it is 720 blocks: static const int64 nTargetTimespan = 0.5 * 24 * 60 * 60; static const int64 nTargetSpacing = 60; static const int64 nInterval = nTargetTimespan / nTargetSpacing; nInterval is number of blocks before difficulty retargets. I was just looking at nTargetTimespan >_> I feel like an idiot. I think those bits were mentioned in shake's cloning guide, so i assume he must've known to change it in doubloons as well.
|
|
|
|
crazyearner
Legendary
Offline
Activity: 1820
Merit: 1001
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 30, 2013, 02:44:47 PM |
|
Wheres best pool for this pirate stuff yarg.
|
|
|
|
mhill12
Newbie
Offline
Activity: 54
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 06, 2013, 01:44:56 AM |
|
Yaargh, Difficulty be walking the plank in less than 24 hours!
|
|
|
|
BitJohn
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 06, 2013, 02:13:50 AM |
|
Great update for a great coin.
|
|
|
|
diatonic
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 06, 2013, 03:06:56 AM |
|
I noticed the ships be backed up in the harbor this morning. I unleashed 5.1 megahash to git the scurvey dogs movin on. Good things coming soon me thinks.
|
|
|
|
Pmalek
Legendary
Offline
Activity: 2870
Merit: 7411
Playgram - The Telegram Casino
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 09, 2013, 03:38:33 PM |
|
Is there gonna be some more pools for this coin, I would mine it but given pool is CRAP. Share submits over the roof, no stratum, high stales, inaccurate hash reading, and developer didnt even change the coin name, it still says BTC in my account... If this coin is gonna be serious please get a decent pool...
|
|
|
|
▄▄███████▄▄███████ ▄███████████████▄▄▄▄▄ ▄████████████████████▀░ ▄█████████████████████▄░ ▄█████████▀▀████████████▄ ██████████████▀▀█████████ █████████████████████████ ██████████████▄▄█████████ ▀█████████▄▄████████████▀ ▀█████████████████████▀░ ▀████████████████████▄░ ▀███████████████▀▀▀▀▀ ▀▀███████▀▀███████ | ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ Playgram.io ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ | ▄▄▄░░ ▀▄ █ █ █ █ █ █ █ ▄▀ ▀▀▀░░
| │ | ▄▄▄███████▄▄▄ ▄▄███████████████▄▄ ▄███████████████████▄ ▄██████████████▀▀█████▄ ▄██████████▀▀███▄██▐████▄ ██████▀▀████▄▄▀▀█████████ ████▄▄███▄██▀█████▐██████ ██████████▀██████████████ ▀███████▌▐██▄████▐██████▀ ▀███████▄▄███▄████████▀ ▀███████████████████▀ ▀▀███████████████▀▀ ▀▀▀███████▀▀▀ | | │ | ██████▄▄███████▄▄████████ ███▄███████████████▄░░▀█▀ ███████████░█████████░░█ ░█████▀██▄▄░▄▄██▀█████░█ █████▄░▄███▄███▄░▄██████ ████████████████████████ ████████████████████████ ██░▄▄▄░██░▄▄▄░██░▄▄▄░███ ██░░░█░██░░░█░██░░░█░████ ██░░█░░██░░█░░██░░█░░████ ██▄▄▄▄▄██▄▄▄▄▄██▄▄▄▄▄████ ███████████████████████ ███████████████████████ | | │ | ► | |
|
|
|
|