I understand the frustration you are feeling unfortunately I have had some family stuff come up. The updated and rebranded windows qt has been build I am waiting for help with the mac build. I have been working on the relay support in wallet and the tor browser. I have been working on them when I can.
I understand ya'll feel I should be more vocal in here and I will try to do that again.

Thank you for your inquiries.

You are correct in that there exists no certifier's certifier for cryptocurrencies. This field is still new, so we must acknowledge that no higher authority certifies our services. However, we did submit to an identification process both with the State of Washington and with Comodo. Essentially they certify our identity. However, as you point out, no one certifies our technical knowledge with respect to cryptocurrencies. If you know of such a certifying authority, we would be grateful if you could point us to it.

We think that this fact is reflected in our pricing, which for the moment is only 0.4 BTC for a Deployment or Launch Certificate. These certifications are the highest levels we offer. A Deployment Certificate, for example, certifies that we have determined from legal documents supplied to us that a developer has the identity they claim. For this certificate, we also look at the source code for any potentially malicious behavior. We further inspect the code to ensure that its behavior complies with specifications provided to us by the developer. We also ensure that the specifications reported to us are faithfully reported at the bitcointalk announcement and coin website, if it exists. Finally, we build and test the code to make sure the behavior conforms to our expectations with respect to coin emssion. If the coin is an ICO, we monitor the behavior of the live block chain during the ICO as well. We sign these builds, which the developer may and should distribute. We only provide signed builds when the ICO is nearly complete, to give us the maximum amount of time to observe the behavior of the live block chain.

If a coin has a CryptoCertify Launch Certificate or Deployment Certificate, then the Windows and OS X builds will bear our cryptographic signature. This signature helps protect the user. If the user does not see evidence of the signature upon starting the program, the user should not use the build.



Finally, because cryptocurrencies are new, we hope to let the public be our certifiers in the absence of a centralized authority. We aim to build our reputation and brand by carefully inspecting the coins and developers we certify. Again, we feel like this lack of a higher certifying authority is reflected in our pricing. But please feel free to link back to this post as proof that no higher certifying authority certifies our services. We fully acknowledge your concern and absolutely do not want to appear that we misrepresent this fact in any way.

Re the release, The source Has been committed to git for a while
I just have been having some issues with my qt 5 environment keeping me from building properly.

I have said it before, and I can say it again. If someone wants to help, by all means they can. I have never been opposed to this. Im usually available on irc in #soniccoin amongst other things. If I dont respond just pm me and I will get back when i can

That is the plan, but unfortunately there are other things in the work currently. SO unless you want to tackle that aspect of the project, or pay for someone to do it, we stay with the form coming out.

Feel free to join the irc. I can help you if I know what the error is. I have it running on 14.04 so I know it works...

you should check the source. This has been done on each revision. There is a bug with the way the clients passes this information on to eachother.
I have not had a chance as of yet to take a look at the ban code and figure out why it isnt working.

As you can see here https://github.com/SonicScrew/SonicScrewdriver/commits/master/src/version.h I have been doing this all along.

Unfortunately I havent had the time to work out a fix to block old peers, The versions you are seeing though are probably new test versions. i have been working on them for a while now and have gone through 2 revisions sofar

close it and open it back up. there are old wallets out there that send bad blocks according to the new wallet. There is a clash at some very specific points in the chain. The best thing to do is close the wallet and open it back up again. You will see the chain start to sync back up again

There'd were a limited number of shares available at a discount when purchased with member coins. I don't remember where the site was but to the best of my knowledge it has been sold out.

Im not sure what your trying to say. As stated in the roadmap though there is an update coming by the beginning of November I anticipate this to be finished by the end of October. I have just pushed the update out to git for version 2.4. 2.2 and 2.3 were test builds for various tweaks. 2.4 is the release. As of this point I need to build the appropriate wallets and daemons, at which point there will be a new release.

Close and open again. If you are syncing a new chain it can hang at spots. This is due to old clients still broadcasting invalid blocks

It has been quiet on my front for I have been working on wallet updates and such.

well at least you realize this. There are so many that would rather belly ache about how much they didn't get that they miss how many are not on the market thanks to those holding

to answer your question Not yet redeemed just means the input has not been used in the block chain to start a transaction. you could relate this to unspent.

So Im curious, out of the top wallets how many of them have actually moved? or has anyone been paying attention to this? Cause from the looks of it, the larger wallets are not the reason for the price decrease. Now that there is a roadmap I feel those that held for long term are actually going to benefit even more.

For the greater part of the last two weeks I have been fighting a cold. As a result I have not been posting up in here. I have logged into IRC a couple times. But mostly I have been working on the next batch of things needed to move Sonic along. As you all have noticed by now I am sure the roadmap has been posted and updated. A little explanation for what the various parts mean.

First, the updated QT. This will complete the re-branding phase of SonicScrewdriver to Sonic-Coin. There will be a new layout to accompany the graphics. I will also be including a poloniex window and links to the casino once it has been confirmed working.

Second
The Steganography App, I have had questions about what will make this different due to some hard to understand wording in the roadmap. What this will be is essentially a steganographic remote for the wallet. You will be able to do most basic functions the wallet already does without having to be at your computer. This will include sending, receiving, transaction history, etc.

Third
The In-Wallet Mail Client. Why this is important is that it will allow fewer steps to be required in order to setup the relay for use with the steganography app.

Forth
In-Wallet TOR Browser. Well why worry about setting up a tor node just to browse the internet, just fire up the qt and use the TOR Browser when you want.

Danoded I told you I already sent them an email. it's been over a month since the last time I heard from them. as you can see with an address lookup the coins havent moved.

As for why the price dumped I wish I knew. seems to already be bouncing back up though.

Crawler Updated
http://Http://www.argakiig.us/blockchain/seed

crawler is updated and on correct chain
http://www.argakiig.us/blockchain/seed/