Just an FYI...

We've shutdown the StableCoin blockexplorer at SBC.BlockExplorer.io.

This may affect the SBC network but, without an active developer, we're wasting resources by supporting what appears to be a dead coin.

We're glad to have been able to support the coin through the years but it's time to call it... StableCoin is dead.

Received tracking info and package is on the way! Thanks for the help.

I've sent a couple emails to the support email address and haven't heard anything back so here goes...

Order #5331 placed on 5/22... haven't received it though it's shown as 'fulfilled.' No tracking information was sent to me, as was promised.

Can I get someone to look up my order and tell me what's going on? Trying to avoid a chargeback at this point.

^- people like you are why we have 'ignore' functionality in forums. thanks for reminding me.

Guys/gals... thinking about shutting down the block explorer @ sbc.blockexplorer.io.

I'm not alone in thinking @artos has singlehandedly birthed and doomed this coin. The best hope for this coin is also its worst enemy.

Having mined LTC and a select few other 'alt coins' for years, I had high hopes for this coin -- even following the inexplicable disappearance and return of @artos from God knows where...

The market value of the coin has dropped many fold and the perceived value has hit rock bottom. Many of us stuck with the coin through the hard times due to the announcement of a ground-breaking privacy angle (mixing service) that would help set the coin apart from the sea of virtual copy-coins.

I've given up hope. Where is @artos? Where is the plan? Where is the mixing service? I guess it doesn't matter because "we've" been beaten to the punch.

Stablecoin *is* 1.5

Node / client tester. Thanks.

Thanks for the update, @artos. I think I speak for everyone when I say that I'm excited for the mixing service. It'll certainly set this coin apart from the endless slew of clone coins. Seems like there's 2 new coins a day. Getting nuts.

Just a heads-up... we're experiencing segfaults on the SBC.BlockExplorer.io block explorer pretty much at a 1 minute interval. Monit is restarting the Abe process lickety-split but I understand that it may be annoying to keep seeing an error page.

It appears to be an issue with API calls and I may have to disable all API access until we can get it sorted out. This will allow web visitors to use the system but you won't be able to use the API to power your coin tools. I don't think Abe was ever meant to directly serve over 1 request per second and it doesn't support a good caching strategy.

I'm going to put out a project proposal for someone to port Abe to a more performant framework/language (NodeJS, Golang, etc). The Abe codebase is a beast, so we'll focus on easily-maintainable code and, above all, generally error-free operation.

Again, sorry about the errors but we'll push ahead.

EDIT: Upgraded all PostgreSQL-related bits and the segfaults have appeared to stop. We'll keep monitoring it but we've re-enabled all API calls, in the mean time.

Just a heads-up... your difficulty estimator is using the old retarget formula (90 blocks). New retarget interval is every 10 blocks.

New target is a 60-second block time. So, 1440 * 25... or ~36,000 SBC. Obviously, this is just a target and doesn't include the transaction fees that may be added to a particular block.

Really glad @artos was here to ensure everything went well... 

Nice, we're back in business.

Over the hump.

Should retarget at block 317010...

Bump. If you haven't updated your StableCoin client to v1.5, you're about to be left behind. The scheduled fork is scheduled to occur in ~250 blocks @ 317,000.

This should occur within the next 8 to 10 hours. I suspect there will be some extra hashing power jumping on nearer to the fork point so that miners can build their round shares for maximum payout potential on the other side of the fork.

This could actually be a feature that sits alongside the mixing service. @artos can sign (with his private key) a checkpoint-like message that's included in newer releases to inform older clients about upcoming, planned forks. Every client that supports the mixing service will have the public key that can be used to determine whether a received checkpoint message is authentic. So, when clients advertise their version information, they might include (encrypted) information about a known, upcoming fork.

Dunno, just an idea.

EDIT: Actually, I read through the Bitcoin protocol docs and found the 'alert' message (see: https://en.bitcoin.it/wiki/Protocol_specification#alert) that can be propagated across the network by @artos. It appears he needs to change the Bitcoin ECDSA pubkey that's set in the source code to his own ECDSA pubkey to make use of it. It's intended to be used to send messages about upcoming forks and it appears it will even communicate these messages to the GUI client's status bar. Cool feature that shows some insight from the BTC developers.

Block explorer : http://sbc.blockexplorer.io/chain/Stablecoin

also, you can use this block explorer as a node:

addnode=66.228.60.13

I have it set as primary in all of my stablecoin.conf files and it's guaranteed to be on latest stablecoind.

Everything above the 25 SBC (+ fees) are actual transactions. 25 SBC is generated every block and that goes to the miner.

You'll see the first line in a block is something like 'Generation: 25 + 0.2 total fees'

Think it's going to take a few more days. The network hash rate is hovering around 90Mh/s. I just threw another 4Mh/s at it to help get over the hump. If you can spare the miners, do it... let's get this thing rocking again.

StableCoin wallet has been updated (v1.5) : https://bitcointalk.org/index.php?topic=349198.msg4230247#msg4230247

Oh, and thanks for this thread! Sent some BTC via Cryptsy trade key.