Nexus - Pure SHA3 + CPU/GPU + nPoS + 15 Active Innovations + More to Come

[Bitdonator]

Can we expect wallet for Android?

[1713482888]

1713482888

[1713482888]

1713482888

[1713482888]

1713482888

[1713482888]

1713482888

[1713482888]

1713482888

[Videlicet]

Can we expect wallet for Android?

Yes, but not at launch. This will be of a lower priority compared to other components [exchange / voting channels, coinshield core, etc.].

~Videlicet

[Videlicet]

Here is an [update] of current [progress]:

1. All major systems coded and implemented in Coinshield Core [clearing up last few bugs / tuning the engine]
2. Upgrading elliptical private/public key system in wallet to 1024 bits [in-process, private key output is 1024 bits, adjusting curve group to have larger modulation than NID_secp256k1]
3. Finally had time [while testing] to work on Qt, got it up to par. I will be doing more development on this post-launch.
4. [in-process] of developing RPC client to handle GetBlockTemplate for external CPU / GPU while [BitSlapper is working on GPU kernal, everyone give him a Big Thank You for offering his help].

My CPU hashrate for SK-1024 is about 50 kh/s per core.
It looks like we will be ready for public testing quite soon.

~Videlicet

edit: slight reformatting

[coinsolidation]

Good work Videlicet, I look forward to testing your code.

Which CPU are you using?

[Videlicet]

Good work Videlicet, I look forward to testing your code.

Which CPU are you using?

Intel Pentium G3220 @ 3Ghz

~Videlicet

[smackii]

Mineable only by CPU?

[Videlicet]

Mineable only by CPU?

There is an SK-1024 GPU channel, and Prime Number CPU channel.

~Videlicet

[GoldenUnity]

I'm not going to be able to rental mine this am I?

[bigreddmachine]

Hi, I just wanted to say... very early on I was quite critical of this project (and I still have qualms about the concept) but I must say that I am impressed with the amount of development that you have put into this coin.  I hope that you are able to have a successful launch and do some good for the altcoin community.  Please remember the little guys when you launch, and be thorough before deciding to take out a coin!

- BRM

[Videlicet]

I'm not going to be able to rental mine this am I?

Yes, I do believe you are correct.

Hi, I just wanted to say... very early on I was quite critical of this project (and I still have qualms about the concept) but I must say that I am impressed with the amount of development that you have put into this coin.  I hope that you are able to have a successful launch and do some good for the altcoin community.  Please remember the little guys when you launch, and be thorough before deciding to take out a coin!

- BRM

I appreciate the support. The way I see it is - if I'm going to take the stance of quality, I better put in the hard work to back it up. I'm sure over time this idea will continually be refined to prevent manipulation as with any new system. Unfortunately sometimes the only way to discover [and prevent] such things is through the experience of them.

My ultimate goal here, is to convey to everyone that we can change the way things are by working together. I personally believe the way to unite the people is through a cause they all can have a part in - the direction. I hope that my hard work here, will encourage other developers to work hard on their projects to really produce unique and useful coins. This will help the public adoption of cryptocurrencies by improving the quality [and image] of the marketplace.

Thank You,
~Videlicet

edit: slight reformatting

[coinsolidation]

Videlicet,

I would like to tip you with 80 Bitmarks out of respect for your hard work and approach to the development of, and communication about, your CoinShield project.

This represents 4 full blocks and is 1/3rd of the coins I own, hopefully one day it will serve to be of some value to you.

If you pass me a Bitmark address I will send you the coins.

Keep up the good work, innovation and hard work are to be admired.

Mark

[Videlicet]

Videlicet,

I would like to tip you with 80 Bitmarks out of respect for your hard work and approach to the development of, and communication about, your CoinShield project.

This represents 4 full blocks and is 1/3rd of the coins I own, hopefully one day it will serve to be of some value to you.

If you pass me a Bitmark address I will send you the coins.

Keep up the good work, innovation and hard work are to be admired.

Mark

Wow, it is wonderful to know there are good people on this planet, Thank You Mark.

~Videlicet

I'll send you a PM


edit: to clarify our position concerning donations
By the nature of how Coinshield works, and the position we have taken, we are unable to accept donations. We hope everyone understands our responsibility to absolute non-bias, in order to make this system successful.

[cryptozim]

edit: to clarify our position concerning donations
By the nature of how Coinshield works, and the position we have taken, we are unable to accept donations. We hope everyone understands our responsibility to absolute non-bias, in order to make this system successful.

Wait. Integrity? That's not how crypto works, is it?

[coinsolidation]

edit: to clarify our position concerning donations
By the nature of how Coinshield works, and the position we have taken, we are unable to accept donations. We hope everyone understands our responsibility to absolute non-bias, in order to make this system successful.

Wait. Integrity? That's not how crypto works, is it?

I can confirm that he refused the BTM I offered also.

So I'll help him with early testing instead

[Videlicet]

Development [Update] : Testnet launch [most likely today {edit: private testing in process} possibly tomorrow]. I am deciding for the last time, to give Coinshield the little extra time it needs for everything to be 100%. I hope everyone understands I keep extending the launch because there have been more things that needed tending. I am ensuring that I can be as thorough as possible, to get this done correctly [the first time]. Below you'll be able to read the list of how everything has finally settled, and what is still needing further development. Pending on how testing goes, Coinshield could launch in 2 days or 5 days. I hope to see some public involvement in the testing, to ensure the Coinshield Core is scrutinized from as many angles as possible. This way I can tend to any issues that may arise, so they do not become problems come launch time.

1. Fractional Rewarding - Finalized: Fractional Rewards are now based on excess created in block index. This allows Coinshield to break up excess into full rewards [~50 CSD]. This will distribute excess supply evenly to more miners, to have a more fair distribution. Due to the nature of the Fractional Excess System, if a miner manipulates their clock to the maximum allowed in Unified Time, they will create excess that will be given to other miners. This will prevent such an act.

2. Shield Target - Finalized: Shield target now works with the Fractional Excess system to deflate difficulty the moment there is excess. This helps the chain recover from long block times much more quickly. Currently fine tuning the parameters to ensure smoothest adjustments

3. CPU: Prime Channel - Finalized: Prime channel finds dense prime clusters off of an SK-1024 hash produced from nBits and hashMerkleRoot. The prime offset is determined by nNonce. This method prevents anyone from submitting just any prime, they would have to build a block and find the prime from the hash in order to successfully generate CSD. Difficulty is represented by a decimal value [ex. 1.5867] where the whole number is the cluster size, and the decimal is the fractional remainder of last composite in cluster. It runs about 1 PPS [Primes Per Second] and 600 SPS [Searches Per Second] per core and finds a cluster of difficulty 2.0 every 150 seconds.

4. GPU: SK-1024 - Miner: In-Process - Core Finalized: Normal methods of hashing, except miner has to hash 1024 bits, not 256 bits.

5. Json RPC Server - In-Process: Updating several commands such as "getmininginfo", "getblocktemplate", "submitblock". Adding commands such as "listprimes", "getprime <hash>", "getlastprime", "getlastblock <channel>". Everything else functions correctly in RPC server [as far as I've seen].

6. Private Keys - In-Process: Using largest curve group NID_sect571k1 or NID_sect571r1 to suit our needs quite well. This provides double the security compared to previous curves used [last issue is serialization from disk].

7. Coinshield-Qt - In-Process All major components work such as signing message, address generation, send transactions, etc. There were a couple issues that had to be resolved, but it is now fully functional. It is still in-process because it is "a little rough around the edges" in the sense of column default sizes being slightly off [because addresses before upgrade were 160 bit]

8. Unified Time - Semi-Finalized: Works perfectly for any node. Making small decisions as to how often unified time is checked for consistency or what the maximum allowable drift should be [to account for propagation time]. Unified Time updates seed from peers successfully if UTM seed goes down, adding other small layers of security such as preventing people from flooding network with a false time seed, or localized clock manipulators [check clock to itself, if it changes more that +- 60 seconds, add temporary offset until unified time is updated].

9. Proof of Stake - Semi-Finalized: Tuning the modifier time, split/combine ratio, yearly output.


I appreciate the continued support through the development of this project.
~Videlicet

[IMJim]

COOL!  I hope the launch gets delayed a few more days, have to go out of town this weekend and was upset I was going to miss the launch.....prob still will, but I can hope:-)

[phzi]

Nice to see the development evolving.

Hopeful we see the miner and a testnet-only client a while before launch?

[Videlicet]

Nice to see the development evolving.

Hopeful we see the miner and a testnet-only client a while before launch?

I just started a round of private testing, based on results I will release a testnet only client for everyone to hop on. After client is deemed stable, I will then release main net binaries with a time-lock for a set launch time. This will let everyone get setup before launch. Finally, I will release the source code at launch [I am keeping it private until launch to protect the time-lock].

As for the miner It is in process and yes will be released before launch. Bitslapper is handling the GPU kernal and making progress, which is greatly speeding up the process.

I'll keep everyone posted on future progress,

~Videlicet

[Superxfast]

Development [Update] : Testnet launch [most likely today {edit: private testing in process} possibly tomorrow]. I am deciding for the last time, to give Coinshield the little extra time it needs for everything to be 100%. I hope everyone understands I keep extending the launch because there have been more things that needed tending. I am ensuring that I can be as thorough as possible, to get this done correctly [the first time]. Below you'll be able to read the list of how everything has finally settled, and what is still needing further development. Pending on how testing goes, Coinshield could launch in 2 days or 5 days. I hope to see some public involvement in the testing, to ensure the Coinshield Core is scrutinized from as many angles as possible. This way I can tend to any issues that may arise, so they do not become problems come launch time.

1. Fractional Rewarding - Finalized: Fractional Rewards are now based on excess created in block index. This allows Coinshield to break up excess into full rewards [~50 CSD]. This will distribute excess supply evenly to more miners, to have a more fair distribution. Due to the nature of the Fractional Excess System, if a miner manipulates their clock to the maximum allowed in Unified Time, they will create excess that will be given to other miners. This will prevent such an act.

2. Shield Target - Finalized: Shield target now works with the Fractional Excess system to deflate difficulty the moment there is excess. This helps the chain recover from long block times much more quickly. Currently fine tuning the parameters to ensure smoothest adjustments

3. CPU: Prime Channel - Finalized: Prime channel finds dense prime clusters off of an SK-1024 hash produced from nBits and hashMerkleRoot. The prime offset is determined by nNonce. This method prevents anyone from submitting just any prime, they would have to build a block and find the prime from the hash in order to successfully generate CSD. Difficulty is represented by a decimal value [ex. 1.5867] where the whole number is the cluster size, and the decimal is the fractional remainder of last composite in cluster. It runs about 1 PPS [Primes Per Second] and 600 SPS [Searches Per Second] per core and finds a cluster of difficulty 2.0 every 150 seconds.

4. GPU: SK-1024 - Miner: In-Process - Core Finalized: Normal methods of hashing, except miner has to hash 1024 bits, not 256 bits.

5. Json RPC Server - In-Process: Updating several commands such as "getmininginfo", "getblocktemplate", "submitblock". Adding commands such as "listprimes", "getprime <hash>", "getlastprime", "getlastblock <channel>". Everything else functions correctly in RPC server [as far as I've seen].

6. Private Keys - In-Process: Using largest curve group NID_sect571k1 or NID_sect571r1 to suit our needs quite well. This provides double the security compared to previous curves used [last issue is serialization from disk].

7. Coinshield-Qt - In-Process All major components work such as signing message, address generation, send transactions, etc. There were a couple issues that had to be resolved, but it is now fully functional. It is still in-process because it is "a little rough around the edges" in the sense of column default sizes being slightly off [because addresses before upgrade were 160 bit]

8. Unified Time - Semi-Finalized: Works perfectly for any node. Making small decisions as to how often unified time is checked for consistency or what the maximum allowable drift should be [to account for propagation time]. Unified Time updates seed from peers successfully if UTM seed goes down, adding other small layers of security such as preventing people from flooding network with a false time seed, or localized clock manipulators [check clock to itself, if it changes more that +- 60 seconds, add temporary offset until unified time is updated].

9. Proof of Stake - Semi-Finalized: Tuning the modifier time, split/combine ratio, yearly output.


I appreciate the continued support through the development of this project.
~Videlicet

No problem, many servers still wait to test for you.

[IMJim]

Well.......looks like I am def gonna miss the launch, but wanted to wish you all well with it!