Topic: Nexus - Pure SHA3 + CPU/GPU + nPoS + 15 Active Innovations + More to Come - page 379. (Read 785514 times)

[Progress] is being made, here is an [update]:

1. Block Header Hashes now 1024 bit. [Most Secure POW Hash]
2. Transaction Hashes [and everything else] now 512 bit.
3. GPU Channel [Right now is SHA512, BLAKE512, SKEIN1024]. TODO: External Solo GPU Miner
4. [IN-PROCESS] Implementing Unified Time Model [Synchronizes network to same time from a Seed Regardless of your time]. No more clock problems.
5. Fractional Rewarding System in Place [with 600% block inflation, coin inflation was only 0.1%]. No more Instamining.
6. CPU POW, searching for large prime numbers [1024 bits and up, size of 10^308]. Testing Difficulty Limitations using Fermat Remainder proportions:
   double difficulty = ((prime - FermatTest(PRIME_DOWN(prime), 2) << 16) / prime) / ((prime - FermatTest(PRIME_UP(prime), 2) << 16) / prime)

Coinshield is really starting to set itself apart from the general Modus Operandi, which couldn't of happened without the suggestions from users like [you]. Thank You  
As always, any questions, suggestions, or concerns ?

EDIT: Here are our two types of hashes:
Coinshield Block Header [1024 bits]:

00003c9d1aa27eb4917c601c59c5d99dcc43441e810419143ba1ebd4639f5090f5d1a2b12ade583 ea6fcea548f80dfc0cd37818231a3471a9b3b2ce44bea8ab943f36cdee63005e9fd766f93400d36 2faceda5a61eb0b499ddb5d2efb9484282458d2ecb2190ee27fdf823effb4776f599362d10eff4f c4846bb56f9e6bb4ad2

Coinshield Tx Hash [512 bits]:

ebf9fc2c4563bac07d164812089222114025733b805312b8b407f4d3b6157e3f5b936067d4d96a3 6cc1c884e54c460e01725aeaf860dd1e01b4345b8124bd4a7

~Videlicet

Flagcoin!?  What is Flagcoin?  Is it premined???

  Best of luck to coin shield.

Cant wait to dump all shitcoins I have, and exchange for shieldcoin 
This coin will be flagcoin of 2014

Man this is serious business!

There is no IPO and 0 premine.

Is there IPO or premine?

Videlicet has created his own time-based distribution. This effectively makes coinshield multi-pool proof. Anyone jumping on with a big hash-rate will receive fractional block rewards (based on block time) until difficulty corrects itself. This will prevent multi-pools from profiting off mining CSD.

+1

big farms and multipools really do ruin cryptos, especially the ones that are new. They get pummeled and then dumped on the first exchange it makes it on. Fair distribution through hashrate limitation is great, especially if your coin only has a limited PoW period anyway.

Hey,

Would you implement something similar to what the Minerals coin did to avoid big farms and multipools reaping all your coins from the start just to dump all of them the next day? What they did is limit the hashrate per user, and their coin could only be mined on their pool during the PoW stage. They didn't release the wallet until PoS stage to avoid solo mining.

It resulted in Minerals having 25 GHs at the start compared to 100 GHs for other recent coins, even really shitty ones such as Hodorcoin, which proves that 75% of the miners are professional dumpers, big farms or multipools targeting new coins for a quick buck and not caring at all about the project.

It also resulted in Minerals being well spread, with a high price and large volumes on exchanges (100 btc+ in a few days).

Cheers

nice project

i like the idea behind this coin
too many shitcoins are out there
let's see how it works

I FUCKING LOVE THIS COIN

Thank you for taking the time to outline your observations. Most of them have been addressed throughout this thread. If you have any specific questions please ask and I will be happy to answer them.

~KryptoKash

some observations.

• by dumping the coin you create new bagholders, so new people have the coin and will need to either dump it, or make it rise again
• people can already manually do this with any coin simply by selling it and using the proceeds to buy another coin
• anybody could create a new coin and create a shitcoin/newcoin, newcoin/btc exchange
• this is open to massive manipulation, if an entity wanted to acquire a huge amount of x-coin they could deem it shit, acquire it all at the lowest price, then make the coin unshit and execute a social 51% attack
• any really shit coin already has zero value and zero orders, so it can't be dumped and turned in to coin shield
• the model is centralized and trust based, trust you with most of the btc from each shitcoin
• the idea of a well known service which immediately classifies new coins as clone or innovative would serve the purpose better, and prevent people from investing in new scams, rather than forcing them to commit to a loss and creating new bag holders
• the countdown, the promise that early traders will make the most profit, the focus on acquiring btc, has all the hall marks of every shit coins produced, and does you no favours
• the coin has no value of itself, no long term incentive, and will be deemed to be a shitcoin itself, with early adopters having guaranteed btc orders to dump in to once they reached their target profit margins
• needlessly complex for such a simple proposition, these complexities don't add value, they detract

The thing you are trying to achieve is fairly decent but creates the problem, old bag holders swap to new bag holders, and it's open to exploit, as is your own coin.

If you could codify this in a different way, without it being a coin, perhaps just a well known coin index and voting system, you'd achieve more with more benefit to the community.

I admire your efforts, but worry as above.

Thank You, Graham [I'll stick to 512 for now]


This is not up to us [it is the community that decides what coin is to be destroyed or protected].

~Videlicet

whatever u do. dont use coinshield on my coin. it will hurt your investors   

I tip my hat to your thorough approach.


As far as I know, only the Skein family runs to 1024 bits, all the rest top out at 512. Probably not worth a special effort.

Cheers

Graham

Graham,

The 512 bits for enhanced security only enhances when [512 bits] are stored in block [every other coin dev didn't take the time to restructure the code to make this possible]. I have spent a good part of today reprogramming the core of Coinshield to allow 512 bit hashing, and success [so far]!

a Coinshield merkle root:
2cc53ea5ff1712c11fb75127e39f975cf9fab950a4a804223f888ac496a1b6d3c65a4ca97c9b527 6f5d7c96be0407e58266f53d9c9c8be99d9a8467696b5a686

I implemented this in the merkle trees, block headers, cscripts, serialization templates, node signatures, block signing, pos checksum [well in fewer words, in all parts].

I think it is about time to phase out 256 bit hashing, I couldn't even write a reasonable miner with 256 bits [couldn't target numbers large enough]. I have implemented [uint1024] and [uint2048] for my own prime conjectures [to test new CPU algorithm], and am *thinking* on whether I should work on 1024 hashing algorithms [you said you have been working on one?]

~Videlicet

Dude......you turned half of this page into complete gibberish to me.....I mean that in a good way btw:-)  I don't think I have seen a thread yet that I understood so little!  Really cool though to have a member of the community that can talk and understand this lingo with a dev who shares so much about the technical side of what he/she is working on!  I don't understand SHIT of what you guys are saying.........but yet, still cool to see and read!

I need to go rest my head now, for some reason it hurts a little

All innovative coins can receive Coinshield Verification. Once verification is given the coin is immune from destruction, and through that it is protected against forgery; this will prevent Coinshield Verified coins from any risk of being blackmailed. By the way Coinshield will work, any future coins that clone a Coinshield Verified coin will have a trade channel opened upon verification of forgery. It will be difficult for anybody attempting that stragegy to have any sort of gains.