@Royero5@prinzpixl Will be converted to Viat. The upcoming testnet will also have a swap so we can do a trial run and resolve any swap/network issues before it actually counts.
Next commit now includes significant overhaul of crypto middleware. Should be out by tomorrow the latest. We have swapped to a new core crypto utility library and we control more of the steps involved. Our prior main library was libsodium while we continue using it, most functions will be from a different library. This gives us greater control and flexibility. Many other changes in this as well paving the way for new $VIAT wallets. All current #VIAT wallet code will be upgraded and features expanded like our new 64byte wallet addresses. 64bytes for a wallet address is rather a rare occurrence in crypto land.
Many think that $TRUMP is just a meme token
I have discovered a massive conspiracy behind it
Very few know it, I might be in trouble for telling you
$TRUMP is much more than you think, it's the beginning 🧵
Do not trust or use anything related to older domains we are transitioning to UW/VIAT domains entirely. We do have a separate domain for VIAT but chances are we will just keep it on the UW one. New site is being put together.
This @UWViat username is likely going to be the new primary account for UW & #VIAT going forward we may see if we can merge the old sntvt account with it. New Discord group is also being setup the old one should not be used.
I have a response back from NIST for if BLAKE3 could be used at all and still potentially be compliant. Strictly speaking we will need to use SHAKE256 instead of BLAKE3 for variants that want to be NIST compliant. We already support both BLAKE3 and SHAKE256 so it would be easy to just swap out for either or but will likely offer additional SHAKE256 variants for all classical encryption. When it comes to any post quantum encryption we will be sticking to SHAKE256 entirely anyway. Will have that change out by end of day.
Offering different variants for services (not wallets) would be ideal for those running none critical apps/services and or simply don’t see a need for anything beyond BLAKE3 hash wise.
Because VIAT has a strict crypto setup that means it will be using SHAKE256 only just to save us the work of trying to manage two different versions of VIAT and or not being NIST algo compliant because of a single hash algo. Over time VIAT wallet/transaction sizes will decrease as classical algorithms are compromised/unneeded & thus removed by then. Strict projections are for 2030-2035 anyway so we got time.
However, I do think there is logic and reason to be had for merely using BLAKE3 for none security related aspects. For now VIAT will continue to move to SHAKE256 which by 2030 it will need to be anyway. This could change but if being prepared for the impending future is the idea then this is the correct course of action.
I like BLAKE3 due to its speed and output flexibility but fully grasp that its long-term potential has a cap compared to SHAKE256 being able to scale its strength/output.
Experience $VIAT: Save data encrypted with your password - protected by the OS account system. UWBrowser offers a unique & anonymous account on the Web, acting as your Bitcoin wallet and universal username/password. Take control of your online identity with top notch security.