TomMarchi

Working on VIAT, UW ::
Post-Quantum Crypto, Web, Blockchain, AI ::
Viat work live stream:

[TomMarchi @tommarchi]

Where Viat fits in the PQ landscape -
Ideal for the vast majority of users and organizations who want a hands free transition platform without upfront cost. If you do not want a complex transition of interruption for smart contracts or defi then Viat is your best platform for that.

Build on Viat safeguard your infrastructure going forward and automate the transition for all users.

Viat is designed to follow NIST’s overall strategy but adapted to the realities of blockchain where upfront cost should be deferred until it’s needed.

Be transition ready - all wallets can be protected at the same time across the network or as users see fit. You get both.

You keep your address, the network doesn’t pay upfront storage costs for the PQ public keys only the initially commitment, smart contracts continue to function, DeFi continues to operate, no complex transition, automate it entirely in the background for users, orgs keep deciding, apps keep moving.

Can BTC, ETH, Solana and beyond do this NO. Pre-existing networks have immutable legacy identities to start with which means users must switch manually or risk losing assets to a quantum computer or a Fork. Many will be left behind and they can choose Viat instead as eventually other algos will fail and Viat is designed so that all wallets have a transition path forward.

[TomMarchi @tommarchi]

@novegreg @chadvivi SOL is ed25519 which is natively supported for us thus easiest to test and confirm before others and a different process is possible.

[TomMarchi @tommarchi]

Our Universal Web Component framework built on native Web Components that runs the new wallet site is now beating out https://t.co/12srmOIUuQ performance and has a larger feature offering along with AI integration. Next is to build out a compiler to match performance levels of Vue3 components while retaining our features. Tons of changes will be uploaded to the beta GitHub repository and will update the master repo.

Once we have the compiler in then we have the capability to build out a UI thats 60FPS and is perfect for a DEX, CEX, and live blockchain analytics for the Viat wallet site. Putting it all on the wallet subdomain but considering maybe it moves to https://t.co/rZ2zLdqVMq while wallet subdomain turns into a slimmed down wallet only version.

Browser addon wallet will be using this same component system for the UI. It’s lightweight GPU accelerated and snappy.

[TomMarchi @tommarchi]

@chadvivi Working on that with the swap feature on the dashboard first will be the dev then bViat and sntvt swap.

[TomMarchi @tommarchi]

Large amount of repo updates heading out tonight. Major performance improvements moving in a ton since we have an operational test net for Viat so now it’s fixing the bugs and enabling more features. Utility libraries are all being updated as well lots of fixes and more performant code moving in. Huge focus on performance now some basic changes resulting in major wins heading to the wallet site much of which already have some of it. Site will be chaotic over next 4hrs as updates move out.

[TomMarchi @tommarchi]

Exactly as I stated finally realizing it.

[Mikli @CryptoMikli]

Nic Carter says Solana will need to be completely rebuilt to survive quantum computing

“It’s gonna be tricky for Solana because they’re highly optimized around some variant of elliptic curves. They’re optimized at the hardware level. The whole concept of Solana is that there’s a ton of throughput”

“It’s not that they can’t survive the transition, and to their credit, I see Solana leadership talking about it. They’ve been very proactive about it. They acknowledge the transition will happen. It’s just gonna be a really annoying rebuild for them”

“When it’s all said and done, maybe they’re using lattice-based cryptography. If I had to guess, that’s what they will do, but it’s gonna be slower. Their throughput might go down, and that’s kind of like the whole point of Solana, is throughput”

[TomMarchi @tommarchi]

Very much agreed.
https://t.co/6wPbTFky1e

[TomMarchi @tommarchi]

Analytics dashboard UI will be moving in tonight for the Viat command & control terminal.

[TomMarchi @tommarchi]

Pushing lots of performance and capability updates to the wallet app. Test net will be reset in short order wallet credentials are the same will be testing the new network wide features.

[TomMarchi @tommarchi]

Mobile support has been added for wallet site, sending is restored, and new AI features are moving in for automation. Lots more coming in tonight. https://t.co/yqLKMXQT5e

[TomMarchi @tommarchi]

https://t.co/pC30CxSscq Minting and some initial requests are re-enabled. New legacy address generation is in which is far more preformant but required we ensure 24 byte addresses now are restricted for legacy address generation only. More URL routes are making their way in but to view new features make sure to remove cache or refresh for new content or ignore cache with inspect tools while new changes are moving in. Moved from /new/ to the root https://t.co/8zW6i9ZlvK

[TomMarchi @tommarchi]

Hooking up back-end to front-end to re-enable transactions for the Viat site wallet app. Site will be up and down over next few hours as it makes its way in.

[TomMarchi @tommarchi]

Hooking up back-end to front-end to re-enable transactions for the Viat site wallet app. Site will be up and down over next few hours as it makes its way in.

[TomMarchi @tommarchi]

The new wallet site (https://t.co/c8zD9aKgGf) uses the HD Seed Tree - the older version was just private key

[TomMarchi @tommarchi]

Current wallet https://t.co/BLmHBKjY42 save is around 1299 bytes that includes 4x128 byte seeds and meta data. Can likely get it smaller but mostly wallet meta data and encryption details. Example struct output. Some of the meta data is important to structure generation but can be brute forced easily if lost seeds are of course vital your PQ private key.

{
kind: 'wallet.viat',
meta: {
app: 'viat',
kind: 'wallet.viat',
extra: {
handle: 'xvOf5CRieDUw1aTFFNwIGYFXrCOAkJpe',
displayName: 'xvOf5CRieDUw1aTFFNwIGYFXrCOAkJpe'
},
label: 'wallet',
cipher: {
algorithm: 'XChaCha20-Poly1305',
nonceLength: 24,
innerEncoding: 'cbor'
},
address: 'xvOf5CRieDUw1aTFFNwIGYFXrCOAkJpe',
version: 1,
password: {
hashMode: 'argon2id',
hashLength: 32,
iterations: 256,
memorySize: 512,
saltLength: 32,
parallelism: 1
},
createdAt: '2026-05-15T18:20:35.738Z',
publicKey: 'jds3KJeu3v/+QYewXeNCpBH8lG2mPb9v9tl68YbAwB4=',
walletType: 'site',
trapdoorHash: 'lNVlYxH3Z6Wy3f+Akv2qMPjUSiCgb80R/pIQU5Yq6jI='
},
version: 1,
encoding: 'cbor',
encrypted: {
data: <Buffer df fc 25 5b 41 99 95 50 11 a0 e1 db c9 c8 b0 2a 1a 7e ca 41 57 1e 53 68 99 cc 59 57 98 33 74 4e 9f af 87 7c 83 ae 49 96 5e 51 59 de 7a a8 38 52 ee 6c ... 577 more bytes>,
salt: <Buffer a9 a7 99 07 f3 59 30 a7 f2 b1 94 1a e5 60 15 fe 61 90 06 83 3b fb 88 56 25 25 2c 7c 0b 12 0b df>,
nonce: <Buffer be ba 9f 4d d3 04 46 31 d0 84 06 de ad ff bf f7 ce 0f 43 4b 9b 5e 69 4c>,
innerEncoding: 'cbor'
}
} 1299

[TomMarchi @tommarchi]

Current wallet https://t.co/BLmHBKjY42 save is around 1299 bytes that includes 4x128 byte seeds and meta data. Can likely get it smaller but mostly wallet meta data and encryption details. Example struct output. Some of the meta data is important to structure generation but can be brute forced easily if lost seeds are of course vital your PQ private key.

{
kind: 'wallet.viat',
meta: {
app: 'viat',
kind: 'wallet.viat',
extra: {
handle: 'xvOf5CRieDUw1aTFFNwIGYFXrCOAkJpe',
displayName: 'xvOf5CRieDUw1aTFFNwIGYFXrCOAkJpe'
},
label: 'wallet',
cipher: {
algorithm: 'XChaCha20-Poly1305',
nonceLength: 24,
innerEncoding: 'cbor'
},
address: 'xvOf5CRieDUw1aTFFNwIGYFXrCOAkJpe',
version: 1,
password: {
hashMode: 'argon2id',
hashLength: 32,
iterations: 256,
memorySize: 512,
saltLength: 32,
parallelism: 1
},
createdAt: '2026-05-15T18:20:35.738Z',
publicKey: 'jds3KJeu3v/+QYewXeNCpBH8lG2mPb9v9tl68YbAwB4=',
walletType: 'site',
trapdoorHash: 'lNVlYxH3Z6Wy3f+Akv2qMPjUSiCgb80R/pIQU5Yq6jI='
},
version: 1,
encoding: 'cbor',
encrypted: {
data: <Buffer df fc 25 5b 41 99 95 50 11 a0 e1 db c9 c8 b0 2a 1a 7e ca 41 57 1e 53 68 99 cc 59 57 98 33 74 4e 9f af 87 7c 83 ae 49 96 5e 51 59 de 7a a8 38 52 ee 6c ... 577 more bytes>,
salt: <Buffer a9 a7 99 07 f3 59 30 a7 f2 b1 94 1a e5 60 15 fe 61 90 06 83 3b fb 88 56 25 25 2c 7c 0b 12 0b df>,
nonce: <Buffer be ba 9f 4d d3 04 46 31 d0 84 06 de ad ff bf f7 ce 0f 43 4b 9b 5e 69 4c>,
innerEncoding: 'cbor'
}
} 1299

[TomMarchi @tommarchi]

https://t.co/qFcr1KiuvJ this will be moved over to the main directory and replace the existing wallet site once it is hooked up to the new backend API. The original wallet site has features disabled like sending but faucet likely will still work.

[TomMarchi @tommarchi]

https://t.co/LNZlmOHMmu QRcode support for click to copy/download as image. Will add QRCode that are link based as an option for sharing and having it auto come up for mobile app support. Signature creation for arbitrary data functional. New dock animations. New UI components. New settings modal and more. Lots of patches and new Viat client SDK is in for wallet trees with some security updates to keep things encrypted in memory with argon2id hashed passwords. Updated basic swap UI prototype. Mobile support is ideally in late tonight but will have a cleaned up and minimized UI for mobile usage but still GPU accelerated.

[TomMarchi @tommarchi]

Lots of new features are in https://t.co/BLmHBKjY42 with new wallet seeds as private key, wallet encryption, profile saving/importing and new UI components. Initial swap UI prototype is in. For laptop/desktop might work on some tablet screens. Mobile support expected late tonight.

[TomMarchi @tommarchi]

Lots of new features are in https://t.co/BLmHBKjY42 with new wallet seeds as private key, wallet encryption, profile saving/importing and new UI components. Initial swap UI prototype is in. For laptop/desktop might work on some tablet screens. Mobile support expected late tonight.

[TomMarchi @tommarchi]

This is why I have been slowly re-writing as many 3rd party dependencies that could cause an issue with the network or wallet app. The entire Web Component system is built from scratch its not React or Vue or Svelte it's entirely home grown and we do not do and will never do Server Side Rendering for what should be client side components. Unit Testing, Documentation Generation, Reactive Web Components, Utility Library everything that I can write quickly is home grown and more will follow.

[International Cyber Digest @IntCyberDigest]

POV: you are downloading npm packages in 2026

[TomMarchi @tommarchi]

https://t.co/jh3NGc471t