The applications are enormous — from AI-driven supply chain automation (where IoT devices verify delivery before payment releases), to financial portfolio rebalancing, to insurance automation, to energy grid trading. Anywhere verification must precede value exchange (which essentially is everywhere and everything), CTS transforms the process. CTS transactions can be implemented not only on financial value, but also on data that drives processes.
Combined with DevvX's comprehensive protection suite — loss protection, theft protection, fraud protection, and privacy that satisfies regulatory requirements — we have an infrastructure stack that no other blockchain can match. These aren't incremental features. They are the requirements for enterprise-scale AI agent deployment, and we've been building them for years.
━━━━━━━━━━━━━━━━━━━━
🔹 𝗧𝗛𝗘 𝗔𝗜 𝗔𝗚𝗘𝗡𝗧-𝗗𝗥𝗜𝗩𝗘𝗡 𝗙𝗨𝗧𝗨𝗥𝗘 𝗢𝗙 𝗙𝗜𝗡𝗔𝗡𝗖𝗘
Here is a key part of our thesis: financial products themselves are moving into an AI agent-driven future. This isn't just about building infrastructure for others — it's about where the volume is going.
In the near future, trading volumes on digital asset exchanges will be dominated by AI agents. The same is true for borrowing, lending, and liquidity provisioning. AI agents will continuously analyze markets, optimize positions, route liquidity, and execute complex strategies — all autonomously and at machine speed. The shift from human-driven to agent-driven financial activity will be enormous, and the platforms that can handle it will capture immense value.
This represents one of the biggest opportunities in front of us: taking the financial products we've already built and positioning them for this new AI-dominated future — a future where there is massive growth ahead and where there aren't already established players with entrenched advantages. We are early to this market, and we have real products.
All existing DevvE use cases remain fully intact — exchange, lending, borrowing, and liquidity routing. Nothing is being taken away. What's changing is where these products are going. We are taking our financial products into this new AI-dominated future with real competitive advantages.
And here's the critical point: for AI agents to actually use financial products at scale, the underlying infrastructure has to meet specific requirements. You need high speed, because agents transact at machine pace. You need high throughput, because millions of agent transactions will happen simultaneously. You need cost effectiveness, because agent-to-agent micropayments have to be economically viable. And you need CTS, because when machines are transacting with machines autonomously, you must have trustless, atomic settlement with zero counterparty risk. DevvX was built with every one of these requirements in mind.
━━━━━━━━━━━━━━━━━━━━
🔹 𝗚𝗥𝗢𝗪𝗜𝗡𝗚 𝗧𝗛𝗘 𝗗𝗘𝗩𝗩𝗘 𝗡𝗘𝗧𝗪𝗢𝗥𝗞
One of the most exciting developments in the Fias-DevvX integration is what it means for the DevvE Network.
Fias opens up an entirely new realm of ability for third parties to create applications that run on DevvX. Until now, building on DevvX required deep programming teams and expertise. With Fias, that barrier drops dramatically. Using Fias Arches, developers and even non-technical creators can build DevvX applications far more easily — applications that run on the DevvE Network, where usage is paid for through the DevvE token.
Combined with DevvX's comprehensive protection suite — loss protection, theft protection, fraud protection, and privacy that satisfies regulatory requirements — we have an infrastructure stack that no other blockchain can match. These aren't incremental features. They are the requirements for enterprise-scale AI agent deployment, and we've been building them for years.
━━━━━━━━━━━━━━━━━━━━
🔹 𝗧𝗛𝗘 𝗔𝗜 𝗔𝗚𝗘𝗡𝗧-𝗗𝗥𝗜𝗩𝗘𝗡 𝗙𝗨𝗧𝗨𝗥𝗘 𝗢𝗙 𝗙𝗜𝗡𝗔𝗡𝗖𝗘
Here is a key part of our thesis: financial products themselves are moving into an AI agent-driven future. This isn't just about building infrastructure for others — it's about where the volume is going.
In the near future, trading volumes on digital asset exchanges will be dominated by AI agents. The same is true for borrowing, lending, and liquidity provisioning. AI agents will continuously analyze markets, optimize positions, route liquidity, and execute complex strategies — all autonomously and at machine speed. The shift from human-driven to agent-driven financial activity will be enormous, and the platforms that can handle it will capture immense value.
This represents one of the biggest opportunities in front of us: taking the financial products we've already built and positioning them for this new AI-dominated future — a future where there is massive growth ahead and where there aren't already established players with entrenched advantages. We are early to this market, and we have real products.
All existing DevvE use cases remain fully intact — exchange, lending, borrowing, and liquidity routing. Nothing is being taken away. What's changing is where these products are going. We are taking our financial products into this new AI-dominated future with real competitive advantages.
And here's the critical point: for AI agents to actually use financial products at scale, the underlying infrastructure has to meet specific requirements. You need high speed, because agents transact at machine pace. You need high throughput, because millions of agent transactions will happen simultaneously. You need cost effectiveness, because agent-to-agent micropayments have to be economically viable. And you need CTS, because when machines are transacting with machines autonomously, you must have trustless, atomic settlement with zero counterparty risk. DevvX was built with every one of these requirements in mind.
━━━━━━━━━━━━━━━━━━━━
🔹 𝗚𝗥𝗢𝗪𝗜𝗡𝗚 𝗧𝗛𝗘 𝗗𝗘𝗩𝗩𝗘 𝗡𝗘𝗧𝗪𝗢𝗥𝗞
One of the most exciting developments in the Fias-DevvX integration is what it means for the DevvE Network.
Fias opens up an entirely new realm of ability for third parties to create applications that run on DevvX. Until now, building on DevvX required deep programming teams and expertise. With Fias, that barrier drops dramatically. Using Fias Arches, developers and even non-technical creators can build DevvX applications far more easily — applications that run on the DevvE Network, where usage is paid for through the DevvE token.
❤9💯5💊2
Think about what this unlocks. Anyone will be able to integrate with DevvX and implement their own tokens and NFTs. Companies and individuals will be able to create AI-powered blockchain applications that run on DevvX — with CTS-backed trustless settlement, DevvX's protection suite, and regulatory-compliant privacy built in from day one. A creator can create a tokenized loyalty program, a supply chain verification system, a real estate fractional ownership platform, automated compliance monitoring systems, intelligent risk assessment tools, AI-driven market making strategies, portfolio optimization engines, or many other applications — all powered by DevvX infrastructure, all paying transaction fees through DevvE. A developer doesn't need to understand the intricacies of blockchain consensus to build a powerful DevvX application. They describe what they want, Fias Arches coordinate the AI Entities needed to build it, and the result runs on the DevvE Network.
Every new application on the DevvE Network means more DevvX transactions, more DevvE utility, and a larger ecosystem. This is the growth engine: Fias makes it dramatically easier to build on DevvX, which drives DevvE Network adoption, which increases DevvE token utility. The more applications that run on the network, the more valuable the entire ecosystem becomes.
It's important to emphasize that while DevvX is opening its network to AI-powered development through Fias, nothing is being taken away from traditional builders. Projects, enterprises, and developers can continue to utilize DevvX as they previously have — through conventional methods, custom codebases, and existing workflows. That path remains supported. What Fias introduces is an entirely new access layer. We're not replacing traditional development — we're adding AI-native development on top of it. The network meets builders wherever they are today. Most blockchains will spend the next few years trying to retrofit themselves for AI. DevvX is being built for it now.
━━━━━━━━━━━━━━━━━━━━
🔹 𝗧𝗘𝗔𝗠 𝗔𝗡𝗗 𝗗𝗘𝗩𝗘𝗟𝗢𝗣𝗠𝗘𝗡𝗧 𝗨𝗣𝗗𝗔𝗧𝗘
I want to address some team changes and give you a clearer picture of where things stand on the development side.
Ray Quintana is no longer involved with Devv. As our direction has evolved toward the AI-blockchain intersection, the path forward requires a different set of skills and focus. This direction simply wasn't a fit for Ray's skills and interests, and we wish him well in his future endeavors.
We currently have 6 developers working across both platforms. Bill continues to manage DevvX and DevvX applications and has already started applying AI toward refactoring efforts on the codebase — a great example of how AI is accelerating our own development, not just what we're building for others.
On the DevvX side, I recently gave an update to the Devv Ecosystem platform, which includes lending and DEX-like exchange capabilities. Those platforms are nearly finalized and available for us to leverage as we grow the Devv Ecosystem. One of the most exciting growth drivers for the DevvE network, though, is the way Fias can be used to build DevvX applications. The integration between DevvX and Fias is an enormous step forward in allowing custom DevvX applications to be created — Fias fundamentally accelerates software development including AI integrations, and that capability becomes incredibly powerful when combined with DevvX and the DevvE network for third-party applications.
More broadly, AI is making software development incredibly fast, and we plan to use it to dramatically accelerate our DevvX development. What used to take months can now take days. We are applying AI across the entire development lifecycle — from code generation and refactoring to testing and deployment. This means we can move faster, ship more, and iterate on the platform at a pace that would not have been possible even a year ago. It's a force multiplier for a team of our size.
Every new application on the DevvE Network means more DevvX transactions, more DevvE utility, and a larger ecosystem. This is the growth engine: Fias makes it dramatically easier to build on DevvX, which drives DevvE Network adoption, which increases DevvE token utility. The more applications that run on the network, the more valuable the entire ecosystem becomes.
It's important to emphasize that while DevvX is opening its network to AI-powered development through Fias, nothing is being taken away from traditional builders. Projects, enterprises, and developers can continue to utilize DevvX as they previously have — through conventional methods, custom codebases, and existing workflows. That path remains supported. What Fias introduces is an entirely new access layer. We're not replacing traditional development — we're adding AI-native development on top of it. The network meets builders wherever they are today. Most blockchains will spend the next few years trying to retrofit themselves for AI. DevvX is being built for it now.
━━━━━━━━━━━━━━━━━━━━
🔹 𝗧𝗘𝗔𝗠 𝗔𝗡𝗗 𝗗𝗘𝗩𝗘𝗟𝗢𝗣𝗠𝗘𝗡𝗧 𝗨𝗣𝗗𝗔𝗧𝗘
I want to address some team changes and give you a clearer picture of where things stand on the development side.
Ray Quintana is no longer involved with Devv. As our direction has evolved toward the AI-blockchain intersection, the path forward requires a different set of skills and focus. This direction simply wasn't a fit for Ray's skills and interests, and we wish him well in his future endeavors.
We currently have 6 developers working across both platforms. Bill continues to manage DevvX and DevvX applications and has already started applying AI toward refactoring efforts on the codebase — a great example of how AI is accelerating our own development, not just what we're building for others.
On the DevvX side, I recently gave an update to the Devv Ecosystem platform, which includes lending and DEX-like exchange capabilities. Those platforms are nearly finalized and available for us to leverage as we grow the Devv Ecosystem. One of the most exciting growth drivers for the DevvE network, though, is the way Fias can be used to build DevvX applications. The integration between DevvX and Fias is an enormous step forward in allowing custom DevvX applications to be created — Fias fundamentally accelerates software development including AI integrations, and that capability becomes incredibly powerful when combined with DevvX and the DevvE network for third-party applications.
More broadly, AI is making software development incredibly fast, and we plan to use it to dramatically accelerate our DevvX development. What used to take months can now take days. We are applying AI across the entire development lifecycle — from code generation and refactoring to testing and deployment. This means we can move faster, ship more, and iterate on the platform at a pace that would not have been possible even a year ago. It's a force multiplier for a team of our size.
❤14💊2
Equally important is that everything is now under a single, unified group. Product, protocol, AI, financial infrastructure, and go-to-market strategy are no longer fragmented. The entire stack — from DevvX and DevvE through to Fias and AI orchestration — is being driven forward by one aligned team with a single roadmap and a clear execution mandate. This enables an all-in-one offering that speaks directly to both traditional finance and enterprises that require compliance, scale, and trust, as well as the emerging AI economy that demands speed, automation, and intelligent infrastructure. One team, one vision, one execution path.
We are working closely with Will Stewart, a highly experienced executive and venture capitalist. Through Will's efforts, we are engaged in discussions with potential partners in categories that we feel are even more exciting than what we've explored previously. I'm genuinely optimistic about where these conversations are headed.
━━━━━━━━━━━━━━━━━━━━
🔹 𝗧𝗥𝗔𝗗𝗙𝗜 𝗣𝗔𝗥𝗧𝗡𝗘𝗥𝗦𝗛𝗜𝗣
Many of you have been asking about our previously disclosed TradFi relationship. I want to set expectations appropriately here.
This relationship is not dead. Over the past 12+ months, we have been actively working alongside the partner’s technical team on implementation of the Exchange, and that work has progressed throughout the year.
Momentum paused when funding was not received, and we are currently in discussions to determine how best to move forward together.
At the same time, we believe our new AI platform creates additional synergies that could be compelling both for this partner and for other institutional relationships. We’ll share more as those conversations develop. I know many of you have been eager for updates on this front, and I appreciate your patience.
━━━━━━━━━━━━━━━━━━━━
🔹 𝗧𝗢𝗞𝗘𝗡 𝗦𝗨𝗣𝗣𝗟𝗬 𝗔𝗡𝗗 𝗟𝗜𝗤𝗨𝗜𝗗𝗜𝗧𝗬
We previously discussed the possibility of expanding the maximum token supply to 2.1 billion tokens. After careful consideration over time, we've determined that a larger supply simply won't be needed. 𝗧𝗵𝗲 𝗺𝗮𝘅𝗶𝗺𝘂𝗺 𝘁𝗼𝗸𝗲𝗻 𝘀𝘂𝗽𝗽𝗹𝘆 𝘄𝗶𝗹𝗹 𝗿𝗲𝗺𝗮𝗶𝗻 𝗮𝘁 𝟯𝟬𝟬 𝗺𝗶𝗹𝗹𝗶𝗼𝗻 𝘁𝗼𝗸𝗲𝗻𝘀.
We are also actively exploring ways to manage and improve liquidity for the tokens. We understand this matters to the community and we're working on it. More details to come as those efforts take shape.
━━━━━━━━━━━━━━━━━━━━
🔹 𝗔 𝗡𝗘𝗪 𝗖𝗢𝗠𝗠𝗨𝗡𝗜𝗖𝗔𝗧𝗜𝗢𝗡𝗦 𝗔𝗣𝗣𝗥𝗢𝗔𝗖𝗛
One thing I've heard loud and clear from this community: you want more visibility into what's happening.
Going forward, we are adjusting our communications strategy for the project as a whole. You'll see more regular updates with more granular descriptions of where we are headed — both on the technology and the business side. With the AI platform, there are also opportunities for the community to become more directly involved, which leads me to...
━━━━━━━━━━━━━━━━━━━━
🔹 𝗖𝗢𝗠𝗠𝗨𝗡𝗜𝗧𝗬 𝗖𝗢𝗡𝗧𝗥𝗜𝗕𝗨𝗧𝗢𝗥 𝗣𝗥𝗢𝗚𝗥𝗔𝗠
We have heard you. Many of you want to get more involved — and now you can.
If you have the time, skills, and experience, we're launching a 𝗻𝗲𝘄 𝗰𝗼𝗻𝘁𝗿𝗶𝗯𝘂𝘁𝗼𝗿 𝗽𝗿𝗼𝗴𝗿𝗮𝗺 that gives you the opportunity to work closely with the core team. This means having a voice, getting involved hands-on, helping drive the project forward, and getting first access to the Fias platform.
Whether your background is in development, AI, marketing, community building, content, or something else entirely — if you're passionate about what we're building and want to contribute, we want to hear from you.
More details on how to participate will be shared shortly. Stay tuned in this channel.
━━━━━━━━━━━━━━━━━━━━
🔹 𝗟𝗢𝗢𝗞𝗜𝗡𝗚 𝗔𝗛𝗘𝗔𝗗
I want to close with this: 𝘄𝗲 𝗮𝗿𝗲 𝗻𝗼𝘁 𝘀𝘁𝗮𝗿𝘁𝗶𝗻𝗴 𝗼𝘃𝗲𝗿. We are taking nine years of development, patented technology, and deep expertise — and directing it at the single largest growth opportunity in blockchain.
We are working closely with Will Stewart, a highly experienced executive and venture capitalist. Through Will's efforts, we are engaged in discussions with potential partners in categories that we feel are even more exciting than what we've explored previously. I'm genuinely optimistic about where these conversations are headed.
━━━━━━━━━━━━━━━━━━━━
🔹 𝗧𝗥𝗔𝗗𝗙𝗜 𝗣𝗔𝗥𝗧𝗡𝗘𝗥𝗦𝗛𝗜𝗣
Many of you have been asking about our previously disclosed TradFi relationship. I want to set expectations appropriately here.
This relationship is not dead. Over the past 12+ months, we have been actively working alongside the partner’s technical team on implementation of the Exchange, and that work has progressed throughout the year.
Momentum paused when funding was not received, and we are currently in discussions to determine how best to move forward together.
At the same time, we believe our new AI platform creates additional synergies that could be compelling both for this partner and for other institutional relationships. We’ll share more as those conversations develop. I know many of you have been eager for updates on this front, and I appreciate your patience.
━━━━━━━━━━━━━━━━━━━━
🔹 𝗧𝗢𝗞𝗘𝗡 𝗦𝗨𝗣𝗣𝗟𝗬 𝗔𝗡𝗗 𝗟𝗜𝗤𝗨𝗜𝗗𝗜𝗧𝗬
We previously discussed the possibility of expanding the maximum token supply to 2.1 billion tokens. After careful consideration over time, we've determined that a larger supply simply won't be needed. 𝗧𝗵𝗲 𝗺𝗮𝘅𝗶𝗺𝘂𝗺 𝘁𝗼𝗸𝗲𝗻 𝘀𝘂𝗽𝗽𝗹𝘆 𝘄𝗶𝗹𝗹 𝗿𝗲𝗺𝗮𝗶𝗻 𝗮𝘁 𝟯𝟬𝟬 𝗺𝗶𝗹𝗹𝗶𝗼𝗻 𝘁𝗼𝗸𝗲𝗻𝘀.
We are also actively exploring ways to manage and improve liquidity for the tokens. We understand this matters to the community and we're working on it. More details to come as those efforts take shape.
━━━━━━━━━━━━━━━━━━━━
🔹 𝗔 𝗡𝗘𝗪 𝗖𝗢𝗠𝗠𝗨𝗡𝗜𝗖𝗔𝗧𝗜𝗢𝗡𝗦 𝗔𝗣𝗣𝗥𝗢𝗔𝗖𝗛
One thing I've heard loud and clear from this community: you want more visibility into what's happening.
Going forward, we are adjusting our communications strategy for the project as a whole. You'll see more regular updates with more granular descriptions of where we are headed — both on the technology and the business side. With the AI platform, there are also opportunities for the community to become more directly involved, which leads me to...
━━━━━━━━━━━━━━━━━━━━
🔹 𝗖𝗢𝗠𝗠𝗨𝗡𝗜𝗧𝗬 𝗖𝗢𝗡𝗧𝗥𝗜𝗕𝗨𝗧𝗢𝗥 𝗣𝗥𝗢𝗚𝗥𝗔𝗠
We have heard you. Many of you want to get more involved — and now you can.
If you have the time, skills, and experience, we're launching a 𝗻𝗲𝘄 𝗰𝗼𝗻𝘁𝗿𝗶𝗯𝘂𝘁𝗼𝗿 𝗽𝗿𝗼𝗴𝗿𝗮𝗺 that gives you the opportunity to work closely with the core team. This means having a voice, getting involved hands-on, helping drive the project forward, and getting first access to the Fias platform.
Whether your background is in development, AI, marketing, community building, content, or something else entirely — if you're passionate about what we're building and want to contribute, we want to hear from you.
More details on how to participate will be shared shortly. Stay tuned in this channel.
━━━━━━━━━━━━━━━━━━━━
🔹 𝗟𝗢𝗢𝗞𝗜𝗡𝗚 𝗔𝗛𝗘𝗔𝗗
I want to close with this: 𝘄𝗲 𝗮𝗿𝗲 𝗻𝗼𝘁 𝘀𝘁𝗮𝗿𝘁𝗶𝗻𝗴 𝗼𝘃𝗲𝗿. We are taking nine years of development, patented technology, and deep expertise — and directing it at the single largest growth opportunity in blockchain.
🔥25❤7👍3🤷♂1💊1
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.
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.
❤43🤪6
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/
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/
YouTube
Introduction to the Tomlucient Channel - Building an AI Company in Real Time
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…
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…
❤53👍11🥰1🤔1🙏1
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.
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.
YouTube
What is Fias? The World's Monetization Platform for AI
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…
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…
🔥13👍5❤2🥰1
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.
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.
👍28❤26😴3🤪3
Hey everyone, Bill told me the password reset on the new site is working again, for those of you who had troubles logging in.
👍14❤2
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.
👍42👏3
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.
🔥70❤16🍓1
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
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
👍17❤2
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.
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.
🔥93❤31👏4👌2🤩1
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.
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.
🔥29❤7🤷♂6
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.
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.
❤57🔥28🤷♂4🤪2👍1
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.
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.
🔥33❤12👍8🥰3
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.
🔥63❤15⚡4👏3🎉3👍2🤪1
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.
🔥81❤🔥11❤6👍4🎉3🥰1👏1
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 👍
🔥63👏14❤12👍8
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
https://platform.fias.io/a/arche_todo_lists/public/fias_roadmap
🔥31❤18