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

[Crypthos]

Just doing some transactions with Nexus, 3 confirmations in more or less one minute an half, is just beautiful...Previously I fell into the hype of DASH with its "Instant X" transactions, turns out for those transactions it just makes you pay a higher fee, that's it. Average transaction fee is 0.0001, "Instant X" transaction is 0.05 that's why they are "instantaneous", it will be amazing when in the future Nexus can do real instant confirmations, reversible transactions, thousands of transactions per second and on top of that no fees, very few coins will be able to compete with this beast =) , cheers guys.

[skunk]

Skunk,

Updated makefile, still had remnants of my custom boost 1_57 directories, this is most likely why the Daemon didn't build.
And Borris I'm looking to have it done by the end of the year, though you'll have a decent frame of reference when I go to beta to test for a week, that is when we can set the release date.

Thank You,
Viz.

it builds (fine) dynamically after removing the comments from makefile.unix:

Code:

ifdef STATIC
        LMODE = static
        ifeq (${STATIC}, all)
                LMODE2 = static
        endif
else
        TESTDEFS += -DBOOST_TEST_DYN_LINK
endif

[Videlicet]

Skunk,

Ah you need to compile some of your dependencies as static to run static binaries, I have the makefile static so that dependencies are compiled into the release. Thanks for your feedback

------------------------

Crypthos,

Yeah InstantX and it's clone ZeroTime (Vanilla Coin) are just network level messages to lock transaction inputs from the memory pool to prevent Finney attacks among others, it does make 0 confirmation safer, but isn't as secure as the blockchain, in some respects they remove a lot of the blockchain security model to supplement faster transactions, where I believe the true speed can come from simultaneous processing, or multiple "branches" in which block chains operate on their own branch for each mining channel, that can give us a 3x increase in processing capability and reduce orphans at the same time. This way attacks would be pushed to individual branches therefore even under a 51% attack on particular channel,  it wouldn't affect the other branches. Working up the architecture too to elimate 51% attacks once and for all, but this will be very tricky to get it right 

Thank You,
Viz.

[borris123]

Skunk,

Ah you need to compile some of your dependencies as static to run static binaries, I have the makefile static so that dependencies are compiled into the release. Thanks for your feedback

------------------------

Crypthos,

Yeah InstantX and it's clone ZeroTime (Vanilla Coin) are just network level messages to lock transaction inputs from the memory pool to prevent Finney attacks among others, it does make 0 confirmation safer, but isn't as secure as the blockchain, in some respects they remove a lot of the blockchain security model to supplement faster transactions, where I believe the true speed can come from simultaneous processing, or multiple "branches" in which block chains operate on their own branch for each mining channel, that can give us a 3x increase in processing capability and reduce orphans at the same time. This way attacks would be pushed to individual branches therefore even under a 51% attack on particular channel,  it wouldn't affect the other branches. Working up the architecture too to elimate 51% attacks once and for all, but this will be very tricky to get it right 

Thank You,
Viz.

Don't have a bloody clue what you on about there but that is why I investing in this coin lol. You clearly have a path in your mind and I willing to wait till you have it sorted. So far your process is slower than other coins but the outcomes have been spot on.

[cestballot]

http://nexusniropool.cestballot.fr/ News :

Providers information :
DDos Attack was detected ...

Detection d'une attaque sur l'IP 51.255.38.3

Code:

SAS OVH - http://www.ovh.com
2 rue Kellermann
BP 80157
59100 Roubaix



Madame, Monsieur,

Nous venons de détecter une attaque sur l'adresse IP 51.255.38.3.

Afin de protéger votre infrastructure, nous avons aspiré votre
traffic sur notre infrastructure de mitigation.

Toute l'attaque sera ainsi filtrée par notre infrastructure, et seul
le traffic légitime arrivera jusqu'à vos serveurs.


A la fin de l'attaque, votre infrastructure sera immédiatement retirée de la mitigation.


Pour plus d'informations sur l'infrastructure de mitigation OVH : https://www.ovh.com/fr/anti-ddos/


Cordialement,

Votre Service Client OVH

I keep you posted here

Edit 1 : attack stoped now, we compare data and we will restart pool server soon
Edit 2 : pool ready and up

[Crypthos]

http://nexusniropool.cestballot.fr/ News :

Providers information :
DDos Attack was detected ...

Detection d'une attaque sur l'IP 51.255.38.3

Code:

SAS OVH - http://www.ovh.com
2 rue Kellermann
BP 80157
59100 Roubaix



Madame, Monsieur,

Nous venons de détecter une attaque sur l'adresse IP 51.255.38.3.

Afin de protéger votre infrastructure, nous avons aspiré votre
traffic sur notre infrastructure de mitigation.

Toute l'attaque sera ainsi filtrée par notre infrastructure, et seul
le traffic légitime arrivera jusqu'à vos serveurs.


A la fin de l'attaque, votre infrastructure sera immédiatement retirée de la mitigation.


Pour plus d'informations sur l'infrastructure de mitigation OVH : https://www.ovh.com/fr/anti-ddos/


Cordialement,

Votre Service Client OVH

I keep you posted here

Edit 1 : attack stoped now, we compare data and we will restart pool server soon
Edit 2 : pool ready and up

wow... Are this DDos attack common thing in alt coins? specially Nexus that is not popular at the moment, so strange.

[Razerglass]

Haters will hate.

[pdogg147]

nex·usˈneksəs' : a connection or series of connections linking two or more things.

"It is not the concept of money – monetary value – that is the issue; it is the implementation of it."

Money is only a container of energy allowing exchange of value between two parties. Nexus applies a decentralized, mathematically regulated, transparent currency designed for stability and sustainability: The denomination of Nexus is termed The Niro. Decentralization is inherent to success, as centralized points only serve as fail points, as malleable targets to be exploited for the benefit of few. In order for a system to be designed in service of the people, its creation must be forged under like principles. This has been brought forth through history, in its successful implementations of self-governance, of liberty, and the right to sustenance for all life. This right has been circumvented, in which, our only choice is to form a Nexus, to combine our strength as global citizens – and preserve our right to life, freedom, and the pursuit of happiness. These Connections of Economies, Ideas, People, Computers, and Resources will free humankind. Nexus fosters Freedom, Innovation, and Self Sufficiency and applies these concepts in the following regions of knowledge: Viz. Psychology, Philosophy, Computer Science, Mathematics, and Economics. Nexus Software, LLC supplements The Nexus by developing these concepts to establish an economy that gives power to the people, the citizens: the working force that is the movement of a system.

SPECIFICATIONS

Algorithm
SHA3 [Skein and Keccak]

Minting Channels
CPU, GPU, and Nexus Proof of Stake (nPOS)

Initial Supply
78 Million over a 10 year distribution period for the CPU and GPU Channels

Maximum Annual Inflation
nPOS: Up to 2% annually
CPU and GPU Minting Channels: 1% annually after initial distribution is complete

Block Time
300 seconds for GPU minting channel and 300 seconds for CPU minting Channel for an average of 150 seconds
60 seconds for nPOS

Block Reward
CPU and CPU Minting Channels: The effective reward is established by the reserve balances. These reserves have a decayed amount deposited every time interval of one minute. If the balance is below a given threshold, the reward value will be based on a time’s value of a decayed amount. This means that the reward will be given based on how long it was taken to create the block. This prevents the reserves from being depleted as large amounts of computing power jump on and off the mining network.

nPOS Minting Channel: The effective reward is an annual interest rate that ranges between 0.5 and 2.0% annually.

Minting Difficulty
The miner’s difficulty is calculated by a proportion generated from the time it took to create the block, and the target time. The target time is calculated by the NIRO Reserves working to deflate the difficulty if the reserves go over a threshold. This is designed to maintain transaction processing in the loss of computing power to given channel, by aiding in the reduction of the difficulty to a more suited level.

NEXUS TEAM

Colin (Videlicet), Founder / Funding / Software Engineer, colin@nexusoft.io
Josh (Razerglass), Market Analyst / Software Development, josh@nexusoft.io
Keith (nightandday), Graphics / Design, keith@nexusoft.io
Manuel (cestballot), Mining Pool Operator, cestballot@nexusoft.io
Patrick (tokyopotato), Social Media / Marketing Specialist, patrick@nexusoft.io
Preston (pdogg147), Public Relations / Community Manager, preston@nexusoft.io

HOW NEXUS IMPROVES UPON THE BITCOIN PROTOCOL

CURRENT FEATURES

Mining Channels: Each channel reinforces each other to prevent 51% attacks on one channel forcing attacker across multiple channels.

Hashing: SK-1024, SK-576, SK-512, and SK-256 used in all hashing. Pure SHA3 using Skein and Keccak.

Keys: 571 Bit Private Keys compared to 256 bit in other currencies. Using NID_sect571r1 as the algorithm.

Difficulty: Calculated with time overlaps and true % over bounds, using weighted block average over past 5 blocks.

SK-1024: Using Skein-1024 and Keccak-1600 for GPU PoW to produce a 1024 bit output hash used for the block hash providing the highest security.

Prime: Searching for Dense Prime Clusters as CPU PoW, finding these clusters of numbers that are ~308 digits to verify prime density in large numbers.

LLP: Lower Level Protocol as a template protocol to allow any protocol to be created with ease without need for repeated network programming.

Core LLP: Protocol responsible for time keeping as an advancement to NTP, keeping clocks on the network synchronized within a few seconds of one another. Maximum clock drift for Nexus is 10 seconds.

Mining LLP: Dedicated Mining Protocol outside of JSON-RPC Server to allow the greatest performance for mining. Protocol can handle 5k + connections allowing solo mining of any magnitude.

No Reward Halving: Rewards are calculated along an exponential decay curve to slowly reduce the value of each block rather than shock both miners and the market with block reward halving which acts as a rudimentary decay model.

Released Reserves: Decayed Amounts are deposited into the Reserves for each channel, preventing a miner from being able to mint more than the projected amount while difficulty is compensating to their amount of computing power.

Fractional Rewards: When reserves are below given thresholds, the mining reward is then based off of the time it took to create a block preventing a miner from ever being able to deplete the reserves.

Decentralized Checkpoints: All blocks must root from the most recent checkpoint which is declared by fitting into a timespan. This allows checkpoints to be automatically created every hour, without the need for any master node or checkpoint broadcast.

Trust Keys: Interest rate is increased the more a node services the main chain giving incentive to active stakers. This also increases the cost of an attack for in order to attack with a trust key it requires time to get it to the same threshold.

Nexus Proof of Stake: Proof of Stake system based on the Peercoin protocol heavily recoded from the ground up utilizing energy efficiency threshold, trust keys, and logarithmic weights to create the fairest and most stable Proof of Stake system to date.

Developer Commission: Built into the protocol levels, gives a small decayed amount to developer addresses every block [~1 Niro] over 10 years amounting to a total of ~2.5% after 10 years, and starting at ~1.5% as a way to bring the benefits of pre-mines, without the risk to investors. This means developer account has no control over the currency as it will never be of a high enough %, but it allows funds to be distributed to development removing need for corruptible foundations such as the Bitcoin Foundation which was spawned to cover developmental costs.

PLANNED FUTURE FEATURES

Reversible Transactions: Transaction can be reversed if below expiration time by sending transaction void to the network.

Two-Way Signatures: Receiver of transaction will be required to sign to prove ownership of txout before it will be processed. This will prevent burning coins by accident.

Trust Network: Using Trust Keys and more sophistication in Checkpoints will create a Trust Network in which nodes will be given the opportunity to vote on checkpoints and blocks to agree on set blockchain. This will prevent a rogue node from trying to manipulate the network.

Sync-less Wallets: Using the Trust Network as a backbone and the LLP for the protocol, will allow wallets to remain sync-less by processing transactions in the Trust Network.

HTML5 Wallet: Probably coming sooner rather then later, essentially building up a clean simple HTML5 wallet using qt web server. Will have all the great visuals that HTML5/CSS3 provides. Most likely coming before transaction features so I can have a cleaner GUI to integrate more functionality into.

Double Spend Protection: Using input locking and checking on reorganizations, can prevent a transaction from ever being able to be overwritten by a longer blockchain after a checkpoint eliminating any threat of 51% attacks.

LLL Integration: Once the Library including Static and Dynamic Databases is finished, next will be integrating LLP, LLD, and LLS with possible LLE for encrypted communications and high efficiencies in protocol responses and data storage.

UPDATES TO BE INCLUDED IN FUTURE RELEASES

Updates Planned for the Full 0.2.1 Release include:

1.   Trust Key Penalties to deprecate Trust Key Expiration.
2.   Possible Trust Key Reactivation.
3.   Push Packets in Mining LLP.
4.   Mining LLP Version 1.1 Update from Pool Server
5.   Possible Sequencing of UTXO into larger outputs every X blocks for Developer and Recycler Addresses.

Updates Planned for the Full 0.2.2 Release include:

1.   LLP Messaging Integration for Better Network Communication
2.   More Messaging Commands due to LLP integration allowing Core level Functions to Exist in greater efficiency.
3.   Checkpoint Voting for Pending Checkpoint.
4.   Auto - re-forking besides just Reorganizations. Detect when your node is on a fork and automatically resolve.
5.   Consensus algorithms by voting with trust key.

Updates Planned for the Full 0.3.0 Release include:

1.   LLD database integration.
2.   Light Blocks due to Memory Pool Synchronization Protocol
3.   New protocols for Transaction Processing vs. Block Processing which means breaking Messaging Protocol to more Specialized Systems so Transactions and Blocks and Voting operate on Separate Protocols.
4.   With lighter blocks, it won't be necessary to include full UTXO transaction information in the block, but rather the transaction hash that can verify the Merkle Root while blocks are validated on the block level upon receive, where the Transactions are verified in a separate call and answers on the validity of the block can be seen through the Trust Protocol. This will speed up block propagation through the network.
5.   Integrating Miners into Trust Keys giving miners incentive to continue contribution to the Network. Miners will be penalized for less trust which means rewards will be less until full trust is established.

WALLET DOWNLOADS

NEXUS VERSION 2.0


RECENT DATABASE BOOTSTRAP

NEXUS MINING

Prime Channel (CPU)
[Miners Created by Videlicet, Optimized by Supercomputing]
Prime Solo Miners:
Source Code [Github]
Windows Binary x86
Windows Binary x64

Nexus Beta Pool: 204.27.62.234:9549

Cestballot Pool: 51.255.38.3:9549 http://nexusniropool.cestballot.fr

Prime Pool Miners:
Source Code [Github]
Windows Binary x86
Windows Binary x64

Hashing (GPU) SK-1024 Channel
[Miners Created by Bitslapper, Optimized by djm34]
SK-Miner [AMD] Binary with Web GUI Monitor v1.2
SK-Miner [NVIDIA] Source
SK-Miner [Github]

SOURCE CODE

MARKETS

NEXUS WIKI

Find out more details of the Nexus protocol including Technological Advancements

SOCIAL MEDIA

www.nexusoft.io





SLACK

Email preston@nexusoft.io for an invite

REDDIT

IRC #nexusniro

YOU, ME, AND BTC PODCAST

The Original Post has been updated.  Thanks everyone for the feedback.  There are still a few things that will be refined, but please let us know what you think.

[merc84]

Looks great just one small thing;


Hashing: SK-1024, SK-576, SK-512, and SK-256 used in all hashing. Pure SHA3 using Skein and Keccak.

Keys: 571 Bit Private Keys compared to 256 bit in other currencies. Using NID_sect571r1 as the algorithm.

Difficulty: Calculated with time overlaps and true % over bounds, using weighted block average over past 5 blocks.

SK-1024: Using Skein-1024 and Keccak-1600 for GPU PoW to produce a 1024 bit output hash used for the block hash providing the highest security.

Prime: Searching for Dense Prime Clusters as CPU PoW, finding these clusters of numbers that are ~308 digits to verify prime density in large numbers.

I would rearrange the sk-1024 and Prime lines to be directly below the Hashing heading since they are directly related to each other.
Also max interest rate is 3%.

[Crypthos]

Skunk,

Ah you need to compile some of your dependencies as static to run static binaries, I have the makefile static so that dependencies are compiled into the release. Thanks for your feedback

------------------------

Crypthos,

Yeah InstantX and it's clone ZeroTime (Vanilla Coin) are just network level messages to lock transaction inputs from the memory pool to prevent Finney attacks among others, it does make 0 confirmation safer, but isn't as secure as the blockchain, in some respects they remove a lot of the blockchain security model to supplement faster transactions, where I believe the true speed can come from simultaneous processing, or multiple "branches" in which block chains operate on their own branch for each mining channel, that can give us a 3x increase in processing capability and reduce orphans at the same time. This way attacks would be pushed to individual branches therefore even under a 51% attack on particular channel,  it wouldn't affect the other branches. Working up the architecture too to elimate 51% attacks once and for all, but this will be very tricky to get it right  

Thank You,
Viz.

What about to put as a Pending Feature that Nexus is 51% Attack Resistant, as Videlicet said a few post back that he'll be working on this feature in the future.

[pdogg147]

Looks great just one small thing;


Hashing: SK-1024, SK-576, SK-512, and SK-256 used in all hashing. Pure SHA3 using Skein and Keccak.

Keys: 571 Bit Private Keys compared to 256 bit in other currencies. Using NID_sect571r1 as the algorithm.

Difficulty: Calculated with time overlaps and true % over bounds, using weighted block average over past 5 blocks.

SK-1024: Using Skein-1024 and Keccak-1600 for GPU PoW to produce a 1024 bit output hash used for the block hash providing the highest security.

Prime: Searching for Dense Prime Clusters as CPU PoW, finding these clusters of numbers that are ~308 digits to verify prime density in large numbers.

I would rearrange the sk-1024 and Prime lines to be directly below the Hashing heading since they are directly related to each other.
Also max interest rate is 3%.

Good idea. Will rearrange that way.

Skunk,

Ah you need to compile some of your dependencies as static to run static binaries, I have the makefile static so that dependencies are compiled into the release. Thanks for your feedback

------------------------

Crypthos,

Yeah InstantX and it's clone ZeroTime (Vanilla Coin) are just network level messages to lock transaction inputs from the memory pool to prevent Finney attacks among others, it does make 0 confirmation safer, but isn't as secure as the blockchain, in some respects they remove a lot of the blockchain security model to supplement faster transactions, where I believe the true speed can come from simultaneous processing, or multiple "branches" in which block chains operate on their own branch for each mining channel, that can give us a 3x increase in processing capability and reduce orphans at the same time. This way attacks would be pushed to individual branches therefore even under a 51% attack on particular channel,  it wouldn't affect the other branches. Working up the architecture too to elimate 51% attacks once and for all, but this will be very tricky to get it right 

Thank You,
Viz.

What about to put as a Pending Feature that Nexus is 51% Attack Resistant, as Videlicet said a few post back that he'll be working on this feature in the future.

Good point.  We will discuss how to word this.

[Conqueror]

New 1st post is much better now.
Great work Nexus team! Thank you

[pdogg147]

New 1st post is much better now.
Great work Nexus team! Thank you

Thanks!  We are glad you like it.

[Stenull]

New 1st post is much better now.
Great work Nexus team! Thank you

Agree, it's looking great

[borris123]

update coming soon? Had to restart wallet and this loading is well bad takes ages

[tokyopotato]

Hey guys, we recorded this 1st podcast a few days ago.  If you guys want to check it out, and give us some feedback.  It's our first one, and was a good learning experience to get a process down.  We hope to produce one each week, and we want to encourage people to give us questions they would like answered.

So, if you have any questions for the next Podcast, please let us know.  If you want to participate in the Podcast, also please let us know.  Thank you.


https://soundcloud.com/nexusoft/nexus-podcast-e1-1

[almond]

Hey guys, we recorded this 1st podcast a few days ago.  If you guys want to check it out, and give us some feedback.  It's our first one, and was a good learning experience to get a process down.  We hope to produce one each week, and we want to encourage people to give us questions they would like answered.

So, if you have any questions for the next Podcast, please let us know.  If you want to participate in the Podcast, also please let us know.  Thank you.


https://soundcloud.com/nexusoft/nexus-podcast-e1-1

nice to hear your voices and thought patterns.

Let's build some guitars ! (and amps )

[Conqueror]

Hey guys, we recorded this 1st podcast a few days ago.  If you guys want to check it out, and give us some feedback.  It's our first one, and was a good learning experience to get a process down.  We hope to produce one each week, and we want to encourage people to give us questions they would like answered.

So, if you have any questions for the next Podcast, please let us know.  If you want to participate in the Podcast, also please let us know.  Thank you.


https://soundcloud.com/nexusoft/nexus-podcast-e1-1

Bit boring, lost focus after 5 minutes. Why you put so many music into it?

[merc84]

Hey guys, we recorded this 1st podcast a few days ago.  If you guys want to check it out, and give us some feedback.  It's our first one, and was a good learning experience to get a process down.  We hope to produce one each week, and we want to encourage people to give us questions they would like answered.

So, if you have any questions for the next Podcast, please let us know.  If you want to participate in the Podcast, also please let us know.  Thank you.


https://soundcloud.com/nexusoft/nexus-podcast-e1-1

"We can’t find that track.

Did you try to access a private track while not being signed in?
Maybe the track has been removed."

Podcast removed already?

[tokyopotato]

Whoops.  Sorry guys, I posted it a little too soon!

I didn't realize it was still work in progress

But good feedback so far anyways.  We definitely want to make the questions and answers engaging.  That's why we ask for your input.

Do you have any questions you would like answered?  Just list them and I will put them in my next list.

Thanks!