The comedy that runs through this place is great. Keep the shameless self promotion going! And now... back to your regularly scheduled programs.
Its not promotion, (Although i dont mind Crypto Prices listing us ![Wink](https://bitcointalk.org/Smileys/default/wink.gif) ) Its a technically sound argument to you not doing quite enough research before you launched. Lets get this straight, This will affect both our coins as has already been proved and I don't want this to become some childish slanging match, we're all professional developers here. So i'm offering my help instead. Let me help you change your CCN code to something else in your wallets so we can live happily side by side. Thanks
|
|
|
★ v2.0 Mandatory Update Available soon! ★Due to recent security vulnerabilities found in the KGW + OpenSSL, we've decided to do a major update to the CCN wallet. This will fix the OpenSSL Heart Bleed vulnerability and replace KGW as a retargeting mechanism. The DIGISHIELD implementation still retargets every block but will retarget downwards much quicker that KGW. It also reports back the correct difficulty value unlike KGW! Upcoming V2.0 Wallet specifications - 1000 KILR per block
- 60 seconds block time
- Retargeting every block
- OpenSSL v1.0.1g, due to the huuuuuge vulnerability found recently in previous versions!
Will be back very soon with a release date!
|
|
|
can't two different coins be named CCN ? Not if they are to be listed on the same exchange, or use the same pool. most exchange and pool owners will have the short name somewhere in their configs Aaaand as i said before, We already had CCN before you guys. Aaaannd again as i said before 2 coins can't be named CCN, as proved here! This was posted in our C-Coin (CCN) thread
http://crypto-prices.com/CCN
What more can i say!
|
|
|
Dont forget to update you wallets to v2.0 before block 42000!!
Updating after 42000 is still fine but a few more steps need to be taken, all the details are in supplied with the installers!
|
|
|
killercoin! the name is cooooooool,I like it
Nice one! Come and mine some while the diff is low. DIGISHIELD will start in a couple of days time, then things will be a bit different !
|
|
|
@mammix2
sounds great!
Did you get a statement from kilr.CryptoPool.eu?
Not yet, ive just contacted them again. Waiting on a reply
|
|
|
★ Update ★
The pool issue has now been fixed, and you all should be receiving your payouts very soon. The issue was caused by bringing the pool offline for a short while to update the wallet daemon code recently. This cause a single block to be unaccounted for within the mpos database, so the pool automatically disabled payouts until the issues was resolved.
Pool is up and ready for you all now :-)
|
|
|
I'm taking the pool offline for a while to fix the issues, sorry for the inconvenience
|
|
|
Ive checked over the pool just now, everything seems fine, COnfirmed and Unconfirmed balances are showing and payouts are working fine too
I'll keep checking the logs....
|
|
|
Morning all, i'll look into it now...
|
|
|
If you ever used the payment protocol (you clicked a bitcoin: link and saw a green box in Bitcoin Core's send dialog), then you should consider your wallet to be compromised.
This vulnerability is caused by a critical bug in the OpenSSL library used by Bitcoin Core. Successfully attacking Bitcoin Core by means of this bug seems to be difficult in most cases, and it seems at this point that even successful attacks may be limited, but I recommend taking the above actions just in case.
I shivered for a monent. Next time try mentioning the good news first. Thanks for the heads up! Exactly, we're not talking about a few £ or $ here and there...LOL!
|
|
|
Just upgraded. No issues.
Nice one ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif)
|
|
|
Yes we're secure... In the new v2.0 mandatory update OpenSSL 1.0.1g has been implemented!
|
|
|
★ v2.0 Mandatory Update Available now ★
You need to upgrade before block 42000 for the new DIGISHIELD implementation to take effect cleanly.As voted for by the community I've implemented DIGISHIELD into the wallet that will take effect at block 42000, which will be in a few days time. This will replace KGW as a retargeting mechanism, due to the vulnerabilities found recently. The DIGISHIELD implementation still retargets every block but will retarget downwards much quicker that KGW. It also reports back the correct difficulty value unlike KGW! Please follow the Readme.rtf file instruction supplied in each distribution to ensure you dont loose any KILR and you stay on the new main net chain. Any coin mined after block 42000 with old v1.0 wallets will not be valid and will be lost when upgrading to V2.0!If you are upgrading after block 42000 there are some different steps to follow, but again they are explained in the Readme file supplied in each distribution. V2.0 Wallet specifications - 1000 KILR per block
- 60 seconds block time
- Retargeting every block
- Total coin supply has been increased to 2 Billion, as all the blocks so far have been created way too fast due to KGW
- OpenSSL v1.0.1g, due to the huuuuuge vulnerability found recently in previous versions!
Windows: Mirror 1: https://mega.co.nz/#!cVphjbyD!wCC9GoQ5_oZCLqVTvGttvr9KS8oXBHCFxvG3Dtqm9vYOSX: Mirror 1: https://mega.co.nz/#!BFhkULpb!WrOC6Bc2J24lWCau4X-U86KOSjpjGHwEsBnSJdNSL2oLinux: https://github.com/killercoin/killercoin-masterSource:https://github.com/killercoin/killercoin-master
|
|
|
The coin needs promotion guys, or it will go on unnoticed by most miners!
Agreed, once the update in available to the public, we need to go on a mass promotion drive
|
|
|
|