DevvE Announcements

Here's a second video, that shows professional applications being built on Fias - again, it shows the type of thing that will be able to be tied in to the blockchain... I had an amazing experience on Fias last week, building powerful applications for a customer who gave us a challenge. We took their challenge, that they thought was aggressive, and not only did what they thought might be impossible, but did 4x the work they were expecting! This is a one-two punch alongside the other video I just posted. Have a look: I Replaced Salesforce, Docusign, and Quickbooks in 5 Days with AI https://youtu.be/7Wlw2XLSuUM

First look at Fias. On the Devv side of things, one thing I’ll point out is that Fias will let people easily build blockchain applications on top of DevvX. Fias is also being used to create the new version of DevvX and the business around it. It's very powerful and a big day for Devv as well. Fias Beta Launch First Look

I just did the first cross shard transfer a few minutes ago. This is an enormous milestone and big day for the new DevvX architecture.

Hey everyone, here is a first iteration of the new roadmap strategy. We'll hone the approach over time, but the general idea is to have a list of items we're working on available for people to see so that everyone can see what is coming, and see progress. I think a little more granular view of what we are doing is a better approach than what Forevver did in the past. The update includes information on both Fias and Devv, but we'll be able to describe more as we close on funding. This week was busy, and we had a hard push. We are going to do QA on everything next week. I'm not positive if we'll be able to open the public beta at the end of the month, but soon after if not. We're close. Please let me know your thoughts on the new approach for the roadmap. thx https://platform.fias.io/a/arche_todo_lists/public/fias_roadmap

Just had another nice DevvX milestone - I got a three validator shard benchmark on staging (actual AWS servers) - It was approaching 2k tps per shard (and you simply add as many shards as you need to reach the overall throughput you're looking to get). The previous note I made a few days ago was on a local computer. This test was transactions coming from the local computer (as is the case in real world use), but hitting the API on the AWS servers, and being processed on those servers. That speed is without any real optimization yet, so overall we are in good shape - the shards are running in a comparable way to what we had built over time with the original DevvX. On a run with an even bigger number of transactions, I couldn't get enough transactions through the network to really test the speed - it processed them all as quickly as they came in. Is nice progress 👍

Hey Everyone, nice DevvX milestone this morning. I just ran a benchmarking test of 100,000 transactions, and it processed it at about 1000 transactions per second on the test shard. That's the right order of magnitude that I need. Then, if you need 1 million tps, you would spin up 1000 shards. I'll caveat that it was a local system running localstack for the simulation (though I expect I can do better on better AWS hardware) and was single validator, but there will be plenty of room to make improvements and optimizations from here as well. This is showing that the approach has the right overall types of concepts to work as I need. It's still early, but also still progressing quickly.

I just had my first 3 validator transaction on staging go through on the new DevvX. This means that we have a shard with permanence running on staging with decentralized validators giving consensus through the newly designed proof of validation consensus mechanism. When I go into the block on the new block explorer, I see all three proof of validation signatures on the block. so awesome.

Hey Everyone, we're ramping up for the Fias closed Beta. I'm going to keep this to our Telegram community to start, and expand our awareness efforts soon. We will let people into the closed beta in waves. Put anything you want us to consider in your application - what you would like to build (this is the main thing),the amount of time and the ways you've been supporting the project, anything else you think we should consider. I want to keep our team from getting overwhelmed with requests, so we are going to start small and grow from there. I can't wait to see what people would like to build with Fias. Please apply here: https://platform.fias.io/a/arche_beta_access/ I'm going to put out a new set of documents overviewing Fias in the next day or two. I also plan to get a roadmap arche out shortly - I hope to get it out before next week. This is the beginning of using Fias itself to help grow everything. It's pretty awesome to have a need (like accepting Beta applications) and simply and quickly create an arche to implement a solution to that need. It's also pretty cool how arches can be implemented. These first few arches have a public flag, so you don't need to be logged in to see them. I think as more and more people create arches, the platform could dramatically grow. Powerful stuff.

Big progress today on two fronts!! First I created the first DevvX transaction on staging (a minting of 100,000,000 TestCoin). This represents the first DevvX transaction in the new AI created version of DevvX, on a persistent blockchain. I had the local version working before, but for an online server, I had to get key management in, all of the AWS stacks in place, auth working, wallet generation, and the blockchain itself running on online servers. The transaction was signed with an ECDSA signature, sent to the INN, and then was allowed to the core blockchain which validated the transaction and added it to a block. I could then see the genesis block and the minting block on the block explorer, and I could see the transaction details in the block explorer. So satisfying to see the transaction appear in the block explorer! Second, and equally importantly, I got the first complex Arche (web app) built in the Fias Arch Builder itself. This is weeks in the making, and the Arche Builder is by far the most complex Arche we've built. With the Arche builder, I created a Provisional Patent Writer that takes users through a 12 step process that I honed when I was actually first working on the Fias patents. The Arche Builder was able to take me through each step and build the flow across each UI for each page, maintaining the final data goal (the resulting patent draft itself). I tried building the same thing on Base 44 with the same input, and it was too complex and not able to do it! This feels good. It was a pretty crazy dev session the last few days. On my left computer I was logged in to a WSL session on my laptop and was working through getting Fias Prod to deploy. I had a number of clean up items on the AWS stacks for both staging and prod, and it was a couple day process getting everything in order. On my middle computer, I have a large wrap around screen - comparable to two monitors. I was using WSL working on the DevvX staging deployment described above (left half of the screen). On that same computer I was using a different WSL instance and implementing the Arche Builder in which the AI interacts with completely separate AWS and Github accounts (right half of the screen). Then, when the Arche Builder was building the Patent Writer, I started that process by testing using it to create a patent draft. The Arche Builder is in essence our own version of Claude Code. So I then had a fourth session going, using the Arche Builder that was essentially within the other session building the Arche Builder. It reminded me of Inception haha - dreams within dreams. On two of the sessions I was figuring out the deployment of the systems where everything ultimately resides. In the next session I was building the Arche Builder itself. Then I was working within the Arche Builder writing a patent. I kind of felt like a Star Wars droid with 6 arms working on many different things. Throw in some Telegram responses, work on email, and investor responses at various bits of time availability (which were not often given I had four full programming sessions going at once). My brain is tired and I'm taking the rest of the night off having hit these two big milestones. And to be sure, they are big milestones. They are both at the heart of the respective platforms - DevvX and Fias.

Hey everyone, I’m gearing up for a more regular flow of information and videos. We are creating a social media arche that makes it easier to post. Also, I am figuring out the mechanical process to do AI led interviews. I am writing here as I would like to hear from folks what topics they want to hear about. A lot of my videos will focus on entrepreneurship and what it takes to start a business. I’ll also give technical and progress updates on Fias and Devv as well. Please respond to this post with your ideas of what you’d like to see.

Ok Everyone, this post may be the most significant post I've done at Devv. This morning is a key moment driving us into the future. After two weeks of design, I am actually starting the programming of the new DevvX platform right now. The first file with code will be created when I tell the AI to start in just a moment. It has already reviewed the entire design document, and has put together a phased plan for implementation. I just this moment read through the phased plan and it's so exciting. It includes a number of features we've struggled to implement in the system from the beginning - this entire system architecture is designed to work as a whole around many of my original designs from nearly 10 years ago. Now, that type of design can be implemented quickly and robustly. I went to lunch yesterday with Bill, and he gave me his feedback on the architecture and approach. It was great feedback, and so I did one final iteration on the design yesterday preparing for this moment now. Yesterday, I got all of the new AWS accounts set up, got the new Github accounts set up, and everything is ready to start. I have a new Linux distribution installed on WSL, linked with CLI interfaces into AWS and GitHub. AWS has a master account in addition to staging and prod accounts initiated. Basically, it is a clean whiteboard, ready to go. The AI just wrote a few minutes ago: I've already read the full design document thoroughly. Since this is a greenfield project (the repo only has a README and the design doc), I don't need extensive codebase exploration. Let me go straight to designing the implementation plan. This morning I woke up and immediately went to my computer to get started in a dark, quiet house. It is kind of a surreal moment. I've spent the last hour getting ready to officially start the implementation. It was pitch black outside, and just now the first tinges of light blue are hitting the sky with dawn about to arrive. I think I would be nervous in letting people know about this moment in time, if I hadn't already had so much success with Fias. I would have been worried that the whole thing might not work, so I'm putting myself out there in giving this play by play at all. That said, I indeed have had the successes in this type of approach already, and I now know what's possible. With Fias, I've already built in months what would have taken a large team years. I have seen what AI is capable of since November of last year, and I have been experiencing how fundamentally changed software is. This is what must be done if you are in software today. The world is going to change quickly from here, and we are going to stay at the leading edge.

┌───────────────────────────────────────┬────────────┬───────────────────────────┐ │ Issue │ User Count │ Resolution │ ├───────────────────────────────────────┼────────────┼───────────────────────────┤ │ Spaces in username │ 6,684 │ Replaced with underscores │ ├───────────────────────────────────────┼────────────┼───────────────────────────┤ │ Leading/trailing spaces │ 4,553 │ Trimmed │ ├───────────────────────────────────────┼────────────┼───────────────────────────┤ │ Accented Latin chars │ ~170 │ Transliterated to ASCII │ ├───────────────────────────────────────┼────────────┼───────────────────────────┤ │ Apostrophes │ 12 │ Stripped │ ├───────────────────────────────────────┼────────────┼───────────────────────────┤ │ Non-Latin scripts (Cyrillic, Chinese) │ ~19 │ Clear error message │ ├───────────────────────────────────────┼────────────┼───────────────────────────┤ │ Name collisions after sanitization │ 806 │ Numeric suffix appended │ └───────────────────────────────────────┴────────────┴───────────────────────────┘

Hey Everyone, Bill updated the auth system to fix more errors with the new wallet. The issue came from the migration to Cognito that the old team had started. It affected about 10% of users. Here is a summary: Problem ~6,900 users in production have usernames that are incompatible with AWS Cognito (spaces, apostrophes, accented characters, etc.). When these users try to log in or reset their password, the lazy migration to Cognito fails with error code 5010 ("Failed to create OAuth user"), leaving them unable to authenticate. Changes Made Devv-INN (PR #768 — fix/sanitize-usernames-for-cognito, tagged v1.1.22-testnet-alpha): - inn/auth/auth_controller.py: - _sanitize_username() — cleans usernames for Cognito compatibility: - Trims leading/trailing whitespace - Transliterates accented Latin chars (é→e, ç→c, ğ→g) - Replaces spaces with underscores - Strips apostrophes (straight and curly) - Removes all remaining non-allowed characters (Cognito allows: a-z A-Z 0-9 _ - . + =) - Collapses consecutive underscores/dots, strips leading dots - Errors gracefully for fully non-Latin usernames (Cyrillic, Chinese) with "Please contact support" - _cognito_user_exists() — checks if a username is already taken in Cognito - _create_oauth_user_without_notification() — now sanitizes the username before creating in Cognito, handles collisions by appending _1, _2, etc., returns the new username if it changed - Login migration (cognito_login) — if username was sanitized: updates vault DB (devvuser.devvusername), updates shard DB (wallet.wallet_name), recomputes the Cognito secret_hash, sets warning on login output - Password reset migration (reset_password) — same rename logic, sets message on output - Password update migration (oauth_update_password) — added lazy migration with rename support (safety net, shouldn't normally trigger) - inn/persistence/vault.py — added rename_user(devvuser_id, new_username) to update devvuser.devvusername - inn/persistence/cache.py — added rename_wallet(old_username, new_username) to update wallet.wallet_name - inn/schema/auth_output_schemas.py — added message field to PassChangeOutputSchema so rename notifications are serialized Wallet Portal (PR #86 — fix/show-login-username-warning): - src/types/auth/auth.response.ts — added warning?: string to LoginResponse - src/hooks/auth/Login.tsx — on login success, if data.warning is present, stores it on window.__loginWarning (survives client-side navigation without triggering re-renders on the login page) - src/app/(wallet)/wallet/page.tsx — reads window.__loginWarning on mount, displays a modal dialog titled "Username Updated" with the warning message, requires user to click OK to dismiss Impact

Hey everyone, had an exciting design day with the new DevvX refactor. In particular I just finished the design of API payments for transactions. This is something we had been working into the previous version of DevvX but now it will be baked in from the beginning. Exciting how it is coming together. I also tackled several other long term issues we never were able to get the cycles to fix, but are baked in from the beginning now (one example is a global registry preventing conflicts around shards, which becomes critical as you move from first party to third party applications). I think this iteration of DevvX is going to be so powerful.

Hey Everyone, we’re going to be shutting down the testnet for the time being. Similar to GlassBlock, we are transitioning to a new refactored version of DevvX. We’ll bring it back better than ever once the refactoring is done.

Hey everyone, Bill told me the password reset on the new site is working again, for those of you who had troubles logging in.

Hey everyone, as an update on the DevvX platform, we have taken down GlassBlock while we refactor everything using AI. You can now go into DevvX.io to see a simplified wallet application. This is the first step in our overall progression on the future of DevvX. We wanted to get the current system into a stable place, and now we are pushing forward in an exciting new overall direction. I expect that in a short amount of time (a few months) we will be in a place where everything is running in a more optimal way, applications in DevvX will be easier to build, and new features will be dramatically faster to implement. I’m excited about what 2026 is going to bring for DevvX. I’m going to be giving an update on the new long-term vision I see for DevvX in the next couple weeks.

Hey everyone, here is a video summary of Fias and Devv. https://youtu.be/rQJW1WuVwHQ What is Fias — and why does it matter? Fias is a monetization platform for AI. Whether you're a developer with specialized models, a designer, or simply someone with deep expertise in a niche, Fias gives you the tools to package what you know and earn from it — no technical skills required. For everyday users, Fias lets you build custom AI applications in minutes, maintain your data privately and securely, and use any AI model best suited to your needs. In this overview, Tom Anderson (tomlucient) — an entrepreneur with 30+ years in AI, robotics, and blockchain — walks through what Fias is, what makes it different from the big AI players, and why the shift from technical infrastructure to financial infrastructure is the real opportunity in AI today. Backed by DevvX, one of the world's most powerful blockchain platforms, Fias is built to handle the speed, cost, safety, and scale that AI agents demand. Massive change is massive opportunity. Fias is built for it.

Hey everyone, I am beginning my channel and podcast releases. Here is the first, kicking things off. It will be more of a flow of content. https://www.youtube.com/watch?v=UP2jWYcxJOU This is the beginning. I'm Tom Anderson — 30 years in AI, robotics, and blockchain. I've brought in over $65M growing businesses, taken companies public, launched the world's first 3D touch robot, and spent the last decade building one of the most advanced blockchain infrastructures in the world. Now I'm building Fias — the world's monetization platform for AI — and I'm taking you along for the ride. This channel is where I share the real journey of growing an AI startup, my perspective on where AI and blockchain are headed, and lessons from three decades of entrepreneurship. Whether you're a builder, an investor, or someone trying to figure out where you fit in the AI age — this is for you. What to expect: 🟢 From Green to Green — The real story of building Fias. Entrepreneurship lessons, startup highs and lows, and how to create value in the AI age. 🧠 The Evolution of Intelligence — Deep dives into evolutionary algorithms, AI and blockchain convergence, and where this technology is really headed. 🔮 The Deeper Questions — Occasional explorations of consciousness, reality, and the philosophical dimensions of building thinking machines. New episodes dropping soon. Subscribe so you don't miss what's coming. Follow tomlucient: 🔗 LinkedIn: / tomlucient 🔗 X/Twitter: https://x.com/tomlucient 🔗 Medium: / tomlucient 🔗 Fias: https://www.fias.io/

AI financial infrastructure is projected to be the fastest-growing category in financial services. The industry is moving from AI experiments to enterprise-wide deployment. AI agents will need blockchain rails to transact. And we have the only blockchain with the speed, cost-efficiency, security protections, and CTS capabilities that autonomous AI commerce requires. The convergence of AI and blockchain is not coming - it's here. Devv and Fias are positioned at the center of it. I think for the first time, we can be perceived as leading the pack rather than creating technology that improves where others have already been. Thank you for your continued support and patience. The best is ahead of us. — Tom ━━━━━━━━━━━━━━━━━━━━ ⚠️ 𝗜𝗠𝗣𝗢𝗥𝗧𝗔𝗡𝗧 𝗗𝗜𝗦𝗖𝗟𝗢𝗦𝗨𝗥𝗘𝗦 FIAS and DevvE are utility tokens designed to facilitate transactions and access services within their respective ecosystems. Neither token is intended to be, nor should be construed as, a security, investment contract, or any form of financial instrument. This update is for informational purposes only and does not constitute investment, legal, tax, or financial advice, nor a solicitation to purchase any tokens. Please consult your own advisors before making any decisions regarding digital assets. This update contains forward-looking statements regarding the Fias platform, DevvX blockchain, partnerships, market trends, and the broader AI and blockchain industries. These statements reflect current expectations and beliefs and involve known and unknown risks and uncertainties that may cause actual results to differ materially. Factors that could cause such differences include changes in regulatory environments, technological developments, market adoption rates, competition, cybersecurity threats, changes in economic conditions, and the ability to attract users, developers, and ecosystem participants. Third-party quotes, market data, and industry projections cited herein are from sources believed to be reliable but have not been independently verified and may not reflect current conditions. No representation or warranty is made as to the accuracy or completeness of information contained herein. Readers should not place undue reliance on forward-looking statements. Devvio, Inc. and Fias Inc. undertake no obligation to update or revise any forward-looking statements except as required by applicable law.