How Seasons Turns Your Wallet Into a Savings Account feat. CEO Andrey Didovskiy
Listen Now
About This Episode
In this episode of DevNTell, Narb interviews Andrey Didovskiy, Founder and CEO of Seasons, an autonomous, internet-native tokenized liquidity system built on Solana. Andrey shares his journey from writing early crypto whitepapers and distributing Bitcoin ATMs to building Seasons to solve crypto's boom-and-bust cyclicality. He demonstrates Seasons' architecture—including its 10% Transfer Tax (TTT), Yield Management System (YMS), yield-bearing stablecoin module (SSYM), and automated twice-weekly wallet payouts in gold, Bitcoin, and jUSDC—as well as Liquidity OS and upcoming commercial applications. Andrey also discusses solving capital efficiency bottlenecks by reducing distribution costs by 99%, how AI agents will leverage Seasons as a digitally native yield source, and practical advice for aspiring founders ahead of Solana Breakpoint.
Key Takeaways
Seasons turns any qualifying Solana wallet into a node (Liquidity Router) that automatically receives yield payouts twice a week in tokenized gold, Bitcoin, and jUSDC without manual claiming.
The protocol operates via a 10% transfer tax (TTT) routed through a Yield Management System (YMS) and yield-bearing stablecoin module (SSYM) to keep positions and yields completely liquid.
Through batching distribution transactions directly from the originating address rather than smart contracts, Seasons reduced distribution costs by ~99% and raised capital efficiency to nearly 99.9%.
Seasons is designed for an agentic-first internet, allowing autonomous AI agents to pay a one-time cost to generate ongoing, digitally native on-chain revenue.
Featured Guest
Andrey Didovskiy
Founder and CEO @ Seasons
Timestamps(click to jump)
Episode Transcript
Read full transcriptHide transcript
GM, GM! Welcome to what's going to be another fantastic episode of DevNTell. So if you didn't know, DevNTell is a 30-minute podcast allowing founders, hackers, and anyone in between the opportunity to come on the show and showcase what they've built. And today I'm excited to welcome Andrey Didovskiy, who is the founder and CEO of Seasons. So if you're not familiar, Seasons is the autonomous, internet-native tokenized liquidity system designed to facilitate the generation, distribution, and accumulation of yield through modern DeFi mechanisms. So if you stick around for today's episode, you'll get to meet Andrey, get an introduction to the Seasons platform, and learn how you can get started using it today. All right, let's get into it.
GM, GM! Welcome to the show, Andrey. I'm excited to have you on today, man.
GM and GN, Narb. Thank you so much for having me on. It's a pleasure to be here.
Yeah, absolutely. It's a pleasure to have you on. Yeah, I know you have a lot of great stuff planned for us around Seasons. I've looked into the platform, it looks really cool, and I can't wait for our audience to learn more about it. But before we get into that, would you just like to give an introduction about yourself?
Yeah, absolutely, absolutely. A little introduction about me—hi everybody, my name is Andrey Didovskiy. I am the founder and CEO of Seasons. Seasons is, as Narb introduced, a DeFi protocol focused on what we call a liquidity system focused on generating yield. That's the long and short of it, effectively. We'll get into the details as we go along. I guess for a quick backdrop about myself to get everybody familiarized: I got into this space, into crypto, informally—just to be clear—at about 2014-2015. I didn't get in, I just learned about crypto through the grapevine of a friend of a friend. Fast forward a couple years, and after actually observing from the sidelines for a little bit—although for the OGs here, if you remember things like BloomBTC, I did back in the day try all those 'compound your Bitcoin then it goes absolutely belly up' kind of things—anyway, fast forward a couple years and in about, call it '17-ish, I took the industry very seriously, like around the altcoin boom, obviously, so it was prime time. And I came in writing white papers, technical documentation of different types, SOPs, creating different workflows for any kind of systems design for startups in this space. I mean, who wasn't a startup in this space at the time? So I worked with a lot of companies, and this wasn't just crypto to be clear; there were even back at that time some autonomous systems, some quality assurance companies, auditing firms, and e-commerce that was in fact exploring how to use blockchain and integrate it into all their things, and this was '17, '18, and '19. Writing these papers, of course, I made a lot of friends and interesting connections along the way, worked with a couple of cool companies such as Prophecy creating an inverted protocol for majority wins, minority loses, TrustSwap—tons of names doing different things. Fast forward again a couple years after that, I fell in love with the deep tech consensus stuff, and life takes me to sales. The fourth largest company in the United States at the time, RocketCoin, brought me on to help them distribute their ATM machines all throughout my coast, so call it Boston to Florida—this whole coast was covered. And I became, I do believe, the number one performer at the very least on this coast for installs. I was just sending these machines out everywhere—no sales background, my tongue barely worked. I just honestly did the most basic thing: I picked up the phone and I told people that they should have a Bitcoin machine because I believed in it. That's where this whole snowflake effect snowballing kept going. That led me to becoming the CPO and CEO of a sports startup from Florida who had their own sport called Bitosteer. They were around until about '21, late '21, even early '22—obviously during FTX times, what's to be expected—they tried hard. A lot of cool experience, of course: real team management, understanding how to do communications, a lot of things came from that that are just honestly infinitely valuable, which led me to starting up my own consulting firm. This consulting firm opened up magnitudes crazier connections and communications, made me the CEO of another sports company actually called Athlete Blockchain. We built a whole Layer 1 using the Rust SDK. It was for sports, but of course with all the parachain XCM functionalities and everything else, it was a much bigger vision, and I do believe it's still out today in spite of what's going on with Polkadot—that's for another day. And after, of course, making all the more connections industry-wise, operators specifically, led to building Seasons. And just to tie this all together, this whole journey, there was always the same theme: why is it cycles? Why is there like a two-year gap, four-year gap, in terms of doing the same thing for so long? Why isn't there more variance? Well, because the industry obviously went in cycles and blew up and busted, and that's where Seasons is born. I was so personally tired—and of course witnessing a lot of the people I know—being dependent on price just destroys quality of life. And that's where Seasons comes in.
That's amazing, man. That's quite the background, and yeah, it seems like all those experiences along the way kind of built your founder mindset. Like the sales stuff—if you can build and you can sell, right, you're invincible, that's what the saying is, right? But yeah, you mentioned you're all around DeFi, tokenomics, and the economics around it, and I'm sure being able to sell the Bitcoin ATMs and get people onboarded and learning and thinking about such a thing must have been a challenge in itself just explaining what Bitcoin is. I've tried to do it multiple times and it can go either way. But coming from the perspective of perhaps somebody watching today who doesn't have this background in Bitcoin or DeFi, and they're thinking why should I care to have an on-chain savings account versus just sticking with their bank savings account—what would you tell them, how would you convince them of that?
Well, first I would start with definitely that's a fair question in this day and age. There's so much going on, even let's forget everything else, just the influx of cybersecurity issues going on, so definitely the right time to ask the question. Ultimately, I believe there is still more opportunity on-chain for the savvy operator who actually understands how each component in solving their problem works the right way, so I do believe it's extremely prime. As for why you would definitely go for a savings account on-chain, honestly basically almost anywhere you put your money on-chain you're going to be making a better return than your bank. I mean, it's been true, it will remain true, and I believe it gets all the more true as we move forward. And that's actually a great little window into Seasons. One of the better ways we talk about it—and this actually comes from the Bitcoin ATM thing, because selling people Bitcoin is effervescent, they can't tangibly make sense of it—so the way it had to be done was repurposing it: I'm not selling them the Bitcoin, I'm asking them how much foot traffic are you getting, why are you not putting this to better use? So that reshaped the understanding of how to frame things, because a lot of tech people tend to get locked into this vision and forget about the whole user experience, not just the product but the real-world life of it. In any case, the window into Seasons is that we like to say you can use it like a savings account. Ultimately, Seasons is a protocol. The protocol can be applied to build a multitude of different applications. The top four commercial applications Seasons enables are enterprise-grade rewards programs—where instead of subsidizing from their own cash flow, they use Seasons—savings accounts, and user retention tools like faucets. If we focus and dial in on the savings accounts, it's actually in the node software technology where all a user has to do is hold tokens: any address on Solana that holds above a certain threshold of tokens is automatically registered as an operator in the network. Operators are also referred to as liquidity routers because that's what the objective of a node is. You get constant flows of revenue, a stream of capital from the system coming to you live twice a week, and it's ultimately up to you to decide what happens with this capital next. If you are truly aligned with the protocol, it's assumed you would compound it or put it to work in some way within the ecosystem, and if you're not, that's okay—that's the whole part of the design where all types of consumers can be satisfied.
Amazing. And yeah, I'd love for our audience to kind of see this in action. If you want to bring up your screen now, we can go through it screen by screen.
Yeah, just to set some context guys, the mechanism works so simple—the whole demo is just open any wallet, get some tokens on it, and let it run. What I wanted to show everybody was that as of recent times, we've been going through a lot of growth because, regardless of what headlines say, there are more assets coming on-chain. That is the long and short of it. User flows will return; you need that reflexivity from different participants—industries, retail, traders, businesses—you need different things organized and orchestrated at the right place at the right time. Right now, what we've been talking about to the public is a lot of this new release from us. That's what I was going to show you, and perfectly enough, this release contains the perfect graphic to explain that mechanism that does not exist anywhere right now. So I will take this as a chance to show everybody what Seasons is and how it works a little bit. All right, drum roll—this is the first public showing of this. Hopefully my team doesn't get too mad at me because I didn't synchronize with them, but guys, enjoy.
All right, bringing it on stage now.
So this is Seasons... Is it visible?
Yeah, it's good. Go for it.
All right. So guys, this is what Seasons is coming to today: Tokenized, Internet-Native Liquidity System. The data is stale—obviously all the numbers are not live, this is just what we're preparing to release. Your question was a little bit about how this mechanism works. This is one of the most comprehensive ways to explain how the mechanism works without having to talk about which protocol frameworks are used in the vaults themselves or which fee models and strategies. Top down, any user—be you a tech nerd or somebody who's not too familiar with crypto—can actually use this. And not only can you use this to take you through the system, there's an actual guide, our AI called Gaia—Mother Earth, Mother of Life—that is an assistant everywhere throughout the site. So the way Seasons works at the highest level: there's three components—TTT, SSYM, and YAV. Top TTT is Transfer Tax, just a service fee anytime the token is touched. The way this is presented to the user—because again, selling Bitcoin does not work—this is insurance on their stream of cash flow. In any case, it's a 10% transfer fee. And SSYM stands for Stablecoin Module. Whenever we are doing distributions, these distributions are queued. While they are in queue, why hold them as just USDC? They are held as yield-bearing stablecoins, and that means the dollar distributed after it's completed distribution has earned whatever tiny fraction amount—multiply that by the hundreds of thousands, millions, and ultimately billions of dollars that will be flowing through the system, that obviously adds up and contributes to protocol-owned liquidity. And ultimately the DeFi strategies—it says 'soon' here—we're actually deploying our vaults within about a week or two, trying to get around Solana Breakpoint to catch that whole vibe. So we're releasing our vaults, open deposits based on whitelists for users. All these things generate fees, and those fees directly go into feeding the Yield Management System (YMS). At the highest level, the YMS is the orchestrator that makes sure each individual component is working right, that capital flows correctly through the system, and it is also tasked with the acquisition of assets that are then used for distribution. The payout model is automatic; assets go into wallets directly, there's no claiming needed. We're talking about Director Nodes right now, and there's also a fine-grained Builder Node tier for users who aren't ready or don't want to become a Director. They get gold, Bitcoin, and jUSDC directly in their wallet twice a week, every Sunday and Wednesday, and that's literally all of it. The yield is liquid, the position remains liquid—that's the key component in all of Seasons' design, why we call it a liquidity system. Every element of the mechanism must be liquid: the position itself, the yield you receive, everything about this is as liquid as can be, designed to optimize capital flows and grow the pie for everybody. Because when you look at protocols in isolation, it almost always feels like they're trying to take share away from each other, whereas yield and stablecoin protocols positioned correctly grow the pie for everybody. There's much more to present. Next is Liquidity OS—one of the four major announcements in this release coming up, before year-end of course. Our terminal was effectively just for data; this has become an entire operating system that tracks and manages—as you see in the screenshot of a cosmology—live tracking the status of how capital is flowing through the system and where it is at any given time, plus new tooling and features for operators. We are not blind to the fact that the world is consolidating around super apps—be it Jupiter, WeChat, whatever—and competing strictly on having your own frontend application will never reach a true level of scale. So the application for us is a Trojan horse to open conversations the right way with substance, integrating a button that says 'you have idle assets, put them to work with Seasons' on platforms like Robinhood, Coinbase, Webull, Revolut, whatever platform you're on. Liquidity OS is the golden Trojan horse for this. And just like today people can claim their physical Pokémon or One Piece cards through crypto, why don't people holding tokenized gold have an option to claim physical pieces? It's coming to you from the Seasons liquidity system—everything is liquid. To wrap this up, the commercial applications: Savings Accounts, Reward Programs, TCC-EX—an exchange of digitally native obligations, basically an on-chain cash advance marketplace where nodes have adequate cash flow that can be provided to the public at a premium for a time horizon without underlying token exposure—Agentic Credit Infrastructure, Perpetual DCA, Automated Portfolio Building, Treasury Diversification, and Trade Financing. One thing you don't see on this screen yet is our API integration, which is currently read-only for data, with commercial version v1 coming out very soon. I'm going to stop sharing and come up for some air—give me some feedback!
Firstly, thank you so much for that alpha. The website and the platform look amazing—looks like a full end-to-end solution, and kudos to you and your team for building that out. That must have been no easy feat, I'm sure.
Shout out to everybody—everybody contributed, honestly.
Yeah, and I'm sure as you guys were building this out, you had your fair share of technical hurdles and things you had to overcome, whether that's UX or the underlying protocols powering the platform. Would you be able to speak to any of those technical challenges and how you overcame them?
Yeah, the most glaring one was when we initially launched: we had a basket of five assets, and those assets were meme coins. That whole epoch, our very first proof-of-concept launch if you will, was very inefficient. That's why we needed to launch in this model, but the first and biggest hurdle was capital efficiency of the system—as capital flows through it, how much is actually spent on conversion and lost in friction across routers. And that number at the time went as low as 95.53%, floating around an average of 97.8% approximately. So very inefficient—left unchecked, this would bleed to nothing. So we needed to find solutions, and the biggest part of that drain was the distribution. New operators and new nodes mean new ATAs for each asset right off the bat, and most people aren't closing them, so that's one cost. Then for each distribution, we were using publicly available tools that were just not cost-efficient. Only in Q3, dealing with this, we finally found a solution that not only solved the distribution problem, but brought the cost of distribution down by roughly 99%. This is our developers' achievement—Pasha specifically—who found a way to be much more effective in distributions via a mass-sending method. From what I understand, rather than using a smart contract to split these things, he just batches them into groups of eight and shoots them from the originating address, and that's it. It's a very simple fix, and this fix now brought our capital efficiency steady to about 99.6%. In addition to this, we also found a couple other optimizations using API calls that brought that level up to about 99.8% or 99.9% approximately. So it's not perfect yet, it's a process, but the transformation is impossible to ignore. That specific tool is also going to become a public airdrop tool that will be more accessible than existing ones—we can provide the service for 75% lower cost, and all the fees generated go straight back into the mechanism as a whole.
That's amazing, and I love it when simple fixes and simple change-ups lead to those massive gains in optimization. Kudos to your engineering team for fighting through all those hurdles and getting to where you are today. You mentioned it while you were doing your screen share: for our developer audience watching today who wants to get involved with Seasons and start building with it, you mentioned you have a read-only API now. Are there any other tools or SDKs you want to call out for people watching to get building?
They will be made available very soon. Right now, anybody who's looking to partner—maybe somebody's already using it or has an idea on how to use it—reach out to us. We're very open to finding ways to integrate technologically with anybody; everybody wins in that situation. Right now the API is read-only. The next version of the API will already have components of SDKs for building—most likely the first, easiest app would be a user retention tool, aka a faucet—and we're going to open that up for the world. If you guys are creative, please contribute.
Excellent. And for people watching and listening today, those details on how to reach Andrey and the team will be in the description of the video below, so definitely reach out if that is something you're interested in. Shifting gears slightly, we know that AI agents are coming—they're going to be new citizens on the web and a new user group. From your perspective, how do you see an AI agent or somebody delegating AI agents interacting with Seasons? Do you think agents will need a way to earn yield?
Man, I just really love good questions—you just gave me such a beautiful setup, honestly. Absolutely. Seasons was actually conceived with an agentic-first internet as the design. Everybody should hopefully understand by now that agents will always prefer a system that is digitally native; they have the same provenance. Banking is not digitally native, so it's not going to be the future rails on which everything's built—it will fall back to blockchain. So AI agents are a massive opportunity, and that is our trillion-dollar vision of applications for credit infrastructure using Seasons to provide loans to agents via smart contracts with SLAs where there is no principal capital risk. This is easily said, much more complex in terms of prompt engineering protection and everything else, but the future will be run by agents—I don't doubt this. Call it 8 billion people; now there's 16 billion operators, each person gets their own agent, maybe your agent has an agent. What does this mean for Seasons? Look, we have Seasons the protocol, and we have Seasons Finance, the institution building applications using the protocol. For the protocol, most open-source agents—those not owned or operated by anybody else, and when governments eventually recognize agents as bankable entities the same way Wyoming set the precedent for DAOs—that unlock is going to be a Cambrian explosion. All open-source agents will always be looking for some way to generate finances, and institutions or operators telling their agents to find yield sources will find this as a prime opportunity. Agents using it themselves will always prefer a tool like Seasons: it's digitally native, and the return capacity is higher because of the TTT mechanism. All traditional yield protocols share the same problem of scale, where at a certain amount of deposits you cannot generate more yield. The TTT in Seasons enables a boundless measure based on activity, which can be driven by marketing or even if volume drops and people sell, reactivating the flywheel. Those nuances in human behavioral psyche are the same things that will make it attractive to agents, where they understand this is a one-time cost for a lifetime of revenue. Who does not want to use this? So the agent future is beautiful.
It is, it indeed will be beautiful, and I'm very grateful that we get to live through it and see it unfold in front of our eyes—definitely exciting times ahead and even now in the present. As we kind of come to time here, I just want to get one final question in. You mentioned at the start you went through a wealth of different experiences leading up to where you are now as a founder, and I'm sure you've learned a lot of lessons along the way. For people watching today who might just be starting their own founder journey or be on the cusp of wanting to become a founder for the first time, are there any words of wisdom or advice you'd be willing to share?
Well, that's high praise, I appreciate that, that's very kind. The only advice that comes to mind when asked this question is circumstantial based on where we are and how things are going. There are two things to do, and this is advice from others: the first one is Uncle Warren Buffett—when there's nothing to do, do nothing. And the second piece of advice is a barbell strategy from Brian Armstrong, talking about just doing something: take action, make mistakes, because mistakes produce information, and that information you can then take to figure out what to do next. So you have to be still and calm, and you have to be hyper-aggressive at the same time. As a founder, I think what served me the most is honestly making mistakes as fast as I can and spending as little time in the emotional state of it. You made a mistake, you're accountable—okay, great, what's next? Intelligence is about course correction through errors. So just do it, man. I know it sounds so mundane, but just do it, or woman, just do it!
Beautifully said, I couldn't agree more. And definitely that point about actions leading to data—data is what you need. You need to do something, learn from it, either fix it or build on top of it, and repeat that cycle. Just before we let you go, Andrey, you mentioned you're going to Breakpoint. Did you want to talk about that and where people watching today who are going can connect with you?
Yeah, guys, if anybody is coming to Breakpoint, I'm flying out—leaving my house in like six or seven hours—going to London, so if anybody's there, I'd love to chat. We are going there with the intention of making friends and finding people to partner with. So whether you're a DeFi protocol, service provider, wallet, or analytics—welcome! Let's see how we can work together. The last year has been crazy, and it's going to get crazier; we get through this together. So see you there.
Beauty. There you have it, folks. And with that, I just want to thank you again, Andrey, so much for taking the time out of your busy day to come chat with us. It was really awesome learning about yourself and the Seasons platform, and yeah, I wish you guys nothing but the best of luck as you continue to evolve here.
Narb, thank you so much. That was great, honestly loved talking to you guys and hope we can do this again sometime.
Of course, it would be my pleasure. And with that, I just want to wish everybody a very happy Friday, happy Saturday, safe travels if you're going to Breakpoint, and we will catch you back here next week for another great episode of DevNTell. Until then, have a good one, folks.
Bye, guys.
Listen On
Resources & Links
Share This Episode
Share on XWatch Episodes Live!
Subscribe to our event calendar and never miss a live episode.
View Event Calendar