Topic: [ANN] CoinShield -SK-1024 | операция "Зачистка скамкоинов" (Read 5078 times)

Launch Dates:
Phase 1: CPU Channel Activation:  9/23/2014 12:00:00 GMT - 6
Unix Timestamp: 1411510800

Version 2 Updates:  10/10/2014 12:00:00 GMT - 6
Unix Timestamp: 1412964000

Phase 2: GPU Channel Activation: 10/21/2014 12:00:00 GMT - 6
Unix Timestamp: 1413914400


Phase 3: POS Channel Activation: 11/04/2014 12:00:00 GMT - 6
Unix Timestamp: 1415124000


Homepage: http://Coinshield.io
Forum: http://CoinshieldTalk.org

We removed the internal miners, it is unnecessary code considering we took the time to write external miners.
So to mine, you must download a CPU Miner, or compile it from my Github

Here are compiled binaries for the CPU Prime Miner [x64 coming soon]:
Primeminer - Windows x86 If you want a linux binary for the primeminer, let us know and Videlicet will compile one.

CSD- Уникальные фичи

Следующие фичи уникальны и были созданы Videlicet.

SK Hashing: Increased Security
SK-1024, SK-512, and SK-256 hashes used for Coinshield Core (to replace SHA2). It is Skein (second runner up in NIST SHA3 Competition) and Keccak (New SHA3 Standard) hashed together. Coinshield is the first to run as a pure SHA3 network.

The SK templates range from SK64 to SK1024. Here is the usage of each SK hashing template:

SK64: Hash for Modifier Checksum as second fingerprint for Decentralized Checkpoints.
SK256: Hash to generate an Address from your Public Key Hash.
SK512: Hash for Transaction
SK576: Hash of Public Keys, which is then Hashed with SK256 to generate your Address.
SK1024: Hash for Block Generation. Used by both the CPU and GPU miners [and Stake Minting] to create new Blocks.


Private Key Upgrades:
Using the EC_KEY algorithms allocated in OpenSSL, Coinshield has upgraded the private keys to a non prime based elliptical curve encryption of 571 bits. This was the largest algorithm that was available, and also not dependent on prime numbers. The reason for this is simple: Coinshield CPU Miners are searching for very large prime numbers, so if any 'discoveries' happen from such actions, it could compromise the whole private key system. The exact algorithm Coinshield uses is secp571r1 compared to sect256k1 that is utilized by most cryptocurrencies today. This compliments the upgraded hashing algorithms to ensure the highest security possible by today's standard.


Coinshield will use Multiple Mining Channels + Proof of Stake
Coinshield has more options as a miner to help make the distribution as fair as possible. Dense Prime Clusters are found on the CPU channel from an SK1024 hash, while GPU miners do conventional SK1024 hashing. Each channel has its own difficulty adjustments and released rewards. The block trust is calculated to prevent streaks per channel, so in other words a different channel block will always break a streak of 2 or more blocks on a single channel. This makes each mining channel reinforce each other to prevent a 51% attack on any of them forcing an attacker to need 51% of all 3 mining channels [CPU, GPU, POS].


CSD Unified Time Model - Synchronizes Clocks Worldwide
Miners can no longer try to gain an unfair advantage by manipulating their clocks. The Unified Time System synchronizes your clocks worldwide from an initial time seed. This seed is then propagated through the network, and maintained. Once the seed is held in the network, it can be retrieved from any node making this a Decentralized, Trustless, Clock synchronization method. Another function is to reduce any dependencies on centralized sources, such as Network Time Protocol [NTP] which has just been found to have very large Amplifiction Attack Vectors [In other words, anything running NTP is vulnerable to DDOS].

The difficulty with this time system though, is that each computer sees a second 1-2 microseconds from each other, which means computer clocks are always drifting + - 2 seconds per day. The way Coinshield has compensated for this is by keeping the Unified Average Moving, so that we get the most recent time seeds from last X hours. This allows the clocks to stay tight, but slightly fluid. The LLP Clock Regulator periodically grabs the Unified Seed from the Seed nodes to continually build and move this average. We usually see about + or - 1 second over a day or so.

CSD Fractional Rewarding - Prevents Inflation / Locks Distribution to Timed Release
Coinshield will use a fractional rewarding system, this helps to ensure coin generation stays “on target” regardless of the number of blocks actually being created by the miners. It will be based per mining channel, which means each channel is awarded 50% of the time released supply (to keep distribution fair). No more instamine. Multipools will no longer profit.

No More Block Reward Halving
Coinshield was designed to have longevity, and be a stable container for wealth for many years to come. This is why Coinshield block reward will never half over night. Coins produced per minute is based on a slow decaying curve. This eases shock to the market by following a very natural time based curve. Mining should be considered “long-term” (~1% inflation after 10 years).

SK-1024 (New GPU Mining Algorithm)
Skein-1024 will be hashed to Keccak-1600 to produce an SK-1024 hash.

Prime Search (New CPU Mining Algorithm)
 This was created for the betterment of Mathematics and Number Theory. CPU miner will look for dense prime number clusters from a 1024 bit hash (~308 digits). This will help in the proving / disproving of The Twin Prime Conjecture, Polignac's Conjecture, and The Hardy-Littlewood Conjecture.

Shield Target Difficulty
This is an asymmetrical difficulty adjustment which gives higher priority to reduction in difficulty than inflation. This will keep the blockchain from getting 'stuck' for periods of time. The second aspect is that of reduced difficulty if too much supply has been released. This will continually reduce the difficulty as long as there is more than 8 minutes of supply available. From this point, miners will be getting a Full Subsidy while the difficulty deflates, to ensure more stimulation in block production, rather than difficulty.


Decentralized Checkpoints
We are really happy how this one came together, it became much simpler than our initial system. It works by passing a checkpoint that is flagged from being the block to set a new time interval through the blockchain onto another time interval. Once this new time interval is reached, that pending checkpoint becomes hardened and a new pending checkpoint is flagged. Currently this Testnet has a Checkpoint Timespan of 10 minutes which means, after you send a transaction, it will be behind a Checkpoint within 10 minutes. This helps to further prevent attackers from causing any harm, for they are only able even with 51% of all three Mining Channels to reorganize the chain for the past 10 minutes. The Checkpointing also uses the Stake Modifier Checksum generated from a CBlockIndex as a second fingerprint for the Checkpoint, so each checkpoint operates on a pair of Stake Modifier and Block Hash for extra security. Stake modifier checkpoints before were hard coded into kernel.cpp, and manually updated as with Peercoin.

Lower Level Protocol
The LLP uses template classes to allow anyone to 'build your own protocol' without having the need for any Network Programming knowledge. It gets rid of the "1 connection per thread" limitation still lingering on a lot of servers, to allow it to scale to your hardware maximums. We maxed the bandwidth on a Server before it broke 1% CPU usage. These results come from the simplicity, but power of this protocol. From these templates, we developed two extra Protocols for Coinshield Core, the Core LLP and the Mining LLP.

The Core LLP is responsible for the Unified Time functions, to have the quickest responses from the Server to ensure the Time Seed isn't diluted by Network Propagation. We have personally ran tests with no allowable clock drift with no forks, but to be sure this Testnet is running with an 8 second allowable clock drift.

The Mining LLP is what miners will connect to in order to generate blocks. This protocol allows any developer to 'plug and play' the LLP Client into their miner to remove the need for Network Programming associated with Mining. In my opinion, the focus of a miner developer should be in the optimization of their algorithms, not messing around with tedious Sockets.

Lower Level Protocol also has built in DDOS protection that functions on a moving average to determine your Score. You as a Client will have a Request Score and a Connection Score. This is because certain operating systems have limitations on the maximum active sockets, and their corresponding timeouts so if you go over 200 Connection Requests per Second without modifying this data, your whole Network Interface will reboot. Not a fun experience. The moving average makes the DDOS protection based on Throttled Requests rather than Normal LLP Request. This helps to distinguish the difference between real traffic, and an active DDOS attack. The more a Client gets banned, the longer they will be banned for to also give slight tolerance to the average user if their client accidentally pushes the requests over the limit [could be public wifi with same IP, etc.]



SUPPORT: CLICK HERE
Though we try, we are not always able to reply to bitcointalk.org posts.
The best place of support for Coin Shield is coinshieldtalk.org.