|
Development on the mixing service continues. The beta signup post was not meant to imply that it is near completion, but rather to preemptively collect a list of interested individuals, as well as to spark interest among new people in the coin itself.
I pop on here and the official forum from time to time, but that is just to check up and make sure the network is running properly. If you folks want daily updates, there isn't much for me to say. I'm just living my life and working on this when I have the spare time. It's really not that interesting. My time is limited, so I don't have the availability to do daily Q&A sessions on here and respond to some of the long messages that I receive.
There's been some talk of others wanting to implement their own mixing service. If you think you can beat me to the punch, and that your finished product is of sufficient quality, feel free to go for it. I won't take offense, and your code will be implemented into the main branch. I would share what I have completed so far, but that would not be wise, as it could get into the hands of a competitor coin. Our development paths will have to remain separate.
|
|
|
|
This thread will be used to collect a list of individuals who are interested in beta testing the mixing feature of StableCoin when it is ready. The following positions will be available: Client tester: You will be testing the new client that will be used to facilitate the mixing service. Testing will be conducted on a new client that uses a different block chain. No technical expertise needed. Node tester: You will deploy a mixing and broadcast node using our custom software. Knowledge of setting up a linux based server that functions on the TOR network is mandatory. You will also assume all costs related to the operation of these servers. Security tester: Your job will be to test the protocol and it's network functions for vulnerabilities, specifically those that compromise privacy. Knowledge of penetration testing will be helpful here. For all positions, compensation will be available for those who assist in finding/fixing bugs. When posting, please list what position(s) you are interested in. More info on the mixing service: https://bitcointalk.org/index.php?topic=353971.0 |
|
|
|
Disappear for a week and everybody is ready to tar and feather you... I just returned from a business trip to Japan. Found some free time to climb Mt Fuji and relax in the Hakone hot spring. Sometimes it's nice to disconnect yourself from everything. Anyway... StableCoin 1.5 Mac and Ubuntu wallets are now available. Mac: https://mega.co.nz/#!0AY3FQbb!T5wdjVvp3oDfr9Ucun4Dw2JaF0wePwP5xy50meuwn9k Ubuntu: https://mega.co.nz/#!zZEzHTzA!CvWvM1c32nmOb6yNU_YI1XqfrN83l2Mz7X_k5D6_Yfk As a bonus, either later today or tomorrow I will be making a post to collect a list of individuals interested in beta testing the mixing service. |
|
|
|
|
Pull requests are welcome, yes. I do not mean to come off as condescending, I'm just slightly miffed at how impatient everyone is being about this whole situation. Hardforks like this are a logistical issue, not a technical issue.
There was nothing wrong with what you submitted; it would have worked fine with a few tweaks. It's just that I had the code already done way you before you even submitted it. I was just waiting to figure out what block number to have the fork happen at.
|
|
|
|
Made an announcement thread for this update. Try to keep it on page 1. https://bitcointalk.org/index.php?topic=386035.new#newChill, 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 |
|
|
|
RELEASE - VERSION 1.5This is a mandatory update before block 317000, approximately 5 days from now. The update consists of the following changes: *Difficulty algorithm fixed. It now properly retargets every 10 blocks, with a maximum of 12% down, or 10% up. PLEASE INFORM YOUR MINING POOLS, EXCHANGES, BLOCK EXPLORER, ETC ABOUT THIS UPDATE.I will do my best to do this myself, but the more people spreading the word, the better. Last time, with 2 weeks noticed, we still had pools that failed to upgrade. Now, with only 5 days notice, it's imperative that everyone updates ASAP. DOWNLOADWindows Client: https://github.com/stablecoin/stablecoin-qt/archive/master.zipMac Client: Coming Soon Source: https://github.com/stablecoin/StableCoin
|
|
|
|
RELEASE - VERSION 1.5This is a mandatory update before block 317000, approximately 5 days from now. The update consists of the following changes: *Difficulty algorithm fixed. It now properly retargets every 10 blocks, with a maximum of 12% down, or 10% up. PLEASE INFORM YOUR MINING POOLS, EXCHANGES, BLOCK EXPLORER, ETC ABOUT THIS UPDATE.I will do my best to do this myself, but the more people spreading the word, the better. Last time, with 2 weeks noticed, we still had pools that failed to upgrade. Now, with only 5 days notice, it's imperative that everyone updates ASAP. DOWNLOADWindows Client: https://github.com/stablecoin/stablecoin-qt/archive/master.zipMac Client: Coming Soon Source: https://github.com/stablecoin/StableCoin
|
|
|
|
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. |
|
|
|
Of course there was a fork. That's when the new difficulty algorithm switched on. http://sbc.blockexplorer.io/ is the correct chain. However, there's a bug in the new algorithm causing the difficulty to be pegged at 5.255, so a fix for that will be issued tomorrow. |
|
|
|
|
The mixing service will come when it's ready. There's a lot to tackle on not only on the developmental side, but also with testing and deployment. I also have to deal with promotion, management, and a multitude of other things associated with the coin in general. I encourage you to get involved in these things if you want to see the coin grow faster.
The only hard timeline is to have it ready before nightmares like CoinValidation become a reality.
|
|
|
|
Website has been fixed; should no longer cause weird scrolling issues on mobile. 125 SBC has been spent from the development fund for the French translation: http://stablecoin.net/fr |
|
|
|
Anyone know why stablecoin price is falling so fast?
I'm more concerned with long term prospects rather than short term price fluctuations. If you're looking for a pump and dump coin, you're in the wrong place. Having said that, those who are selling off now will likely regret it in the not too distant future. |
|
|
|
Somebody please explain to me what a paper wallet is in contrast to the qt wallets I have on my computer.
Thanks.
It's exactly as it sounds. Your private key is stored on a piece of paper rather than on a computer. It's a more secure way of storing coins. |
|
|
|
|
Show Posts
