News:Project Update 2025-04-05

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.