After my “Initial Thoughts On Nexus” post blew up on Reddit, had been circulated on Discord servers, and even shared on Facebook… I realized I had left something out. It’s been great to see how many people enjoy my writing! Along with this exposure, came some new knowledge upon how the Nexus blockchain functions. It seems I’ve left out a crucial feature, It’s actually multi-dimensional. That’s right, here’s how each and every transaction gets processed.
Transaction Locks
The weight of a transaction is calculated based on how many nodes have verified it’s valid. The transaction is passed between multiple “trust nodes” randomly. After a certain amount of trust is built, from multiple nodes confirming it’s data is accurate, the more weight it carries as a valid piece of data. The algorithm depicting the “transaction lock” status, is based on a combination of time since it was locked, and number of nodes that have proved the data is correct.
Trust Locks
After the initial transaction lock is in place, a trust lock using proof of stake must interweave these sets of locks into a two-dimensional structure. As they’re chained together in this set time interval, and hashed together, they create a single trust lock hash. Once the hash is created, the trust node (using their stake) will sign off that it agrees on the data and it’s ordering. Other trust nodes are free to sign off on it as well. This links the trust nodes to each other through the same interval, which is essentially creating a consensus that it’s confirmed valid data. This second level lock (L2), has to verify the transaction level agreement and ensure that there was no “invalid data”, such as double spends.
If a trust node signs off on data that is verified by another node on the L2 locks, it will have its trust reduced, along with the trust of the L1 lock signers.
Miner Locks
At this stage, the transaction will be packaged into nice multi-dimensional pieces, with each containing their timespan (z-index), their frequency (x-index), and their amplitude (y-index). Amplitude can be understood as weight and trust giving validity to the data. Frequency can be seen as the transactions per second in that given interval. Timespan can be seen as the necessary grouping times on the L1 Locks. L2 Locks done with Trust and Holdings should contain only 3 interval hashes, locking all the data in each set of L1 objects. This then comes to the Miners, who hash the L2 hashes into a new hash including a nonce. Given it has a provable number of work, adding more weight to this interval data, and including Trust in their signature chain will further give validity to data. If this miner hashing the L3 lock assumes the data is good and doesn’t check it, the trust of the miner and their reward will be reduced. The combination of miner trust and total shares submitted of the L3 locks, determines how much Nexus they’ll earn for that interval. All the shares of miners are then hashed together into a merkle tree to give one L3 root hash. This is how it functions as a decentralized mining pool, and allows checks and balances between L1, L2, and L3 locks;
Transaction Validity
As all three levels are verified, anyone can see this structure grow and determine the validity of the minimum threshold they will accept. A simple L1 lock should be sufficient for micro-transactions, and should take no longer than 5-10 seconds to clear on the network. L2 locks will take 20-30 seconds based on the timespan in the z-index, and be secure enough for larger transfers such as purchasing a small car. L3 locks will take 1-2 minutes, but lock the data with all checks and balances, deeming it safe for spending at very large amounts. For the more paranoid, a few L3 locks may be determined for extra security.
In Conclusion
This multi-dimensional chain allows for CPU and GPU miners to get fair work, and makes transactions get confirmed on multiple levels(enabling better security), faster than ever seen before. This also builds the chain one second at a time, chaining the data in real time rather than at predetermined times, often known as “block time” with other cryptocurrencies. An MDC (multi-dimensional chain) does not have “blocks” such as bitcoin, and does not “tangle” transaction such as IOTA. It’s a simple multi level locking mechanism, done through checks and balances and spreading resource input and chain building into an “all the time” process. This allows node count to increase capacity in each lock level, and data partitioning to be spread across all nodes, giving it scale ability architecturally at whatever capacity the node count determines.
Sources:
NexusNewsletter, State of the Union Conference, and Collin Cantrell himself.
0 Comments