cobrabyte



Offline



Activity: 70

Merit: 10







MemberActivity: 70Merit: 10 Re: [ANN][SBC] From Death Comes Life  The Rebirth of StableCoin - URGENT UPDATE December 26, 2013, 01:39:33 PM #1041 I've have to wonder if we've reached the point where there *needs* to be more than one developer on this project.



@artos, it's obvious you still have shit going on in your life that keeps you from addressing issues with this coin. We're now into the third day of a situation where the difficulty is pegged... and will only rise. Your response: it's being monitored. There is nothing to monitor. We need a fix. It's a simple fix. It's a fix that's been posted here. It's a fix that's been committed via GitHub... it's a matter of merging code. It simply couldn't be any easier.



There are a lot of us that have a great deal of money invested in SBC and we're left thinking 'am I an idiot for thinking this guy will stick with the project... after having abandoned it already?'



Dude, what the hell can we do to help? This thing is dying here and YOU are responsible. http://sbc.blockexplorer.io/ - saRcSpjGxGWk9mGwFSpNTRbwjDvwLmqSkz

Catswold



Offline



Activity: 518

Merit: 251









Sr. MemberActivity: 518Merit: 251 Re: [ANN][SBC] From Death Comes Life  The Rebirth of StableCoin - URGENT UPDATE December 26, 2013, 03:04:29 PM #1042 Quote from: cobrabyte on December 26, 2013, 01:39:33 PM I've have to wonder if we've reached the point where there *needs* to be more than one developer on this project.



@artos, it's obvious you still have shit going on in your life that keeps you from addressing issues with this coin. We're now into the third day of a situation where the difficulty is pegged... and will only rise. Your response: it's being monitored. There is nothing to monitor. We need a fix. It's a simple fix. It's a fix that's been posted here. It's a fix that's been committed via GitHub... it's a matter of merging code. It simply couldn't be any easier.



There are a lot of us that have a great deal of money invested in SBC and we're left thinking 'am I an idiot for thinking this guy will stick with the project... after having abandoned it already?'



Dude, what the hell can we do to help? This thing is dying here and YOU are responsible.

Couldn't have said this better.



For the time being, I am moving my mining resources to another currency (DGC). I am not certain I feel comfortable with Stablecoin until I begin to see some real responsiveness from artos.



Not certain at this time that eagle eye wasn't closer to the truth than not.



I made this comment before and it still holds true.

Quote Those of us who have been mining SBC have not been doing so out of the goodness of our hearts, we are doing so in the hopes that we are mining a coin that has a bright future and that will ultimately reward those who have expended their mining capacity on SBC's rather than another coin.



The key to success in any venture is open, frequent and informative updates. We are all making a bet that our efforts will be rewarded and we're comfortable with that decision, as long as we feel that things are moving in the correct direction. When communication lags, then investors (and miners--especially newbie miners) begin to get nervous . . . especially when you see the coin value and market cap in a slow, steady decline.



Gamblers and investors are a skittish lot and they require some degree of reassurance that they are not 1. Fools betting on a horse that can't cross the finish line, or 2. Gullible fools who are being played by those more experienced and knowledgeable than they.



Patience is needed on both sides, the miners and gamblers need to allow artos the time necessary to get whatever maintenance and corrective measures accomplished. On the other hand, artos, hazard and others need to understand what the rest are going through and provide a little more thorough communications and updates--maybe even a pep-talk or two. Grin



Artos, Hazard, I know you aren't baby-sitters, but in taking on the responsibility for creating and promoting the StableCoin, you also incurred some responsibility to the people you are asking to trust you. Couldn't have said this better.For the time being, I am moving my mining resources to another currency (DGC). I am not certain I feel comfortable with Stablecoin until I begin to see some real responsiveness from artos.Not certain at this time that eagle eye wasn't closer to the truth than not. https://bitcointalk.org/index.php?topic=349198.msg4051283#msg4051283 I made this comment before and it still holds true.

colonelmustard



Offline



Activity: 35

Merit: 0







NewbieActivity: 35Merit: 0 Re: [ANN][SBC] From Death Comes Life  The Rebirth of StableCoin - URGENT UPDATE December 26, 2013, 03:07:18 PM #1043



In the meantime, I have some coins trapped in limbo because the client isn't syncing.



Is this partly due to the hardfork??





Here is the appended error file. (part of it)





Code:

trying connection 58.183.127.170:17500 lastseen=60.0hrs

connection timeout

trying connection 203.59.132.204:17500 lastseen=357797.2hrs

connection timeout

trying connection 93.212.196.180:17500 lastseen=22.4hrs

UPnP Port Mapping successful.

Flushed 9703 addresses to peers.dat 39ms

connection timeout

trying connection 86.22.130.144:17500 lastseen=357797.2hrs

Added time data, samples 54, offset -2 (+0 minutes)

receive version message: version 60001, blocks=318030, us=210.186.159.34:62418, them=62.194.165.209:17500, peer=62.194.165.209:17500

getblocks 309830 to f0a479c43d2061b64b1b limit 500

getblocks stopping at limit 310329 c8162a3a1e91022aa797

received block cada1293915e45b7a712

ProcessBlock: ORPHAN BLOCK, prev=7824c12b433227710f1a

received block e088325bdb574665e5bf

ProcessBlock: ORPHAN BLOCK, prev=cada1293915e45b7a712

ERROR: FetchInputs() : a2fed928ce mempool Tx prev not found 8b0d95521f

stored orphan tx a2fed928ce (mapsz 11)

received block 8751124d6619787f1ec4

ProcessBlock: ORPHAN BLOCK, prev=e088325bdb574665e5bf

connection timeout

getblocks 310330 to 00000000000000000000 limit 500

getblocks stopping at limit 310829 4a7dd8ca9f2ba0cd9f9d

received block fe39681f8993d260e1e8

nActualTimespan = 417 before bounds

GetNextWorkRequired RETARGET

nTargetTimespan = 600 nActualTimespan = 417

Before: 1c461778 0000000046177800000000000000000000000000000000000000000000000000

After: 1c30b6b5 0000000030b6b5f5c28f5c28f5c28f5c28f5c28f5c28f5c28f5c28f5c28f5c28

ERROR: AcceptBlock() : incorrect proof of work

ERROR: ProcessBlock() : AcceptBlock FAILED

disconnecting node 62.194.165.209:17500

Disconnected 62.194.165.209:17500 for misbehavior (score=100)

trying connection 108.9.45.178:17500 lastseen=2.6hrs

connected 108.9.45.178:17500

send version message: version 1040000, blocks=313853, us=210.186.159.34:17501, them=108.9.45.178:17500, peer=108.9.45.178:17500

trying connection 98.208.236.116:17500 lastseen=19.3hrs

connection timeout

trying connection 59.167.189.49:17500 lastseen=357797.2hrs

received getdata (2 invsz)

connection timeout

trying connection 71.85.220.167:17500 lastseen=707.6hrs

connection timeout

trying connection 72.84.189.238:17500 lastseen=357797.2hrs

connection timeout

trying connection 71.21.140.83:17500 lastseen=45.6hrs

connection timeout

trying connection 85.217.147.117:17500 lastseen=357797.2hrs

socket no message in first 60 seconds, 0 1

disconnecting node 190.174.9.158:17500

connection timeout

trying connection 211.137.20.208:17500 lastseen=11.6hrs

connection timeout

accepted connection 75.155.136.206:58414

send version message: version 1040000, blocks=313853, us=210.186.159.34:17501, them=75.155.136.206:58414, peer=75.155.136.206:58414

Added time data, samples 55, offset -19 (+0 minutes)

nTimeOffset = -2 (+0 minutes)

receive version message: version 60001, blocks=318030, us=210.186.159.34:17500, them=75.155.136.206:17500, peer=75.155.136.206:58414

getblocks 38616 to ba7723d78bffa1791425 limit 500

getblocks stopping at 38891 ba7723d78bffa1791425

connection timeout

trying connection 70.134.73.115:17500 lastseen=6.9hrs

connection timeout

trying connection 193.110.115.124:17500 lastseen=41.8hrs

received block 3abcba6988fc5238b712

SetBestChain: new best=3abcba6988fc5238b712 height=313854 work=1113018976110540 date=12/26/13 15:00:17

ProcessBlock: ACCEPTED

getblocks -1 to 00000000000000000000 limit 500

getblocks -1 to 00000000000000000000 limit 500

getblocks -1 to 00000000000000000000 limit 500

getblocks 38616 to 247be120b701ee36126f limit 500

getblocks stopping at limit 39115 8808075afb1ade0b75ac

getblocks -1 to 00000000000000000000 limit 500

getblocks -1 to 00000000000000000000 limit 500

Flushing wallet.dat

Flushed wallet.dat 159ms

connection timeout

trying connection 98.168.188.82:17500 lastseen=6.2hrs

socket no message in first 60 seconds, 0 1

disconnecting node 5.69.63.209:17500

connection timeout

trying connection 75.171.141.140:17500 lastseen=0.7hrs

connected 75.171.141.140:17500

send version message: version 1040000, blocks=313854, us=210.186.159.34:17501, them=75.171.141.140:17500, peer=75.171.141.140:17500

trying connection 46.14.27.20:17500 lastseen=0.6hrs

received block 5697ddc6e3e01a3927ff

ProcessBlock: ORPHAN BLOCK, prev=8751124d6619787f1ec4

connection timeout

trying connection 206.248.184.174:17500 lastseen=3.9hrs

received block 2715478a7810832d8269

ProcessBlock: ORPHAN BLOCK, prev=6f90eed2523d0ffed6fd

accepted connection 192.222.136.171:57320

send version message: version 1040000, blocks=313854, us=210.186.159.34:17501, them=192.222.136.171:57320, peer=192.222.136.171:57320

Added time data, samples 56, offset +6 (+0 minutes)

receive version message: version 1040000, blocks=313854, us=210.186.159.34:17500, them=192.222.136.171:17501, peer=192.222.136.171:57320

connection timeout

trying connection [2001:0:9d38:6abd:140d:1f57:47c4:21cb]:17500 lastseen=0.6hrs

connected [2001:0:9d38:6abd:140d:1f57:47c4:21cb]:17500

send version message: version 1040000, blocks=313854, us=210.186.159.34:17501, them=[2001:0:9d38:6abd:140d:1f57:47c4:21cb]:17500, peer=[2001:0:9d38:6abd:140d:1f57:47c4:21cb]:17500

trying connection 83.236.208.138:17500 lastseen=2.7hrs

connection timeout

trying connection 67.183.126.156:17500 lastseen=2.1hrs

socket no message in first 60 seconds, 0 1

disconnecting node 108.9.45.178:17500

received block 2fdcdefccc1a06a6ed32

ProcessBlock: ORPHAN BLOCK, prev=5697ddc6e3e01a3927ff

connection timeout

trying connection 78.148.123.143:17500 lastseen=53.8hrs

getblocks 139931 to 985628d459e2e1220590 limit 500

getblocks stopping at limit 140430 dc248feec2697c6eb6a7

connection timeout

trying connection 50.102.222.206:17500 lastseen=3.4hrs

connection timeout

trying connection [2001:0:9d38:90d7:202f:fbff:91a5:7073]:17500 lastseen=5.8hrs

received block 138db4ff0b2961073561

ProcessBlock: ORPHAN BLOCK, prev=2fdcdefccc1a06a6ed32

connection timeout

getblocks 34255 to 985628d459e2e1220590 limit 500

getblocks stopping at limit 34754 057b80d99859588bec3f

received getdata for: block 3abcba6988fc5238b712

trying connection 87.117.50.114:17500 lastseen=54.0hrs

received block d2f085e8ee3eb167fd9c

ProcessBlock: ORPHAN BLOCK, prev=138db4ff0b2961073561

connection timeout

trying connection 178.4.211.145:17500 lastseen=29.4hrs

connection timeout

trying connection 24.39.226.146:17500 lastseen=6.0hrs

Flushed 9703 addresses to peers.dat 66ms

connection timeout

trying connection 78.148.234.156:17500 lastseen=20.5hrs

Added 1 addresses from 86.3.86.71: 687 tried, 9016 new

socket recv error 10054

disconnecting node 75.171.141.140:17500

connection timeout

trying connection 217.67.117.210:17500 lastseen=389.0hrs

connection timeout

trying connection 88.223.2.162:17500 lastseen=2.7hrs

socket recv error 10054

disconnecting node 192.222.136.171:57320

received block a298d10677a040569d43

ProcessBlock: ORPHAN BLOCK, prev=d2f085e8ee3eb167fd9c

getblocks 140431 to 00000000000000000000 limit 500

getblocks stopping at limit 140930 74b38e85ccaa302b773c

connection timeout

socket no message in first 60 seconds, 0 1

disconnecting node [2001:0:9d38:6abd:140d:1f57:47c4:21cb]:17500

trying connection 124.197.25.116:17500 lastseen=6.3hrs

received block fe39681f8993d260e1e8

nActualTimespan = 417 before bounds

GetNextWorkRequired RETARGET

nTargetTimespan = 600 nActualTimespan = 417

Before: 1c461778 0000000046177800000000000000000000000000000000000000000000000000

After: 1c30b6b5 0000000030b6b5f5c28f5c28f5c28f5c28f5c28f5c28f5c28f5c28f5c28f5c28

ERROR: AcceptBlock() : incorrect proof of work

ERROR: ProcessBlock() : AcceptBlock FAILED

disconnecting node 75.155.136.206:58414

Disconnected 75.155.136.206:58414 for misbehavior (score=100)

connection timeout

trying connection 62.243.86.200:17500 lastseen=137.5hrs

accepted connection 83.145.61.116:56811

send version message: version 1040000, blocks=313854, us=210.186.159.34:17501, them=83.145.61.116:56811, peer=83.145.61.116:56811

Added time data, samples 57, offset -9 (+0 minutes)

nTimeOffset = -2 (+0 minutes)

Moving 83.145.61.116:17500 to tried

receive version message: version 1040000, blocks=313854, us=210.186.159.34:17500, them=83.145.61.116:17500, peer=83.145.61.116:56811

connection timeout

trying connection 125.78.10.154:17500 lastseen=62.0hrs

connection timeout

trying connection 75.176.14.241:17500 lastseen=29.8hrs

connection timeout

trying connection 67.81.32.177:17500 lastseen=11.6hrs

trying connection 108.186.237.29:17500 lastseen=357797.3hrs

connection timeout

trying connection 84.106.217.238:17500 lastseen=7.5hrs

connection timeout

trying connection 109.121.82.231:17500 lastseen=357797.3hrs

connection timeout

trying connection 199.119.140.197:17500 lastseen=8.0hrs

connection timeout

trying connection 184.171.221.204:17500 lastseen=357797.3hrs

connection timeout

trying connection 124.150.25.211:17500 lastseen=90.1hrs

connection timeout

trying connection 109.80.94.251:17500 lastseen=357797.3hrs

connection timeout

trying connection 192.222.136.171:17500 lastseen=3.7hrs

connected 192.222.136.171:17500

send version message: version 1040000, blocks=313854, us=210.186.159.34:17501, them=192.222.136.171:17500, peer=192.222.136.171:17500

trying connection 118.113.168.33:17500 lastseen=11.3hrs

connection timeout

trying connection 93.138.167.14:17500 lastseen=357797.3hrs

connection timeout

trying connection 183.247.75.166:17500 lastseen=10.2hrs

connection timeout

trying connection 31.207.20.162:17500 lastseen=357797.3hrs

connection timeout

trying connection 60.241.208.1:17500 lastseen=3.6hrs

connected 60.241.208.1:17500

send version message: version 1040000, blocks=313854, us=210.186.159.34:17501, them=60.241.208.1:17500, peer=60.241.208.1:17500

connection timeout

trying connection 216.81.25.170:17500 lastseen=253.0hrs

accepted connection [2002:1804:2ddb:0:c195:34a:5355:95a0]:43375

socket recv error 10054

disconnecting node [2002:1804:2ddb:0:c195:34a:5355:95a0]:43375

trying connection 198.143.188.42:17500 lastseen=357797.3hrs

getblocks 140931 to 00000000000000000000 limit 500

getblocks stopping at limit 141430 0b1e17a3f5f28109e5b9

connection timeout

trying connection 98.151.191.57:17500 lastseen=8.3hrs

connection timeout

trying connection 113.162.188.201:17500 lastseen=357797.3hrs

connection timeout

trying connection 68.113.238.39:17500 lastseen=67.1hrs

connection timeout

trying connection 203.59.132.204:17500 lastseen=357797.3hrs

connection timeout

trying connection 62.210.131.147:17500 lastseen=52.5hrs

connection timeout

trying connection 86.22.130.144:17500 lastseen=357797.3hrs

accepted connection 86.210.169.134:65256

send version message: version 1040000, blocks=313854, us=210.186.159.34:17501, them=86.210.169.134:65256, peer=86.210.169.134:65256

Added time data, samples 58, offset +0 (+0 minutes)

receive version message: version 60001, blocks=318037, us=210.186.159.34:17500, them=86.210.169.134:17501, peer=86.210.169.134:65256

connection timeout

trying connection 95.174.98.224:17500 lastseen=6.0hrs

connection timeout

trying connection 59.167.189.49:17500 lastseen=357797.3hrs

Flushed 9703 addresses to peers.dat 35ms

connection timeout

trying connection 108.250.120.149:17500 lastseen=4.6hrs

connection timeout

trying connection 72.84.189.238:17500 lastseen=357797.3hrs

received block 8237f802e13d0b8e2407

SetBestChain: new best=8237f802e13d0b8e2407 height=313855 work=1113051528403998 date=12/26/13 15:02:49

ProcessBlock: ACCEPTED

getblocks -1 to 00000000000000000000 limit 500

getblocks 186141 to 985628d459e2e1220590 limit 500

getblocks stopping at limit 186640 1ea4a19abbafe5bca139

Flushing wallet.dat

Flushed wallet.dat 149ms

connection timeout

trying connection 128.71.224.143:17500 lastseen=35.7hrs

connection timeout

getblocks 43016 to 247be120b701ee36126f limit 500

getblocks stopping at limit 43515 ca8c5d3052d801299227

getblocks -1 to 00000000000000000000 limit 500

trying connection 85.217.147.117:17500 lastseen=357797.3hrs

received getdata for: block 8237f802e13d0b8e2407

connection timeout

getblocks 43140 to fb1e49e77d3adb8a4241 limit 500

getblocks stopping at 43216 fb1e49e77d3adb8a4241

trying connection 217.197.0.46:17500 lastseen=48.4hrs

connection timeout

connection timeout

trying connection 113.235.121.246:17500 lastseen=13.2hrs

CTxMemPool::accept() : accepted a9a49b89b4 (poolsz 1)

CTxMemPool::accept() : accepted f7f18e5ace (poolsz 2)

getblocks 186641 to 00000000000000000000 limit 500

getblocks stopping at limit 187140 e8ebb9050e680bf42874

received getdata for: tx a9a49b89b4283f336cd6

CTxMemPool::accept() : accepted 81859eafb4 (poolsz 3)

getblocks 34755 to 985628d459e2e1220590 limit 500

getblocks stopping at limit 35254 33a7fd76f516d63b9687

socket no message in first 60 seconds, 0 1

disconnecting node 192.222.136.171:17500

connection timeout

trying connection 95.97.59.146:17500 lastseen=2.9hrs

received getdata for: tx 81859eafb49f83c95457

getblocks 187141 to 00000000000000000000 limit 500

getblocks stopping at limit 187640 913eabc16ecb1887b4b4

connection timeout

trying connection 188.230.238.89:17500 lastseen=3.6hrs

socket no message in first 60 seconds, 0 1

disconnecting node 60.241.208.1:17500

connection timeout

trying connection 61.177.207.190:17500 lastseen=3.1hrs

getblocks 141431 to 00000000000000000000 limit 500

getblocks stopping at limit 141930 a5b622f7201a19c3ad04

connection timeout

trying connection 88.199.101.1:17500 lastseen=3.8hrs

connection timeout

trying connection 89.100.141.229:17500 lastseen=7.1hrs

connection timeout

trying connection 194.73.135.165:17500 lastseen=307.1hrs

connection timeout

trying connection 188.67.255.178:17500 lastseen=4.5hrs

accepted connection 50.71.153.7:64079

send version message: version 1040000, blocks=313855, us=210.186.159.34:17501, them=50.71.153.7:64079, peer=50.71.153.7:64079

Added time data, samples 59, offset -1 (+0 minutes)

nTimeOffset = -1 (+0 minutes)

receive version message: version 1040000, blocks=313855, us=210.186.159.34:17500, them=50.71.153.7:17500, peer=50.71.153.7:64079

connection timeout

trying connection 188.238.240.203:17500 lastseen=3.4hrs

socket recv error 10053

disconnecting node 184.70.2.74:11928

received block 6fcadea8334e252258ac

ProcessBlock: ORPHAN BLOCK, prev=ae9d8b8af377350d834d

connection timeout

trying connection 46.14.27.20:17500 lastseen=0.7hrs

received block fe39681f8993d260e1e8

nActualTimespan = 417 before bounds

GetNextWorkRequired RETARGET

nTargetTimespan = 600 nActualTimespan = 417

Before: 1c461778 0000000046177800000000000000000000000000000000000000000000000000

After: 1c30b6b5 0000000030b6b5f5c28f5c28f5c28f5c28f5c28f5c28f5c28f5c28f5c28f5c28

ERROR: AcceptBlock() : incorrect proof of work

ERROR: ProcessBlock() : AcceptBlock FAILED

disconnecting node 86.210.169.134:65256

Disconnected 86.210.169.134:65256 for misbehavior (score=100)

connection timeout

trying connection 108.180.221.104:17500 lastseen=2.5hrs

connection timeout

trying connection 14.107.34.75:17500 lastseen=3.0hrs

connection timeout

trying connection 116.25.102.62:17500 lastseen=0.8hrs

connection timeout

trying connection 86.74.107.62:17500 lastseen=310.6hrs

connection from 93.189.45.68:34521 dropped (banned)

connection timeout

trying connection 88.11.65.211:17500 lastseen=0.6hrs

Flushed 9703 addresses to peers.dat 54ms

connection timeout

trying connection 83.226.60.166:17500 lastseen=31.2hrs

connection from 67.6.71.244:62720 dropped (banned)

connection timeout

trying connection 173.21.154.211:17500 lastseen=0.2hrs

connected 173.21.154.211:17500

send version message: version 1040000, blocks=313855, us=210.186.159.34:17501, them=173.21.154.211:17500, peer=173.21.154.211:17500

trying connection 218.82.205.110:17500 lastseen=277.0hrs

connection timeout

trying connection 112.66.53.161:17500 lastseen=6.4hrs

connection timeout

trying connection 1.0.227.34:17500 lastseen=107.7hrs





Guys, is it just me or is the client intermittently trying to sync with the network (~4172 blocks remaining) but unable to update.In the meantime, I have some coins trapped in limbo because the client isn't syncing.Is this partly due to the hardfork??Here is the appended error file. (part of it)

artos



Offline



Activity: 84

Merit: 10





http://stablecoin.net







MemberActivity: 84Merit: 10http://stablecoin.net Re: [ANN][SBC] From Death Comes Life  The Rebirth of StableCoin - URGENT UPDATE December 26, 2013, 03:32:07 PM #1045 Quote from: cobrabyte on December 26, 2013, 01:39:33 PM I've have to wonder if we've reached the point where there *needs* to be more than one developer on this project.



@artos, it's obvious you still have shit going on in your life that keeps you from addressing issues with this coin. We're now into the third day of a situation where the difficulty is pegged... and will only rise. Your response: it's being monitored. There is nothing to monitor. We need a fix. It's a simple fix. It's a fix that's been posted here. It's a fix that's been committed via GitHub... it's a matter of merging code. It simply couldn't be any easier.



There are a lot of us that have a great deal of money invested in SBC and we're left thinking 'am I an idiot for thinking this guy will stick with the project... after having abandoned it already?'



Dude, what the hell can we do to help? This thing is dying here and YOU are responsible.

Had I merged your code, the blockchain would have been forked instantly, 1800 blocks in the past. Does that sound like an acceptable solution? The actual fix is an extremely simple one, and has been ready for days. I've been monitoring block generation trends so that I could set a reasonable point for the next fork to occur at. Hardforks are a delicate art, and screwing this part up would surely be the final nail in the coffin. Why are you all suggesting that we rush into it? Is 3 days of low mining rewards worth jeopardizing the coin over? I've gathered enough data, and the fork will occur at block 317,000. Had I merged your code, the blockchain would have been forked instantly, 1800 blocks in the past. Does that sound like an acceptable solution? The actual fix is an extremely simple one, and has been ready for days. I've been monitoring block generation trends so that I could set a reasonable point for the next fork to occur at. Hardforks are a delicate art, and screwing this part up would surely be the final nail in the coffin. Why are you all suggesting that we rush into it? Is 3 days of low mining rewards worth jeopardizing the coin over? I've gathered enough data, and the fork will occur at block

StableCoin Forums: StableCoin Development Fund: shQpTvLDsgCURkfqyBuCjL79aqYwti2FEJStableCoin Forums: http://forums.stablecoin.net

Catswold



Offline



Activity: 518

Merit: 251









Sr. MemberActivity: 518Merit: 251 Re: [ANN][SBC] From Death Comes Life  The Rebirth of StableCoin - URGENT UPDATE December 26, 2013, 03:43:21 PM

Last edit: December 26, 2013, 04:39:42 PM by Catswold #1047 Quote from: artos on December 26, 2013, 03:32:07 PM Quote from: cobrabyte on December 26, 2013, 01:39:33 PM I've have to wonder if we've reached the point where there *needs* to be more than one developer on this project.



@artos, it's obvious you still have shit going on in your life that keeps you from addressing issues with this coin. We're now into the third day of a situation where the difficulty is pegged... and will only rise. Your response: it's being monitored. There is nothing to monitor. We need a fix. It's a simple fix. It's a fix that's been posted here. It's a fix that's been committed via GitHub... it's a matter of merging code. It simply couldn't be any easier.



There are a lot of us that have a great deal of money invested in SBC and we're left thinking 'am I an idiot for thinking this guy will stick with the project... after having abandoned it already?'



Dude, what the hell can we do to help? This thing is dying here and YOU are responsible.

Had I merged your code, the blockchain would have been forked instantly, 1800 blocks in the past. Does that sound like an acceptable solution? The actual fix is an extremely simple one, and has been ready for days. I've been monitoring block generation trends so that I could set a reasonable point for the next fork to occur at. Hardforks are a delicate art, and screwing this part up would surely be the final nail in the coffin. Why are you all suggesting that we rush into it? Is 3 days of low mining rewards worth jeopardizing the coin over? I've gathered enough data, and the fork will occur at block 317,000.

Had I merged your code, the blockchain would have been forked instantly, 1800 blocks in the past. Does that sound like an acceptable solution? The actual fix is an extremely simple one, and has been ready for days. I've been monitoring block generation trends so that I could set a reasonable point for the next fork to occur at. Hardforks are a delicate art, and screwing this part up would surely be the final nail in the coffin. Why are you all suggesting that we rush into it? Is 3 days of low mining rewards worth jeopardizing the coin over? I've gathered enough data, and the fork will occur at block

Chill, artos, it's not about you, it's about the coin. Had you communicated this information, you would not have had the sort of reaction you see here. You say the fix has been ready for days, but you didn't inform us.



We need timely information, especially when things aren't going as expected. We all want this coin to succeed. We all have a vested interest in it succeeding, but when we don't hear anything for a couple of days, it leads to folks asking serious questions.



AS I said before. By choosing to create this coin and push it's development, you have taken on the additional burden of communicating with your base. Perhaps cobrabyte is correct, and you need some assistance in running the coin (preferably someone with plenty of knowledge and expertise. It appears there are some in this community with the knowledge to help.



Please give it some thought.



And thanks for the update. Chill, artos, it's not about you, it's about the coin. Had you communicated this information, you would not have had the sort of reaction you see here. You say the fix has been ready for days, but you didn't inform us.We need timely information, especially when things aren't going as expected. We all want this coin to succeed. We all have a vested interest in it succeeding, but when we don't hear anything for a couple of days, it leads to folks asking serious questions.AS I said before. By choosing to create this coin and push it's development, you have taken on the additional burden of communicating with your base. Perhaps cobrabyte is correct, and you need some assistance in running the coin (preferably someone with plenty of knowledge and expertise. It appears there are some in this community with the knowledge to help.Please give it some thought.And thanks for the update.

colonelmustard



Offline



Activity: 35

Merit: 0







NewbieActivity: 35Merit: 0 Re: [ANN][SBC] From Death Comes Life  The Rebirth of StableCoin - URGENT UPDATE December 26, 2013, 03:48:20 PM #1050







Quote from: colonelmustard on December 26, 2013, 03:07:18 PM



In the meantime, I have some coins trapped in limbo because the client isn't syncing.



Is this partly due to the hardfork??





Here is the appended error file. (part of it)





Code:

trying connection 58.183.127.170:17500 lastseen=60.0hrs

connection timeout

trying connection 203.59.132.204:17500 lastseen=357797.2hrs

connection timeout

trying connection 93.212.196.180:17500 lastseen=22.4hrs

UPnP Port Mapping successful.

Flushed 9703 addresses to peers.dat 39ms

connection timeout

trying connection 86.22.130.144:17500 lastseen=357797.2hrs

Added time data, samples 54, offset -2 (+0 minutes)

receive version message: version 60001, blocks=318030, us=210.186.159.34:62418, them=62.194.165.209:17500, peer=62.194.165.209:17500

getblocks 309830 to f0a479c43d2061b64b1b limit 500

getblocks stopping at limit 310329 c8162a3a1e91022aa797

received block cada1293915e45b7a712

ProcessBlock: ORPHAN BLOCK, prev=7824c12b433227710f1a

received block e088325bdb574665e5bf

ProcessBlock: ORPHAN BLOCK, prev=cada1293915e45b7a712

ERROR: FetchInputs() : a2fed928ce mempool Tx prev not found 8b0d95521f

stored orphan tx a2fed928ce (mapsz 11)

received block 8751124d6619787f1ec4

ProcessBlock: ORPHAN BLOCK, prev=e088325bdb574665e5bf

connection timeout

getblocks 310330 to 00000000000000000000 limit 500

getblocks stopping at limit 310829 4a7dd8ca9f2ba0cd9f9d

received block fe39681f8993d260e1e8

nActualTimespan = 417 before bounds

GetNextWorkRequired RETARGET

nTargetTimespan = 600 nActualTimespan = 417

Before: 1c461778 0000000046177800000000000000000000000000000000000000000000000000

After: 1c30b6b5 0000000030b6b5f5c28f5c28f5c28f5c28f5c28f5c28f5c28f5c28f5c28f5c28

ERROR: AcceptBlock() : incorrect proof of work

ERROR: ProcessBlock() : AcceptBlock FAILED

disconnecting node 62.194.165.209:17500

Disconnected 62.194.165.209:17500 for misbehavior (score=100)

trying connection 108.9.45.178:17500 lastseen=2.6hrs

connected 108.9.45.178:17500

send version message: version 1040000, blocks=313853, us=210.186.159.34:17501, them=108.9.45.178:17500, peer=108.9.45.178:17500

trying connection 98.208.236.116:17500 lastseen=19.3hrs

connection timeout

trying connection 59.167.189.49:17500 lastseen=357797.2hrs

received getdata (2 invsz)

connection timeout

trying connection 71.85.220.167:17500 lastseen=707.6hrs

connection timeout

trying connection 72.84.189.238:17500 lastseen=357797.2hrs

connection timeout

trying connection 71.21.140.83:17500 lastseen=45.6hrs

connection timeout

trying connection 85.217.147.117:17500 lastseen=357797.2hrs

socket no message in first 60 seconds, 0 1

disconnecting node 190.174.9.158:17500

connection timeout

trying connection 211.137.20.208:17500 lastseen=11.6hrs

connection timeout

accepted connection 75.155.136.206:58414

send version message: version 1040000, blocks=313853, us=210.186.159.34:17501, them=75.155.136.206:58414, peer=75.155.136.206:58414

Added time data, samples 55, offset -19 (+0 minutes)

nTimeOffset = -2 (+0 minutes)

receive version message: version 60001, blocks=318030, us=210.186.159.34:17500, them=75.155.136.206:17500, peer=75.155.136.206:58414

getblocks 38616 to ba7723d78bffa1791425 limit 500

getblocks stopping at 38891 ba7723d78bffa1791425

connection timeout

trying connection 70.134.73.115:17500 lastseen=6.9hrs

connection timeout

trying connection 193.110.115.124:17500 lastseen=41.8hrs

received block 3abcba6988fc5238b712

SetBestChain: new best=3abcba6988fc5238b712 height=313854 work=1113018976110540 date=12/26/13 15:00:17

ProcessBlock: ACCEPTED

getblocks -1 to 00000000000000000000 limit 500

getblocks -1 to 00000000000000000000 limit 500

getblocks -1 to 00000000000000000000 limit 500

getblocks 38616 to 247be120b701ee36126f limit 500

getblocks stopping at limit 39115 8808075afb1ade0b75ac

getblocks -1 to 00000000000000000000 limit 500

getblocks -1 to 00000000000000000000 limit 500

Flushing wallet.dat

Flushed wallet.dat 159ms

connection timeout

trying connection 98.168.188.82:17500 lastseen=6.2hrs

socket no message in first 60 seconds, 0 1

disconnecting node 5.69.63.209:17500

connection timeout

trying connection 75.171.141.140:17500 lastseen=0.7hrs

connected 75.171.141.140:17500

send version message: version 1040000, blocks=313854, us=210.186.159.34:17501, them=75.171.141.140:17500, peer=75.171.141.140:17500

trying connection 46.14.27.20:17500 lastseen=0.6hrs

received block 5697ddc6e3e01a3927ff

ProcessBlock: ORPHAN BLOCK, prev=8751124d6619787f1ec4

connection timeout

trying connection 206.248.184.174:17500 lastseen=3.9hrs

received block 2715478a7810832d8269

ProcessBlock: ORPHAN BLOCK, prev=6f90eed2523d0ffed6fd

accepted connection 192.222.136.171:57320

send version message: version 1040000, blocks=313854, us=210.186.159.34:17501, them=192.222.136.171:57320, peer=192.222.136.171:57320

Added time data, samples 56, offset +6 (+0 minutes)

receive version message: version 1040000, blocks=313854, us=210.186.159.34:17500, them=192.222.136.171:17501, peer=192.222.136.171:57320

connection timeout

trying connection [2001:0:9d38:6abd:140d:1f57:47c4:21cb]:17500 lastseen=0.6hrs

connected [2001:0:9d38:6abd:140d:1f57:47c4:21cb]:17500

send version message: version 1040000, blocks=313854, us=210.186.159.34:17501, them=[2001:0:9d38:6abd:140d:1f57:47c4:21cb]:17500, peer=[2001:0:9d38:6abd:140d:1f57:47c4:21cb]:17500

trying connection 83.236.208.138:17500 lastseen=2.7hrs

connection timeout

trying connection 67.183.126.156:17500 lastseen=2.1hrs

socket no message in first 60 seconds, 0 1

disconnecting node 108.9.45.178:17500

received block 2fdcdefccc1a06a6ed32

ProcessBlock: ORPHAN BLOCK, prev=5697ddc6e3e01a3927ff

connection timeout

trying connection 78.148.123.143:17500 lastseen=53.8hrs

getblocks 139931 to 985628d459e2e1220590 limit 500

getblocks stopping at limit 140430 dc248feec2697c6eb6a7

connection timeout

trying connection 50.102.222.206:17500 lastseen=3.4hrs

connection timeout

trying connection [2001:0:9d38:90d7:202f:fbff:91a5:7073]:17500 lastseen=5.8hrs

received block 138db4ff0b2961073561

ProcessBlock: ORPHAN BLOCK, prev=2fdcdefccc1a06a6ed32

connection timeout

getblocks 34255 to 985628d459e2e1220590 limit 500

getblocks stopping at limit 34754 057b80d99859588bec3f

received getdata for: block 3abcba6988fc5238b712

trying connection 87.117.50.114:17500 lastseen=54.0hrs

received block d2f085e8ee3eb167fd9c

ProcessBlock: ORPHAN BLOCK, prev=138db4ff0b2961073561

connection timeout

trying connection 178.4.211.145:17500 lastseen=29.4hrs

connection timeout

trying connection 24.39.226.146:17500 lastseen=6.0hrs

Flushed 9703 addresses to peers.dat 66ms

connection timeout

trying connection 78.148.234.156:17500 lastseen=20.5hrs

Added 1 addresses from 86.3.86.71: 687 tried, 9016 new

socket recv error 10054

disconnecting node 75.171.141.140:17500

connection timeout

trying connection 217.67.117.210:17500 lastseen=389.0hrs

connection timeout

trying connection 88.223.2.162:17500 lastseen=2.7hrs

socket recv error 10054

disconnecting node 192.222.136.171:57320

received block a298d10677a040569d43

ProcessBlock: ORPHAN BLOCK, prev=d2f085e8ee3eb167fd9c

getblocks 140431 to 00000000000000000000 limit 500

getblocks stopping at limit 140930 74b38e85ccaa302b773c

connection timeout

socket no message in first 60 seconds, 0 1

disconnecting node [2001:0:9d38:6abd:140d:1f57:47c4:21cb]:17500

trying connection 124.197.25.116:17500 lastseen=6.3hrs

received block fe39681f8993d260e1e8

nActualTimespan = 417 before bounds

GetNextWorkRequired RETARGET

nTargetTimespan = 600 nActualTimespan = 417

Before: 1c461778 0000000046177800000000000000000000000000000000000000000000000000

After: 1c30b6b5 0000000030b6b5f5c28f5c28f5c28f5c28f5c28f5c28f5c28f5c28f5c28f5c28

ERROR: AcceptBlock() : incorrect proof of work

ERROR: ProcessBlock() : AcceptBlock FAILED

disconnecting node 75.155.136.206:58414

Disconnected 75.155.136.206:58414 for misbehavior (score=100)

connection timeout

trying connection 62.243.86.200:17500 lastseen=137.5hrs

accepted connection 83.145.61.116:56811

send version message: version 1040000, blocks=313854, us=210.186.159.34:17501, them=83.145.61.116:56811, peer=83.145.61.116:56811

Added time data, samples 57, offset -9 (+0 minutes)

nTimeOffset = -2 (+0 minutes)

Moving 83.145.61.116:17500 to tried

receive version message: version 1040000, blocks=313854, us=210.186.159.34:17500, them=83.145.61.116:17500, peer=83.145.61.116:56811

connection timeout

trying connection 125.78.10.154:17500 lastseen=62.0hrs

connection timeout

trying connection 75.176.14.241:17500 lastseen=29.8hrs

connection timeout

trying connection 67.81.32.177:17500 lastseen=11.6hrs

trying connection 108.186.237.29:17500 lastseen=357797.3hrs

connection timeout

trying connection 84.106.217.238:17500 lastseen=7.5hrs

connection timeout

trying connection 109.121.82.231:17500 lastseen=357797.3hrs

connection timeout

trying connection 199.119.140.197:17500 lastseen=8.0hrs

connection timeout

trying connection 184.171.221.204:17500 lastseen=357797.3hrs

connection timeout

trying connection 124.150.25.211:17500 lastseen=90.1hrs

connection timeout

trying connection 109.80.94.251:17500 lastseen=357797.3hrs

connection timeout

trying connection 192.222.136.171:17500 lastseen=3.7hrs

connected 192.222.136.171:17500

send version message: version 1040000, blocks=313854, us=210.186.159.34:17501, them=192.222.136.171:17500, peer=192.222.136.171:17500

trying connection 118.113.168.33:17500 lastseen=11.3hrs

connection timeout

trying connection 93.138.167.14:17500 lastseen=357797.3hrs

connection timeout

trying connection 183.247.75.166:17500 lastseen=10.2hrs

connection timeout

trying connection 31.207.20.162:17500 lastseen=357797.3hrs

connection timeout

trying connection 60.241.208.1:17500 lastseen=3.6hrs

connected 60.241.208.1:17500

send version message: version 1040000, blocks=313854, us=210.186.159.34:17501, them=60.241.208.1:17500, peer=60.241.208.1:17500

connection timeout

trying connection 216.81.25.170:17500 lastseen=253.0hrs

accepted connection [2002:1804:2ddb:0:c195:34a:5355:95a0]:43375

socket recv error 10054

disconnecting node [2002:1804:2ddb:0:c195:34a:5355:95a0]:43375

trying connection 198.143.188.42:17500 lastseen=357797.3hrs

getblocks 140931 to 00000000000000000000 limit 500

getblocks stopping at limit 141430 0b1e17a3f5f28109e5b9

connection timeout

trying connection 98.151.191.57:17500 lastseen=8.3hrs

connection timeout

trying connection 113.162.188.201:17500 lastseen=357797.3hrs

connection timeout

trying connection 68.113.238.39:17500 lastseen=67.1hrs

connection timeout

trying connection 203.59.132.204:17500 lastseen=357797.3hrs

connection timeout

trying connection 62.210.131.147:17500 lastseen=52.5hrs

connection timeout

trying connection 86.22.130.144:17500 lastseen=357797.3hrs

accepted connection 86.210.169.134:65256

send version message: version 1040000, blocks=313854, us=210.186.159.34:17501, them=86.210.169.134:65256, peer=86.210.169.134:65256

Added time data, samples 58, offset +0 (+0 minutes)

receive version message: version 60001, blocks=318037, us=210.186.159.34:17500, them=86.210.169.134:17501, peer=86.210.169.134:65256

connection timeout

trying connection 95.174.98.224:17500 lastseen=6.0hrs

connection timeout

trying connection 59.167.189.49:17500 lastseen=357797.3hrs

Flushed 9703 addresses to peers.dat 35ms

connection timeout

trying connection 108.250.120.149:17500 lastseen=4.6hrs

connection timeout

trying connection 72.84.189.238:17500 lastseen=357797.3hrs

received block 8237f802e13d0b8e2407

SetBestChain: new best=8237f802e13d0b8e2407 height=313855 work=1113051528403998 date=12/26/13 15:02:49

ProcessBlock: ACCEPTED

getblocks -1 to 00000000000000000000 limit 500

getblocks 186141 to 985628d459e2e1220590 limit 500

getblocks stopping at limit 186640 1ea4a19abbafe5bca139

Flushing wallet.dat

Flushed wallet.dat 149ms

connection timeout

trying connection 128.71.224.143:17500 lastseen=35.7hrs

connection timeout

getblocks 43016 to 247be120b701ee36126f limit 500

getblocks stopping at limit 43515 ca8c5d3052d801299227

getblocks -1 to 00000000000000000000 limit 500

trying connection 85.217.147.117:17500 lastseen=357797.3hrs

received getdata for: block 8237f802e13d0b8e2407

connection timeout

getblocks 43140 to fb1e49e77d3adb8a4241 limit 500

getblocks stopping at 43216 fb1e49e77d3adb8a4241

trying connection 217.197.0.46:17500 lastseen=48.4hrs

connection timeout

connection timeout

trying connection 113.235.121.246:17500 lastseen=13.2hrs

CTxMemPool::accept() : accepted a9a49b89b4 (poolsz 1)

CTxMemPool::accept() : accepted f7f18e5ace (poolsz 2)

getblocks 186641 to 00000000000000000000 limit 500

getblocks stopping at limit 187140 e8ebb9050e680bf42874

received getdata for: tx a9a49b89b4283f336cd6

CTxMemPool::accept() : accepted 81859eafb4 (poolsz 3)

getblocks 34755 to 985628d459e2e1220590 limit 500

getblocks stopping at limit 35254 33a7fd76f516d63b9687

socket no message in first 60 seconds, 0 1

disconnecting node 192.222.136.171:17500

connection timeout

trying connection 95.97.59.146:17500 lastseen=2.9hrs

received getdata for: tx 81859eafb49f83c95457

getblocks 187141 to 00000000000000000000 limit 500

getblocks stopping at limit 187640 913eabc16ecb1887b4b4

connection timeout

trying connection 188.230.238.89:17500 lastseen=3.6hrs

socket no message in first 60 seconds, 0 1

disconnecting node 60.241.208.1:17500

connection timeout

trying connection 61.177.207.190:17500 lastseen=3.1hrs

getblocks 141431 to 00000000000000000000 limit 500

getblocks stopping at limit 141930 a5b622f7201a19c3ad04

connection timeout

trying connection 88.199.101.1:17500 lastseen=3.8hrs

connection timeout

trying connection 89.100.141.229:17500 lastseen=7.1hrs

connection timeout

trying connection 194.73.135.165:17500 lastseen=307.1hrs

connection timeout

trying connection 188.67.255.178:17500 lastseen=4.5hrs

accepted connection 50.71.153.7:64079

send version message: version 1040000, blocks=313855, us=210.186.159.34:17501, them=50.71.153.7:64079, peer=50.71.153.7:64079

Added time data, samples 59, offset -1 (+0 minutes)

nTimeOffset = -1 (+0 minutes)

receive version message: version 1040000, blocks=313855, us=210.186.159.34:17500, them=50.71.153.7:17500, peer=50.71.153.7:64079

connection timeout

trying connection 188.238.240.203:17500 lastseen=3.4hrs

socket recv error 10053

disconnecting node 184.70.2.74:11928

received block 6fcadea8334e252258ac

ProcessBlock: ORPHAN BLOCK, prev=ae9d8b8af377350d834d

connection timeout

trying connection 46.14.27.20:17500 lastseen=0.7hrs

received block fe39681f8993d260e1e8

nActualTimespan = 417 before bounds

GetNextWorkRequired RETARGET

nTargetTimespan = 600 nActualTimespan = 417

Before: 1c461778 0000000046177800000000000000000000000000000000000000000000000000

After: 1c30b6b5 0000000030b6b5f5c28f5c28f5c28f5c28f5c28f5c28f5c28f5c28f5c28f5c28

ERROR: AcceptBlock() : incorrect proof of work

ERROR: ProcessBlock() : AcceptBlock FAILED

disconnecting node 86.210.169.134:65256

Disconnected 86.210.169.134:65256 for misbehavior (score=100)

connection timeout

trying connection 108.180.221.104:17500 lastseen=2.5hrs

connection timeout

trying connection 14.107.34.75:17500 lastseen=3.0hrs

connection timeout

trying connection 116.25.102.62:17500 lastseen=0.8hrs

connection timeout

trying connection 86.74.107.62:17500 lastseen=310.6hrs

connection from 93.189.45.68:34521 dropped (banned)

connection timeout

trying connection 88.11.65.211:17500 lastseen=0.6hrs

Flushed 9703 addresses to peers.dat 54ms

connection timeout

trying connection 83.226.60.166:17500 lastseen=31.2hrs

connection from 67.6.71.244:62720 dropped (banned)

connection timeout

trying connection 173.21.154.211:17500 lastseen=0.2hrs

connected 173.21.154.211:17500

send version message: version 1040000, blocks=313855, us=210.186.159.34:17501, them=173.21.154.211:17500, peer=173.21.154.211:17500

trying connection 218.82.205.110:17500 lastseen=277.0hrs

connection timeout

trying connection 112.66.53.161:17500 lastseen=6.4hrs

connection timeout

trying connection 1.0.227.34:17500 lastseen=107.7hrs







Guys, is it just me or is the client intermittently trying to sync with the network (~4172 blocks remaining) but unable to update.In the meantime, I have some coins trapped in limbo because the client isn't syncing.Is this partly due to the hardfork??Here is the appended error file. (part of it) Upgraded to version 1.5, coins still missing and not syncing properly with network....

Ch3rub



Offline



Activity: 64

Merit: 10







MemberActivity: 64Merit: 10 Re: [ANN][SBC] From Death Comes Life  The Rebirth of StableCoin - URGENT UPDATE December 26, 2013, 04:05:20 PM #1052



The sad truth is there are still pools running on the wrong "prior to 1.4" chain out there with quite a few people mining completely worthless shares One I have in mind doesn't even have contact details for the pool owner.



Another fork now, while necessary and I understand that, will add to the overall confusion



Thanks for the update artos I've passed the news to http://sbc.nordicminers.eu The sad truth is there are still pools running on the wrong "prior to 1.4" chain out there with quite a few people mining completely worthless sharesOne I have in mind doesn't even have contact details for the pool owner.Another fork now, while necessary and I understand that, will add to the overall confusionThanks for the update artos

artos



Offline



Activity: 84

Merit: 10





http://stablecoin.net







MemberActivity: 84Merit: 10http://stablecoin.net Re: [ANN][SBC] From Death Comes Life  The Rebirth of StableCoin - URGENT UPDATE December 26, 2013, 04:11:05 PM

Last edit: December 26, 2013, 04:45:36 PM by artos #1053



https://bitcointalk.org/index.php?topic=386035.new#new



Quote from: Catswold on December 26, 2013, 03:43:21 PM Chill, artos, it's not about you, it's about the coin. Had you communicated this information, you would not have had the sort of reaction you see here. You say the fix has been ready for days, but you didn't inform us.



We need timely information, especially when things aren't going as expected. We all want this coin to succeed. We all have a vested interest in it succeeding, but when we don't here anything for a couple of days, it leads to folks asking serious questions.



AS I said before. By choosing to create this coin and push it's development, you have taken on the additional burden of communicating with you base. Perhaps cobrabyte is correct, and you need some assistance in running the coin (preferably someone with plenty of knowledge and expertise. It appears there are some in this community with the knowledge to help.



Please give it some thought.



And thanks for the update.

There's been a lot of unnecessary personal attacks, even though I am just as concerned with the success of this coin as any of you are. This thread feels like a witch hunt in recent days. I've posted both in this thread and on the official forums that a fix was forthcoming.



For the curious, the issue was related to integer rounding. Shifting around the parenthesis is all that needs to be done.



nActualTimespanMax = nTargetTimespan * (112/100) <- This rounds to 1

nActualTimespanMin = nTargetTimespan * (100/111) <- This rounds to 0



Fixed:



nActualTimespanMax = (nTargetTimespan * 112) / 100

nActualTimespanMin = (nTargetTimespan * 100) / 111 Made an announcement thread for this update. Try to keep it on page 1.There's been a lot of unnecessary personal attacks, even though I am just as concerned with the success of this coin as any of you are. This thread feels like a witch hunt in recent days. I've posted both in this thread and on the official forums that a fix was forthcoming.For the curious, the issue was related to integer rounding. Shifting around the parenthesis is all that needs to be done.nActualTimespanMax = nTargetTimespan * (112/100)

StableCoin Forums: StableCoin Development Fund: shQpTvLDsgCURkfqyBuCjL79aqYwti2FEJStableCoin Forums: http://forums.stablecoin.net