<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Zvezdin Besarabov on Medium]]></title>
        <description><![CDATA[Stories by Zvezdin Besarabov on Medium]]></description>
        <link>https://medium.com/@zvezdin?source=rss-eabd29afcd9f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*9tPZhaqwGqQ-jhajjCT68g.jpeg</url>
            <title>Stories by Zvezdin Besarabov on Medium</title>
            <link>https://medium.com/@zvezdin?source=rss-eabd29afcd9f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 16:31:37 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@zvezdin/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[ScyNet tech update #3]]></title>
            <link>https://medium.com/scynet/scynet-tech-update-3-6a952750c06?source=rss-eabd29afcd9f------2</link>
            <guid isPermaLink="false">https://medium.com/p/6a952750c06</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[consensus]]></category>
            <category><![CDATA[deep-learning]]></category>
            <category><![CDATA[techupdates]]></category>
            <dc:creator><![CDATA[Zvezdin Besarabov]]></dc:creator>
            <pubDate>Mon, 29 Apr 2019 20:04:57 GMT</pubDate>
            <atom:updated>2019-05-02T12:01:58.315Z</atom:updated>
            <content:encoded><![CDATA[<p>Blockchain protocol — More ways to publish and report ScyNet agents</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4nyRRSS38US4rz1zYrZlog.png" /></figure><h3>Validating AI Agents</h3><p>The latest idea for validation within the ScyNet network, included computational nodes who submit their best agents (AI solutions) to compete in tournaments. Tournaments are blockchain processes that cryptographically verify the performance of the participating agents, rewarding the best ones. Only so external clients utilize dependable AI agents.</p><p>In theory, this sounds great, but it actually creates a lot of practical complications and deadlock scenarios. Tournaments require a separate <a href="https://medium.com/scynet/scynet-tech-update-1-ee38dbbeb6a">Tendermint-based blockchain network for each domain</a> (AI problem) type, yet we want to have a single, unified ScyNet token. One way to counter this is to create an ERC20 contract somewhere and then use Cosmos’s IBC protocol to allow people to transfer tokens from that main chain to domain chains.</p><p>Even if this works perfectly fine, consider the following scenario. Person A wants to create a new domain type, so he modifies our controller code and generates the Tendermint chain. He uses IBC to transfer 10 ScyNet tokens in this new Tendermint chain and stakes them to become the first validator in this network. Then comes person B, who transfers 30 ScyNet tokens to the same chain, also becoming a validator. Since B holds more than ⅔ of the consensus power in this small chain, he could easily withdraw any ScyNet tokens he wants from this chain to the main chain, including stealing A’s stake.</p><h3>Solution</h3><p>We don’t want to have this significant risk in the creation of new domain networks, which is why we’re making tournaments optional. Here’s how. First, let’s forget about any custom blockchains — we have a couple of ScyNet nodes, each one specializing in specific AI problem. Each one of those announces its existence in a global smart contract (for example, somewhere on Aeternity mainnet). Harvesters use this contract to publish their data agents. Miners purchase access to this data and publicly announce their most performant agents in this contract, self-reporting their performance.</p><p>This sounds great, but how can we trust that the reported performance of the agent is true? It’s a free market, and false-advertising your product will eventually lose your clients. However, there’s still a risk for the first clients of the agent. We can resolve this by introducing a <strong>P2P agent validation protocol</strong>. The client communicates with the agent’s hatchery node until the former is cryptographically convinced of the agent’s performance. We can implement this by having the client and the hatchery privately execute the tournament validation protocol to validate one particular agent. And since this is only between two participants, we do not need a separate blockchain network.</p><p>But what if a hatchery wants to compete with others in a Tournament? While not mandatory, that’s still possible. The hatcheries that wish to contest will form their own Tendermint-based blockchain network, transfer their participation fees through IBC, execute the standard Tournament process, distribute the Tournament reward, and then withdraw the ScyNet tokens back to the main chain. The risk to steal others’ tokens still remains, but since all tokens in circulation in this Tournament are high-risk anyways, the problem is not that significant.</p><p>It’s interesting how the problem of vulnerability on small Tendermint chains led us to this central connecting contract that allows for every vital ScyNet function, while still keeping the tournament functionality intact.</p><h3>Next Steps</h3><p>Our next steps are to run a ScyNet node end-to-end locally — with a “Harvester” to provide domain related data and a “Queen” to produce a constant flow of AI agents. (agent producer).</p><p>But if you’re nervously waiting, why not <a href="https://discord.gg/Rx98x4H">join our discord</a> now and figure out what we’re up to?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6a952750c06" width="1" height="1" alt=""><hr><p><a href="https://medium.com/scynet/scynet-tech-update-3-6a952750c06">ScyNet tech update #3</a> was originally published in <a href="https://medium.com/scynet">ScyNet</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ScyNet tech update #1]]></title>
            <link>https://medium.com/scynet/scynet-tech-update-1-ee38dbbeb6a?source=rss-eabd29afcd9f------2</link>
            <guid isPermaLink="false">https://medium.com/p/ee38dbbeb6a</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[tendermint]]></category>
            <category><![CDATA[techupdates]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[deep-learning]]></category>
            <dc:creator><![CDATA[Zvezdin Besarabov]]></dc:creator>
            <pubDate>Mon, 04 Mar 2019 08:47:15 GMT</pubDate>
            <atom:updated>2019-05-01T10:13:56.697Z</atom:updated>
            <content:encoded><![CDATA[<h4><strong>Blockchain consensus — implementation &amp; validation challenges</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3m8ZvJhnnSyOn5k4RVKypw.png" /></figure><p>Hello there, dear ScyNet reader! This post marks the first from a series of regular ScyNet development updates. The objective is to present the tech behind ScyNet while also updating you on our most recent progress — what are we doing behind the scenes? What are we challenged by? What are our next steps?</p><p>As you may know, ScyNet is all about building a blockchain network that incentivizes independent computing nodes to provide GPU resources for the training of AI agents. In this post, we’ll focus on our progress about the design and implementation of such a blockchain consensus.</p><p><strong><em>TLDR</em></strong><em>: We defined the consensus protocol on paper, chose to implement it using Tendermint and Cosmos SDK, and stumbled upon an interesting problem about validating timed transactions on the blockchain.</em></p><p>First of all, what do we need our blockchain consensus to do? In layman’s terms, the objective is to organize timed tournaments, where the participating computing nodes compete on who managed to create the highest performing agent. To evaluate performance, we require every competing node to send a specific set of transactions at specific timed deadlines. For example, in a ScyNet domain about stock market predictions, the consensus may require all nodes to submit real-time predictions from their agents for a specific period.</p><p>We decided that it would be best to implement this protocol using Tendermint consensus — a scalable framework for Byzantine Fault-Tolerant blockchains. It handles transaction propagation and block creation while exposing a flexible API for us to write our own state machine on top of it.</p><p>If that’s not enough, we’re also utilizing the Cosmos SDK — a modular framework for creating Tendermint-based applications. The exciting thing about Cosmos is that it gives us access to modules about token transactions and IBC (Inter-Blockchain Communication aka sending tokens in-between blockchains) functionality out of the box and allows us to build our application on top of them. Our most recent progress is on designing the modules we will implement through Cosmos to allow for our ScyNet consensus logic, as well as working on their implementation.</p><p>Doing so, we also focused on resolving an interesting consensus challenge. Back to the stock market predictions example, some nodes may try to cheat by submitting their predictions much later than the expected deadline, which means that the blockchain consensus must enforce time-based transaction validation. Sounds great in theory, but in practice, if every node would validate transactions against its own clock, the small variations in these clocks will create a huge disparity between the nodes and is likely to tear the network apart.</p><p>One could propose to use the time in the block header as the deterministic source of time instead. Yet there’s a catch — in Tendermint, the time in the header of a block is actually the timestamp of the previous block. And in order to validate the transactions in a block, you actually need to wait for the next one and use its timestamp instead. For now, this seems like a plausible solution, but we’re also discussing other potential strategies with Tendermint devs in the meantime.</p><p>Great! We have a stable tech stack, a strictly defined blockchain protocol, and we are working on its implementation. Now it’s time to deliver a working Proof-of-Concept blockchain node. This will be our short-term goal for the next couple of weeks. After it is stable enough, we plan to launch a public testnet.</p><p>“But wait!” you may ask, “How am I going to learn about this?.” Thanks for reminding me! We’ll keep writing development updates, but if you want to be the first to hear about an exciting new update, seek direct contact with the core team, or have an interesting idea or suggestion about ScyNet, make sure to <a href="https://discord.gg/Rx98x4H">join us on Discord</a>!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ee38dbbeb6a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/scynet/scynet-tech-update-1-ee38dbbeb6a">ScyNet tech update #1</a> was originally published in <a href="https://medium.com/scynet">ScyNet</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>