Nexus Wiki - User contributions [en]

Board:Maintenance

2025-05-06T03:47:48Z

Nexus wiki: Created page with "= Bounty Board Maintenance = ''This page is for administrators only'' == Weekly Maintenance Tasks == === Check Stalled Bounties === {| class="wikitable sortable" style="width: 100%;" ! Task !! Assigned To !! Last Edit !! Days Inactive |- {{#dpl: category=In Progress Bounties |include={BountyTask}:title,assigned_to |include=<%LASTMODIFIED%> |table=class="wikitable sortable" style="width: 100%;",Title,Assigned To,Last Modified,Days Inactive |tablerow=\n|-\n|%PAGE%|%TI..."

= Bounty Board Maintenance =
''This page is for administrators only''

== Weekly Maintenance Tasks ==

=== Check Stalled Bounties ===

{| class="wikitable sortable" style="width: 100%;"
! Task !! Assigned To !! Last Edit !! Days Inactive
|-
{{#dpl:
category=In Progress Bounties
|include={BountyTask}:title,assigned_to
|include=<%LASTMODIFIED%>
|table=class="wikitable sortable" style="width: 100%;",Title,Assigned To,Last Modified,Days Inactive
|tablerow=\n|-\n|[[%PAGE%|%TITLE%]]||%assigned_to%||%<LASTMODIFIED:date>%||{{#expr:{{CURRENTTIMESTAMP}} - %<LASTMODIFIED:ts>% / 86400 round 0}}
|noresultsheader=No in-progress bounties at this time.
}}
|}

=== Bounties Needing Review ===

{| class="wikitable sortable" style="width: 100%;"
! Task !! Submitted By !! Submission Date
|-
{{#dpl:
category=Bounties
|include={BountyTask}:title,assigned_to,status=Under Review
|include=<%LASTMODIFIED%>
|table=class="wikitable sortable" style="width: 100%;",Title,Submitted By,Submitted On
|tablerow=\n|-\n|[[%PAGE%|%TITLE%]]||%assigned_to%||%<LASTMODIFIED:date>%
|noresultsheader=No bounties awaiting review.
}}
|}

== Administrative Tools ==

=== Reset Stalled Bounty ===

To reset a stalled bounty (inactive for 14+ days):
# Edit the bounty page
# Change status from "In Progress" to "Open"
# Change assigned_to value to "Not assigned"
# Add a note to the talk page explaining the reset
# Notify the original assignee

=== Close a Bounty ===

To close a bounty that's no longer needed:
# Edit the bounty page
# Change status to "Cancelled"
# Remove Category:Open Bounties
# Add Category:Cancelled Bounties
# Add a brief explanation to the bounty page

=== Approve Completed Work ===

To approve completed work:
# Review the submission thoroughly
# If acceptable, edit the bounty page
# Change status from "Under Review" to "Completed"
# Remove Category:In Progress Bounties
# Add Category:Completed Bounties
# Arrange for reward distribution
# Notify the contributor with thanks

== System Maintenance ==

* Check template functionality monthly
* Update any broken links in resource sections
* Archive completed bounties older than 6 months to archive namespace
* Review and update categories as needed

Board:Help

2025-05-06T03:46:22Z

Nexus wiki: Created page with "= How to Use the Bounty Board = Our bounty board is a system for organizing and incentivizing contributions to our project. This guide explains how to use it effectively. == For Contributors == === Finding a Bounty === # Visit the Bounty Board main page # Browse available bounties by category or browse the full list # Click on any bounty to view its details === Claiming a Bounty === # Find a bounty you'd like to work on # Edit the bo..."

= How to Use the Bounty Board =

Our bounty board is a system for organizing and incentivizing contributions to our project. This guide explains how to use it effectively.

== For Contributors ==

=== Finding a Bounty ===

# Visit the [[Bounty Board]] main page
# Browse available bounties by category or browse the [[:Category:Open Bounties|full list]]
# Click on any bounty to view its details

=== Claiming a Bounty ===

# Find a bounty you'd like to work on
# Edit the bounty page
# Change the status parameter from "Open" to "In Progress"
# Add your username to the "assigned_to" parameter
# Save the page

=== Submitting Completed Work ===

# Edit the bounty page
# Change the status parameter from "In Progress" to "Under Review"
# Add a comment in the discussion page with links to your contribution
# Notify an admin (see the contact information on the bounty page)

=== Receiving a Reward ===

After your work is reviewed and approved:
# An admin will change the status to "Completed"
# Your reward will be provided according to the details on the bounty page
# The bounty will be moved to the [[:Category:Completed Bounties|Completed Bounties]] category

== For Bounty Creators ==

=== Creating a New Bounty ===

# Visit the [[Template:NewBounty|New Bounty template page]]
# Click "Create/Edit Bounty Task" (create a page with an appropriate name like "Bounty: Task Name")
# Copy the template and fill in all required fields
# Add detailed requirements and acceptance criteria
# Add appropriate categories at the bottom of the page
# Save the page

=== Managing Bounties ===

# Check [[:Category:In Progress Bounties|In Progress Bounties]] regularly
# Follow up with contributors who claimed bounties
# Review submitted work promptly
# Update status accordingly

== Bounty Statuses ==

* '''Open''' - Available for anyone to claim
* '''In Progress''' - Currently being worked on by someone
* '''Under Review''' - Work has been submitted and is being reviewed
* '''Completed''' - Successfully finished and reward has been given
* '''Cancelled''' - No longer available or needed

== Timeouts ==

If no progress is made on an "In Progress" bounty for 14 days, any admin may reset it to "Open" status and remove the assignee.

Board:Bounties

2025-05-06T03:44:31Z

Nexus wiki: Created page with "= Community Bounty Board = Welcome to our project's bounty board! This is where you can find tasks that need attention and earn rewards for contributing to our community. == How It Works == # '''Browse''' the available bounties below # '''Claim''' a bounty by editing its page and changing status to "In Progress" (don't forget to add your username) # '''Complete''' the task according to the requirements # '''Submit''' your work by updating the bounty page with links to..."

= Community Bounty Board =

Welcome to our project's bounty board! This is where you can find tasks that need attention and earn rewards for contributing to our community.

== How It Works ==

# '''Browse''' the available bounties below
# '''Claim''' a bounty by editing its page and changing status to "In Progress" (don't forget to add your username)
# '''Complete''' the task according to the requirements
# '''Submit''' your work by updating the bounty page with links to your contribution
# '''Receive''' your reward after review

== Current Open Bounties ==

{{#ask:[[Category:Open Bounties]]
|?Description
|?Difficulty
|?Reward
|format=table
|sort=Posted date
|order=desc
|limit=10
}}

[[:Category:Open Bounties|See all open bounties →]]

== Bounties by Category ==

* [[:Category:Coding Bounties|Coding Tasks]] - Programming and development tasks
* [[:Category:Documentation Bounties|Documentation Tasks]] - Help improve our documentation
* [[:Category:Design Bounties|Design Tasks]] - UI/UX and graphical work
* [[:Category:Maintenance Bounties|Maintenance Tasks]] - Help keep things running smoothly

== Submit a New Bounty ==

Have a task that needs attention? [[:Form:NewBounty|Create a new bounty →]]

== Bounty Status ==

* [[:Category:Open Bounties|Open Bounties]] - Available for anyone to claim
* [[:Category:In Progress Bounties|In Progress Bounties]] - Currently being worked on
* [[:Category:Completed Bounties|Completed Bounties]] - Successfully finished tasks

== Bounty Rules ==

# A bounty can be claimed by editing its page and changing status to "In Progress"
# If no progress is made within 14 days, the bounty returns to "Open" status
# Bounty rewards are distributed after task completion is verified
# All contributions must follow our project's guidelines and code of conduct

Main Page

2025-05-06T03:38:05Z

Nexus wiki:

== Nexus Wiki ==

A community-driven project for information about [https://nexus.io Nexus].

{{Special:AllPages}}

=== Developer Documentation ===

Under [https://nexus-wiki.org/index.php?search=&title=Special%3ASearch&profile=advanced&fulltext=1&ns0=1&ns3000=1 Advanced search], select the "Dev" namespace to include these pages.

{{Special:AllPages/Dev:}}

=== Community Board ===

Under [https://nexus-wiki.org/index.php?search=&title=Special%3ASearch&profile=advanced&fulltext=1&ns0=1&ns3000=1 Advanced search], select the "Board" namespace to include these pages.

{{Special:AllPages/Board:}}

=== News ===

Under [https://nexus-wiki.org/index.php?search=&title=Special%3ASearch&profile=advanced&fulltext=1&ns0=1&ns3000=1 Advanced search], select the "News" namespace to include these pages.

{{Special:AllPages/News:}}

=== Recent Changes ===

{{Special:RecentChanges}}

''Original content provided by [https://nexus.io Nexus].''

Board:Template:NewBounty

2025-05-06T03:36:45Z

Nexus wiki: Created page with "To create a new bounty, copy the following template, click "Create/Edit Bounty Task", and fill in the details: <pre> = Task Title Here = {{BountyTask |title=Task Title Here |description=Detailed description of what needs to be done |category=Coding |difficulty=Medium |reward=Any reward or recognition offered |posted_by=~~~ |posted_date={{CURRENTTIMESTAMP}} |deadline=None |status=Open }} == Detailed Requirements == Add detailed requirements here... == Acceptance Crit..."

To create a new bounty, copy the following template, click "Create/Edit Bounty Task", and fill in the details:

<pre>
= Task Title Here =

{{BountyTask
|title=Task Title Here
|description=Detailed description of what needs to be done
|category=Coding
|difficulty=Medium
|reward=Any reward or recognition offered
|posted_by=~~~
|posted_date={{CURRENTTIMESTAMP}}
|deadline=None
|status=Open
}}

== Detailed Requirements ==

Add detailed requirements here...

== Acceptance Criteria ==

* Criterion 1
* Criterion 2
* Criterion 3

== Resources ==

* Link to relevant documentation
* Link to code repository
* Other helpful resources

[[Category:Bounties]]
[[Category:Open Bounties]]
[[Category:Coding Bounties]]
</pre>

Remember to adjust the categories at the bottom based on the type of bounty.

Board:Template:BountyTask

2025-05-06T03:34:24Z

Nexus wiki: Created page with "<div class="bounty-task"> <table class="wikitable" style="width: 100%;"> <tr> <th colspan="2" style="background-color: #4CAF50; color: white; text-align: center;"> {{{title|Untitled Task}}} <span style="float: right; padding: 2px 8px; background-color: {{#switch: {{{status|Open}}} | Open = #2ECC71 | In Progress = #3498DB | Under Review = #F39C12 | Completed = #95A5A6 | Cancelled = #E74C3C }}; border-radius..."

<div class="bounty-task">
<table class="wikitable" style="width: 100%;">
<tr>
<th colspan="2" style="background-color: #4CAF50; color: white; text-align: center;">
{{{title|Untitled Task}}}
<span style="float: right; padding: 2px 8px; background-color: {{#switch: {{{status|Open}}}
| Open = #2ECC71
| In Progress = #3498DB
| Under Review = #F39C12
| Completed = #95A5A6
| Cancelled = #E74C3C
}}; border-radius: 3px;">{{{status|Open}}}</span>
</th>
</tr>
<tr>
<td style="width: 20%;">'''Description:'''</td>
<td>{{{description|No description provided}}}</td>
</tr>
<tr>
<td>'''Category:'''</td>
<td>{{{category|General}}}</td>
</tr>
<tr>
<td>'''Difficulty:'''</td>
<td>{{{difficulty|Medium}}}</td>
</tr>
<tr>
<td>'''Reward:'''</td>
<td>{{{reward|None}}}</td>
</tr>
<tr>
<td>'''Posted by:'''</td>
<td>{{{posted_by|Anonymous}}}</td>
</tr>
<tr>
<td>'''Posted date:'''</td>
<td>{{{posted_date|}}}</td>
</tr>
<tr>
<td>'''Deadline:'''</td>
<td>{{{deadline|None}}}</td>
</tr>
<tr>
<td>'''Assigned to:'''</td>
<td>{{{assigned_to|Not assigned}}}</td>
</tr>
<tr>
<td>'''Contact:'''</td>
<td>{{{contact|See discussion page}}}</td>
</tr>
</table>
</div>

News:Project Update 2025-04-19

2025-04-26T13:10:36Z

Nexus wiki: Created page with "= Summary = == Development Focus == * Extensive rigorous testing in progress * Current build: 5.1.5-rc13, build 8 * Major bug fixes and race condition checks completed == Architecture & Synchronization == * New mint architecture finalized — simplified and efficient * Chain state value synchronization improved — now stable * Sequential sync feature finalized — will be enabled by default == Node Deployment == * Bootstraps deployed to new nodes * TradeOgre e..."

= Summary =

== Development Focus ==

* Extensive rigorous testing in progress
* Current build: 5.1.5-rc13, build 8
* Major bug fixes and race condition checks completed

== Architecture & Synchronization ==

* New mint architecture finalized — simplified and efficient
* Chain state value synchronization improved — now stable
* Sequential sync feature finalized — will be enabled by default

== Node Deployment ==

* Bootstraps deployed to new nodes
* TradeOgre exchange is believed to be back online and stable

== AI & Use Case Development ==

* Initial architecture for AI use case funding underway
* White paper and presentations being prepared

== Hard Fork & Release Timeline ==

* Preparing for hard fork deployment
* 6.0 Beta release timeline:
* Public beta for ~1 week
* Full release after 1 week
* Hard fork activation: 2 weeks after initial beta release

== Impact for Users ==

* Address sanitizer results are clean
* Long-term wallet stability significantly improved

== Future Plans ==

* Final testnet activation
* Transition from 5.1.5 to 6.0 incoming

= Transcription =

Hey, guys. Today is, Friday, 04/18/2025, and this is this week's development update. Don't have a whole lot to report on the new development front. I've been doing a lot of rigorous testing. I have 5.1.5-rc13, I think -8 now, build number eight, out.

I've been continuing to run address sanitizer and fix any bugs that come up. Also, thread sanitizer to make sure that I'm checking for race conditions. I'm finishing up the build out. I've changed my architecture for how we're gonna be doing the the mint for the new funds, But that is, much more simplified now, thankfully. So I've also been working on synchronization of some certain values that are calculated through the actual chain state, and that's all looking really nice and solid now.

I've deployed a couple of bootstraps on some new nodes. I also got the sequential sync pretty much ready and polished, so that's gonna be something that's gonna be enabled by default for everyone on the newest updates. And I've also been preparing and finishing, the initial stages of our architectural development for one or two use cases and developing the funding for the artificial intelligence one and getting those presentations ready and the white paper and then getting us ready to have this hard fork deployed. So as I said earlier, once we go to beta out, we'll probably run that beta in public for about a week, and then we'll be ready for a full release, which will have a, timer in it. So most likely, we'll have the time lock set for two weeks after the release of the initial beta, which is gonna be a 6.0 beta.

And then we will, let it run for a week and then really set it to full. And then it'll be one week from there before it activates. And once it activates, we will get all of these new pursuits moving. So I believe, TradeOgre is up and running. I'd have to double check with them, but I've gotten them to update.

I got them online, making sure everything's solid there. And like I said, all of the address sanitizer messages are coming back clean now, so it should be much more stable. What that means to you is, if you've ever had, you know, the wallet potentially go down over long periods of time, this prevents that from happening anymore. So it's it's very solid under the hood. I found a lot of very, very, very important bugs to resolve over the last week or two.

So a lot of it is just watch and wait in this, these ending phases of this testing. And I'm getting the test net ready to go and doing a final test and activation, and then we shall be ready to release the beta for 6.0 instead of 5.1.5 and get it packed and shipped and ready to go out the door. So thank you again, guys, for your patience this week, and, I will give another update next week.

News:Project Update 2025-04-12

2025-04-26T13:09:59Z

Nexus wiki: Created page with "= Summary = == Development Focus == * Sanitizer Testing: Heavy use of AddressSanitizer, ThreadSanitizer, and UndefinedSanitizer on live mainnet nodes * Bug Fixes: Found and resolved 3-4 significant bugs causing undefined behavior * Hardening Soft Float: Addressed casting issues to improve stability * Resolved macOS Core Connection Issue: OSX instability issue resolved (previously affecting Ken) == Syncing Enhancements == * Sync Test from Block 0: Completed in ~1 hour..."

= Summary =

== Development Focus ==

* Sanitizer Testing: Heavy use of AddressSanitizer, ThreadSanitizer, and UndefinedSanitizer on live mainnet nodes
* Bug Fixes: Found and resolved 3-4 significant bugs causing undefined behavior
* Hardening Soft Float: Addressed casting issues to improve stability
* Resolved macOS Core Connection Issue: OSX instability issue resolved (previously affecting Ken)

== Syncing Enhancements ==

* Sync Test from Block 0: Completed in ~1 hour and 3 minutes
* Sequential Sync Mode: Near production-ready; improves sync speed by optimizing hard drive read patterns
* Legacy Contracts: Achieves 20-25k contracts/second
* Tritium Optimization in Progress: Using Valgrind/Callgrind for performance profiling

== Upcoming Release ==

* Target Version: 6.0.0 (Hard Fork)
* Current Version: 5.1.5rc13.6
* Testnet Activation: Planned with Neal, followed by release readiness
* Release Timeline: Estimated 2 weeks to 6.0 release, then 1-week activation timer

== Use Cases & Funding ==

* AI Use Case: Progressing well, securing funding, finalizing whitepapers
* Media Use Case: Starting development—backend setup and dev servers

== Future Plans ==

* Expect 6.0.0 Hard Fork activation by end of April

= Transcription =

Hey, guys. Welcome to the development update. Today is Friday, April 11, 2025, and I'm gonna be going through what has been completed this week. So mainly this week, I've been focusing on debugging and hardening. So if anybody's familiar, there's something called address sanitizers and thread sanitizers and undefined sanitizers.

I was running that quite a bit last week, but I've been running that even more this week, running on live nodes, running over the main network, and making sure everything's really solid, which I think as of late, I think I got three or four pretty good bugs that would cause undefined behavior. So this is really important because if anybody's know, sometimes undefined behavior can manifest in just the undefined ways. So, you know, your node could be running, and then next thing you know, it's not generally is the way that it's experienced.

But I've been very happy to find these number of issues. I also hardened out some of our soft float. We basically had some casting issues and things like that. Address sanitizer, non defined sanitizer have been actually really, really helpful, especially running on main network nodes that are receiving lots of API requests. I guess I think I mentioned last week I solved the bug that Ken was having. There was an instability issue with OSX. Anybody that was having trouble having it connecting to core, that's resolved now.

I believe Kendall should be submitting that in. I've been having some Internet outages in and out this week, so I haven't been able to get online as much as I would have liked to as far as doing some codes on the test net, or even over the main net. But I have been getting the syncing. I just did a actual sync test from block zero, and it synced all the way in about one hour and three minutes, which is pretty dang good, which means that I synced all the way in about an hour. That's obviously with really fast Internet, which I did this just as a local test, so that's not accounting for external bandwidth.

But the sequential sync code that I've gotten, I've gotten that, I think pretty close to being ready to be deployed as a a default feature. So that'll also help with people syncing from other people's hard drives because it basically takes advantage of sequential reads. Basically, reading big batches off your hard drive a lot faster than, you know, doing random reads. You know, solid state drives are a little bit better at random reads, but our drives are, pretty good. Once they get wound up, they're gonna read really quickly.

So I got that. Like I said, I've had to fix some of the bugs in that, the stability wasn't quite where I liked it to be. But now I've been sinking like crazy off of it. And like I said, it delivers blocks. I mean, down in the legacy contracts, it does up to twenty, twenty five thousand contracts per second as far as download speed.

I'm working on improving the speed on the tritium ones. Those calculations should be a lot faster, so that's something I'm investigating. I'm using a tool inside Valgrind called Callgrind that's telling me basically what's being called. It does basically profiling, so it tells me how what parts are fast or what parts are slower. So, ideally, these, these bugs should be just about wrapped up, this week.

And like I said, Neal and myself will be getting on the test net and be doing a test net activation. And once we feel pretty confident in that and we have a couple activations right through, Then we're gonna get ready for our release. And once the wallet is released, then it's gonna be a one week timer. So make sure and this is a full release. This will be version 6.0.0.

I'm currently on version 5.10.5, release candidate 13, build six. I added an extra build, hyphenation so that anytime I'm doing slight little tweaks or bug fixes, I can just iterate the build number versus release candidates or subsets of features underneath the actual, the minor version number. So anytime we iterate a major version number, that's going to be a hard fork. So once for six point zero point zero, that will be our hard fork. And like I said, I think Kendall will be getting some of those builds out next week.

And like I said, we're starting on couple use cases actually, which is the AI one is moving along very well, and I'm securing funding on that. Ideally, I've been waiting on some of the funders to make sure that we have our white papers all just about wrapped and good to go. So I'm feeling pretty confident on that. And then the media use case is we're starting the initial development on that as far as getting development servers and building some of the back end. So it's all pretty much ready to go.

I hope to have all the test net testing done by the end of next week so that I'll be able to give you an official timeline on the release. Once all the test net testing is done, I'll probably do another week of hardening like I've been doing this week, and then have that finally released at the end of that week. So I'd estimate about two weeks from now, we should have six point o out and then one week to activate. So most likely by the April, we should be good to go on the activation, and that's gonna start a cascade of a lot of new possible outcomes, such as getting ourselves on new exchanges and solving a lot of those issues. So, again, thank you everybody for your patience, and I will give you another development update in one more week.

Take care, everybody.

News:Project Update 2025-04-05

2025-04-26T13:09:22Z

Nexus wiki: Created page with "= Summary = == Current Progress: Bug Fixes & Crashes == * Week focused on hardening and sync tests * New bootstrap up and running * Pearl scripts being updated (previously down) == Technical Updates == * Bootstrap size reduced by ~2GB → now ~19GB vs. 21GB (≈10% improvement) * Stability issues on OSX identified and fixed * Bug: daemon crashing * UUsed address sanitizers to find issues in casting and supply calculations * New beta should be much more stable, es..."

= Summary =

== Current Progress: Bug Fixes & Crashes ==

* Week focused on hardening and sync tests
* New bootstrap up and running
* Pearl scripts being updated (previously down)

== Technical Updates ==

* Bootstrap size reduced by ~2GB → now ~19GB vs. 21GB (≈10% improvement)
* Stability issues on OSX identified and fixed
* Bug: daemon crashing
* UUsed address sanitizers to find issues in casting and supply calculations
* New beta should be much more stable, especially for OSX users
* Some bugs potentially affecting iOS and Android builds now resolved

== Ongoing Debugging ==

* Running sanitizers from block zero to ensure:
* Stable sync
* Correct memory allocation
* Several bugs causing random, undefined behavior now fixed

== Testnet & Hard Fork ==

* Testnet launching tomorrow with Neal
* Hard fork features nearly complete
* Legacy code turned off
* Working on indexes for total supply and fee assets
* Fees will be updatable via community vote, avoiding future forks
* This fork is key to getting listed on MEXC

== Builds & Releases ==

* Kendall to release beta builds next week
* New UI + daemon fixes (w/ Krysto)
* Current version: v5.1.5-rc12.2
* Next beta: likely build 3 or 4
* Hard fork version: v6.0.0
* One-week deadline to update wallets post-release
* Legacy coin burn will be tallied at activation

== Timeline ==

* Assuming smooth testing:
* Beta: next week
* Hard fork release: mid-April
* Exchange listing process starts after

== Exchange & Market ==

* TradeOgre fix instructions sent
* XeggeX: some users successfully recovered balances
* Reminder: "Not your keys, not your crypto"

== AI & Media Use Cases ==

* Funding + white papers underway
* Media platform architecture wrapping up
* Development starting soon (servers, front end)
* These are strategic for adoption and growth
* Full media details to come at a later time.

== Future Plans ==

* Interest in decentralized exchanges, including fiat support
* Idea: "Local Nexus" like LocalBitcoins
* Matching + reputation system for secure cash trades

= Transcription =

Hello, everybody. Welcome to this week's update. Today is Friday, April 4, 2025. So this last week, I've been mainly doing a lot of hardening, doing some sync tests. I got the new bootstrap up and running. I'm updating some of the Perl scripts. Those seem to have been going down. So if you've noticed that the bootstrap is a little out of date, we're getting that back online, but the final numbers are about two gigabytes reduced in your disk utilization. So I'm using about 19 gigabytes versus 21 gigabytes prior to that, which is a pretty decent improvement. That's about a 10% improvement. 10% less disk space, store an extra movie or whatever else on your disk, which is good.

Then, there's also been some stability. So I've had some bug reports. One reason we haven't released the beta yet is Kendall was having trouble getting it to work on OSX. The daemon kept coming down. And so I've been investigating that. If anybody understands how software is investigating and finding some of these bugs could be very quite difficult and time consuming. But if anybody has had stability issues on OSX as far as having difficulties with the daemon staying up, the wallet staying up, that should be resolved with this new beta. So we've been running address sanitizers on it, and I found an issue in some of the casting and also in some of the supply calculations that is, now resolved. So that's on the merging-sync branch if you wanna keep up to date with the newest code.

I've also just uncovered another bug that I've been working on tonight. I've been basically synchronizing the chain from block zero and running all sorts of sanitizers on it to make sure that everything is completely stable. Make sure all of our memory allocations are correct and everything's really tight. So I'm pretty sure this next release should be much, much more stable if anybody's had any issues, especially for OSX. But some of these bugs that I found actually would create very random undefined behavior.So, it's hard to say exactly how it would manifest on your device specifically. And some of these actually might have been affecting some of the stability in our iOS and Android builds. So that's good. I'm glad I got those. So, basically, a lot of hardening, a lot of buttoning up.

Neal and myself are firing up the testnet tomorrow. We're gonna be getting some of the code into live testing as far as getting our testnet running and then doing an activation with all of the new features for the hard fork. Like I said, most of the hard fork features are just about built out. I have all of the legacy turned off. A lot of the monitoring.
I'm just working out the indexes for the total supply and then having that transaction come out at a specific block, and then having our fees assets so that we'll be able to dynamically update our fees. So we'll be able to do that through community vote, which means we won't have to do a hard fork as we modify the fees as we continue going forward. And then this has been the only holdup that we've had as far as getting listed. We're still in contact with the MEXC listing team. So we are pretty much good to go once we get this hard fork out the door.

Kendall should have some, beta builds out for you next week. He's been waiting on me to get this fix in, and I found a couple fixes. And as I said, I've been synchronizing from block zero. Everything's been running pretty smooth, and I've been uncovering a few other little idiosyncrasies. TradeOgre should be getting back online, if not already. I gave them instructions to fix their node a number of days ago. So I will check in again with them and see how they're doing on that. And then, hopefully, sometime early next week, Kendall will be able to get you a new build with some of the new UI changes Kendall and Krysto have been working on and some of the new daemon stability fixes. We're currently on 5.1.5rc12.2, but build number, revision number will be three or four. I think by the time we get that beta out, and then the hard fork will be version 6.0.0. And once that wallet is fully released and ready to go, we will have, a one week time limit for you to get updated. So make sure now if you still have legacy coins to move your legacy coins over. The final number for the amount of legacy coins that have been burnt will be tallied at the point of activation, which will be one week after that wallet is released.

So assuming everything goes well on our testnet with Neal and myself this weekend, and our beta builds next week, we should be able to have it out the door end of next week, maybe early the week after. So we're looking at activation sometime in mid April, which means that we can start the listing process to get added to additional exchanges. I've also been waiting to discuss with the market maker. They have the capability to get us on to other mid-range exchanges such as Gate.io or any of the others. So that's another good sign. If you haven't been, in contact with Xeggex, I have had confirmation from some people in the Nexus community. They have been able to recover their account and show the balances that are available there. So if you haven't done so, let's see if we can keep doing that. See anybody that has coins. I hope that you can get them off.

And for the future, not your keys, not your crypto. This is one of the problems with centralization, exchanges, all of that. We need to figure out solutions against that. So I would really like to start some more discussions about decentralized, exchanges, especially relating to fiat. So if anybody's interested and would like to, spitball some ideas with me, I'd like to do so. Maybe even creating, like, a local nexus, like local Bitcoin used to be, where you can buy and sell and trade. We don't even have to have custodial wallet services where you can just do a matching system and a reputation system so that people can buy and sell nexus for cash. And, I mean, Bitcoin too.I mean, it could be a really cool big platform if anybody wants to take that on. And then as I said, AI use cases moving forward. I'm working on the funding prospects. I've been having a few people just waiting to get some of the white papers done. So, that's moving forward, which is really good.

And then the other media use case is moving forward. Just finishing some of the preliminary architectures, and we're gonna start modeling and developing some of that and getting some servers and building some of the front end. And we'll be able to give you guys some more information on that as that develops. And so I just said, these are two strategic use cases that should help us get the proper amount of adoption. The AI being, I think, a huge new industry and all that liquidity moving into our market could be substantial and really important for our growth.

And then also some of the connections I have related to media. We should be able to start getting a good footing with the new media use case. Something that kind of works anonymously with the AI, but it'll be a very powerful platform. But I will omit details on that until the time of my choosing in the future. Until then, everybody, I hope you have a great weekend, and we will speak again next week and hopefully have the hard fork out a number of weeks after.

News:Project Update 2025-03-29

2025-04-26T13:08:35Z

Nexus wiki: Created page with "= Summary = == Bug Fixes & Crashes == * Resolved a few crashes recently * If not updated, the current build is 5.1.5rc12.2 == Syncing Improvements == * Improved syncing speed, especially from hard drives * Reduced dataset size by ~17 GB through better indexing * Bootstrap file size also reduced by 1–2 GB == Development Progress == * Working on merging branch 6.0 (some time locks set, but delayed) * Plan to release the wallet in the next 1–2 weeks == Use Cases..."

= Summary =

== Bug Fixes & Crashes ==

* Resolved a few crashes recently
* If not updated, the current build is 5.1.5rc12.2

== Syncing Improvements ==

* Improved syncing speed, especially from hard drives
* Reduced dataset size by ~17 GB through better indexing
* Bootstrap file size also reduced by 1–2 GB

== Development Progress ==

* Working on merging branch 6.0 (some time locks set, but delayed)
* Plan to release the wallet in the next 1–2 weeks

== Use Cases in Development ==

* Three new use cases under active development
* One related to media
* Another connected to an existing real-world popular app

== Exchange Issues ==

* Addressing challenges related to Xeggex
* Plans for listing on new exchanges

== Hardware & Research ==

* Doing hardware-related research (schematics available on request)
* Applications may extend to mining, communication nodes, and even
propulsion

== Community & UI ==

* Planning to revive the beta testing channel
* UI updates being developed by Kendall and Krysto

== Future Plans ==

* Additional use cases and features in development
* More updates expected in next week’s development update.

= Transcription =

Hey, guys. Welcome to the development update for today, Friday, March 28. This last week, I've spent a bit of time working and tracking down some bugs. We had a couple crashes that I've had to resolve. If you're not on the newest, it is 5.1.5rc12.2. That would be the build number. I found some stability issues. I've been doing some testing and improvements on the syncing code again. As I said, I did a sequential sync that I've gotten it to sync much faster off of hard drives. So, I got a fresh new, sync that I'm actually updating on some of our our bootstrap nodes. I think that should cut about 10 or 15 gigabytes off of the dataset just because of the way those were built. Basically, the indexes were built after it was already synced, and so I wasn't actually overriding any of that, data chain data. So it should cut quite a bit off. I'm seeing pretty good reduction, I think, 17 gigabytes. So that should help improve the download speed. It cut a few hundred megabytes off of the actual bootstrap file, so that uncompressed should be, yeah, about a gigabyte or two, which is good. And that should also help the sequential sync since the data was written in that, more consistently.

And then, I'm just getting getting ready for the merging-6.0. If you wanna see that, that's the branch that I've been working on. I've got some of the time locks set, but I did not meet my mark for this week as far as getting it out the door. We've got a couple more things to go on that. I'm also working on a couple new use cases. I said one for media. I also have another really cool one. This is gonna be used in in the real world based off of an app that has a pretty large usage already. So that's another one. So currently, we have about three use cases that are in the development, which is good. I definitely see good things coming for us in the future. Once we get on some new exchanges too, I've been seeing that's a big issue. It's unfortunate kinda what's happened with Xeggex.

But, again, we'll get through this, and, we'll get all these these challenges. You know, anything that, doesn't kill us will make us stronger. And, I mean, I think by now, it's pretty easy to see that Nexus is here to stay. We ain't going anywhere. Everybody can see my dedication and passion for the project. And there's a lot of different facets to it. One of such facets I've actually been working on this week. I don't talk too much about it publicly. But anybody that's interested, if you wanna find out some of the new research that I've been doing as far as hardware is concerned, I'd be happy to share some of the schematics. Those things I think will be very beneficial for not only our mining industry, but for the communication nodes and eventually propulsion, which is really interesting.

So, that pretty much concludes us for this week. Short update. I hope to have more to report to you guys next week. As I said, a little bit more lab work this week and kinda bug fixes, so I didn't get as much future development done as I would have liked to. But I do would like to see that next week. So looking for the next week or two to have that wallet out the door. We'll create a beta testing channel or we'll revive that beta testing channel to get you guys starting new builds, and I think there's some UI updates that Kendall and Chris have been working on as well. So until next time, guys. We will speak again next week.

News:Project Update 2025-03-21

2025-03-25T13:53:08Z

Nexus wiki: Created page with "= Summary = == Release Candidate Update == * Pushed code for version 5.1.5RC12 * Build identifier: "-1" * Users should update to this version to stay current == Sync Improvements == * New branch: merging-sync for better syncing quality * Added new CLI argument: sequential sync * Optimized for slower computers and hard drives * Achieved 2x speed improvement * Exploring ways to reduce bootstrap/database size (currently 50–60 GB) == Activation and Timeline == * Acti..."

= Summary =

== Release Candidate Update ==

* Pushed code for version 5.1.5RC12
* Build identifier: "-1"
* Users should update to this version to stay current

== Sync Improvements ==

* New branch: merging-sync for better syncing quality
* Added new CLI argument: sequential sync
* Optimized for slower computers and hard drives
* Achieved 2x speed improvement
* Exploring ways to reduce bootstrap/database size (currently 50–60 GB)

== Activation and Timeline ==

* Activation timestamp set for release in one week
* One-week window for activation to continue mining/staking
* Legacy chain holders: ~2 weeks left to move coins

== Code Development ==

* Ongoing progress on merging-6.0 branch
* Code running smoothly

== Xeggex Exchange ==

* Uncertainty due to potential malfeasance
* Xeggex likely not returning

== Exchange Listings ==

* Working toward MEXC exchange listing
* Engaged with a market maker to explore more exchange opportunities
* New exchange listings expected to benefit market activity

== Community Support ==

* MEXC listing requires significant fees
* Price increase on TradeOgre would help reduce listing costs
* Community contributions could aid in securing more listings

== Mobile Apps ==

* Android version should be back online soon
* iOS version will follow post-hard fork, aiming for App Store release

== Future Plans ==

* Additional use cases and features in development
* More updates expected in next week’s development update

= Transcription =

Hello, everybody. Welcome to the development update for March 21, 2025. I've just recently pushed code for 5.1.5-rc12, so that's release candidate twelve. You'll see hyphen one ("-1") for the build number. If you're up to date and wanna stay up to date with the newest cores, that's the one that you wanna be using. If you're wanting to play around with any of the new sync code, you can check out the merging hyphen sync ("merging-sync") branch that improves the syncing quality. There's a new command line argument called "sequential sync" that should help synchronizing from more hard drive slower computers. Helps improve the sync speed. I've gotten at least a two times speed up on that. I'm also seeing if I can reduce the size of the bootstrap and the overall database. Right now, it looks like it's 50 or 60 gigabytes. I might be able to knock some gigabytes off of that.

And as far as the activation time stamp I have, set, we're working towards releasing it by, a week from today. I'll give you guys further information, in Telegram next week, but there will be a one week expiration time on that. So there will be one week for you to be activated if you wanna keep mining and staking. So make sure that you keep up to date with that. And that also gives you about a two week timer now if anybody is still holding legacy coins on the legacy chain, make sure to move those coins over. The code is coming together very well. It's running smooth. The "merging-6.0" branch is the one that I'm mainly doing work on for that. And that just about wraps it up.

As I said, we'll, once we get this hard fork, we're kind of in a little bit of a limbo between Xeggex. It looks like their hack might have some malfeasance in you know, associated. I'm not sure. I can't point any fingers, but I would not expect Xeggex to be coming back, unfortunately. So we are moving forward with additional exchange listings. We have the MEXC listing that we're working towards, and then also I've been in contact with the market maker. We're gonna be discussing terms with them, see if they'll be able to help us get on to some of the other exchanges. I think new exchanges will, be nice and refreshing for our markets. But in the meantime, anybody that wants to help out, as I said, we have a pretty large listing fee for MEXC. So those of you that are willing to help, the more, we can get the price up on TradeOgre, then the less NXS it will take for us to get listed, which means that we will be able to get listed on more exchanges, and have more funds available to do more things. So if anybody wanted to take that into their hands, I should be, having a little bit of liquidity. I'm gonna be buying some more, hopefully, soon in the next few months.

Lots of things happening in my personal life that I should say are, looking, looking good. So I will, keep you guys up to date for next week's development update. Ideally, like I said, we would like to get it out the door in one week. The Android should be back online. And then after this hard fork, I'm gonna be getting the iOS wrapped up so that we can get the iOS release into the App Store. And then I'm also working on another use case, some really cool things. So, I will, keep you guys in the loop and talk to you next week.

News:Project Update 2025-03-15

2025-03-16T02:01:35Z

Nexus wiki: Created page with "= Summary = == Alternative Media Tool == * Emerging markets with a larger audience than mainstream media * New contacts from the SaaS conference to aid development == Podcast Launch == * Weekly discussions on Nexus, current events, and blockchain adoption * Aimed at engaging a broader audience beyond blockchain enthusiasts == AI Architecture Development == * Moving from architectural planning to actual development * Drawing comparisons to Hugging Face and i0.net *..."

= Summary =

== Alternative Media Tool ==

* Emerging markets with a larger audience than mainstream media
* New contacts from the SaaS conference to aid development

== Podcast Launch ==

* Weekly discussions on Nexus, current events, and blockchain adoption
* Aimed at engaging a broader audience beyond blockchain enthusiasts

== AI Architecture Development ==

* Moving from architectural planning to actual development
* Drawing comparisons to Hugging Face and i0.net
* Discussed GPT-5’s paradox: more parameters but potentially weaker
intelligence due to self-training

== Hard Fork Progress ==

* Merging TLS by integrating the embed TLS library
* Work on X509 certificates for enhanced security
* Reducing overhead by deprecating legacy code after the fork
* Indexing improvements for proof, address, and coin tracking

== Google Play & Apple Wallet ==

* Android wallet issue with Google ID resolved; returning to Play Store
* Apple wallet rollout expected after the hard fork

== UI Enhancements ==

* Kendal & Krysto have implemented major UI changes
* Beta testers can reach out for early access

== Future Plans ==

* More hands-on coding next week after heavy architectural work
* Finalizing hard fork code
* Continued development of AI initiatives and alternative media tools

= Transcription =

Hello, everybody. Welcome to the development update for Friday, March 14, 2025. I'll keep this one rather brief. Most of this week, I've been doing, use case architectural development, on the two primary use cases. As I said, the one that we're focusing on with alternative media, that being a massive new emerging market, many more viewers in alternative media than all of the actual collective mainstream media combined. So developing that tool, that's gonna be really powerful. And as I said, from the SaaS conference, I developed a lot of new contacts that will be really, really beneficial for that.

Item number two, I'm drafting some initial subjects and structures for a podcast that I'm going to be releasing. That's going to most likely be a weekly podcast discussing things that are related to Nexus, current events, everything else like that. That'll be on a separate website. Something to kinda keep content going, help kinda bring people in that may not necessarily be entirely involved in blockchain.

And then number three on the AI, I've been drafting some of the architectures for that. I've been working with, some of my partners, developing some of our priority plans, some of the initial architecture, our priorities, as I said. So that's coming along pretty well. We're getting we're getting down into, you know, out of the architectural development and into more actual hard development. And as I've stated before, that's going to ideally bring a lot of liquidity in the Nexus. If anybody's seen Hugging Face, that's, not close to what we're doing, but that's a huge new emerging platform. And, it's valued in the hundreds of millions. Or io.net is another one that is completely different, but similar. Basically, facilitating the, you know, direct computational capabilities for artificial intelligence.

If anybody actually wasn't aware, ChatGPT 5 was actually releasing, it found out to be a little bit dumber even though it had more parameters because it trained off of itself, right? It actually, some of its input training data was actually, um, some of its output data from GPT 4, which that throws an interesting wrench in the idea of artificial intelligence right now because people have primarily thought of artificial intelligence as being something that will
develop itself. But now, we see that going from GPT 4 to GPT 5, it actually got stupider, because it's good at mimicking human intelligence, but they don't seem to quite have abstract reasoning or capabilities beyond that. So, by simply feeding itself, you could call it ouroboros, it, became dumber. Which is an interesting thing to ponder. And some of these things are also gonna be discussed more in-depth on the podcast. I wanna get some really good juices flowing on that.

On the hard fork, I have basically been working on the merging-tls. When I was in London, I met up with Wilder.Earth, one of the founders, Mike, and we got some of the priorities, so I've been kinda juggling that a little bit. Merging-tls is basically porting in the embed TLS library. I'm working on the X509 certificate. So a lot of that coding is actually being done offline right now, but that's gonna make us completely portable from openssl, especially after this hard fork because we're gonna be able to deprecate all the legacy code. Then I've been aggregating some of the indexing functions for index proof, index address, and also adding in basically, an index that derives the current amount of coins on Tritium so that we can use that, make sure that's consensus safe and then also brushing up the unit tests. So, I'll be, be able to do a lot more of the actual coding next week. I've been doing a lot of architecture this week. So, ideally, I would like to see that. So keep your eyes, the branches that I'm working on are typically merging, merging-tls and merging-6.0, with hyphens, obviously.

We also finally dug through all the paperwork and we got the issue resolved with the Google ID. So you should be seeing our, uh, Android mobile wallet back in the Google Play Store. And that also sets the stage for our Apple, which is very nice. So we should be able to get those out. And as I said, morning to time all of those, those will be released, fully after this hard fork. And then the hard fork code should be done relatively soon. And as I said, Kendal and Krysto have also done a lot of UI changes, so that's gonna also be included in this next release. So keep your eyes on betas. You can, message Kendal and Krysto if you wanna use any of the betas, and I will talk to you guys next week.

News:Project Update 2025-03-10

2025-03-11T13:49:35Z

Nexus wiki: Created page with "= Summary = == Hard Fork Progress == * The hard fork is almost complete * A beta wallet release is expected next week * The final wallet release will follow a week after. == Front-End Updates == * Many front-end improvements have been made * Updates are first being implemented in the 5.1.5 core, then moving to the 6.0 core == Google Play Store & iOS Wallet == * Delays due to missing paperwork, but progress has been made * Mobile wallet should be available on the Pl..."

= Summary =

== Hard Fork Progress ==

* The hard fork is almost complete
* A beta wallet release is expected next week
* The final wallet release will follow a week after.

== Front-End Updates ==

* Many front-end improvements have been made
* Updates are first being implemented in the 5.1.5 core, then moving to the 6.0 core

== Google Play Store & iOS Wallet ==

* Delays due to missing paperwork, but progress has been made
* Mobile wallet should be available on the Play Store soon
* iOS wallet release will follow

== Exchange Listings ==

* MEXC listing expected post-hard fork
* More exchange listings planned to improve liquidity
* Encouraging trading on Trade Ogre to strengthen MEXC negotiations

== Artificial Intelligence & Distributed Computing ==

* Initial project planning and development started
* Dedicated one day a week to development
* Strong interest and use cases lined up

== Community Involvement ==

* Encouraging bug reporting during beta testing
* Emphasizing the communal effort to increase liquidity for better exchange deals
* Supporting trading efforts to enhance market stability

== Future Plans ==

* Hard fork completion will unlock funds for exchange listings
* Ongoing updates and new features in the pipeline
* More details on upcoming developments to be shared soon

= Transcription =

Hey, guys. Welcome to this week's development update. I've just been getting wrapped up with a hard fork. It looks like we should be on track to be getting at least a beta wallet release out next week. We're working on another release.

There's been a lot of frontend adjustments that have been made, a lot of, uh, things that have been completed. So we're getting that done with the 5.1.5 core initially, and then we're going to be pushing that into the 6.0 core. We also have been searching around for some paperwork to get added into the Google Play Store. That's been something that's been snagging. If anybody noticed that it was unavailable in the Play Store, that is the primary reason.

We have since found that, thankfully. So we are starting the process of getting the mobile wallet added into the Google Play Store, and then the iOS wallet will be following shortly thereafter. As I said, the mobile launch will be following after the release of this hard fork. This hard fork is also very important because this is going to help get us some funds to get listed on some new exchanges. So we're still in the talks with MEXC post hard fork.

We're going to be getting listed on there, which should help drive more liquidity into our markets, getting on a better exchange. We've been having some bad luck with exchanges lately, but something very easily remedied. So that is pretty much where we're at. I've been doing the artificial intelligence. We're working on the distributed computing element of it, currently.

Starting some of that development. I'm doing that on, uh, at least one day a week. We're also doing another use case, as I stated, that, uh, we started drafting some of the initial project plan and developing that one out. I have a lot of people lined up to be able to start using it once it's complete. So that's gonna be another really powerful use case.

The two of those together combined with a few good new exchange listings, I think will be very beneficial for us. So keep your eyes peeled for some new, uh, I think we're doing beta next week. With the 5.1.5 core, please report any bugs. If you find them, report them to Neil. Keep your eye on the project plan.

And then I should have everything wrapped up probably early to mid next week for the hard fork. And then a little bit more testing, and then we'll be releasing that. So keep your eyes for the beta wallets. And then once that is completed, then we're going to be releasing the funds at the activation, which will then start the ball rolling for getting added on the additional exchange listings.

Everybody, I think right now, Xeggex is having some troubles. I'm not sure the entirety of the details of the situation with them, but, we would recommend you trading on Trade Ogre. This would actually, the more communal effort we have on that, the better the deal we're gonna be able to get for MEXC. So if you guys wanna help out in that pursuit of helping us get on more exchanges, The better our prices, the more exchanges we're gonna be able to get on, based on how many available funds that we have. So, yes. That's what I have to say about that.

So, anyway, I'll keep you guys in the loop, and we'll be getting, as I said, we're gonna be releasing another beta wallet next week. The hard fork should be wrapped up by then. And then the final wallet release end of next week, early the week after with a one week activator. And then that will start us getting on MEXC.

As I said, it's a communal effort. Everybody work together, see if we can help kinda get some of the liquidity driving in the trade over a little bit more. So that can help us get a little bit more, better deal for the MEXC listing, and also help support the market. Know that there's lots of things in the pipeline, and, I think a lot of our hard work is finally starting to pay off. There's some other things that, um, are happening that I will give details on as they materialize, and I will talk to you guys next week. So until next time, guys. Goodbye.

News:Project Update 2025-02-07

2025-02-08T14:17:12Z

Nexus wiki: Created page with "= Summary = == Hard Fork & Version 6.0 == * Hard fork update focusing on version 6.0. * Users with coins on the legacy chain must move their coins. * Once the 6.0 wallet is released, there will be a specific timeframe to move funds. * After the deadline, legacy transactions will be permanently disabled. * This marks block version 9 activation and transaction version 4. == Technical Changes & Updates == * Opcodes disabled: 1. op_ledger_time_stamp 2. op_ledger_supply 3..."

= Summary =

== Hard Fork & Version 6.0 ==

* Hard fork update focusing on version 6.0.
* Users with coins on the legacy chain must move their coins.
* Once the 6.0 wallet is released, there will be a specific timeframe to move
funds.
* After the deadline, legacy transactions will be permanently disabled.
* This marks block version 9 activation and transaction version 4.

== Technical Changes & Updates ==

* Opcodes disabled:
1. op_ledger_time_stamp
2. op_ledger_supply
3. Conditional virtual machine
* Security enhancements added.
* Difficulty adjustments and indexing updates completed.
* Aggregation of tau sig chains finalized.

== Staking & Minting ==

* Staking rate adjusted to 5% for five years (per community vote).
* 15,300,000 coins to be minted due to the difference between Tridium and
Legacy chains.
* New transaction on the first version 9 hard fork block to mint this amount.

== Legacy Chain & Supply ==

* Legacy transactions disabled:
1. Any attempt to create a legacy transaction will be rejected.
2. Transactions from Tridium SIG chain to legacy UTXO will also be
rejected.
* Locked total amount of Tridium SIG chain coins into the money supply.
* Total supply:
1. 79,000,000 coins in total.
2. 63,000,000 coins on the Tridium chain.
* Minted funds allocation:
1. $6,000,000 to developer payments, loan repayments, and exchange
listing fees.
2. $10,000,000 reserved for satellite funding.
* Nexus One Satellite Plan:
1. Satellite deployment at various price points.
2. Estimated cost: $20,000 - $30,000 plus launch costs.

== Testing & Activation Timeline ==

* All updates are in testing and finalized.
* Public testing phase expected before final release.
* Hard fork activation expected in late February.
1. Estimated between February 23 - February 28.
* Wallet testing and release planned before departure for the ARC
Conference.

== ARC Conference & Industry Connections ==

* Attending ARC Conference in London (Feb 15-22).
* Conference is invite-only and organized by Jordan Peterson.
* Opportunity to network with industry leaders and policymakers.

== Xeggex Hack & Exchange Listings ==

* Xeggex CEO hacked, but no loss of coins reported.
* Xeggex is in recovery mode, and protocols are in place.
* Indexing system on Nexus side has been fixed.
* Working on new exchange listings to reduce reliance on single exchanges.
* Exploring Tier 1 exchange listings with market makers.

== Community Vote & Developer Funding ==

* Community voted 78-80% in favor of using minted funds for project funding.
* Coins on UTXO are unspendable and considered burned.
* Funding needed for developers:
1. Kendall, Crystal, and CEO have worked for free since mid-2022.
2. Developer salaries range from $1,000 - $1,500 per month.
3. New funding will help repay developers and fund satellite projects.
* Hiring more developers currently not possible due to budget constraints.

== Future Plans ==

* Finalize hard fork testing.
* Prepare for public testing.
* Release mobile wallet after the hard fork.
* Develop Ledger-level Virtual Machine for access control patterns.
* Google Play Store verification delaying the Android mobile wallet release.
* Mobile wallet expected post-hard fork.

== Community & Collaboration ==

* Emphasizing the importance of decentralization and community support.
* Encourages collaboration rather than competition.
* Plans to continue developer updates on AI and Nexus developments.

= Transcription =

*Notice: This text was transcribed using AI. There is a high likelihood of spelling, grammatical, and translative errors.

Hey, guys. Welcome to the weekly update. This week, I've mainly been, concentrating on
the hard fork. As I said before, this is version 6.0. So, if you are still running and
having any coins on the legacy chain, please make sure to move your coins.

Once the 6.0 wallet is released, you will know that you have a specific time to do it
by. And then after that time, that's gonna be basically the end of legacy transactions as we
know it. So this will be a block version nine activation and transaction version four. So I've
disabled some opcodes, like the op ledger time stamp, op ledger supply, and the
conditional virtual machine. I've added some additional some security parameters.

We're also changing this staking rate to 5% for five years as it was voted prior. And then we
are minting about 15,300,000.0 coins based off of the difference in the Tridium chain and
the legacy chain. So just for a frame of reference, this is all on the same blockchain. The
legacy chain, was the blocks prior to the first Tridium block, but legacy transactions were still
supported after that date. And so the way it works is there's an interoperability that I
developed a protocol that allows legacy coins to transfer in and out of the trading
protocol.

But as we all know, UTXO has a lot of issues. I think it's about twenty, thirty percent of the
UTXO set on any other chain is unspendable. And there's no real way to prove that you own
any of those coins once you've lost that, key. So, you know, basically, what's been
happening, I just wanna explain the procedure, is legacy transactions will be disabled,
which means if you try to create a legacy transaction, it will be rejected by the network.
And if you try to send from a, a Tridium SIG chain to a legacy UTXO, that transaction will be
rejected as well.

So that's gonna essentially lock the total amount of coins that are on Tridium SIG chains into
the money supply. And, you know, since the first Tridium block, the mint has all been going
into the Tridium chain. And it looks like mostly everybody is on the Tridium chain. I saw one
last movement from an old, holder that was on legacy that moved all of their coins into
Tridium. But pretty much everything, it's it's there now.

So, basically, what's gonna happen is these transactions will be disabled, which means that
any coins that were still on legacy are going to be unspendable. Now they're all pretty
much unspendable right now as far as the legacy coins that, you know, about 15,300,000.0
is essentially how many coins have been lost, how many private keys got lost. So we're not
actually going in and accessing any of those coins because that would be a violation of
the protocol. What we're developing is a difference in the money supply. So currently, the
money supply is about 79,000,000, and there's about 63,000,000 on the Tridium chain.

So there's gonna be a special transaction on the hard fork, the very first version nine hard
fork block that's going to mint essentially this fifth point 15,300,000.0 based on the allocations
that we have decided as a community. It's looking right now about 6,000,000 will be going
to pay back pay for some developers, paying back some loans and also exchange listing
fees. And then about 10,000,000 is going to be staying and sitting there to be reserved for
satellite funding once we get to, you know, given price points. We wanna do a Nexus One
satellite at some point, maybe 50¢, and we're gonna be developing a a series of price
points to determine how many new satellites that we're gonna be deploying. I mean, if we
built some of the satellites ourselves, we could do it for 20 or $30,000, it looks like, plus launch
costs.

So I just wanted to clarify that that's that's essentially how it's gonna be working. There's
gonna be a new transaction that's going to mint that amount from the coin supply. The
money supply at a certain at that first block will be reduced by the total amount of Tridium
coins or the total amount of legacy coins difference, and then that mint will then mint that
certain amount that will essentially be the difference between Tritium and legacy coins. So
it'll be new coins. It's not trying to access anyone's account.

The chain is pure. There's nothing like that in the chain. I just wanted to be really clear that
that's how it works. So I have pretty much everything just about in testing right now. I have
the all of the opcodes disabled.

I have some difficulty adjustments done. I have the aggregation of some of the tau sig
chains. That's another big one. I also have some of the chain state parameters set up now. I
have some indexing updates done on it.

So it's pretty much ready to go next week. I'm going to be testing and getting it ready for
release. And then most likely, we'll do more of a public testing bed because I'm going to be
gone the week from the fifteenth to the twenty second in London for, the ARC conference.
It's an invite only, kind of counter WEF conference. So it's, the Alliance for Responsible
Citizenship.

Jordan Peterson started it. So I got invited. I'm on the short list, so I'm gonna be there making
contact with a lot of the people. There's a lot of big players there. Anybody that wants to
do your own research, you can search ARC Conference twenty twenty five, and you'll see
some of the speakers.

And as I said, it's an invite only conference, so I'm going to be attending. And there's a lot of
other things in the pipeline from that. So, ideally, I'm going to be getting this update out. I
wanna have it activate after I have, returned. So the activation time will sometime be in
late February.

I would give as a conservative estimate. Most likely, the wallet will be tested and released
by by the time that I leave, and then then we'll have an activation be, you know, probably
it could be as early as the twenty third, '20 fourth of February, but it could be as late as the
February 28. But pretty much consider by the February, all this is going to be sorted and
settled. So like I said, that's all just about done. Xeggex, from what I understand, they have
the situation under control.

It looks like their CEO was hacked. I don't think there was any breach of coins. I don't think
there was any loss as far as I'm aware. We've been in communication with them. It seems
like they're just going through standard protocol to lock everything down and make sure
that there is no issues at hand.

So, hopefully, Xeggex will be getting back online in a reasonable time. We've already fixed
the issues on our side. I've redone the entire indexing system, and it's running smoothly. So it's
pretty much balls in their court. Once they decide to open back up, hopefully, they will
enable deposits and withdrawals at that point in time.

And as I said, we're working on additional exchange listings. There's a market maker that
we're working with, and there's also some open offers that we have on some tier one
exchanges. We're looking at getting ourselves distributed to more exchanges. That'll be very
important for us in the coming months and years. So as we saw, the Xeggex hack, the fear
of that caused a lot of discontent in the community, and we need to not be completely
reliant on single exchanges.

So we are working on getting ourselves distributed. And that's what's really nice about this
new coin mint is that it essentially gives us a lot of these new opportunities. This was voted by
the community. As I said, all of the prior coins on UTXO are unspendable. So they're
essentially already burnt.

They're inaccessible. Somebody the people that had them cannot access those coins
anymore. A lot of them might be old community members from seven years ago as far as
we're aware, that are just inaccessible coins at this point. So like I said, the way it's gonna
happen is legacy transactions are gonna be completely shut off, which means once that
activation happens, there's not gonna be the possibility for you to transact legacy
transactions anymore. And that difference in coins will be minted.

If we did it the other way where we just said, okay. Leave it burned, then we would be
reducing the money supply by 15,300,000. And it wouldn't really change our economics in
any way, shape, or form. It would just change the psychological value of it. So as a
community, it was, I think, 78 to 80% voting in favor of it.

It was fairly unanimous that we should save these any award chest to help pay back
developers and funding and everything. Because if people weren't aware, Kendall and
Crystal and myself have been working virtually for free, since about mid twenty twenty two.
I've been paid maybe a thousand dollars a month, $1,500 a month, and Kendall and Chris
are the same, even less than that. So this is gonna be helping give us, you know, some coins
to pay us back for work that we've done and also a lot of the the money that I donated to,
get Tridium over the line in 2019 and exchange listings and bounty programs and then a
long term war chest to allow us to deploy satellites or potentially hire more funding and
developers. That's one reason why we have a very small developer pool right now is the
funding has not been able to produce enough to support even us three developers.

So hiring more developers is not necessarily in the question currently. But as we get on better
exchanges and price goes up and we have a little bit more of a buffer, I should say, where
there's more coins available, to you know, depending on the price point, it's not entirely
reliant on our income, then we'll be able to make those adjustments and, you know, hire
new help. So I, I'm looking forward to that. I have a few candidates in mind that I would like
to work with, people that I've worked with before, very, very good developers, but good
developers are expensive. And, if anybody wants to look at the going market rate, what
we're doing too is totally new architecture, never been done before, so it's not somebody
you can necessarily just pick off out of college.

I've hired people out of college, and they deer in the headlights. So, anyhow, that's what's
going on currently with Nexus. Next week, ideally, I would like to see most of the testing
done, hard fork ready to go, print and wrap. And if I can get to while we're testing, I'd
ideally like to get the mobile one out more. The Android Play Store, we're dealing with
company verification right now and a bunch of other, you know, potential drawbacks in
that.

So we're working on getting that deployed as quickly quickly as possible. And, so those are
the things to be looking forward to. We'll most likely be getting the wallet, mobile wallet
released after this hard fork since it will be a consensus upgrade. And then I'm going to be
diving into some of the new features, as I was stating earlier, such as the Ledger level virtual
machine where you can program access control patterns and all of that good stuff. So I
guess I will talk to you guys next week.

Thanks for being patient. Updates are a little bit late in the night sometimes, but I've been
keeping up with it. So, everybody, I hope you have a wonderful weekend, and I will talk to
you again next week.

News:Project Update 2025-02-01

2025-02-08T14:11:28Z

Nexus wiki: Created page with "System and Development Updates * Revamped the Xeggex indexing system and fixed several bugs. * Wrote approximately 3,000 lines of code this week. * Developing a new artificial intelligence algorithm. 1. Testing side-by-side with traditional neural networks. 2. Focused on distributed computing clusters and accuracy. 3. Developing from scratch and optimizing iteration count. Hard Fork & Wallet Upgrades * Preparing wallet version 6.0.0, marking the next hard fork. * Hard..."

System and Development Updates

* Revamped the Xeggex indexing system and fixed several bugs.
* Wrote approximately 3,000 lines of code this week.
* Developing a new artificial intelligence algorithm.
1. Testing side-by-side with traditional neural networks.
2. Focused on distributed computing clusters and accuracy.
3. Developing from scratch and optimizing iteration count.

Hard Fork & Wallet Upgrades

* Preparing wallet version 6.0.0, marking the next hard fork.
* Hard forks are indicated by major version number changes.
* Legacy transactions will be locked after a 2-week activation period.
* Users must move coins before activation to avoid loss.
* Expecting around 15.3 million lost Nexus coins over 10 years on UTXO.

Authentication & Security Improvements

* Working on a ledger-level virtual machine for smart contract-based authentication.
* Allows for account recovery systems, password resets, and access controls.
* Feature is postponed to the next update for further refinement.

Exchange Listings & Liquidity Strategy

* Negotiating with MEXC for an exchange listing.
* Many new exchange listing offers received.
* Plans to gradually expand listings as price and liquidity improve.
* Engaging with market makers to optimize liquidity.

On-Chain Voting & Nexus Allocation

* Planning on-chain voting to ratify allocations.
* Approx. 6 million Nexus allocated to team bounties.
* 10 million Nexus reserved for a satellite war chest.
* Will encode allocation details into the blockchain for transparency.

Infrastructure & Mobile Wallet

* Mobile wallet development progressing.
* Google Play Store registration in process.
* Mobile wallet testing and final touches are high-priority.

Decentralized AI & Computing Network

* Developing a decentralized AI computing network.
* Enables users to deploy AI models on a decentralized infrastructure.
* Expected to drive liquidity and adoption.

Future Plans:

* Expanding awareness and marketing efforts for Nexus.
* Exploring partnerships in South America.
* Satellite deployment plans for network enhancement.
* Allocating funds for effective market positioning.

Community & Collaboration

* Emphasizing the importance of decentralization and community support.

* Encourages collaboration rather than competition.
* Plans to continue developer updates on AI and Nexus developments.
* Would you like any specific sections expanded or modified?

Full transcription:
* Notice: This text was transcribed using AI. There is a high likelihood of spelling, grammatical, and translative errors.

Hey, everybody. Thanks for the patience. This is a little bit delayed. It's kinda late late Friday
night. So, I spent a lot of this week getting, Xeggex back online and revamping the indexing
system, and I fixed a few bugs in that.

I think total, if you pull the merging code, I think I ended up doing about 3,000 lines of code
this week. And then after I got all that done, I think I got all that done on Wednesday. I've
been pivoting. I've been working on new artificial intelligence algorithm right now. I have
kind of a side by side comparison going with the typical neural network architecture,
getting some of the, I guess, distributed computing clusters going, getting that, I guess,
some of the initial task list, getting names sorted.

And I've actually been coding this particular neural network from scratch, being able to test
the number of iterations that are, required to get this similar amount of accuracy. So I think
it's it's a really important metric. I have a really cool algorithm that I'm testing out and
implementing. Ultimately, I think it could bring, I guess, a lot of benefit. I I want to to take
artificial intelligence kind of outside of this artificial realm and bringing it kinda more sentient.

I think there could be a really beautiful symbiosis between, you know, man and machine at
some point in the future. So that I've been doing over the last couple days. I've also been
preparing some of the original hearts fork code. I've been getting some of the time lock
activations put in, and I have just a few more things. I've also started working on the ledger
level virtual machine as I've told you guys about that before.

That's basically gives you smart contracts for your authentication system. I think I'm gonna
push that back to the next update, the next hard fork, just because I wanna really spend
time with that and I make sure I get that really solid, and I don't know. I I I would like to
include it in this next one because it is really important for security. It'll really improve your
account security. I mean, you'll basically be able to create account recovery systems.

You know? Saying, oh, hey. My sig change inactive for 2 weeks or if, you know, this specific
user, you know, has this access pattern or whatever, you'll be able to put basically that that
in there. So you'll be able to create these password recovery systems or, hey. You know,
after this certain date, this person can access this account or whatever else for your wills
and all of that.

So I'm probably pushing that. I wanted to do that. We've got most of the allocation pretty
well settled, for the the hard fork allocation. I haven't seen any legacy coins move, but you'll
know when the hard fork's coming out because that's gonna be released as wallet version
6.0.0. For anybody that wasn't aware, the whole version numbers are hard forks.

So anytime you go from 5 to 6, that's a hard fork. And then any sub number is not a hard
fork. So you'll know that if we ever bump from 5 to 6 or 6 to 7, it's always gonna be a
mandatory upgrade. I wanted to do an on chain vote for ratifying essentially what our
allocation is gonna be. I got just about all the numbers from everybody so that I'm gonna
be putting it in an asset, and we're gonna do kind of a simple vote like we did before,
where you transfer a certain amount of nexus from your trust account.

You know, it'll be 1 biz worth, 1 0.0001 to the account, and it'll be, like, the yes or the no
account. And then I'm gonna actually encode the allocations in the chain as well. So that
will be ratified on chain, and then that'll show. It's looking like, you know, about 6,000,000
have been allocated to team bounties. And it looks like it'll be about 10,000,000 locked up
in the satellite war chest.

As I said, I will be publishing that next week, so you guys get a good idea of that. If you are
compiling your wallet and you're a minor in particular, I would recommend upgrading to
the recent this would be 5 point 1.5 release candidate 11. That has the entirely revamped
indexing system. It's very fast. It's reliable.

I feel good about the code now. I told you guys last time it was always something that I
would look at and feel like it could be better. And all the little idiosyncrasies added up to
the point where I decided to finally get that sorted. So Zedgex, I think, is just wrapping up a
few things on their side, and we should be able to start opening up deposits and
withdrawals. I'd estimate next week, but I will chase down their tech guy and let you guys
know.

I think I need to do a few test deposits once I do that. Once he gets back to me, then that
will be a marker to know that we're getting ready. We've also negotiated with MEXC. I think

we've got an agreement, so we're gonna be starting that listing process after this hard fork.
So that's another reason why I'm kind of pushing the the virtual machine for the,
authentication system out because I think that's an important issue.

I also have been getting actually heaps of new exchange offers. It's really cool. So we're
going to be starting with MEXC, but we're gonna be deploying to more exchanges in a
runway price point fashion. So, you know, MEXC will be the most expensive to start because
our price is lower. But then as we start seeing, you know, improved price gains and liquidity,
then we'll be adding and spreading out on more exchanges.

I really firmly believe that's one of the biggest things that we've been missing. There's a lot
there in nexus. There's a lot of available technology. I've heard it time and time again. And
even fortune 100 companies when I was going around speaking with them in 2018, they're
always blown away by our tech stack.

So it's just a matter of marketing it. It's something that we're working on. And now we're
gonna be having a nice war chest to be able to market, to be able to getting on more
exchange listings. And I think we're we're getting some marketing packages with some of
those exchange listings. We're rebooting them down.

I'm also speaking to the market maker next week with some members of the team. They'll
be able to help us get the best deals to get on more exchanges. So if any of you have any
suggested exchanges, feel free to always drop a note. And then again, next week, I'm
going to be providing the list of our allocations that we've come to consensus on as a team,
and then we'll vote on that. And that'll be one of the last standing items before the hard
fork.

I've gotten most of the time lock activations done. I have a couple more rules that I wanna
change, such as the fees asset and the change state parameters, and some of the
difficulty adjustments. And once that is done, then we'll be doing a test and an activation
first to make sure everything goes smoothly. We're gonna be upgrading our transaction
version and our block version. Because we're changing a lot of those values.

The legacy chain will be locked initially, so legacy transactions will no longer be able to be
sent, and you will no longer be able to send from a tritium to a legacy. So make sure that
you've moved your coins over by the time the 2 week activation happens. So like I said, the
wallet will be released version 6.0.0, And after that, there will be a 2 week timer to move
your coins still. So as far as I've seen, I don't think anybody's got anything on legacy

anymore. It looks like it's at about 15,300,000 nexus that were lost over the last 10 years on
UTXO, which seems about right if you do any research.

Litecoin and Bitcoin and all of them, I think a large part of their UTXO set is actually
unspendable. It's a big issue with UTXO, so I'm glad that we don't have that issue. So I
suspect by the end of next week, I'll be doing some of the time lock activation. We're also
working with Google Play Store, getting our company registration put in there so that we
can get ready to release that. I have to just do the blocking timeouts and do a little bit
more hardy testing on that.

Now that I've gotten the pressing issue with the exchanges out of the way, I can be free to
focus on that. So I'm gonna be putting that as my higher priority next week to get the
mobile wallet ready to pack and ship, and then getting the hard fork done. And then we're
gonna be doing our vote. And then as I said, we're working on an m e x c listing and,
obviously, more in the future and developing, you know, a really strong marketing package
in that way. And I'd also like to propose different price points for our initial satellite.

Like I said, I found some reasonable ones for about $100,000 where we could get 2 or 3 u,
that we can start getting something orbital, so we can at least know that we've done 1.
We'll choose a price point for that, and then we'll obviously be deploying more and more as
the time goes on. We wanna utilize that 10,000,000 Nexus effectively, and I really do believe
that it's just a matter of time and marketing and communicating in the right way to get us
from, you know, a to z. If huakta coin and all of these other coins can succeed, there's
nothing to say that we shouldn't. It's just a matter of how we present it and how we do it,
and also how we work together, guys.

Remember, decentralization becomes very powerful when all of us work together. That's so
important. I think we all need each other now more than ever. So let's try to be supportive of
each other in the community. Let's help each other out.

Let's all work together. Let's all contribute our talents. Let's look at it as we're all here to
enhance each other rather than to compete with each other, because all of us succeed as
NICE succeeds. So let's all keep kicking butt together and doing all of that. I will, continue
on these developer updates, give you guys progress updates on both the AI and Nexus.

I did spend 2 days this week after the exchanges doing the AI and getting a really good
start on that. As I was saying, because there's the main artificial intelligence neural network
architecture that I'm developing, and then there's also the distributed computing network
that'll make it really easy for anybody to be able to deploy their own AI and have it

compute directly on in a decentralized way. As I said, I think this will be really important for
driving liquidity. I mean, something comparable would be io.net, and that's valued at about
2,000,000,000. So I do believe this is gonna be something that's gonna be very powerful for
driving liquidity into our markets.

And I'm also working on a couple other use cases, as I said, down some places south, I think,
Columbia, some really large apps. There's some people that have, have large apps that
they'd like to start integrating nexus on and stuff. So the mobile watch really the the main
hold up on that, and then we're gonna be pursuing that. So I I guess I will wrap it up for this
week. We will, convene again next week.

I'll try to get it a little bit earlier in the evening next week. Been preoccupied with many
things today. So, again, thank you everybody, and I will chat with you next week.

News:Project Update 2025-01-25

2025-02-08T14:08:22Z

Nexus wiki: Created page with "GitHub Projects Organization * Creation of three projects: desktop wallet, mobile wallet, and LLL-TAO. * Improved tracking of issues, enhancements, bugs, and project milestones. Indexing System Revamp * Breaking database instances into a sessions database and a global index database. * Bug fixes completed, with critical issues resolved for exchanges. * Trade functionality should be back online after one more update. Assistance with XeggeX * Supporting Geraldo in fix..."

GitHub Projects Organization

* Creation of three projects: desktop wallet, mobile wallet, and LLL-TAO.
* Improved tracking of issues, enhancements, bugs, and project milestones.

Indexing System Revamp

* Breaking database instances into a sessions database and a global index database.
* Bug fixes completed, with critical issues resolved for exchanges.
* Trade functionality should be back online after one more update.

Assistance with XeggeX

* Supporting Geraldo in fixing implementation issues and initial logic.

Hard Fork Development

* Implementing version checks and testing on test and private networks.
* Solidifying reorganization code through local tests.
* Active work on the following branches:
1. merging-indexing: Indexing system work.
2. merging-6.0: Hard fork development.

Ledger Level Virtual Machine

* Key feature for enhanced security and access control patterns.
* Allows creation of multiple credentials with restricted access to specific
actions (e.g., staking, debits, credits).

* Supports programmable access control, AND/OR logic, time limits, and multi-
signature authentication.

* Enables functionalities like:
1. Automatically executing wills with time-based access control.

2. Granular authentication for signature chains.
3. 2-factor authentication via mobile wallet or app integration.

Progress on Hard Fork Features

* Chain state parameters: In progress.
* Asset management: Not done.
* Difficulty adjustments: Nearly complete.
* Aggregate sig chains: Not done.
* Truncating the legacy chain: Not done.
* Next Hash authentication scripts: In progress.

Index System Revamp Progress

* Aiming for completion by the end of the weekend.
* Approximately 2,000-3,000 lines of code, 50-60% completed.

Ledger Level Virtual Machine Timeline

* Targeting completion within a week.
* Hard fork expected within 2-4 weeks, followed by a 2-week activation period.

Legacy Coin Migration

* Reminder to move coins from the legacy chain.
* Approximately 15,300,000 coins burned/lost on the legacy chain.

Unburned Coin Distribution

* Finalizing allocations for unburned coins.
* Planned on-chain vote for approval.
* Proposed distribution:
1. 6,000,000 coins to the team for bounties.
2. 10,000,000 coins to the satellite war chest.

Future Plans:

* Updates on progress in the coming weeks.
* On-chain vote to ratify unburned coin allocations.

Full transcription:
* Notice: This text was transcribed using AI. There is a high likelihood of spelling, grammatical, and translative errors.

GitHub Projects

Hey, guys. This update this week is gonna be short. What I've been working on primarily is
working on an indexing system revamping. So I've been essentially breaking the database
instances into a sessions database and then a regular global's index database. I've been
doing some bug fixes.

I got pretty much all of the the critical bugs resolved for the exchanges. Trade over should
be back online. We're having, I think, one more update, and then everything should be
good. A lot of it's been also helping XeggeX with Geraldo. They're still fixing some of their
implementation issues as far as some of their initial logic.

And then I've also been starting on the hard fork. So some of that is essentially putting in
different version checks, doing some tests on the test net, private net. I've been getting
some of the reorganization code really solid, so doing a lot of local tests with that. And really
deciding how everything's gonna be broken up. If you wanna monitor the branches,
merging indexing is the branch in which I'm doing all of the, work on the indexing system.

Merging-6.0 is the one that I'm doing the hard fork work. And then I also started on the
ledger level virtual machine. So I pushed this feature up into present time for this next hard
fork because this one's gonna be a really important security measure. So what you're gonna
be able to do is create access control patterns for your signature chain. So I've mentioned
this before, but just to give you a quick rundown of how it works.

You'll have your master credentials, and that'll be able to execute anything in your sig
chain. Right? Debits, credits, transfers, claims, all of that. But then you'll be able to create
any other set of credentials. So the set of credentials, think of that as just a different
password/pin combination.

And for instance, one of them you could say, I want this access credentials to only be able
to stake and only be able to add stake to my trust, but not take away stake. And only be
able to credit to accounts, but never be able to debit. So the result of that would be if any
of those credentials get compromised. Let's say, you get a virus on your computer or
malware, any of the sorts, it won't matter. Because the attacker will not actually have full
access to your section.

They'll have a limited access. So when you're staking and you're running your wallet and
you're leaving it open, nobody will be able to withdraw funds or even unstake any of your
coins. So that'll be a really powerful feature. It adds a lot of additional security. And this
virtual machine basically will support AND and OR logic.

So you could say that this set of credentials can do this, or this set of credentials can do
that. Or you can combine them together, and you can put a time limit on it. So you can
say, this set of credentials, plus this set of credentials, plus this set of credentials have full
access on my sig chain if the sig chain has not produced a transaction for the period of 1
year. So what that would be is an automatically activating will. So you'll be able to even put
credentials that have access to one account.

So if you do have 3 children, you could say, okay. Well, this account will be able to be
accessed by this child after my sick change inactive for a year. Or this account, this other
account will be able to access by that child if my sick change inactive for a year. Or this
deed, this asset will be accessible by this other account, this other person after a period of 1
year. So what that means is that those credentials will not be able to access a sig chain as
long as your sig chain is producing transactions.

And you'll be able to set that time limit, so that creates kind of an automatically executing
last will and testimony. And like I said, it'll be a programmable access control pattern. So it's
gonna be, essentially, smart contracts for your led ledger level authentication system, and
it's gonna follow some of the conditional contract logic. So I've started coding that. That's a
really important one, and I want it to be really powerful so that you can have access to all
of these different parts of the state of your sig chain.

This will also allow you to do multi signature credentials as well. So you'll have your master,
and then you could create another set of credentials for debits that requires 2 sets of
credentials to sign off on the transaction in order for that to be authenticated. So like I said,
it's gonna add a lot of really powerful functionality. It'll also allow us to prevent your account
from being hacked in many, many different ways. It'll allow you to create multi signature
authentication.

It'll also allow us to add 2 factor authentication, where you can have a separate 2 factor
authentication app and Nexus app per se, or we can make a 2FA code built into our
mobile wallet so that you'll have to sign off on both devices. And that would be like a multi
sig in order to do a debit, for instance, but maybe a credit could sign off with each
individual one. So we'd be able to control these granular aspects of your signature

authentication system. So that's one of the the main features for this hard fork. As I said,
we're basically doing chain state parameters and an asset That's not done.

Difficulty adjustments, that's just about done. The asset, that's not done. Aggregate the dial
sig chains, that's not done. Truncate the legacy chain, that's not done. And then the Next
Hash authentication scripts, that's in progress right now.

These things are being built. Now the the index system revamp, I'm gonna have that done
by the end of the weekend. That's a huge milestone for the indexing system. I haven't as I've
said earlier, been totally satisfied with the indexing system, so it's good to be getting that
done. Getting that sorted.

And that's a lot of code. It's about 2 or 3,000 lines of code. So I'd say that's probably about
50, 60 percent there. Just gotta clean up some of the additional logic. And then the ledger
level of virtual machine, ideally, I would like to have that done within a week.

And then we're wanting to get the hard fork out within the next 2 weeks. Potentially a little
potentially later than that. It might be 2 weeks to a month. That would be ideal, and then it'll
be a 2 week activation. If you still have legacy coins on the legacy chain, make sure you
move them.

We did have somebody found to move their coins out of the legacy chain. So now there's
about 15,300,000 coins that have been burnt and lost. So that's currently what our unburned
is being set at. We're also working on the list of people, for the that unburned of where
they're gonna be distributed to. I have most everybody's numbers just waiting on one more
to get that finalized.

And then I'm gonna publish that in the main channel, and we're going to do an on-chain
vote. So we're gonna do it like we did with the embassy on-chain vote. We're gonna create
an account with a name, and I'm gonna put in that asset all the allocations to each
individual. And then you'll send the smallest amount of NXS .0001 to that account, and you'll
vote with your trust. And so we're gonna ratify that specifically on-chain.

But it's looking like about 6,000,000 will be distributed to the team for bounties and
everything, and about 10,000,000 will remain in the satellite war chest. So I will keep you
guys in the loop next week. I look forward to the next development update, and, till next
time, guys.

News:Project Update 2025-01-17

2025-02-08T14:02:12Z

Nexus wiki: Created page with "GitHub Projects Organization: * Creation of three projects: desktop wallet, mobile wallet, and LLL-TAO. * Improved tracking of issues, enhancements, bugs, and project milestones. Development Updates: * Revamped the indexing system to improve performance. * Addressed and resolved several bugs related to the mempool and transactions. * Improved syncing performance, achieving twice the speed compared to the old architecture. * Removed certain opcodes (e.g., OP:LEDGER:TIM..."

GitHub Projects Organization:

* Creation of three projects: desktop wallet, mobile wallet, and LLL-TAO.
* Improved tracking of issues, enhancements, bugs, and project milestones.

Development Updates:

* Revamped the indexing system to improve performance.
* Addressed and resolved several bugs related to the mempool and transactions.
* Improved syncing performance, achieving twice the speed compared to the old architecture.
* Removed certain opcodes (e.g., OP:LEDGER:TIMESTAMP) for better reliability.

Upcoming Features and Focus Areas:

* Development of session management for remote login in both desktop and mobile wallets.
* Peer-to-peer messenger integration, likely coinciding with or slightly after the hard fork.
* Focus on optimizing mobile wallet for specific use cases in South America and the media industry.

Testing and Deployment:

* Significant progress on the new syncing code for better performance across nodes.
* Efforts to ensure stable integration with platforms like TradeOgre and XeggeX.
Media Use Case:
* Early-stage development of a use case tailored for the alternative media industry.

Future Plans:

* Completion of indexing system revamping by early next week.
* Mobile wallet development prioritized for release to address emerging use cases.
* Preparation for hard fork milestones.

Full transcription:

* Notice: This text was transcribed using AI. There is a high likelihood of spelling, grammatical, and translative errors.

GitHub Projects

Hello everybody. Welcome to development update for January 17, 2025. One of the main
things that I've been doing this week is getting really organized with goo GitHub projects
again. So if anybody recalls, we used to use this. So I have made 3 projects.

1 for the desktop wallet, 1 for the mobile wallet, and one for the LLL-TAO. So I posted a link in
this in the General channel. I encourage anybody that's not technically minded to be
checking on this to keep an eye on what the development is happening. This is also good.
This is where I'm tracking issues in.

So you'll see there's a hard fork section. These are the features that are going to be
necessary to launch the 6 point o hard fork. And then I have an enhancement section. This
is basic feature request enhancements, to improve the protocol. And then I have bugs, and
that's just issues that people submit, and then I put them in bugs, and then in progress, and
done.

Indexing System Revamp

So, currently, I have removed the OP:LEDGER:TIMESTAMP. I'm in the process of revamping
the indexing system. I improved sanitize unconfirmed, and I got a lot of that logic. I also
found an interesting logic issue with the mempool and transactions. They, when there's a
reorganization, it should be resurrected in the mempool.

But in the mempool check for the accept function, I was checking if it was on disk already,
but if it's already been accepted and reorganized, it's already on disk. And so the
transactions weren't getting brought back into the mempool. So that was the first problem.

TradeOgre and Xeggex Resolutuion

Then the second problem was that I wasn't checking if that transaction was indexed when I
was reading the contract for a memory pool state, so that your notifications processor
would see that and think that was an expired contract and try to claim it. And that's
essentially what happened to TradeOgre and Xeggex.

And there was another issue on XeggeX side too, where they weren't they were checking
confirmations based off of the debit and not off the credit. And so that created a couple
other issues. So we got all of that sorted. It was a myriad of different things. The last little bit
that I have right now is revamping the indexing system.

So I've already split it up into 2 different database instances. Then I'm going through and I'm
changing the internal indexing logic. It seems sometimes the indexes don't fire, and I
haven't been particularly super enthusiastic with the code. It was something that worked,
but I wasn't looking at it as, oh, wow. This is this is great work.

Mobile Wallet

So and I've noticed that with Nexus. If if I ever leave something like that, usually at some
point, you run into issues and it kinda kicks it back and, you know, has these weird
idiosyncrasies that happen. So that's being completely revamped. I'm gonna have that
done by Monday or Tuesday. I did not get too much in a mobile wallet this week.

I know that was a goal that I had for last week, so I'm going to be pushing that milestone for
next week. But I did start in the mobile project. Kendal and Krysto are starting for the
desktop wallet and the mobile wallet, the, sessions management. This is a front end that's
gonna be important for remote login. So that's gonna be a feature that's gonna be coming
out along with the peer-to-peer messenger, probably around the hard fork time, maybe a
little bit past the hard fork time because we do need to have a functional interface for it to
be valuable to people.

Sync Improvements

Anyhow, so I've basically gone through I improved the syncing code. So I've actually gotten
my metrics about twice as fast. And this will also be for any any specific computer because
it was basically doing random reads for the transactions, and that can get really, really slow
for hard drives because the disk seek is the slowest part of a hard drive. So, basically, what
I'm doing is I'm doing a sequential read of the transactions and a sequential read of the
blocks so that it's more optimized for hard drives and solid state drives as well, which
improves our throughput on the sender's side. So I'm just testing 2 nodes side by side, one
running the old syncing architecture and one running the new syncing architecture.

I've managed to improve the syncing by a factor of 2. So that's very good numbers for us.
That means that, you know, what would take 2 hours would take about 1 hour depending
on the node that you're connecting to. Since we have a much better distributed topology
on our network too, we're gonna be syncing from each other more, and that could cause
you to sync pretty slowly if you have somebody with a really slow connection or with a slow
disk. So this will help with that substantially as well.

So I spent a lot of time fine tuning that this week. And little granular details, like I said, I
added index checks inside the read contracts. I checked the index on connect for
mempool states because you should have the dependent already confirmed in order for it
to be accepted into the mempool. And made a couple other micro adjustments. I
changed some of the syncing code to show the number of contracts that I've been
processing so that I can kinda keep an eye on that rather than the number of blocks.

LEDGER:TIMESTAMP

And then I have added some initial hard fork. I have removed the OP:LEDGER:TIMESTAMP
and OP:LEDGER:SUPPLY. Basically, the ledger variables because the ledger if you have it
tied to a ledger contract that can be kind of right on the the outer edge. So if you say, like, I
want to take the the best blocks time stamp, when it gets accepted into the memory pool,
it works. But then it gets accepted onto the block, and then that tells you your ledger time
stamp.

But that timestamp will continually change as new blocks get added, and you could run
into a window of error issue there. So I've just removed the ledger timestamp. I don't think
that's a good opcode for us to be able to use. I've started some of the basic legacy
truncation, architecture and code so that basically you're gonna be able to sync from the
first tritium block. And, you know, we're going to be having that fully activate on the hard
fork.

New Use Case – Alternative Media

I've also, added a couple new rules for OP:DEBIT, a few version 4 activations for the hard
fork. And, also, Kendal and and myself are working on a new use case. This, is beyond just
the AI one. This is gonna be focused on media. I have some contacts in the media industry,
alternative media.

Very well known people. I'm not gonna mention names, but once we get this specific use
case done, we have a really nice launching pad for it. So I'm gonna just leave that at that.
We're working on something that's gonna be actually really, really beneficial for alternative

media, essentially. So I'm not gonna say much more than that, but we have started the
initial drafting on that.

Wrap-Up and Future Plans

We're doing our dev calls every Thursday. So next Friday, I'll be adding updates from what
Kendal and have been working on. And, I think that's pretty much it for this week. So if you
want to watch the, GitHub, check the GitHub's projects. You can see little projects tab.

You should see the 3 projects. There's LLL-TAO, Nexus mobile wallet, and Nexus desktop
wallet. We're gonna have all 3 of those so that we can start doing better task
management. That's for the layman people that don't understand all the code and
commits and all of that different stuff. So this should help you guys monitor progress and
priorities and milestones and all of that, in the interim.

And yeah. And then next week, hopefully, we get a new beta out next week. This week is
really a lot of it has been chasing these bugs, which I'm glad we found them because this
was a this was a combination of a few that happened only in a very specific circumstance,
which is good to catch these now before we get on MEXC and all that. We wanna make
sure everything's solid there. So that wraps up for this development update for January 17,
2025.

I will be doing another update next Friday. And, also, any questions, feel free to post them in
the community. We will be having, you know, interim text updates throughout the week and
then another developer update next Friday. Like I said, I will have the indexing system
revamping done by Monday or Tuesday. TradeOgre should be getting online fairly soon.

They needed to make one adjustment on their side. I believe XeggeX is getting online
relatively soon as well. I did develop a feature for them, for showing the spending credit
and stuff like that. So everything looks to be in a good state there. So, I'm not sure if they've
opened up their deposits and withdrawals yet, but that should be relatively soon.

And trade over the same. Like I said, I will be working on this, and getting that is my next
major priority for Monday, Tuesday. And then getting some of the more hard fork stuff done.
And I'm gonna be really focusing on mobile lot next week because there's a use case, 2 use
cases in South America that's gonna really need the mobile wallet. And this new media use
case is gonna really need the mobile wallet.

And all of you really need the mobile wallet out and about. So I've got a couple things on
that to get tidied up, and then we should be able to start getting that out and ready to go.
So, I guess, until next time, everybody. I will talk to you again next week.

News:Project Update 2025-01-10

2025-02-08T13:54:55Z

Nexus wiki: Created page with "Indexing System Revamp: * Redesigned the global indexing architecture to address bugs and inefficiencies. * Separated the indexing system into API and Sessions folders for modularity and improved maintenance. * Debugged issues related to transaction credits and ledger timestamps, including reorganization problems. Fee Structure Improvements: * Transitioning fees from hardcoded values to dynamic, chain-state-based parameters. * Allowing community-driven changes without th..."

Indexing System Revamp:
* Redesigned the global indexing architecture to address bugs and
inefficiencies.
* Separated the indexing system into API and Sessions folders for modularity
and improved maintenance.
* Debugged issues related to transaction credits and ledger timestamps,
including reorganization problems.
Fee Structure Improvements:
* Transitioning fees from hardcoded values to dynamic, chain-state-based
parameters.
* Allowing community-driven changes without the need for hard forks.
Transaction and Consensus Adjustments:
* Disabling problematic opcodes and refining timestamp handling.
* Enhancements to ensure stability during chain reorganizations.
Mobile Wallets:
* iOS and Android wallets prioritized.
* Addressing client mode issues for large signature chains.
Hard Fork Preparation:
* Plans to reallocate unclaimed legacy coins for developers, satellites, and
exchange listings.
* Locking a significant portion of funds for future satellite deployments.
New Features:
* Introducing signature aggregation to reduce disk space usage.
* Migrating from OpenSSL to embedded TLS for enhanced security and
compatibility.

Future Plans:
Mobile Wallet Release:
* Completing back-end work by next week for testing.
Artificial Intelligence Use Cases:
* Developing a structured AI model with predictable neural pathways to
democratize AI access.
Community Engagement:
* Creating a bounty system to incentivize contributions and enhance
ecosystem participation.
Exchange Listings:
* Securing listings on major platforms like MEXC and exploring future options
with Bybit.
Satellite Deployment:
* Setting milestones for launching Nexus satellites to expand project capabilities
and visibility.
Economic Ecosystem:
* Exploring micro-economy integration and local currency use cases to drive
liquidity into Nexus.

Full transcription:
*Notice: This text was transcribed using AI. There is a high likelihood of spelling, grammatical, and translative errors.

Everybody, thanks for being patient, for this dev update. I've been walking in a lot of stuff.
And I've also been building a nice to do list for next week. So, I'm gonna go over what I've
done this week, and then I'm gonna go over next week. This week's primarily been
dominated.

Indexing System chat

I've been working on the exchanges. So found a bug in the indexing system, but I've never
been super, super happy with the way that some of the indexing logic worked. And I've
essentially had one database called underscore API, if anybody's familiar with it. And this
API contains all of the global index. For those that don't understand, a global index
essentially allows you to know with a single read where something is in the blockchain.

Otherwise, you rely on iterating blocks or iterating transactions or iterating sig chains. So,
name records, for instance, are 1. So, I've developed a I I like the indexing system that I
have in that sense, where I basically have a polymorphic function that can essentially be
inherited by each new API, and you can create your own custom indexing systems. That's
how the market works and all of that. But from some of these designs, I've decided I'm
gonna revamp a lot of it.

So that's one thing that I've been primarily focusing on, is revamping this indexing system. So
redesigning the architectures, I guess it's just a feel too. When I look at the code, I just I just I I
haven't been completely satisfied with it. So, I just am seeing some of the bugs, I think we
had a bug with, some of the credits not firing off for coin bases. I'm debugging that with
Neil, and there's these little idiosyncrasies that happen, and that's usually a symptom of
something that's maybe not coded entirely as well as it could.

So, this is kinda how I go. I just start coding. And if I see something I don't like, I keep doing it
over and over until I get it right. So I haven't really revamped the indexing system for quite
some time. So it's it's it's well and due.

So anybody that's had, you know, transactions where they notice that they don't credit
entirely correctly, this is this is gonna fix all of that entirely. So I'm breaking the indexing
system up into an API and a sessions folder. What this is gonna allow us to do is it'll allow you
to reset the state right now. If you have to reset your your sessions level indexes, they're all
coupled in with the global level indexes. And then it has to rescan the chain and rebuild all
those indexes because it's usually built when it's synchronizing.

But if you've already synchronized and you need to rebuild the chain itself or rebuild those
indexes, then you've gotta go through and start all over again, linear read of all the
transactions and so on and so forth. So that's something that I've been getting done. I've
been also, debugging some of the issues. I think one of the issues that I found is this op
ledger time stamp. It's a specific conditional op code that we have in our conditional virtual
machine, And it basically takes the timestamp of the ledger and the current ledger, but I'm
noticing that that's actually been causing quite a few problems.

I wanna completely I'm gonna disable that op code in in the hard fork and just rely on the
transaction timestamp for the caller. The the reason I had the op ledger is because it's
something that's reliable and you can't forge it and you can't try to manipulate the
timestamps. But I'm gonna put some tighter time tolerances in the transaction so that you
can't try to make a transaction happen too much in the past when it's actually received

into the memory pool and so and so forth, and it won't be able to be too much in the
future. So this will help with the expiring. It'll help it also, if there's a reorganization.

I have noticed that a transaction could get reorganized. And if it's an op ledger timestamp
and then the new block happens to be right out of bounds of that, then that transaction will
never actually get reprocessed. And then that can cause a halt in your sig chain and the
transaction processing. So I'm getting all of that put in. These are this is kinda 2 pronged
issues.

Xeggex and TradeOgre Issues

So those are 2 things that I've been working on this week. I've identified a lot of the issues
that we found with TradeOgre and Xeggex. Like as I said, I'm waiting on, some fixes from
Geraldo for, Xeggex. There's some implementation issues they had on their side, and then
there was an indexing bug on our side, and it didn't seem to, become apparent until the
indexes didn't fire off. Which I'm glad this happened though because we caught this
problem early. If it would've continued on, it could become a much bigger problem.

Fee Structure Improvements

So I'm also working on the fees asset. So what this is gonna do, if anybody saw, I made an
economics, voice memo earlier. But we're gonna be putting the fees in an asset. So what
this means is that some of these chain state parameters such as the cost of a name space
or the cost of a name or even the cost of a global name or any of the other types.

These will be actually stored in the chain state instead of a hard coded variable. So hard
coded means that it's something that's actually a constant that's compiled into the code.
So in order to change a hard coded variable, you have to update the software. And if it's a
consensus critical constant value, then that requires a hard fork. So this has been something
that I've noticed as the market has gone up.

We've always had this issue where the fees were more, you know, tolerable and negligible
when the price was low, but then the price goes up, and then the fees become a lot more
expensive. And then that requires a hard fork to undo. So we haven't really changed the
fees for, I think, a year or 2, which is good that I'm glad that we're finally getting this. But
what this is gonna happen is it's going to make it a dynamic allocation. So with a
transaction and a vote from the the community, we will be able to say, okay, well, we
wanna change these fees to this and these fees to that.

And without the need for a hard fork, we'll be able to change some of these chain state
parameters. Now this is also another important feature that we're gonna be able to be
using for other types of chain state parameters. Right? Most likely gonna be adding a few
additional ones because sometimes it is advantageous to be able to tweak some of these
such as the minimum stake interval, as far as how many blocks you have to wait for a new
stake block, and some of the other fundamental constant values. And this is cool because
this allows us to start bootstrapping off of our own blockchain state, which allows it to be a
lot more dynamic, easier to change, and ultimately, limiting the number of hard forks that
we have to do.

Hard forks

We wanna limit the number of hard forks because it's a big, I guess, challenge. You have to
take a couple weeks. Everybody has to update, and people don't necessarily always like to
have to force updates. So we're, we're trying to minimize that as much as possible.

IOS and Android Mobile Wallet

So one thing, I guess, big priorities that I have for next week, everybody to know mobile
wallets for the iOS and Android are our main priorities. So some of the things that I'm gonna
be doing that, I'm, figuring out this timeouts issue on the client mode. I think some of you
that have really large sig chains, if you log in on your client mode, you'll notice your balance
may not be entirely correct or some of the transaction history is missing. And that's because
this time out is basically going from the start to the end. So we're doing these different
batches of 50 to a 100 transactions for your sig chain or notifications. But if there happens to
be a hiccup or a slow and the Internet is not checking actually the last time that it was
received, it's just checking from how long it took for the request to fulfill entirely.

It's called a blocking message that I've developed and actually the lower level protocol.
And that way, we can basically send a request out to another node and wait for a
response, and it'll block waiting for that, which is really useful for the API if you're wanting to
load any state from the chain that you need to wait on from another node to deliver it to
you. So that's essentially how the client mode works. So that's something that I think has
been an issue, but what I'm also gonna be doing is I'm gonna test all of the features in the
API in client mode. Once I get that, like, I'm gonna get the iOS, which I need to make sure
that I I get some of the initialization code working better.

Make sure that's running really solid, actually running directly on my device. And then
Android, obviously. And then fixing time out issues, but I wanna run every API command,
such as running invoices, and make sure everything is running completely solid in there.
Ideally, I would like to see at least my back end work done on the mobile wallet by the end
of next week so that we can be ready to deploy those onto the app stores. I think it's time.

I appreciate everybody's patience on the matter, and it's it's gonna be good to get that all
done. So one of the big hurdles I've had is getting the build environment set up and then all
the others. And, you know, setting my priorities, I think, has been another challenge of mine
as well, because there's so much going on in my head and so many things I see to do. I
guess, setting the ones that are the most conceivable, reachable, and, you know, brings
the best benefit to you guys. And so that's one thing I've also been working on in
developing this week is setting my priorities correctly and making sure that I'm executing on
those priorities and setting my own internal deadlines and all of those good things.

Developer Updates

So, hopefully, we should be seeing a lot more progress next week. As I said, I'm gonna be
doing these development updates every Friday. If they're late at night, it's because I've
usually been working all day or I wanna get something done before. So I apologize if this is
too late for some people, but I guess you will get it as your Saturday morning.

Testing for Mobile Wallet / Full Release

So anyway, as I was saying earlier with the indexing, I'm gonna be breaking the API into
essentially a session and an API database. So this will help rebuilding indexes much better,
revamping the indexing system, and then this also is something that's heavily relied on for
the client mode. So between all of those things together, I think we'll have a much more
solid back end. And then we'll wanna get everybody testing. We're gonna release a new
beta, ideally, by the next time I do a development update. So if everybody could really
help on getting those tested out and report bugs, so that we can make sure we get all of
that squashed because, we need to get this we need to get these mobile wallets out.

There's been many, many people that have been asking and saying this is our highest
priority and most important. There's also some new use cases that I'm developing, not me
personally, but, somebody in the community has actually been forging connections with, in
in South America. And these these are gonna potentially be really amazing, beautiful use
cases, but we need to get the mobile wallets completely out and ready to go, so
everybody could use it. That's gonna be a big big slice of cheese for us, but once we get it,
I think it's gonna open a lot of doors for us. So what I would ideally like to get to next week,
this is something that I've been working on, kind of, in the back burner.

Embedded TLS

It's a branch called merging TLS, and you won't see a whole lot of commits on there
because I'm essentially deciphering. This is called embed TLS. So I'm having to basically
convert this old embedded TLS library into replacing a lot of our open SSL functions. So as
everybody knows, I'm working on getting open SSL almost completely eradicated from our
core. Getting rid of the legacy transactions, that will be one major step towards it.

And then we just have to support the brain pool 512 t 1 curves. And as we natively support
the, the Falcon, Falcon sign algorithms, which I think we use Falcon 1024.

Signature Aggregation

But anyway, another big feature that I'm actually focusing on as well, along with all of that is
signature aggregation. This is gonna be a big one. It's gonna save a lot of disk space.
Essentially, a signature chain is is a link. It's like your own blockchain. So one of the beautiful
things about this is that you can chain the signatures together. You know that if the very first
signature of the Genesis is included in a block and has a valid signature and you know the
very last transaction of the chain is included in a block and has a valid signature, you don't
need to have all of the signatures for every single transaction between those two points. So
for instance, a Falcon key, I think is about 800 bytes for a public key, and I think it's close to
900 bytes.

About 1.5, 1.6 kilobytes for the public key and the signature. This is one downside to
quantum resistant encryption is it's usually a lot larger key sizes, which means that you're
gonna have more disk space utilization. But what this is gonna do is it gets you aggregation.
So if you have 10 transactions in your sig chain, let's just say 1.5 kilobytes for, you know, or 2
kilobytes. Let's say just for a more conservative number.

Ten transactions means that you're gonna have 20 kilobytes of data that's going to be
included on the blockchain state. It's gonna be saved onto your disk. You do a 100, you
have 200 kilobytes, and you do a 1,000, and you have 2 megabytes worth of signatures. So
a thousand transaction in the sig chain is really not a large sig chain. Some people can
have multiple stakes per day.

I've seen some sig chains that have 5 to 10000. But as I said, 2 megabytes of data. Now
when you only have to aggregate the signature chain with the first and the last signatures in
the chain, then voila, you have now saved 2 megabytes of data. Now multiply that by a
1000 people, now you save 2 gigabytes of disk space. So this is a huge feature as far as
really taking advantage of our signature chain architecture so that we can know for sure
that we don't have to consume more disk space than we really need, and that it retains the
same level of security.

There's a few more nuances than just that. It's not quite so cut and dry on first and end
because you do have to keep a number of signatures available until a checkpoint until the
the chain can't be rolled back past that point. Because if you do have a reorganization,
then you do need to have the signatures so that you can continue to maintain that head of
the chain. So these are things that I'm thinking about all the time, and this is something that
I'm actually really excited to get put together.

New Use Cases

Onto the use cases as I was saying, there's a couple new use cases we're exploring for the
next couple weeks. Gig economy and even potentially, you know, local economic systems
we're working on. Kinda developing little micro economies. Anybody has any ideas too, or
or we're trying to figure out if you if you develop your own local currency that ends up being
something for a town or a city or a state even. You can create a lot of economic value for
people, but we wanna figure out besides this transaction fees are really helpful way that
when these micro economies are are created, it's gonna boost their own local economic
production because they're not gonna be tied to the existing currency system. But how are
we gonna bring this into Nexus?

This is something that we're wanting to look into, because we want all of the use cases in
some way to tie back in to provide liquidity in a Nexus, which is ultimately gonna help the
price maintain its value or increase in value, which is something that's going to then bring us
a more liquid market. And when we have more liquid market, then it's more usable as a
currency and so on and so forth. So that's something food for thought. That's something that
I've been brainstorming with somebody in the community about. Like I said, if anybody has
any fun ideas, feel free to jot them down here in in this channel about how creating your
own tirk token, to represent some sort of micro economy can bring liquidity into nexus.

Because there's a lot of places that could actually use developing their own local
currencies, and you create your fiat on and off, and you create kind of a stable coin. But
with these stable coins, besides transaction fees, because we want these people to be able
to transact for free, how are we gonna drive liquidity into nexus from that? It's a good
question. We're still working on the answer, so I can't say that we have it. But we're working
on it. But I just wanted to put that out there for anybody that wants to mull on it or has any
great ideas, please do let us know.

AI Neural Network

On the artificial intelligence use case, I'm currently modeling a very basic neural network
based off of a control. So my algorithm essentially is using more structured mathematics to
create more structured, predictable, and neural pathways, rather than unpredictable ones,
which also allows us to not have to compute for every single one of these in there. You only
compute a specific path, which is a mathematical structure. So ultimately, what this is
gonna do is it's gonna save us this exponential time calculation.

As long as these paths become ideal and it actually provides, you know, a greater intellect,
we're gonna save substantial amounts of computing power. And what this means is that if
we can get our algorithm, let's say, doing a 100 times faster than your typical artificial
intelligence algorithm, the hardware that is used to train and run these then becomes a 100

times more valuable. So an h one hundred is about 25,000 US dollars, which is a very
popular graphics card for, actually training these hey guys. So now take 25,000 and multiply
it by 100. You have $2,500,000, which is a very large amount.

That's essentially the amount of hardware. You've taken 1 card, 25,000 worth, and it now
has the power of $2,500,000 worth of hardware. So this is also a huge step for democratizing
AI and making it put it in everybody's hands. Most of the AIs are closed source, closed box.
You know, they have their own neural nets and everything like that, but what we wanna do
is put that in everyone's hand.

But even more so, we wanna make them safer and more predictable. It's a big issue with
MIT is that they have no idea how these things wire themselves. There's a lot of money being
thrown at it right now to understand that. We're looking to solve that and like I said, through
the proper structured mathematics and predictable neural routes, we're not gonna
necessarily be able to predict it entirely. You're gonna have some sort of standard
deviations off of that.

But based off of that, we're gonna have more predictable. So I just wanted to say more.
Not necessarily it's gonna be predictable, but that's hitting a really, really strong value
proposition. So like I said, I'm developing this with a control, with a typical neural network
architecture, sigmoid activation function, and then comparing that with our structured
mathematical neural networks and calculating the number of iterations that it takes to
reach a certain level of training data and to reach a certain level of accuracy. And that's
our control comparing it against so that we can compare our algorithmic improvements.

Now ideally, we would like to see as you add more neurons, it usually scales exponential.
What I mean what I mean by that is it's exponential time. It takes exponentially more
resources the more neurons you add. Ideally, we would like, if this works as we anticipate, to
have that scale more linearly. We wanna have more linear time scaling, which means that
the hardware that's required as far as 100 of 1000 h one hundreds may not be necessitated
at this point, which really opens the doors for everyday mom pops to actually be able to
start to have these powerful artificial intelligence systems that can help start running their
businesses, anything else.

I think the blockchain hype, at least what it was in 2018, is not what it used to be. I think a lot
of people have explored what it can and can't do. And blockchain's always gonna be
around, but I mean with quackta coins and all these other meme coins and all this
madness, I think there is a large amount of the population that is, I guess, disenfranchised
from it. Disenchanted from it. And so we're looking for the proper liquidity providers.

Like, as I was saying earlier about having use cases, you know, micro economies that can
provide liquidity into the nexus token. Ideally, we would like to see the same thing with this
artificial intelligence. And as I've said earlier, we have massive amounts of idle hardware.
Now imagine where, you know, everybody wanting to deploy their own AI has to buy Nexus
in order to do so. I think this is gonna generate a huge amount of liquidity and, you know,
basically be a petrodollar for Nexus.

And this is something I've been talking about for a long time that we need to find is we
need to find something that allows us to, I guess, reach this something that allows us to
basically reach this new liquidity that's just this bridge between using it as a currency and it
being just something that's a speculative instrument. Bridging that by having utility, and I
said this many times, and the utility that we're really I think is gonna be our hot one is, as I
said, artificial intelligence and this this network that we're creating. So this is something that
I've been doing on the side. Anybody that's concerned, if I'm not spending as much time on
Nexus, I'm doing my best to spend, you know, equal time, if not more, on Nexus. Nexus is
actually the more important one right now.

This other one that we are working on getting funding for it. And so, you know, we're gonna
be seeing that start to come fruition a lot more, but they're quite symbiotic because the
more matured this new network we can get that's gonna be built on Nexus, then the more
liquidity will drive into Nexus. Kinda like I said, the petrodollar. And so once the markets
become more liquid, then it becomes a more viable instrument for currency exchange and
using it as actual currency. Until then, our liquidity is based completely on speculation,
maybe transaction fees, maybe how people use it, but we want that to be based off of
actual use.

And I believe artificial intelligence is going to continue to grow over many decades to
come in ways that I don't know if blockchain is capable of doing. But with the combination
of the 2 together, I think we have a very, very powerful tool that can solve a lot of significant
issues.

Legacy Coins / Hard Fork / Satellites
Anyway, moving forward, hard fork. We are I'm working on this next week as well. What
we're doing, we voted on it. There's 16,000,000 coins in legacy. We're gonna truncate.
Basically, all of those coins were lost, and that's the difference between the actual coins on
Tridium and the coins on legacy. So if you still have coins on legacy, move your coins out.

We're gonna be taking the difference of how many's on Tridium and then the total money
supply, and that's going to mint out a certain amount of coins. If you wanna see in the
trading channel, we had a vote on it, and everybody really unanimously agreed. We want

to lock a bunch of that away, 10 to 12,000,000, into a kind of satellite war chest, and that's
gonna just basically sit in a locked account that'll be unspendable. That will sit there until we
reach a certain price point so that we can use that to start to deploy our own satellites. As I
was saying in some of the general channel, I'm gonna reach out to the original satellite
vendor.

Nexus 1

We spent about $30,000 on the Nexus 1 and see if they potentially would provide credit.
There's no guarantees on that. But ideally, we would like to see, at a certain price point, and
this is something that we can all discuss together, what price that we wanna start launching
Nexus 1. Generally, satellite vendor has launch services built in or very simply, you just
piggyback on a SpaceX rocket. That's what everybody does.

It's not a big deal. It's really easy to do, but I would like to start seeing that in the pipeline at
some point in the future so that it can be on our road map. So if you guys wanna start
thinking about what price you think we should launch Nexus 1 at, that would be a really
good discussion to have. It would be great to have that up. I mean, it's not gonna be an
incredibly functional satellite.

It'll, you know, fly over you every once in a while, and you may be able to up and down link
data to it. We can do some fun stuff with that as well if we wanna have it, you know,
represent something. It may not necessarily be running blockchain per se, but we can do
some fun stuff with the satellite. Maybe use it as a an encrypted messaging system, and
then it can pick up messages and then deliver them, store them forward, however we
wanna do. But that's another important one to put into the pipeline.

As I said, probably around 10 to 12,000,000 that we're gonna be having locked up for a
certain price point, and we should develop these price points to know how we're gonna
deploy each one of these individual satellites. And, you know, at 25¢, we launched Nexus 1.
50¢, we launched Nexus 2 and 3 and 4, so on so forth, etcetera, etcetera. And as I said, 5.8
gigahertz is what we're gonna be using. That's an ISM frequency.

Nexus 1 prior was a UHF VHF. It stands for ultra high frequency, very high frequency, and it's
basically ham radio. And so, yeah, I need an amateur radio license. ISM frequencies, you
don't need that. It's a really important distinction, and it's a really important innovation that
we're gonna be driving forward with this.

Other Redistributions

So, anyhow, there's also some other redistributions that are gonna be happening. Some of
the developers are gonna be paid for some of the back pay. I'm gonna be paid back for
some of the, amounts of nexus that I actually put towards the project through, I think it was,
like, 2019, 2020, to basically get Tritium over the line and that's really good because we not
gonna lie, we've had FOMO in 2021 and the price going up and it's hard for us to get a
stack. So I think that'll be really good for everybody to know too that the developers are
well taken care of and we're highly motivated. The other things that we're gonna be doing
is we're gonna be developing an exchange war chest.

New Exchange Listings

So right now, we have 2 offers for exchanges, MEXC and Digifinix. Now the listing fees are
rather large, but the, we're from the what we've discussed with the team, we're gonna be
going with m e x c. They have a refundable security deposit. That's gonna be in, USDT
tether. So that's gonna be pretty much one of the first uses of some of those funds beyond
the funds that are gonna be locked up for satellites.

So that we can get on a really good top tier one exchange. I think that's gonna change an
incredible amount of things to be on much more reputable, higher volume exchanges. So
that's our primary pursuit. As far as exchanges, then we can start getting into other ones. If
you guys wanna get us on Bybit, we need lots and lots of community activity, and we need
lots of volume.

So keep telling your friends. Let's keep building volume, keep building liquidity. We'll
eventually be able to get to Bybit, but the market makers that we've discussed with said
that Bybit is very difficult to get on. And I think they've just been getting bigger and bigger,
so it's most likely harder and harder. But we're up for a challenge.

Right? At some point, we'll be able to maintain that. So that's something to look forward to
in the future. Something that we're gonna wanna be developing towards. Right?

And I think that's something that I think will be really inspiring for all of us is to have things that
we know that we're all working towards. What would also be good is in the community, if
there's any bounties or things that you guys believe should be done that could be really
cool community activities, please write it in this chat. And let's start building a bounty list,
because now that we'll have more of these funds available, we can start building bounty
lists, and we can start creating more incentives for other people that wanna get more
involved or wanna earn a little bit more nexus. Let's really get that kicking. Having funding

limited as we have for the past 4 or 5 years, as far as the emission has been something that
has, been a challenge for us.

But with this legacy unburned, this really opens up a lot of doors for all of these things to be
possible that we had once wished to be possible. Now for anybody that's concerned about
that, just so you know, these funds are not gonna be hitting the market. Basically, 10 to
12,000,000 are gonna be locked up entirely until a certain price point. And then the
developers, the the little stacks that we receive, that's gonna be held. We're gonna be
staking that.

We wanna also show we're not here to spend that. That's our stack for as we grow. There
might be some liquidity depending on how m e x c uses to use. We have to give them some
of the nexus coin as well, with the Nexus. And then we also have to, get Tether.

MEXC Listing Fees

So for anybody that's open to it, we're gonna be doing a crowd fund for the m e x c listing,
which will essentially be an over the counter trade to get the listing fees so that none of that
touches the market. We don't want to touch the market at all. So figured, all of you guys,
you wanna get some Nexus for cheap before we get listed on a tier one exchange. That'll
also help us get listed on the tier one exchange. It's a double whammy.

Please, be open to, communicating that. So this will all be happening after the hard fork.
Once the code is deployed, we're gonna be doing a test on the test net, doing the hard
fork, activating on the test net, making sure everything goes well. And then once we
release that wallet update, it's gonna have a time activation. It's gonna be most likely 2
weeks from that point.

Legacy Coins Notice

And that means that you will have 2 weeks, if you still have legacy coins, to move your
legacy coins into a trading address. Otherwise, those coins are going to be considered
gone. Anybody that doesn't transfer any coins, you have to have a certain measure to
know, hey, these coins were, burnt. So that's gonna be our time limit. So between now and
when the wallet's released, you've got time if you still are holding on legacy.

And once that is released, we'll put a little timer in the wallet to let you know to make sure
that you switch over. And if you use legacy mode, that will also tell you to move all of your
coins. Big warning messages. We wanna make sure all of that's clean. There's not gonna be
any coin that's minted.

All we're gonna be doing is taking the difference between the actual supply and then the
supply that's on Tritium, and that's gonna become the new mint. And we're gonna have it
minted in a decentralized way to different addresses and different wallets. And like I said,
I'm gonna make a special account for the satellite funding that will be unlockable at a
specific hard fork in the future. We're gonna be having more hard forks because we're
gonna be adding more features, such as augmented contracts and all of this. So we want
to create that assurance so people know that we're gonna get the best of both worlds.

We can recover some of these lost coins, but then in a way, it is not gonna create any
negative economic impact. Right now, those coins are already out of circulation. So if we
removed them, from the supply list, it's not gonna change our economics in any way,
shape, or form. It's just gonna change the psychological belief of it. Since everybody's
already pretty well tuned to how much Nexus is in circulation, it would seem silly to not
essentially utilize that for all of these purposes that we've described.

Community Poll Results

So as I said, if you wanna verify the poll, it was done in the trading channel. We had actually
a very high voter turnout compared to normal polls, and it was pretty close to unanimous in
favor. We wanna get our new exchanges. We wanna get our satellites off the ground, and
we wanna make sure that all of the people that have been working hard for Nexus are
taken care of as well, as they've been taking care of us. So this is been my, progress update
for this past week, and I will give another progress upgrade next week.

I'm gonna start taking this format where I tell you what I've done for the week, and then tell
you what I'm gonna do for the next week. And then we can compare, and you guys can
check and say, hey, Colin. Did you choose this and choose that? And anything falling
behind, then we'll push that onto the next week. Ideally, I would like to be knocking out all
of these goals for the next week.

Wrap-Up

So as I said, ideally, I would like to see the mobile app pretty much ready to pack and ship.
So by next Friday, which means we'd have new betas, and we'll wanna test that out for a
week, at least after that, make sure all the bugs are fixed. Get exchanges back online. As I
said, removing up ledger, breaking up the indexing database into API and sessions, and
fixing some of the, like I said, issues in the the time out for the blocking message to make it
block, not based off of when the message is received, but to when it's gonna be finally,
when there's a a change in the actual state or a new message is received. Because you
could have a list of, like, a 100 transactions, and you wanna set the time out based off of
each transaction that's received, not after the entire list.

So and then again, the fees asset for the hard fork so that we can dynamically modify the
fees and potentially some change state parameters. And within the next few weeks, we're
also gonna be getting more clarity on some of these new use cases. And so that essentially
wraps us up for this week, and I will speak to you guys

Main Page

2025-02-08T13:31:52Z

Nexus wiki: add news section

== Nexus Wiki ==

A community-driven project for information about [https://nexus.io Nexus].

{{Special:AllPages}}

=== Developer Documentation ===

Under [https://nexus-wiki.org/index.php?search=&title=Special%3ASearch&profile=advanced&fulltext=1&ns0=1&ns3000=1 Advanced search], select the "Dev" namespace to include these pages.

{{Special:AllPages/Dev:}}

=== News ===

Under [https://nexus-wiki.org/index.php?search=&title=Special%3ASearch&profile=advanced&fulltext=1&ns0=1&ns3000=1 Advanced search], select the "News" namespace to include these pages.

{{Special:AllPages/News:}}

=== Recent Changes ===

{{Special:RecentChanges}}

''Original content provided by [https://nexus.io Nexus].''

TAO Roadmap

2025-02-02T15:04:42Z

Nexus wiki: update roadmap

= TAO Roadmap =

Our roadmap shows the progress made in each of the core stages of the TAO Framework which include the deployment of the Three-Dimensional Chain (3DC). Each letter represents one of the three consensus upgrades that correspond to the addition of a lock level on the 3DC.

== The roadmap to success ==

=== What are our major goals? ===

==== Mobile and Web Dapps ====

* Mobile Wallet Official Release
* Mobile P2P Quantum Resistant Encrypted Chat App with Programmable chat rooms and user authentication
* Mobile Wallet additions to allow Remote Sessions for using Mobile Wallet and/or Desktop Wallet as a 2FA source
* Decentralized Search Engine (https://nexus.io/search) for censorship free search and personalized results based on local data. No tracking, no ads, no censorship. Reputation and results ordering maintained on-chain
* LLD and LLP Service Layer for use in Web-Apps and also accessible through the LLL-TAO API System
* Mobile P2P and decentralized Uber dapp with 0% fees, on-chain reputation, and collateralized delivery functionality
* Mobile P2P DEX Interface for trading tokens on Nexus or Hybrid/Sister chains in a mobile Dapp
* Mobile P2P decentralized Geo-Spacial markets where you can buy and sell locally any legal product(s). This combines with the P2P decentralized delivery system so that goods can be transported as another additional revenue for drivers
* Mobile Filesystem Backup to use LLL-TAO File System to backup files on your device and allow access with the Nexus Dapp Suite
* LX-OS Microkernel with Linux Compatibility Layer to run certain flavors of Android OS such as Graphene and allow hardware compatibility and security beyond the Google Pixel

== Tritium++ ==

=== 5.1.x ===

==== Mobile Wallet ====

* Final Bugfixes to get Mobile wallet released

=== 5.2 ===

* SQL Language Updates: Upgrades to the SQL language in the API to add additional functionality and operators
* Removal of OpenSSL: Complete Removal of OpenSSL using our own embedded TLS and Cryptography in the LLC
* Integration of O(!) LLD Service: Integrate O(!) LLD Service completely into the complete Network
* New APIs: P2P Messenger API, Crypto API

=== 5.3 ===

* Remote Login System and API, Sigchain Ledger VM to create programmable access patterns to your sigchain with multiple sets of credentials

=== 6.0 ===

* Hard Fork for Difficulty Adjustments, Security Updates, Initial Filesystem Hosting, and Initial Augmented Contracts

=== 6.1 ===

* Post hard fork maintenance, DSL for Initial Augmented Contracts, Signature Chaining Space Reduction Complete

=== 7.0 ===

* Hard Fork for Security Updates, Pooled Staking, Incentivized Hybrid Mode, Final Incentivized Filesystem, and Final Augmented Contracts

=== 7.1 ===

* Post hard fork maintenance, Final DSL for Augmented Contracts

=== 8.0 ===

* Hard Fork for implementation of Starfish Funding Model as an on-chain enforced protocol, currently allocation is voted via trust keys on-chain but is not enforced by the ledger

== Amine ==

=== 9.0 ===

* Hard Fork to add additional hash reference ID for an Amine Shard(s)
* Initially 4 shards will be created using pBFT and nPoW + Trust that reference the main chain
* A user will be required to opt-in to a shard to process within in it, or can opt-out and process transactions using the Tritium Protocol
* This will be ongoing throughout Amine if any adjustments need to be made
* Hard Fork to deprecate UTxO, retain support for it in processing but not allow new UTxO transactions to be made

=== 9.1.x ===

* Post Hard-Fork Maintenance while releasing TAO only mode where we can truncate the chain at the first Tritium Block, and keep headers of the Legacy chain to save disk space
* Processing of Legacy transactions will be stopped and their history locked
* Any coins not in a sigchain at this point will be considered lost, and we can update our coin-supply

=== 10.0 ===

* Add Trust System to Mining Nodes to weight their proof of work with trust along with the actual work completed
* Add Trust System to Hybrid Network Sigchains to develop an algorithm of consistent contributions to the network in the form of NXS payments for use with the hybrid systems
* Add Trust System to Ambassador Network Sigchains to develop the algorithm of voting allocated funded between Embassies and as our final voting group

=== 10.1.x ===

* Post Hard-Fork maintenance, add global network data sharding using the LLD so that your node only has to retain part of the chain dataset, while keeping the main chain as a list of block headers for reference
* This is a stair stepped process that will eventually lead to full data and process sharding

== Obsidian ==

=== 11.0 ===

* Hard Fork to link all the voting groups into global systems maintenance such as fee management, and fund management to each DAO (Embassy) that's been allocated

=== 11.1.x ===

* Post Hard Fork Maintenance updates

=== 12.0 ===

* Hard Fork to develop a mining share system, where initial merkle proofs of all miners shares can be submitted over a Tritium Block and the reward distributed among the submitters of the given share
* This also weights the block based on the total proof of work, and the total trust that generated it
* Every miner can then contribute to each individual block, but must agree on the same merkleRoot to hash together

=== 12.1.x ===

* Post Hard Fork Maintenance updates

=== 13.0 ===

* Hard Fork to develop nPoS shards and cross links between L1 State channels along with full Data Sharding of transaction and register states

=== 13.1.x ===

* Post Hard Fork Maintenance updates

=== 14.0 ===

* Hard Fork to deprecate the main chain from the first 3D block, weave the L1, L2, and L3 layers together, still retaining only 4 L1 state channels

=== 14.1.x ===

* Post Hard Fork Maintenance updates

=== 15.0 ===

* Hard Fork to add the mitosis process for splitting of L1 state channels and L2 nPoS shards to increase capacity, or merging them to decrease capacity

=== 15.1.x ===

* Post Hard Fork Maintenance updates

=== 16.x.x ===

* Hard Fork and maintenance updates to adjust consensus parameters as final upgrade to the core protocol
* This could include modifying certain values for security, and touching up on any updates that need to be done to the 3DC

Nexus Constitution

2024-10-29T17:59:24Z

Nexus wiki: Protected "Nexus Constitution" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

== Article I ==

=== Section 1 ===

There are three branches of an Embassy: viz. Legislative, Executive, and Judicial. Each of these branches performs a specific task related to the healthy functioning of an Embassy.

=== Section 2 ===

There is a monthly budget allocated to a given Embassy by voting members of the global Nexus ecosystem. This budget is not to be managed by any one branch but two of three branches must sign to resolve budgets between branches. Budget ratification between branches must be completed every 90 days, whether to adjust budgets or maintain the same allocation. At these intervals, a State of the Branch must be issued to the voting members of the Embassy.

=== Section 3 ===

A branch is governed by a working body of no more than five individuals – each of whom have been elected as representatives of their given working groups. Each of these five representatives is allocated to facilitate strategic discussion, and is herein called a “chair”. Each chair is responsible for representing their groups budget requirements and signature chain – and facilitating consensus between their peers.

=== Section 4 ===

an arm is governed by a working body of no more than eight individuals – each of whom have been elected as representatives of their base working groups. Peers within an arm are namely responsible for taking the overall strategy developed by the five chairs of their corresponding branch – and generating a list of tasks to be executed. If this is the base group, meaning there are not more than eight individuals in the arm, it is then considered a task execution group.

=== Section 5 ===

Once an arm has established eight key roles, through the eight individuals, and it requires more personnel to complete the daily requirements – then it is appropriate for each of the eight individuals to form base groups of thirteen. A base group operates as the authority to elect representation – but also is the group responsible for task execution. If a group of thirteen – herein called a “node” has been formed by one of the eight individuals in the arm, then they are automatically the “node chair” until the next election cycle is to be held. If a node chair is not voted in on next election cycle – they are required to leave the arm’s group of eight, to be replaced with the new node chair.

=== Section 6 ===

Election cycles for chairs will be held on intervals not exceeding ninety days. When an election cycle is executed – the chair must alert their group of the election cycle, and ask them if they would like to nominate a challenger. If challenger(s) are nominated, a poll is created including challenger(s) and current chair. Nominee’s are required to have been involved in a given arm for no less than 90 days, and cannot be ‘self nominated’. The results of the poll determines the chair until the next election cycle. If a chair is not re-elected, they must leave all group(s) above their peer group that just voted. Election of chair requires a majority to pass (greater than 51%); this threshold cannot be modified with any internal processes.

a. chair must update group on quarterly basis to hold elections and provide proof
b. chair must transfer group ownership to new chair if not re-elected

=== Section 7 ===

If further capacity is needed in an arm, the group size can grow exponentially with the following group size layers:

8 => 13 => 21 => 34 => 55 => 89 => 144

Each layer would require election cycles of representation to move to the next layer, outlined in Section 6.

=== Section 8 ===

The working body of five individuals that govern a branch together vote to create a majority three of five for any of the following items:

a. vote to ratify joint budget proposals
b. request incident response or investigative audit of another branch or arm
c. ratify incident response documents from another branch or arm
d. vote to ratify joint protocols for internal branch standardization across arms

Main Page

2024-10-29T17:59:10Z

Nexus wiki: Protected "Main Page" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

Dev:Build a Nexus Mining Pool

2024-10-17T19:53:06Z

Nexus wiki:

Pool for Nexus Hash and Prime channels: https://github.com/Nexusoft/Mining-Pool

= Set Up NexusWebUI =

Instructions for Ubuntu 20.04

[https://github.com/Nexusoft/Mining-Pool/tree/main/NexusWebUI NexusWebUI]

Replace requirments.txt with the following (Python 3.12):

apply_defaults==0.1.6
asgiref==3.8.1
attrs==24.2.0
bson==0.5.10
certifi==2024.8.30
cffi==1.17.1
charset-normalizer==3.3.2
click==8.1.7
cryptography==43.0.1
Django==5.1.1
django-tables2==2.7.0
Faker==30.1.0
greenlet==3.1.1
grpcio==1.66.2
gunicorn==23.0.0
idna==3.10
importlib_metadata==8.5.0
jsonschema==4.23.0
jsonschema-specifications==2023.12.1
numpy==2.1.2
packaging==24.1
pandas==2.2.3
protobuf==5.28.2
pybson==0.5.9
pycparser==2.22
pyrsistent==0.20.0
python-dateutil==2.9.0.post0
python-decouple==3.8
pytz==2024.2
PyYAML==6.0.2
referencing==0.35.1
requests==2.32.3
rpds-py==0.20.0
setuptools==75.1.0
six==1.16.0
SQLAlchemy==2.0.35
sqlparse==0.5.1
text-unidecode==1.3
typing_extensions==4.12.2
tzdata==2024.2
urllib3==2.2.3
zipp==3.20.2

Run the following commands for basic UI setup:

sudo apt install -y cmake make python3.8-venv
git clone https://github.com/Nexusoft/Mining-Pool.git
cd Mining-Pool/NexusWebUI
python3 -m venv ./venv
source venv/bin/activate
pip install -r requirements.txt

.env:

SECRET_KEY=88888888888888888888888888888888
ALLOWED_HOSTS=localhost,127.0.0.1,hashpool.nexus-wiki.org
POOL_IP=127.0.0.1
POOL_PORT=50000
POOL_HOST=hashpool.nexus-wiki.org
POOL_USER=<user>
POOL_PWD=<pass>

mkdir logs
python3 manage.py migrate
python3 manage.py runserver 0.0.0.0:80

gunicorn test:

source venv/bin/activate
gunicorn --bind 0.0.0.0:80 NexusWebUI.wsgi

gunicorn setup:

sudo nano /etc/systemd/system/gunicorn.socket

[Unit]
Description=Gunicorn socket for Django project
[Socket]
ListenStream=/run/gunicorn.sock
[Install]
WantedBy=sockets.target

sudo nano /etc/systemd/system/gunicorn.service

[Unit]
Description=Gunicorn service for Django project
Requires=gunicorn.socket
After=network.target
[Service]
User=root
Group=www-data
WorkingDirectory=/root/Projects/GitHub/Mining-Pool/NexusWebUI
ExecStart=/root/Projects/GitHub/Mining-Pool/NexusWebUI/venv/bin/gunicorn \
--access-logfile - \
--error-logfile - \
--bind unix:/run/gunicorn.sock \
NexusWebUI.wsgi:application
[Install]
WantedBy=multi-user.target

sudo systemctl start gunicorn.socket
sudo systemctl enable gunicorn.socket
sudo systemctl status gunicorn.socket

nginx setup:

sudo apt install -y nginx
sudo nano /etc/nginx/sites-available/NexusWebUI

server {
listen 80;
server_name hashpool.nexus-wiki.org;

location = /favicon.ico { access_log off; log_not_found off; }

location / {
include proxy_params;
proxy_pass http://unix:/run/gunicorn.sock;
}
}

sudo ln -s /etc/nginx/sites-available/NexusWebUI /etc/nginx/sites-enabled
nginx -t
sudo systemctl restart nginx

certbot setup

sudo snap install --classic certbot
sudo ln -s /snap/bin/certbot /usr/bin/certbot
sudo certbot --nginx

Mining-Pool Setup

sudo apt-get install -y libssl-dev libsqlite3-dev sqlite3

update CMakeLists.txt to link openssl

cmake_minimum_required(VERSION 3.19)

project(NexusPool VERSION 1.0 LANGUAGES CXX C)

set(CMAKE_CXX_STANDARD 17)
set(CMAKE_CXX_STANDARD_REQUIRED ON)

configure_file(src/version.h.in version.h)

set(CPM_DOWNLOAD_VERSION 0.35.0)
set(CPM_DOWNLOAD_LOCATION "${CMAKE_BINARY_DIR}/cmake/CPM_${CPM_DOWNLOAD_VERSION}.cmake")

if(NOT (EXISTS ${CPM_DOWNLOAD_LOCATION}))
message(STATUS "Downloading CPM.cmake")
file(DOWNLOAD https://github.com/TheLartians/CPM.cmake/releases/download/v${CPM_DOWNLOAD_VERSION}/CPM.cmake ${CPM_DOWNLOAD_LOCATION})
endif()

include(${CPM_DOWNLOAD_LOCATION})

find_package(Threads REQUIRED)
# Find OpenSSL
find_package(OpenSSL REQUIRED)

#spdlog
CPMAddPackage(NAME spdlog GITHUB_REPOSITORY gabime/spdlog VERSION 1.9.2)

#nlohmann json
CPMAddPackage(NAME nlohmann_json GITHUB_REPOSITORY nlohmann/json VERSION 3.10.5)

#ASIO
CPMAddPackage("gh:chriskohlhoff/asio#asio-1-18-1@1.18.1")

# ASIO doesn't use CMake, we have to configure it manually. Extra notes for using on Windows:
#
# 1) If _WIN32_WINNT is not set, ASIO assumes _WIN32_WINNT=0x0501, i.e. Windows XP target, which is
# definitely not the platform which most users target.
#
# 2) WIN32_LEAN_AND_MEAN is defined to make Winsock2 work.
if(asio_ADDED)
add_library(asio INTERFACE)

target_include_directories(asio SYSTEM INTERFACE ${asio_SOURCE_DIR}/asio/include)
target_compile_definitions(asio INTERFACE ASIO_STANDALONE ASIO_NO_DEPRECATED)
target_link_libraries(asio INTERFACE Threads::Threads)

if(WIN32)
# macro see @ https://stackoverflow.com/a/40217291/1746503
macro(get_win32_winnt version)
if(CMAKE_SYSTEM_VERSION)
set(ver ${CMAKE_SYSTEM_VERSION})
string(REGEX MATCH "^([0-9]+).([0-9])" ver ${ver})
string(REGEX MATCH "^([0-9]+)" verMajor ${ver})
# Check for Windows 10, b/c we'll need to convert to hex 'A'.
if("${verMajor}" MATCHES "10")
set(verMajor "A")
string(REGEX REPLACE "^([0-9]+)" ${verMajor} ver ${ver})
endif("${verMajor}" MATCHES "10")
# Remove all remaining '.' characters.
string(REPLACE "." "" ver ${ver})
# Prepend each digit with a zero.
string(REGEX REPLACE "([0-9A-Z])" "0\\1" ver ${ver})
set(${version} "0x${ver}")
endif()
endmacro()

if(NOT DEFINED _WIN32_WINNT)
get_win32_winnt(ver)
set(_WIN32_WINNT ${ver})
endif()

message(STATUS "Set _WIN32_WINNET=${_WIN32_WINNT}")

target_compile_definitions(asio INTERFACE _WIN32_WINNT=${_WIN32_WINNT} WIN32_LEAN_AND_MEAN)
endif()
endif()

# Howard Hinnant's date library
CPMAddPackage(NAME date GITHUB_REPOSITORY HowardHinnant/date VERSION 3.0.1)

include_directories(${CMAKE_SOURCE_DIR}/include/)
link_directories(${CMAKE_SOURCE_DIR}/libs)

option(WITH_TESTS "Build with unit tests" OFF)

# OpenSSL
set(OPENSSL_USE_STATIC_LIBS TRUE)
find_package(OpenSSL REQUIRED)
include_directories(${OPENSSL_INCLUDE_DIR})

if(UNIX)
add_definitions(-DUNIX)
find_package(SQLite3 REQUIRED)
if (SQLITE3_FOUND)
include_directories(${SQLITE3_INCLUDE_DIRS})
endif (SQLITE3_FOUND)
endif()

if(WIN32)
add_definitions(-D_WIN32_WINT=0x0601 -DNOMINMAX -D_CRT_SECURE_NO_WARNINGS)
endif()

CPMAddPackage(NAME oatpp GITHUB_REPOSITORY GIT_REPOSITORY https://github.com/oatpp/oatpp.git VERSION 1.3.0 GIT_TAG "1.3.0" OPTIONS "OATPP_BUILD_TESTS OFF")

# add submodules
add_subdirectory(src/chrono)
add_subdirectory(src/common)
add_subdirectory(src/network)
add_subdirectory(src/config)
add_subdirectory(src/api)
add_subdirectory(src/LLP)
add_subdirectory(src/LLC)
add_subdirectory(src/TAO)
add_subdirectory(src/persistance)
add_subdirectory(src/reward)
add_subdirectory(src/nexus_http_interface)
add_subdirectory(src/pool)

if(WITH_TESTS)
add_subdirectory(tests)
endif()

add_executable(NexusPool
src/main.cpp
src/pool.cpp)

target_include_directories(NexusPool PUBLIC "${PROJECT_BINARY_DIR}")

target_link_libraries(NexusPool pool asio)

target_link_libraries(NexusPool Threads::Threads)

# Add the OpenSSL libraries to your target
target_link_libraries(NexusPool OpenSSL::SSL OpenSSL::Crypto)

# find_package(Threads REQUIRED)
target_link_libraries(NexusPool OpenSSL::SSL OpenSSL::Crypto Threads::Threads)

set_target_properties(NexusPool PROPERTIES VS_DEBUGGER_COMMAND_ARGUMENTS "-a F:/Work/Nexus Project/LLL-HPP/out/build/x64-Debug/api.conf -p pool.conf")

cmake CMakeLists.txt
make

pool.conf

{
"wallet_ip" : "127.0.0.1",
"wallet_port" : 8080,
"local_ip" : "127.0.0.1",
"local_port" : 0,
"public_ip" : "0.0.0.0",
"miner_listen_port" : 50000,
"mining_mode" : "HASH",
"connection_retry_interval" : 5,
"get_height_interval" : 2,
"session_expiry_time" : 30,
"legacy_mode" : false,
"pool" :
{
"account" : "default",
"pin" : "<pin>",
"fee" : 1,
"difficulty_divider" : 4,
"round_duration_hours" : 24,
"nxs_api_user" : "<user>,
"nxs_api_pw" : "<pass>"
},
"enable_ddos" : true,
"ddos" :
{
"ddos_rscore" : 20,
"ddos_cscore" : 2
},
"logfile" : "pool.log",
"log_level" : 2,
"persistance" :
{
"type" : "sqlite",
"file" : "nexuspool.db"
},
"update_block_hashes_interval" : 600,
"get_hashrate_interval" : 300,
"miner_notifications" : true
}

Dev:Build a Nexus Mining Pool

2024-10-17T19:43:15Z

Nexus wiki:

Pool for Nexus Hash and Prime channels: https://github.com/Nexusoft/Mining-Pool

= Set Up NexusWebUI =

Instructions for Ubuntu 20.04

[https://github.com/Nexusoft/Mining-Pool/tree/main/NexusWebUI NexusWebUI]

Replace requirments.txt with the following (Python 3.12):

apply_defaults==0.1.6
asgiref==3.8.1
attrs==24.2.0
bson==0.5.10
certifi==2024.8.30
cffi==1.17.1
charset-normalizer==3.3.2
click==8.1.7
cryptography==43.0.1
Django==5.1.1
django-tables2==2.7.0
Faker==30.1.0
greenlet==3.1.1
grpcio==1.66.2
gunicorn==23.0.0
idna==3.10
importlib_metadata==8.5.0
jsonschema==4.23.0
jsonschema-specifications==2023.12.1
numpy==2.1.2
packaging==24.1
pandas==2.2.3
protobuf==5.28.2
pybson==0.5.9
pycparser==2.22
pyrsistent==0.20.0
python-dateutil==2.9.0.post0
python-decouple==3.8
pytz==2024.2
PyYAML==6.0.2
referencing==0.35.1
requests==2.32.3
rpds-py==0.20.0
setuptools==75.1.0
six==1.16.0
SQLAlchemy==2.0.35
sqlparse==0.5.1
text-unidecode==1.3
typing_extensions==4.12.2
tzdata==2024.2
urllib3==2.2.3
zipp==3.20.2

Run the following commands for basic UI setup:

sudo apt install -y cmake make python3.8-venv
git clone https://github.com/Nexusoft/Mining-Pool.git
cd Mining-Pool/NexusWebUI
python3 -m venv ./venv
source venv/bin/activate
pip install -r requirements.txt

# edit .env_example and copy to .env
SECRET_KEY=88888888888888888888888888888888
ALLOWED_HOSTS=localhost,127.0.0.1,hashpool.nexus-wiki.org
POOL_IP=127.0.0.1
POOL_PORT=50000
POOL_HOST=hashpool.nexus-wiki.org
POOL_USER=<user>
POOL_PWD=<pass>

mkdir logs
python3 manage.py migrate
python3 manage.py runserver 0.0.0.0:80

gunicorn test:

source venv/bin/activate
gunicorn --bind 0.0.0.0:80 NexusWebUI.wsgi

gunicorn setup:

sudo nano /etc/systemd/system/gunicorn.socket

[Unit]
Description=Gunicorn socket for Django project
[Socket]
ListenStream=/run/gunicorn.sock
[Install]
WantedBy=sockets.target

sudo nano /etc/systemd/system/gunicorn.service

[Unit]
Description=Gunicorn service for Django project
Requires=gunicorn.socket
After=network.target
[Service]
User=root
Group=www-data
WorkingDirectory=/root/Projects/GitHub/Mining-Pool/NexusWebUI
ExecStart=/root/Projects/GitHub/Mining-Pool/NexusWebUI/venv/bin/gunicorn \
--access-logfile - \
--error-logfile - \
--bind unix:/run/gunicorn.sock \
NexusWebUI.wsgi:application
[Install]
WantedBy=multi-user.target

sudo systemctl start gunicorn.socket
sudo systemctl enable gunicorn.socket
sudo systemctl status gunicorn.socket

nginx setup:

sudo apt install -y nginx
sudo nano /etc/nginx/sites-available/NexusWebUI

server {
listen 80;
server_name hashpool.nexus-wiki.org;

location = /favicon.ico { access_log off; log_not_found off; }

location / {
include proxy_params;
proxy_pass http://unix:/run/gunicorn.sock;
}
}

sudo ln -s /etc/nginx/sites-available/NexusWebUI /etc/nginx/sites-enabled
nginx -t
sudo systemctl restart nginx

certbot setup

sudo snap install --classic certbot
sudo ln -s /snap/bin/certbot /usr/bin/certbot
sudo certbot --nginx

Mining-Pool Setup

sudo apt-get install -y libssl-dev libsqlite3-dev sqlite3

update CMakeLists.txt to link openssl

cmake_minimum_required(VERSION 3.19)

project(NexusPool VERSION 1.0 LANGUAGES CXX C)

set(CMAKE_CXX_STANDARD 17)
set(CMAKE_CXX_STANDARD_REQUIRED ON)

configure_file(src/version.h.in version.h)

set(CPM_DOWNLOAD_VERSION 0.35.0)
set(CPM_DOWNLOAD_LOCATION "${CMAKE_BINARY_DIR}/cmake/CPM_${CPM_DOWNLOAD_VERSION}.cmake")

if(NOT (EXISTS ${CPM_DOWNLOAD_LOCATION}))
message(STATUS "Downloading CPM.cmake")
file(DOWNLOAD https://github.com/TheLartians/CPM.cmake/releases/download/v${CPM_DOWNLOAD_VERSION}/CPM.cmake ${CPM_DOWNLOAD_LOCATION})
endif()

include(${CPM_DOWNLOAD_LOCATION})

find_package(Threads REQUIRED)
# Find OpenSSL
find_package(OpenSSL REQUIRED)

#spdlog
CPMAddPackage(NAME spdlog GITHUB_REPOSITORY gabime/spdlog VERSION 1.9.2)

#nlohmann json
CPMAddPackage(NAME nlohmann_json GITHUB_REPOSITORY nlohmann/json VERSION 3.10.5)

#ASIO
CPMAddPackage("gh:chriskohlhoff/asio#asio-1-18-1@1.18.1")

# ASIO doesn't use CMake, we have to configure it manually. Extra notes for using on Windows:
#
# 1) If _WIN32_WINNT is not set, ASIO assumes _WIN32_WINNT=0x0501, i.e. Windows XP target, which is
# definitely not the platform which most users target.
#
# 2) WIN32_LEAN_AND_MEAN is defined to make Winsock2 work.
if(asio_ADDED)
add_library(asio INTERFACE)

target_include_directories(asio SYSTEM INTERFACE ${asio_SOURCE_DIR}/asio/include)
target_compile_definitions(asio INTERFACE ASIO_STANDALONE ASIO_NO_DEPRECATED)
target_link_libraries(asio INTERFACE Threads::Threads)

if(WIN32)
# macro see @ https://stackoverflow.com/a/40217291/1746503
macro(get_win32_winnt version)
if(CMAKE_SYSTEM_VERSION)
set(ver ${CMAKE_SYSTEM_VERSION})
string(REGEX MATCH "^([0-9]+).([0-9])" ver ${ver})
string(REGEX MATCH "^([0-9]+)" verMajor ${ver})
# Check for Windows 10, b/c we'll need to convert to hex 'A'.
if("${verMajor}" MATCHES "10")
set(verMajor "A")
string(REGEX REPLACE "^([0-9]+)" ${verMajor} ver ${ver})
endif("${verMajor}" MATCHES "10")
# Remove all remaining '.' characters.
string(REPLACE "." "" ver ${ver})
# Prepend each digit with a zero.
string(REGEX REPLACE "([0-9A-Z])" "0\\1" ver ${ver})
set(${version} "0x${ver}")
endif()
endmacro()

if(NOT DEFINED _WIN32_WINNT)
get_win32_winnt(ver)
set(_WIN32_WINNT ${ver})
endif()

message(STATUS "Set _WIN32_WINNET=${_WIN32_WINNT}")

target_compile_definitions(asio INTERFACE _WIN32_WINNT=${_WIN32_WINNT} WIN32_LEAN_AND_MEAN)
endif()
endif()

# Howard Hinnant's date library
CPMAddPackage(NAME date GITHUB_REPOSITORY HowardHinnant/date VERSION 3.0.1)

include_directories(${CMAKE_SOURCE_DIR}/include/)
link_directories(${CMAKE_SOURCE_DIR}/libs)

option(WITH_TESTS "Build with unit tests" OFF)

# OpenSSL
set(OPENSSL_USE_STATIC_LIBS TRUE)
find_package(OpenSSL REQUIRED)
include_directories(${OPENSSL_INCLUDE_DIR})

if(UNIX)
add_definitions(-DUNIX)
find_package(SQLite3 REQUIRED)
if (SQLITE3_FOUND)
include_directories(${SQLITE3_INCLUDE_DIRS})
endif (SQLITE3_FOUND)
endif()

if(WIN32)
add_definitions(-D_WIN32_WINT=0x0601 -DNOMINMAX -D_CRT_SECURE_NO_WARNINGS)
endif()

CPMAddPackage(NAME oatpp GITHUB_REPOSITORY GIT_REPOSITORY https://github.com/oatpp/oatpp.git VERSION 1.3.0 GIT_TAG "1.3.0" OPTIONS "OATPP_BUILD_TESTS OFF")

# add submodules
add_subdirectory(src/chrono)
add_subdirectory(src/common)
add_subdirectory(src/network)
add_subdirectory(src/config)
add_subdirectory(src/api)
add_subdirectory(src/LLP)
add_subdirectory(src/LLC)
add_subdirectory(src/TAO)
add_subdirectory(src/persistance)
add_subdirectory(src/reward)
add_subdirectory(src/nexus_http_interface)
add_subdirectory(src/pool)

if(WITH_TESTS)
add_subdirectory(tests)
endif()

add_executable(NexusPool
src/main.cpp
src/pool.cpp)

target_include_directories(NexusPool PUBLIC "${PROJECT_BINARY_DIR}")

target_link_libraries(NexusPool pool asio)

target_link_libraries(NexusPool Threads::Threads)

# Add the OpenSSL libraries to your target
target_link_libraries(NexusPool OpenSSL::SSL OpenSSL::Crypto)

# find_package(Threads REQUIRED)
target_link_libraries(NexusPool OpenSSL::SSL OpenSSL::Crypto Threads::Threads)

set_target_properties(NexusPool PROPERTIES VS_DEBUGGER_COMMAND_ARGUMENTS "-a F:/Work/Nexus Project/LLL-HPP/out/build/x64-Debug/api.conf -p pool.conf")

cmake CMakeLists.txt
make

pool.conf

{
"wallet_ip" : "127.0.0.1",
"wallet_port" : 8080,
"local_ip" : "127.0.0.1",
"local_port" : 0,
"public_ip" : "0.0.0.0",
"miner_listen_port" : 50000,
"mining_mode" : "HASH",
"connection_retry_interval" : 5,
"get_height_interval" : 2,
"session_expiry_time" : 30,
"legacy_mode" : false,
"pool" :
{
"account" : "default",
"pin" : "<pin>",
"fee" : 1,
"difficulty_divider" : 4,
"round_duration_hours" : 24,
"nxs_api_user" : "<user>,
"nxs_api_pw" : "<pass>"
},
"enable_ddos" : true,
"ddos" :
{
"ddos_rscore" : 20,
"ddos_cscore" : 2
},
"logfile" : "pool.log",
"log_level" : 2,
"persistance" :
{
"type" : "sqlite",
"file" : "nexuspool.db"
},
"update_block_hashes_interval" : 600,
"get_hashrate_interval" : 300,
"miner_notifications" : true
}

Dev:Build a Nexus Mining Pool

2024-10-17T19:16:11Z

Nexus wiki:

Pool for Nexus Hash and Prime channels: https://github.com/Nexusoft/Mining-Pool

= Set Up NexusWebUI =

Instructions for Ubuntu 20.04

[https://github.com/Nexusoft/Mining-Pool/tree/main/NexusWebUI NexusWebUI]

Replace requirments.txt with the following (Python 3.12):

apply_defaults==0.1.6
asgiref==3.8.1
attrs==24.2.0
bson==0.5.10
certifi==2024.8.30
cffi==1.17.1
charset-normalizer==3.3.2
click==8.1.7
cryptography==43.0.1
Django==5.1.1
django-tables2==2.7.0
Faker==30.1.0
greenlet==3.1.1
grpcio==1.66.2
gunicorn==23.0.0
idna==3.10
importlib_metadata==8.5.0
jsonschema==4.23.0
jsonschema-specifications==2023.12.1
numpy==2.1.2
packaging==24.1
pandas==2.2.3
protobuf==5.28.2
pybson==0.5.9
pycparser==2.22
pyrsistent==0.20.0
python-dateutil==2.9.0.post0
python-decouple==3.8
pytz==2024.2
PyYAML==6.0.2
referencing==0.35.1
requests==2.32.3
rpds-py==0.20.0
setuptools==75.1.0
six==1.16.0
SQLAlchemy==2.0.35
sqlparse==0.5.1
text-unidecode==1.3
typing_extensions==4.12.2
tzdata==2024.2
urllib3==2.2.3
zipp==3.20.2

Run the following commands for basic UI setup:

sudo apt install -y cmake make python3.8-venv
git clone https://github.com/Nexusoft/Mining-Pool.git
cd Mining-Pool/NexusWebUI
python3 -m venv ./venv
source venv/bin/activate
pip install -r requirements.txt

# edit .env_example and copy to .env
SECRET_KEY=88888888888888888888888888888888
ALLOWED_HOSTS=localhost,127.0.0.1,hashpool.nexus-wiki.org
POOL_IP=172.0.0.0
POOL_PORT=50000
POOL_HOST=hashpool.nexus-wiki.org
POOL_USER=<user>
POOL_PWD=<pass>

mkdir logs
python3 manage.py migrate
python3 manage.py runserver 0.0.0.0:80

gunicorn test:

source venv/bin/activate
gunicorn --bind 0.0.0.0:80 NexusWebUI.wsgi

gunicorn setup:

sudo nano /etc/systemd/system/gunicorn.socket

[Unit]
Description=Gunicorn socket for Django project
[Socket]
ListenStream=/run/gunicorn.sock
[Install]
WantedBy=sockets.target

sudo nano /etc/systemd/system/gunicorn.service

[Unit]
Description=Gunicorn service for Django project
Requires=gunicorn.socket
After=network.target
[Service]
User=root
Group=www-data
WorkingDirectory=/root/Projects/GitHub/Mining-Pool/NexusWebUI
ExecStart=/root/Projects/GitHub/Mining-Pool/NexusWebUI/venv/bin/gunicorn \
--access-logfile - \
--error-logfile - \
--bind unix:/run/gunicorn.sock \
NexusWebUI.wsgi:application
[Install]
WantedBy=multi-user.target

sudo systemctl start gunicorn.socket
sudo systemctl enable gunicorn.socket
sudo systemctl status gunicorn.socket

nginx setup:

sudo apt install -y nginx
sudo nano /etc/nginx/sites-available/NexusWebUI

server {
listen 80;
server_name hashpool.nexus-wiki.org;

location = /favicon.ico { access_log off; log_not_found off; }

location / {
include proxy_params;
proxy_pass http://unix:/run/gunicorn.sock;
}
}

sudo ln -s /etc/nginx/sites-available/NexusWebUI /etc/nginx/sites-enabled
nginx -t
sudo systemctl restart nginx

certbot setup

sudo snap install --classic certbot
sudo ln -s /snap/bin/certbot /usr/bin/certbot
sudo certbot --nginx

Mining-Pool Setup

sudo apt-get install -y libssl-dev libsqlite3-dev sqlite3

update CMakeLists.txt to link openssl

cmake_minimum_required(VERSION 3.19)

project(NexusPool VERSION 1.0 LANGUAGES CXX C)

set(CMAKE_CXX_STANDARD 17)
set(CMAKE_CXX_STANDARD_REQUIRED ON)

configure_file(src/version.h.in version.h)

set(CPM_DOWNLOAD_VERSION 0.35.0)
set(CPM_DOWNLOAD_LOCATION "${CMAKE_BINARY_DIR}/cmake/CPM_${CPM_DOWNLOAD_VERSION}.cmake")

if(NOT (EXISTS ${CPM_DOWNLOAD_LOCATION}))
message(STATUS "Downloading CPM.cmake")
file(DOWNLOAD https://github.com/TheLartians/CPM.cmake/releases/download/v${CPM_DOWNLOAD_VERSION}/CPM.cmake ${CPM_DOWNLOAD_LOCATION})
endif()

include(${CPM_DOWNLOAD_LOCATION})

find_package(Threads REQUIRED)
# Find OpenSSL
find_package(OpenSSL REQUIRED)

#spdlog
CPMAddPackage(NAME spdlog GITHUB_REPOSITORY gabime/spdlog VERSION 1.9.2)

#nlohmann json
CPMAddPackage(NAME nlohmann_json GITHUB_REPOSITORY nlohmann/json VERSION 3.10.5)

#ASIO
CPMAddPackage("gh:chriskohlhoff/asio#asio-1-18-1@1.18.1")

# ASIO doesn't use CMake, we have to configure it manually. Extra notes for using on Windows:
#
# 1) If _WIN32_WINNT is not set, ASIO assumes _WIN32_WINNT=0x0501, i.e. Windows XP target, which is
# definitely not the platform which most users target.
#
# 2) WIN32_LEAN_AND_MEAN is defined to make Winsock2 work.
if(asio_ADDED)
add_library(asio INTERFACE)

target_include_directories(asio SYSTEM INTERFACE ${asio_SOURCE_DIR}/asio/include)
target_compile_definitions(asio INTERFACE ASIO_STANDALONE ASIO_NO_DEPRECATED)
target_link_libraries(asio INTERFACE Threads::Threads)

if(WIN32)
# macro see @ https://stackoverflow.com/a/40217291/1746503
macro(get_win32_winnt version)
if(CMAKE_SYSTEM_VERSION)
set(ver ${CMAKE_SYSTEM_VERSION})
string(REGEX MATCH "^([0-9]+).([0-9])" ver ${ver})
string(REGEX MATCH "^([0-9]+)" verMajor ${ver})
# Check for Windows 10, b/c we'll need to convert to hex 'A'.
if("${verMajor}" MATCHES "10")
set(verMajor "A")
string(REGEX REPLACE "^([0-9]+)" ${verMajor} ver ${ver})
endif("${verMajor}" MATCHES "10")
# Remove all remaining '.' characters.
string(REPLACE "." "" ver ${ver})
# Prepend each digit with a zero.
string(REGEX REPLACE "([0-9A-Z])" "0\\1" ver ${ver})
set(${version} "0x${ver}")
endif()
endmacro()

if(NOT DEFINED _WIN32_WINNT)
get_win32_winnt(ver)
set(_WIN32_WINNT ${ver})
endif()

message(STATUS "Set _WIN32_WINNET=${_WIN32_WINNT}")

target_compile_definitions(asio INTERFACE _WIN32_WINNT=${_WIN32_WINNT} WIN32_LEAN_AND_MEAN)
endif()
endif()

# Howard Hinnant's date library
CPMAddPackage(NAME date GITHUB_REPOSITORY HowardHinnant/date VERSION 3.0.1)

include_directories(${CMAKE_SOURCE_DIR}/include/)
link_directories(${CMAKE_SOURCE_DIR}/libs)

option(WITH_TESTS "Build with unit tests" OFF)

# OpenSSL
set(OPENSSL_USE_STATIC_LIBS TRUE)
find_package(OpenSSL REQUIRED)
include_directories(${OPENSSL_INCLUDE_DIR})

if(UNIX)
add_definitions(-DUNIX)
find_package(SQLite3 REQUIRED)
if (SQLITE3_FOUND)
include_directories(${SQLITE3_INCLUDE_DIRS})
endif (SQLITE3_FOUND)
endif()

if(WIN32)
add_definitions(-D_WIN32_WINT=0x0601 -DNOMINMAX -D_CRT_SECURE_NO_WARNINGS)
endif()

CPMAddPackage(NAME oatpp GITHUB_REPOSITORY GIT_REPOSITORY https://github.com/oatpp/oatpp.git VERSION 1.3.0 GIT_TAG "1.3.0" OPTIONS "OATPP_BUILD_TESTS OFF")

# add submodules
add_subdirectory(src/chrono)
add_subdirectory(src/common)
add_subdirectory(src/network)
add_subdirectory(src/config)
add_subdirectory(src/api)
add_subdirectory(src/LLP)
add_subdirectory(src/LLC)
add_subdirectory(src/TAO)
add_subdirectory(src/persistance)
add_subdirectory(src/reward)
add_subdirectory(src/nexus_http_interface)
add_subdirectory(src/pool)

if(WITH_TESTS)
add_subdirectory(tests)
endif()

add_executable(NexusPool
src/main.cpp
src/pool.cpp)

target_include_directories(NexusPool PUBLIC "${PROJECT_BINARY_DIR}")

target_link_libraries(NexusPool pool asio)

target_link_libraries(NexusPool Threads::Threads)

# Add the OpenSSL libraries to your target
target_link_libraries(NexusPool OpenSSL::SSL OpenSSL::Crypto)

# find_package(Threads REQUIRED)
target_link_libraries(NexusPool OpenSSL::SSL OpenSSL::Crypto Threads::Threads)

set_target_properties(NexusPool PROPERTIES VS_DEBUGGER_COMMAND_ARGUMENTS "-a F:/Work/Nexus Project/LLL-HPP/out/build/x64-Debug/api.conf -p pool.conf")

cmake CMakeLists.txt
make

pool.conf

{
"wallet_ip" : "127.0.0.1",
"wallet_port" : 8080,
"local_ip" : "127.0.0.1",
"local_port" : 0,
"public_ip" : "172.236.125.79",
"miner_listen_port" : 0,
"mining_mode" : "HASH",
"connection_retry_interval" : 5,
"get_height_interval" : 2,
"session_expiry_time" : 30,
"legacy_mode" : false,
"pool" :
{
"account" : "default",
"pin" : "<pin>",
"fee" : 1,
"difficulty_divider" : 4,
"round_duration_hours" : 24,
"nxs_api_user" : "<user>,
"nxs_api_pw" : "<pass>"
},
"enable_ddos" : true,
"ddos" :
{
"ddos_rscore" : 20,
"ddos_cscore" : 2
},
"logfile" : "pool.log",
"log_level" : 2,
"persistance" :
{
"type" : "sqlite",
"file" : "nexuspool.db"
},
"update_block_hashes_interval" : 600,
"get_hashrate_interval" : 300,
"miner_notifications" : true
}

Dev:Build a Nexus Mining Pool

2024-10-16T23:25:49Z

Nexus wiki:

Pool for Nexus Hash and Prime channels: https://github.com/Nexusoft/Mining-Pool

= Set Up NexusWebUI =

Instructions for Ubuntu 20.04

[https://github.com/Nexusoft/Mining-Pool/tree/main/NexusWebUI NexusWebUI]

Replace requirments.txt with the following (Python 3.12):

apply_defaults==0.1.6
asgiref==3.8.1
attrs==24.2.0
bson==0.5.10
certifi==2024.8.30
cffi==1.17.1
charset-normalizer==3.3.2
click==8.1.7
cryptography==43.0.1
Django==5.1.1
django-tables2==2.7.0
Faker==30.1.0
greenlet==3.1.1
grpcio==1.66.2
gunicorn==23.0.0
idna==3.10
importlib_metadata==8.5.0
jsonschema==4.23.0
jsonschema-specifications==2023.12.1
numpy==2.1.2
packaging==24.1
pandas==2.2.3
protobuf==5.28.2
pybson==0.5.9
pycparser==2.22
pyrsistent==0.20.0
python-dateutil==2.9.0.post0
python-decouple==3.8
pytz==2024.2
PyYAML==6.0.2
referencing==0.35.1
requests==2.32.3
rpds-py==0.20.0
setuptools==75.1.0
six==1.16.0
SQLAlchemy==2.0.35
sqlparse==0.5.1
text-unidecode==1.3
typing_extensions==4.12.2
tzdata==2024.2
urllib3==2.2.3
zipp==3.20.2

Run the following commands for basic UI setup:

sudo apt install -y cmake make python3.8-venv
git clone https://github.com/Nexusoft/Mining-Pool.git
cd Mining-Pool/NexusWebUI
python3 -m venv ./venv
source venv/bin/activate
pip install -r requirements.txt

# edit .env_example and copy to .env
SECRET_KEY=88888888888888888888888888888888
ALLOWED_HOSTS=localhost,127.0.0.1,hashpool.nexus-wiki.org
POOL_IP=172.0.0.0
POOL_PORT=80
POOL_HOST=hashpool.nexus-wiki.org
POOL_USER=<user>
POOL_PWD=<pass>

mkdir logs
python3 manage.py migrate
python3 manage.py runserver 0.0.0.0:80

gunicorn test:

source venv/bin/activate
gunicorn --bind 0.0.0.0:80 NexusWebUI.wsgi

gunicorn setup:

sudo nano /etc/systemd/system/gunicorn.socket

[Unit]
Description=Gunicorn socket for Django project
[Socket]
ListenStream=/run/gunicorn.sock
[Install]
WantedBy=sockets.target

sudo nano /etc/systemd/system/gunicorn.service

[Unit]
Description=Gunicorn service for Django project
Requires=gunicorn.socket
After=network.target
[Service]
User=root
Group=www-data
WorkingDirectory=/root/Projects/GitHub/Mining-Pool/NexusWebUI
ExecStart=/root/Projects/GitHub/Mining-Pool/NexusWebUI/venv/bin/gunicorn \
--access-logfile - \
--error-logfile - \
--bind unix:/run/gunicorn.sock \
NexusWebUI.wsgi:application
[Install]
WantedBy=multi-user.target

sudo systemctl start gunicorn.socket
sudo systemctl enable gunicorn.socket
sudo systemctl status gunicorn.socket

nginx setup:

sudo apt install -y nginx
sudo nano /etc/nginx/sites-available/NexusWebUI

server {
listen 80;
server_name hashpool.nexus-wiki.org;

location = /favicon.ico { access_log off; log_not_found off; }

location / {
include proxy_params;
proxy_pass http://unix:/run/gunicorn.sock;
}
}

sudo ln -s /etc/nginx/sites-available/NexusWebUI /etc/nginx/sites-enabled
nginx -t
sudo systemctl restart nginx

certbot setup

sudo snap install --classic certbot
sudo ln -s /snap/bin/certbot /usr/bin/certbot
sudo certbot --nginx

Mining-Pool Setup

sudo apt-get install -y libssl-dev libsqlite3-dev sqlite3

update CMakeLists.txt to link openssl

cmake_minimum_required(VERSION 3.19)

project(NexusPool VERSION 1.0 LANGUAGES CXX C)

set(CMAKE_CXX_STANDARD 17)
set(CMAKE_CXX_STANDARD_REQUIRED ON)

configure_file(src/version.h.in version.h)

set(CPM_DOWNLOAD_VERSION 0.35.0)
set(CPM_DOWNLOAD_LOCATION "${CMAKE_BINARY_DIR}/cmake/CPM_${CPM_DOWNLOAD_VERSION}.cmake")

if(NOT (EXISTS ${CPM_DOWNLOAD_LOCATION}))
message(STATUS "Downloading CPM.cmake")
file(DOWNLOAD https://github.com/TheLartians/CPM.cmake/releases/download/v${CPM_DOWNLOAD_VERSION}/CPM.cmake ${CPM_DOWNLOAD_LOCATION})
endif()

include(${CPM_DOWNLOAD_LOCATION})

find_package(Threads REQUIRED)
# Find OpenSSL
find_package(OpenSSL REQUIRED)

#spdlog
CPMAddPackage(NAME spdlog GITHUB_REPOSITORY gabime/spdlog VERSION 1.9.2)

#nlohmann json
CPMAddPackage(NAME nlohmann_json GITHUB_REPOSITORY nlohmann/json VERSION 3.10.5)

#ASIO
CPMAddPackage("gh:chriskohlhoff/asio#asio-1-18-1@1.18.1")

# ASIO doesn't use CMake, we have to configure it manually. Extra notes for using on Windows:
#
# 1) If _WIN32_WINNT is not set, ASIO assumes _WIN32_WINNT=0x0501, i.e. Windows XP target, which is
# definitely not the platform which most users target.
#
# 2) WIN32_LEAN_AND_MEAN is defined to make Winsock2 work.
if(asio_ADDED)
add_library(asio INTERFACE)

target_include_directories(asio SYSTEM INTERFACE ${asio_SOURCE_DIR}/asio/include)
target_compile_definitions(asio INTERFACE ASIO_STANDALONE ASIO_NO_DEPRECATED)
target_link_libraries(asio INTERFACE Threads::Threads)

if(WIN32)
# macro see @ https://stackoverflow.com/a/40217291/1746503
macro(get_win32_winnt version)
if(CMAKE_SYSTEM_VERSION)
set(ver ${CMAKE_SYSTEM_VERSION})
string(REGEX MATCH "^([0-9]+).([0-9])" ver ${ver})
string(REGEX MATCH "^([0-9]+)" verMajor ${ver})
# Check for Windows 10, b/c we'll need to convert to hex 'A'.
if("${verMajor}" MATCHES "10")
set(verMajor "A")
string(REGEX REPLACE "^([0-9]+)" ${verMajor} ver ${ver})
endif("${verMajor}" MATCHES "10")
# Remove all remaining '.' characters.
string(REPLACE "." "" ver ${ver})
# Prepend each digit with a zero.
string(REGEX REPLACE "([0-9A-Z])" "0\\1" ver ${ver})
set(${version} "0x${ver}")
endif()
endmacro()

if(NOT DEFINED _WIN32_WINNT)
get_win32_winnt(ver)
set(_WIN32_WINNT ${ver})
endif()

message(STATUS "Set _WIN32_WINNET=${_WIN32_WINNT}")

target_compile_definitions(asio INTERFACE _WIN32_WINNT=${_WIN32_WINNT} WIN32_LEAN_AND_MEAN)
endif()
endif()

# Howard Hinnant's date library
CPMAddPackage(NAME date GITHUB_REPOSITORY HowardHinnant/date VERSION 3.0.1)

include_directories(${CMAKE_SOURCE_DIR}/include/)
link_directories(${CMAKE_SOURCE_DIR}/libs)

option(WITH_TESTS "Build with unit tests" OFF)

# OpenSSL
set(OPENSSL_USE_STATIC_LIBS TRUE)
find_package(OpenSSL REQUIRED)
include_directories(${OPENSSL_INCLUDE_DIR})

if(UNIX)
add_definitions(-DUNIX)
find_package(SQLite3 REQUIRED)
if (SQLITE3_FOUND)
include_directories(${SQLITE3_INCLUDE_DIRS})
endif (SQLITE3_FOUND)
endif()

if(WIN32)
add_definitions(-D_WIN32_WINT=0x0601 -DNOMINMAX -D_CRT_SECURE_NO_WARNINGS)
endif()

CPMAddPackage(NAME oatpp GITHUB_REPOSITORY GIT_REPOSITORY https://github.com/oatpp/oatpp.git VERSION 1.3.0 GIT_TAG "1.3.0" OPTIONS "OATPP_BUILD_TESTS OFF")

# add submodules
add_subdirectory(src/chrono)
add_subdirectory(src/common)
add_subdirectory(src/network)
add_subdirectory(src/config)
add_subdirectory(src/api)
add_subdirectory(src/LLP)
add_subdirectory(src/LLC)
add_subdirectory(src/TAO)
add_subdirectory(src/persistance)
add_subdirectory(src/reward)
add_subdirectory(src/nexus_http_interface)
add_subdirectory(src/pool)

if(WITH_TESTS)
add_subdirectory(tests)
endif()

add_executable(NexusPool
src/main.cpp
src/pool.cpp)

target_include_directories(NexusPool PUBLIC "${PROJECT_BINARY_DIR}")

target_link_libraries(NexusPool pool asio)

target_link_libraries(NexusPool Threads::Threads)

# Add the OpenSSL libraries to your target
target_link_libraries(NexusPool OpenSSL::SSL OpenSSL::Crypto)

# find_package(Threads REQUIRED)
target_link_libraries(NexusPool OpenSSL::SSL OpenSSL::Crypto Threads::Threads)

set_target_properties(NexusPool PROPERTIES VS_DEBUGGER_COMMAND_ARGUMENTS "-a F:/Work/Nexus Project/LLL-HPP/out/build/x64-Debug/api.conf -p pool.conf")

cmake CMakeLists.txt
make

pool.conf

{
"wallet_ip" : "127.0.0.1",
"wallet_port" : 8080,
"local_ip" : "127.0.0.1",
"local_port" : 0,
"public_ip" : "172.236.125.79",
"miner_listen_port" : 0,
"mining_mode" : "HASH",
"connection_retry_interval" : 5,
"get_height_interval" : 2,
"session_expiry_time" : 30,
"legacy_mode" : false,
"pool" :
{
"account" : "default",
"pin" : "<pin>",
"fee" : 1,
"difficulty_divider" : 4,
"round_duration_hours" : 24,
"nxs_api_user" : "<user>,
"nxs_api_pw" : "<pass>"
},
"enable_ddos" : true,
"ddos" :
{
"ddos_rscore" : 20,
"ddos_cscore" : 2
},
"logfile" : "pool.log",
"log_level" : 2,
"persistance" :
{
"type" : "sqlite",
"file" : "nexuspool.db"
},
"update_block_hashes_interval" : 600,
"get_hashrate_interval" : 300,
"miner_notifications" : true
}

2024-10-10T13:26:50Z

Nexus wiki: Created page with "= NEXUS WIKI CAN BE WRONG = Nexus Wiki is an encyclopedia on the Internet that is edited by anyone who wants to help. The way it works means that anyone with who can view the Internet can change what is written. When you read Wikipedia, you should remember that we cannot make sure that our information is checked by people who can make it complete, accurate or reliable. That does not mean that there is not useful, correct information in Nexus Wiki; there is lots. Howev..."

Dev:Nexus API Specification

2024-10-08T19:03:28Z

Nexus wiki: Created page with "he Nexus Framework contains a powerful RESTful Application Programming Interface or API that allows developers to easily develop decentralized applications or Dapps for short. This API is broken into a set of commands that are a logically grouped collection of functions. [https://app.swaggerhub.com/apis/nexus.nexipedia/Nexus-API Nexus API Specification]"

he Nexus Framework contains a powerful RESTful Application Programming Interface or API that allows developers to easily develop decentralized applications or Dapps for short. This API is broken into a set of commands that are a logically grouped collection of functions.

[https://app.swaggerhub.com/apis/nexus.nexipedia/Nexus-API Nexus API Specification]

TAO Roadmap

2024-10-08T18:11:07Z

Nexus wiki:

= Tritium =

== Trust System ==

This milestone marks the introduction of the new trust key decay rate, with trust decreasing 3 times faster than it accrues. Replacing the hard 24-hour time limit in September 2018, the new decay rate gives staking wallets greater ability to retain trust and more accurately reflects the effort invested in securing the blockchain.

Released 2018-09-16

== LISP ==

The Locator/ID Separation Protocol is an important network protocol that allows one to control their IP addressing, without relying on ISPs for allocation.

Released 2019-01-31

== Legacy Mode ==

Full update to Nexus Core software supporting Legacy blockchain operation. This mode features fast sync times, instant loading, and a small memory and disk footprint.

Released 2019-06-26

== Interface / Wallet ==

The Nexus interface supports full wallet function. Modular functionality allows custom themes and addon modules such as Binance trading, multi-coin storage, a block explorer, Tritium features, and anything module developers might dream up.

Released 2019-06-26

== API / SDK ==

Our API gives developers access to a wide set of features available through a simple HTTP interface. This provides easy access to smart contracts that can be embedded directly into web applications and existing login systems.

Released 2019-11-05

= Tritium++ =

== Hybrid Mode ==

An important feature, hybrid mode is capable of forming an individual network out of the box, making it a highly useful tool for businesses that wish to utilize our blockchain technology, while retaining high levels of privacy.

Release 2021-09-07

== Contract Domain Specific Languages ==

Contract-specific programming languages will be provided that will include internal safety mechanisms such as catching overflows to allow more complex contract development, while remaining less prone to error.

== P2P Market API ==

The Decentralized Exchange will sit mainly in the Logical / Interface layers, with the exchange itself being facilitated by a conditional contract on the Operations layer. The DEX will be able to be used to trade tokens and assets listed on Nexus, promoting the development of decentralized marketplaces where any type of asset can be traded in a truly free, peer to peer manner without a need for a custodian service. There is no authority that designates the process of listing, and there are no other parties involved in the exchange other than the buyer and the seller.

Released 2023-04-26

== Mobile Wallet ==

Our official mobile wallet will be developed using most of the software that runs the desktop wallet, with changes to the interface to be more mobile friendly, and daemon packages that incrementally will be improved over time to enable more contract functionality and staking. The Mobile Wallet will still have the modular design of the Nexus Wallet, so that developers can extend it with their DApps by simply deploying new modules to the Wallet.

== Pooled Staking ==

As more people continue to join the staking process, the network becomes more secure through the increase in the Trust channel difficulty. Though this provides benefits to the network as a whole, it constantly drives up the required amount of coins to maintain a Trust key. Pooled Staking solves this by giving smaller balances the ability to collaborate with peers, ultimately resulting in increased staking access to the regular user, and higher network security. This approach does not require a central service, since it will work as a sub network inside Nexus, that itself comes to consensus on the Trust keys to be included. This is a pure, decentralized, staking protocol that will benefit the entire network as a whole.

== Object Modeling ==

Object Modeling is a new feature that will extend the API layer allowing developers to model their Object Registers in languages such as XML (Extensible Markup Language). This will also contain modeling languages that will make it possible for advanced developers to work with lower level object operations. These could include using specific data types and specifiers, developing more complex object behavior through Augmented Contracts, or creating extra conditions that regulate the object’s overall behavior.

== Augmented Contracts ==

Augmented Contracts are the second type of contracts that will be available in the Tritium Protocol. These types of contracts extend the Conditional VM (Virtual Machine that processes Conditional Statements) to provide additional benefits including, but not limited to, methods, functions, operation overloading, and encapsulation. Augmented contracts add a layer of complexity and processing, so will carry a higher fee to execute. This will require more on-chain processing, but overall makes our Contract Engine much more powerful.

== Protected Assets ==

Protected Assets are a type of asset with the addition that a ‘Master’ owner retains the right to revoke access to the asset. This essentially allows the asset creator to have permanent access to an asset, which is necessary for securities, collateralized loans (DeFi), non-transferable assets (Tickets, Educational/Professional Awards and Certificates, Certificates of Insurance, Licenses etc.). They are also useful for protecting the asset from being transferred to unqualified parties, or in other words, parties that do not fulfill the requirements set out by asset creator.

== LLD Global File System ==

The LLD global file system will support secondary files that record assets to be stored and retrieved through network operations, providing a seamless interface for managing assets and data.

= Amine =

== pBFT + Reputation Channels (L1) ==

This new architectural component will process transactions in parallel, using reputation as an additional weight to provide higher security. The transaction speed of L1 channels will vary based on the risk that a merchant wishes to assume, ranging from sub-second speeds to 5 seconds. For higher value transactions, it will be recommended that they receive additional weight from validation on the next consensus layer: L2, reducing transaction speed to 15 seconds plus.

== pBFT + PoS Trust Network (L2) ==

As an extension to the existing Proof of Stake system, L2 will form the second layer of consensus above the L1. The L2 layer ensures safety and liveness, cross-shard communication, and resolves conflicts from the L1 layer. It represents the horizontal chaining of the L1 channels, and is a major step towards a truly decentralized and scalable ledger.

== Network Data Sharding ==

Data sharding is an essential facet of our ledger design in order to achieve long-term scalability. Amine will provide the opportunity for nodes to run in “shard” mode, which will lower their disk and memory usage, even when the network is under high load.

== LISP Multicast Links for (L1) and (L2) ==

Using LISP, the L1 and L2 layers will have their own Multicast links, therefore packets and transactions will route in constant time no matter how many nodes are part of the system.

== Application Store ==

Here applications and modules will be able to be shared and sold in a decentralized marketplace. Modules will provide developers the building blocks to create applications.

= Obsidian =

== Extended Network Data Sharding ==

Data sharding in Obsidian will extend to critical network functions, resulting in nodes being required to store only a portion of the overall chain. Note, this is data sharding, not computational sharding, which means once data has been processed, it can be partitioned and stored between nodes. The result will be an increase of data storage as more nodes join the network.

== Decentralized Mining & Merkle Share Pool (L3) ==

This component will use Proof of Work based mining shares computed from the work performed by the nodes of L2. Consensus will be determined by the largest value of shares + trust, in order to reach the final agreement on the most valid 3D block.

== DAO: L1 Voting Group (Implement) ==

The L1 voting group will provide voting rights to validators who are new to the network, and therefore do not have enough resources to participate in the L2 consensus. Voting weight is based on reputation.

== DAO: L2 Voting Group (Extend) ==

The L2 voting group will extend Tritium’s “Ambassador DAO” and provide voting rights to validators who have reached a reputation threshold. Voting weight is based on reputation multiplied by stake.

== DAO: L3 Voting Group ==

The L3 voting group will provide voting rights to miners. Voting weight is based on mining power (average weight of mined shares over time) multiplied by reputation.

== LISP Multicast Links for L3 ==

Shares on L3 will use LISP Multicast links allowing the efficient broadcasting of mined shares, and the acceptance of L2 hashes for computation by L3 nodes.

Nexus Wiki:About

2024-10-08T17:27:29Z

Nexus wiki: Created page with "A community-driven project for information about [https://nexus.io Nexus]."

A community-driven project for information about [https://nexus.io Nexus].

2024-10-06T23:22:04Z

Nexus wiki:

The Finance API provides methods for sending and receiving NXS or other tokens between users / accounts, creating accounts, and managing staking. The full supported endpoint of the finance URI is as follows:

finance/verb/noun/filter/operator

Minimum required components of the URI:

finance/verb/noun

= Direct Endpoints =

The following commands are direct endpoints not using the supported nouns and verbs:

finance/get/balances
finance/get/stakeinfo
finance/set/stake
finance/void/transaction
finance/migrate/accounts

= Supported Nouns =

The following nouns are supported for this API command-set:

{| class="wikitable"
! Noun !! Description
|-
| account || An object register containing a token-id and balance
|-
| any || An object selection noun allowing mixed accounts of different tokens
|-
| all || An object selection noun to collect all accounts for given token type
|-
| token || An object register containing a token-id, balance, supply, and decimals
|-
| trust || An object register containing a token-id, balance, and trust
|}

= Supported Verbs =

The following verbs are currently supported by this command-set:

{| class="wikitable"
! Verb !! Description !! Nouns
|-
| burn || Remove a given token from circulation || account
|-
| create || Generate a new object of supported type || account, token
|-
| credit || Claim funds issued to account from debit || account, any, token
|-
| debit || Issue funds from a supported type || account, any, token
|-
| get || Get object of a supported type || account, trust, token
|-
| history || Generate the history of all last states || account, trust, token
|-
| list || List all objects owned by a given user || account, trust, token
|-
| transactions || List all transactions that modified specified object || account, trust, token
|}

= Verbs =

=== burn ===

This method can be used to take tokens permanently out of the current supply in a process commonly known as "burning". The method will debit a token account and send the tokens back to the token address. However the transaction contains a condition that will always evaluate to false, guaranteeing that the debit cannot be credited by the token issuer nor the sender. The result is that the amount burned will always appear in the "pending" balance of the token.

finance/burn/account

This command only supports the account noun.

==== Parameters ====

{| class="wikitable"
! Name !! Description !! Required
|-
| address || Register address of the account to debit the tokens from the be burnt || Required if name is not provided
|-
| amount || amount of tokens to burn || yes
|-
| name || In the format username:name (for local names) or namespace::name (for names in a namespace). If you are logged in, the username: field is not required. || Required if address is not provided
|-
| pin || PIN for this profile. || Required if locked.
|-
| reference || A 64-bit unsigned integer in the range of 0 to 18446744073709551615. || no
|-
| session || User session ID || Required if argument -multiuser=1 is set
|}

==== Return Values ====

{| class="wikitable"
! Name !! Description
|-
| address || Register address
|-
| success || Boolean flag indicating that the burn was successful
|-
| txid || The hash of the transaction that was generated for this tx. If using -autotx this field will be omitted.
|}

==== Example Response JSON ====

{
"success": true,
"address": "8BfLgEprhbHs82LxUkJR9jhQufRZf49g73Nt8XTGevfiyy7ijhb",
"txid": "01854fe4fdf0d59aebb3a880141484f0542af061cbebfd468db3fcecd13f63a986d990cf669ca4a60822a82b2d4fc7e7e474801a01bff86a35fd0a147a5a62da"
}

=== create ===

Create a new object register specified by given noun.

finance/create/noun

This command does not support the any or all nouns.

==== Parameters ====

{| class="wikitable"
! Name !! Description !! Required
|-
| data || Input for the data object || Optional for any noun
|-
| decimals || Total number of significant figures. Defaults to 2. || no
|-
| name || UTF-8 encoded string that will generate a name object register that points to new object. If noun is token this will be created as a global name. || no
|-
| pin || PIN for this profile. || Required if locked.
|-
| session || User session ID || Required if argument -multiuser=1 is set
|-
| supply || Sets the maximum token supply || Required for token noun
|-
| token || Base58-encoded address or ticker name. Defaults to NXS. || no
|}

==== Return Values ====

{| class="wikitable"
! Name !! Description
|-
| address || Register address of the created object
|-
| success || Boolean flag indicating whether the object register has been created
|-
| txid || The hash of the transaction that was generated for this tx. If using -autotx this field will be omitted.
|}

==== Example Response JSON ====

{
"success": true,
"address": "8ESvYizqdApiuKEBjZMF1hnB8asDqECaDwAstcH3UtJ4Z6ceCn2",
"txid": "0131e17af8029b414814283a3d90813d12c238db6ddab213440249b795090a9cd77079d5804ec38303a59414d87108d4e44bf31f54a6c176285281a88ab5d737"
}

=== credit ===

Create a new object register specified by given noun.

finance/credit/noun

This command supports the account, any, and token nouns.

==== Parameters ====

{| class="wikitable"
! Name !! Description !! Required
|-
| pin || PIN for this profile. || Required if locked.
|-
| session || User session ID || Required if argument -multiuser=1 is set
|-
| txid || The transaction hash being credited || yes
|}

==== Return Values ====

{| class="wikitable"
! Name !! Description
|-
| success || Boolean flag indicating whether the object register has been credited
|-
| txid || The ID (hash) of the transaction that was generated. If using -autotx this field will be omitted.
|}

==== Example Response JSON ====

{
"success": true,
"txid": "01f51d6b23b871fc8da848afa57cf066cb9e3b8fb845a666335e8c678ef5249e98d4f3e477659098918e4bb590472a63d0ed0a17fa87904fcff6316158e9edfd"
}

=== debit ===

Deduct an amount of NXS or token specified by the noun and send it to another account or legacy UTXO address. Only NXS can be sent to the legacy address.

finance/debit/noun

This command supports the account, any, and token nouns.

==== Parameters ====

{| class="wikitable"
! Name !! Description !! Required
|-
| amount || The amount of NXS or token to debit || true
|-
| expires || Number of seconds until the transaction can no longer be claimed by the recipient. If expires is set to 0, the transaction will never expire, making the sender unable to ever void the transaction. If omitted, a default expiration of 7 days (604800 seconds) is applied. || no
|-
| from || Name or register address of the account to debit. The name should be in the format name (for global token names), username:name (for local names) or namespace::name (for names in a namespace). || true
|-
| pin || PIN for this profile. || Required if locked.
|-
| reference || A 64-bit unsigned integer in the range of 0 to 18446744073709551615. || no
|-
| session || User session ID || Required if argument -multiuser=1 is set
|-
| to || Name or the register address of the account to credit || true
|}

==== Return Values ====

{| class="wikitable"
! Name !! Description
|-
| success || Boolean flag indicating whether the debit was successful
|-
| txid || The ID (hash) of the transaction that was generated. If using -autotx this field will be omitted.
|}

==== Example Response JSON ====

{
"success": true,
"txid": "01f51d6b23b871fc8da848afa57cf066cb9e3b8fb845a666335e8c678ef5249e98d4f3e477659098918e4bb590472a63d0ed0a17fa87904fcff6316158e9edfd"
}

=== get ===

Retrieves information for a single object for a type specified by the noun

finance/get/noun

This command supports the account, trust and token nouns.

==== Parameters ====

{| class="wikitable"
! Name !! Description !! Required
|-
| address || Register address of the account to debit the tokens from the be burnt || Required if name is not provided
|-
| name || In the format username:name (for local names) or namespace::name (for names in a namespace). If you are logged in, the username: field is not required. || Required if address is not provided
|-
| session || User session ID || Required if argument -multiuser=1 is set
|}

==== Return Values ====

{| class="wikitable"
! Name !! Description
|-
| address || Register address that has been retrieved
|-
| age || Age of the trust account in the format "(x) days, (x) hours, (x) minutes"
|-
| balance || The available balance of this account. This is the last confirmed balance added to any new debits made since the last block.
|-
| created || UNIX timestamp when the account was created
|-
| currentsupply || Amount of tokens that have been distributed to token accounts
|-
| decimals || Maximum number of decimal places that can be applied to token amounts
|-
| maxsupply || Maximum token supply amount
|-
| modified || UNIX timestamp when the account was last modified
|-
| owner || Genesis hash of the profile that owns this account
|-
| rate || Current annual percentage reward rate from staking
|-
| stake || Amount of NXS currently staked in a trust account
|-
| ticker || Name of the token object. For NXS accounts will show NXS.
|-
| token || Register address of the token. Set to 0 for NXS accounts.
|-
| trust || Trust score of the trust account
|-
| type || The type of register. Can be OBJECT, RAW or READONLY
|-
| version || The serialization version of the transaction
|}

==== Example Response JSON ====

{
"owner": "b1b5b4f4197548886016586f95735f0cb8235183a9185b8720bd27502a2e2850",
"version": 1,
"created": 1638020495,
"modified": 1655118914,
"type": "OBJECT",
"balance": 300.536104,
"stake": 15000.0,
"token": "0",
"ticker": "NXS",
"trust": 3399813,
"age": "39 days, 8 hours, 23 minutes",
"rate": 3.0,
"address": "8EunQ82qVdnuQkX2gXKZr5P55kQRz4KbpaLdCVBjBNu8jeys4C4"
}

=== history ===

This will get the history of the specified noun.

finance/history/noun

This command supports the account, trust and token nouns.

==== Parameters ====

{| class="wikitable"
! Name !! Description !! Required
|-
| address || register address of the asset || Required if name is not provided
|-
| name || In the format username:name (for local names) or namespace::name (for names in a namespace). If you are logged in, the username: field is not required. || Required if address is not provided
|-
| session || User session ID || Required if argument -multiuser=1 is set
|}

==== Return Values ====

{| class="wikitable"
! Name !! Description
|-
| action || The action that occurred - CREATE | MODIFY | TRANSFER | CLAIM.
|-
| address || Register address that has been retrieved
|-
| age || Age of the trust account in the format "(x) days, (x) hours, (x) minutes"
|-
| balance || The available balance of this account. This is the last confirmed balance added to any new debits made since the last block.
|-
| created || UNIX timestamp when the account was created
|-
| currentsupply || Amount of tokens that have been distributed to token accounts
|-
| decimals || Maximum number of decimal places that can be applied to token amounts
|-
| maxsupply || Maximum token supply amount
|-
| modified || UNIX timestamp when the account was last modified
|-
| name || Name identifying the account, trust or token
|-
| owner || Genesis hash of the profile that owns the object
|-
| rate || Current annual percentage reward rate from staking
|-
| stake || Amount of NXS currently staked in a trust account
|-
| ticker || Name of the token object. For NXS accounts will show NXS.
|-
| token || Register address of the token. Set to 0 for NXS accounts.
|-
| trust || Trust score of the trust account
|-
| type || The type of register. Can be OBJECT, RAW or READONLY
|-
| version || The serialization version of the transaction
|}

==== Example Response JSON ====

[
{
"owner": "b7fa11647c02a3a65a72970d8e703d8804eb127c7e7c41d565c3514a4d3fdf13",
"version": 1,
"created": 1654808903,
"modified": 1654809207,
"type": "OBJECT",
"balance": 1000.0,
"token": "8DXmAmkTtysSZUxM3ePA8wRmbSUofuHKSoCyDpN28aLuSrm1nDG",
"ticker": "XYZ",
"address": "8Bk5PxsecfXWpbHsDXeZ47MCgDF7qDLsU4Y4MJw2VB29LsTR98z",
"name": "local:XYZToken",
"action": "CREDIT"
},
{
"owner": "b7fa11647c02a3a65a72970d8e703d8804eb127c7e7c41d565c3514a4d3fdf13",
"version": 1,
"created": 1654808903,
"modified": 1654808903,
"type": "OBJECT",
"balance": 0.0,
"token": "8DXmAmkTtysSZUxM3ePA8wRmbSUofuHKSoCyDpN28aLuSrm1nDG",
"ticker": "XYZ",
"address": "8Bk5PxsecfXWpbHsDXeZ47MCgDF7qDLsU4Y4MJw2VB29LsTR98z",
"name": "local:XYZToken",
"action": "CREATE"
}
]

=== list ===

This will list off all of the object register details specified by the noun.

finance/list/noun

This command supports the account, trust and token nouns.

==== Parameters ====

{| class="wikitable"
! Name !! Description !! Required
|-
| session || User session ID || Required if argument -multiuser=1 is set
|-
| where || An array of clauses to filter the JSON results. More information can be found on [[Dev:Queries|Queries]] page. || no
|}

==== Return Values ====

{| class="wikitable"
! Name !! Description
|-
| address || Register address that has been retrieved
|-
| age || Age of the trust account in the format "(x) days, (x) hours, (x) minutes"
|-
| balance || The available balance of this account. This is the last confirmed balance added to any new debits made since the last block.
|-
| created || UNIX timestamp when the account was created
|-
| currentsupply || Amount of tokens that have been distributed to token accounts
|-
| decimals || Maximum number of decimal places that can be applied to token amounts
|-
| maxsupply || Maximum token supply amount
|-
| modified || UNIX timestamp when the account was last modified
|-
| name || Name identifying the account, trust or token
|-
| owner || Genesis hash of the profile that owns the object
|-
| rate || Current annual percentage reward rate from staking
|-
| stake || Amount of NXS currently staked in a trust account
|-
| ticker || Name of the token object. For NXS accounts will show NXS.
|-
| token || Register address of the token. Set to 0 for NXS accounts.
|-
| trust || Trust score of the trust account
|-
| type || The type of register. Can be OBJECT, RAW or READONLY
|-
| version || The serialization version of the transaction
|}

==== Example Response JSON ====

[
{
"owner": "b7fa11647c02a3a65a72970d8e703d8804eb127c7e7c41d565c3514a4d3fdf13",
"version": 1,
"created": 1654808816,
"modified": 1655061950,
"type": "OBJECT",
"balance": 5998.0,
"decimals": 2,
"currentsupply": 4002.0,
"maxsupply": 10000.0,
"token": "8DXmAmkTtysSZUxM3ePA8wRmbSUofuHKSoCyDpN28aLuSrm1nDG",
"ticker": "XYZ",
"address": "8DXmAmkTtysSZUxM3ePA8wRmbSUofuHKSoCyDpN28aLuSrm1nDG"
}
]

=== transactions ===

This will list off all of the transactions for the specified noun.

finance/transactions/noun

This command supports the account, trust and token nouns.

==== Parameters ====

{| class="wikitable"
! Name !! Description !! Required
|-
| session || User session ID || Required if argument -multiuser=1 is set
|-
| verbose || determines the transaction data included in the response. Supported values are default, summary, and detail. || no
|}

==== Return Values ====

{| class="wikitable"
! Name !! Description
|-
| blockhash || Hash of the block containing this transaction. Blank if not yet included in a block.
|-
| confirmations || Number of confirmations this transaction has obtained by the network
|-
| contracts || Described in the contracts table below
|-
| sequence || Sequence number of this transaction within the signature chain
|-
| timestamp || Unix timestamp when the transaction was created
|-
| txid || Transaction hash
|-
| type || Transaction type (legacy | tritium base | trust | genesis | user)
|-
| version || The serialization version of the transaction
|}

{| class="wikitable"
|+ contracts
|-
! Name !! Description
|-
| amount || Token amount of the transaction.
|-
| contract || Contract ID within the transaction for the credit/claim.
|-
| for || For CREDIT transactions, the contract that this credit was created for . Can be COINBASE, DEBIT or LEGACY.
|-
| from || For DEBIT, CREDIT, FEE transactions, the register address of the account that the debit is being made from.
|-
| from_name || For DEBIT, CREDIT, FEE transactions, the name of the account that the debit is being made from. Only included if the name can be resolved.
|-
| id || The sequential ID of this contract within the transaction.
|-
| object || Returns a list of all hashed public keys in the crypto object register for the specified profile. The object result will contain the nine default keys(app1, app2, app3, auth, cert lisp, network, sign and verify).
|-
| OP || Contract operation. Can be APPEND, CLAIM, COINBASE, CREATE, CREDIT, DEBIT, FEE, GENESIS, LEGACY, TRANSFER, TRUST, STAKE, UNSTAKE, or WRITE.
|-
| proof || Register address proving the credit
|-
| reference || For DEBIT and CREDIT transactions this is the user supplied reference used by the recipient to relate the transaction to an order or invoice number.
|-
| ticket || Name of the token related to the transaction
|-
| to || For DEBIT and CREDIT transactions, the register address of the recipient account
|-
| to_name || For DEBIT and CREDIT transactions, the name of the recipient account. Only included if the name can be resolved.
|-
| token || Register address of the token related to the transaction. Set to 0 for NXS transactions.
|-
| txid || The transaction ID hash of the transaction for the credit/claim.
|}

==== Example Response JSON ====

[
{
"txid": "0123517ca0f1ca110c7b07de9e3c9b33ccbe717f96911e1449b7c73bb9695fbc9c14a58f01f5fb7e9b64756f658af91daec9f0f579df2fad8df61843defae833",
"type": "tritium user",
"version": 4,
"sequence": 23,
"timestamp": 1655061950,
"blockhash": "8b206ab2ee4b46a835f74af0ff5d4e0b395acdb94d66468a24083f2a5fd01a07a93956774001bab1a801d53d7bf6ed60ee84a573650eef1a9feaf6fa9beb308bd20b567663cc7ec4f85796b261164ef3452ebfaa13a60141b42fc49d6d2eb2792440925b1b19248ad9fe65e01d3742f2d3dec2817c56c8e4f6e03a10f4147308",
"confirmations": 4,
"contracts": [
{
"id": 0,
"OP": "DEBIT",
"from": "8DXmAmkTtysSZUxM3ePA8wRmbSUofuHKSoCyDpN28aLuSrm1nDG",
"to": "8Bk5PxsecfXWpbHsDXeZ47MCgDF7qDLsU4Y4MJw2VB29LsTR98z",
"amount": 1.0,
"token": "8DXmAmkTtysSZUxM3ePA8wRmbSUofuHKSoCyDpN28aLuSrm1nDG",
"ticker": "XYZ",
"reference": 57891358795
}
]
},
{
"txid": "01f1a3f9227a69382f9811a5b1497a865ace17ad83b03118b24f875f6ade83117887c35d08375c259aa1076b91f42206110314756a11a943760bb5c0dd0523d7",
"type": "tritium user",
"version": 4,
"sequence": 21,
"timestamp": 1655060214,
"blockhash": "048f3b308e8bd8c1aa31ec1ec2e136a9ccc91ec4498283d07fc5d0a00c8576e2c199567a44058222961f474626c6f2c5d7e774eee34c34f98acafaeb50b7abaaade7e9c641fe9727fe62533b1ec6bf2f75ffbf19d17d74671e2458bd73b6407b4bba1951fc84e1af11c2c4fbce1d05d7739e910fdb8a37197c1c422521e2e9f3",
"confirmations": 6,
"contracts": [
{
"id": 0,
"OP": "DEBIT",
"from": "8DXmAmkTtysSZUxM3ePA8wRmbSUofuHKSoCyDpN28aLuSrm1nDG",
"to": "8Bk5PxsecfXWpbHsDXeZ47MCgDF7qDLsU4Y4MJw2VB29LsTR98z",
"amount": 1.0,
"token": "8DXmAmkTtysSZUxM3ePA8wRmbSUofuHKSoCyDpN28aLuSrm1nDG",
"ticker": "XYZ",
"reference": 0
}
]
}
]