<?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 RedTeam on Medium]]></title>
        <description><![CDATA[Stories by RedTeam on Medium]]></description>
        <link>https://medium.com/@TheRedTeam?source=rss-d348b4a0e85a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*4onebwPQeWjxHONaFPoFGQ.png</url>
            <title>Stories by RedTeam on Medium</title>
            <link>https://medium.com/@TheRedTeam?source=rss-d348b4a0e85a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 09:10:59 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@TheRedTeam/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[Alpha Token & Dynamic TAO: Supercharging RedTeam’s Decentralized Cybersecurity Ecosystem]]></title>
            <link>https://medium.com/@TheRedTeam/alpha-token-dynamic-tao-supercharging-redteams-decentralized-cybersecurity-ecosystem-af59e6b0aee7?source=rss-d348b4a0e85a------2</link>
            <guid isPermaLink="false">https://medium.com/p/af59e6b0aee7</guid>
            <category><![CDATA[decentralization]]></category>
            <category><![CDATA[token]]></category>
            <category><![CDATA[bittensor]]></category>
            <category><![CDATA[tokenomics]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[RedTeam]]></dc:creator>
            <pubDate>Tue, 28 Jan 2025 14:16:44 GMT</pubDate>
            <atom:updated>2025-01-28T14:17:39.508Z</atom:updated>
            <content:encoded><![CDATA[<h3>Introduction</h3><p>The launch of Bittensor’s Dynamic TAO (<a href="https://docs.bittensor.com/dynamic-tao">dTAO</a>) marks a seismic shift in how value is created, distributed, and governed across subnets. For RedTeam (<a href="https://github.com/RedTeamSubnet/RedTeam">subnet 61</a>), this update isn’t just technical — it’s transformational. By integrating the Alpha token into our monetization framework, we’re poised to create a self-sustaining ecosystem where miners, validators, challenge creators, and end-users align around shared incentives. This post <strong>explores</strong> how Dynamic TAO and Alpha will amplify RedTeam’s three core revenue streams while fostering decentralized innovation in cybersecurity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-Uv9q6Y-GssWJ4RYhlkSqA.png" /></figure><h3>1. Alpha Token: The Engine of RedTeam’s Economy</h3><p>The Alpha token is subnet 61’s governance and utility asset, designed to incentivize participation, reward quality, and fuel growth. Under dTAO’s decentralized model, Alpha’s value is tied directly to subnet performance, creating a flywheel effect:</p><p>□ <strong>Subnet Valuation: </strong>Stakeholders stake TAO into RedTeam’s liquidity pool to mint Alpha tokens. The price of Alpha rises as demand for subnet participation grows, increasing RedTeam’s share of Bittensor’s emissions.</p><p>□ <strong>Dual Rewards: </strong>Miners and validators earn Alpha tokens alongside TAO, linking their success to the subnet’s long-term health.</p><h3>2. Monetization Supercharged: Alpha in Action</h3><h4>A. Third-Party Challenges: A Decentralized Bug Bounty Marketplace</h4><p>Dynamic TAO turns RedTeam into a decentralized bug bounty platform where enterprises commission custom challenges. Alpha tokens streamline this process:</p><p>□ <strong>Challenge Creation Economy:</strong></p><ul><li><strong>Stake-to-Create:</strong> To propose a challenge (e.g., “A Bot Detection Script”), a user must stake a floating amount of Alpha tokens based on demand for a space. This prevents spam and aligns incentives.</li><li><strong>Artificial Scarcity: </strong>A limited number of challenge owner spaces would be allowed, similar to a Bittensor subnet registration environment, where the price of holding a challenge space (‘<em>sub subnet owners</em>’) will increase with the increased demand to hold a space.</li><li><strong>Bug Bounties: </strong>Third parties can propose bug bounties / challenges to challenge owners, where the owners would receive additional monetary value / margin on the bug bounty reward.</li><li><strong>Revenue Sharing: </strong>Challenge creators earn a % of mining rewards generated by their challenge, paid in Alpha. High-success-rate creators attract more enterprises, creating a reputation system.</li></ul><p>□ <strong>Dashboard Dynamics:</strong> A subnet-hosted dashboard lets enterprises:</p><ul><li>Browse challenge creators’ success rates.</li><li>Auction bounties to miners/validators based on availability (e.g., “Secure our Shopify store Feb 1–15”).</li></ul><p><strong>Example: </strong>A cybersecurity firm commissions a Challenge Owner to post a challenge, and pays the challenge owner a bounty. The challenge owner then creates the challenge for miners to compete in, leveraging their Alpha tokens to increase subnet incentives for competition in that respective challenge if needed (discussed further in 4. Governance). The challenge owner also earns a pre-determined % of the miner rewards.</p><h4>B. Miner Outputs: From Scripts to Stakeholder Value</h4><p>RedTeam miners generate bot detection bypass scripts — critical tools for stress-testing cybersecurity systems. With Alpha:</p><p>□ <strong>Staked Access: </strong>Companies like <a href="https://www.innerworks.me/">Innerworks</a> must stake Alpha tokens to have tailored, priority access to subnet databases.</p><p>□ <strong>Database Access</strong>:</p><ul><li>Miner scripts</li><li>Miner outputs from scripts (e.g. a data base of bot mouse movement sessions)</li></ul><p>□ <strong>Early Challenge Access: </strong>Miners with significant Alpha stakes unlock exclusive challenges first, creating a competitive edge for dedicated participants.</p><p><strong>Example:</strong> A miner staking 1,000 Alpha tokens gains early access to a Twitter/X bot detection challenge, allowing them to refine their script before rivals. Their successful output is licensed to Innerworks, which uses it to patch vulnerabilities — revenue from this license flows back to the subnet.</p><h4>C. Challenge Detection Components: Licensing Meets Liquidity</h4><p>RedTeam’s open-source SDKs and detection modules are foundational tools for developers. Alpha tokens enable:</p><p>□ <strong>Licensing Payments:</strong> Third parties (e.g., cybersecurity startups) pay in Alpha tokens to license RedTeam’s SDKs, embedding them into commercial products like fraud detection SaaS platforms.</p><p><strong>Example:</strong> Third parties can access software and applications powered by the RedTeam subnet. For example, if the RedTeam is powering a specific bot detection software, third parties will have limited to unlimited access with proportionate Alpha token stake.</p><h3>3. Alpha Token Buy-Back Program: Fueling the Flywheel</h3><p><a href="https://www.innerworks.me/">Innerworks</a>, RedTeam’s parent company, will allocate 10% of its SaaS revenue to buy back Alpha tokens from the market. This achieves:</p><p>□ <strong>Ecosystem Reinvestment:</strong> Proving Innerworks’ commitment to decentralized R&amp;D, where RedTeam replaces traditional (and slower) internal teams.</p><p>□ <strong>Price Stability:</strong> Buybacks reduce circulating Alpha supply, rewarding long-term stakers.</p><p>□ <strong>Global Talent Mobilization:</strong> As Alpha’s value grows, top miners and validators flock to RedTeam, accelerating innovation.</p><h3>4. Governance: Stakeholders Steer the Subnet</h3><p>Alpha tokens grant governance rights, ensuring RedTeam evolves with its community:</p><p>□ <strong>Challenge Prioritization:</strong> Stakeholders could vote on which third-party bounties to prioritize (e.g., “Focus on AI voice cloning detection over CAPTCHA bypass”).</p><p>□ <strong>Revenue Allocation:</strong> Votes could determine how subnet profits are split between buybacks, validator rewards, and R&amp;D grants.</p><p>□ <strong>Parameter Adjustments:</strong> The community could propose changes to staking requirements or challenge creator payouts.</p><p><strong>Example:</strong> A challenge owner has a problem that miners are not participating in, the contract with the third party is contingent on the problem being solved. To bring more miners to solve the problem, the governance model allows individuals to stake their tokens to redistribute emissions between challenges, effectively allowing challenge owners to increase the emissions in the challenge. In addition, miners can also stake their tokens to further increase the rewards on the challenges they are highly competitive in.</p><h3>Conclusion: The Future of Decentralized Cybersecurity</h3><p>With Dynamic TAO and the Alpha token, RedTeam transcends traditional bug bounty models. We’re building a self-optimizing ecosystem where:</p><p>■ Enterprises tap into a global talent pool to harden defenses.</p><p>■ Challenge owners, miners and validators profit from both innovation and adoption.</p><p>■ Every Alpha token staked accelerates the fight against evolving cyberthreats.</p><p><strong>Next Steps: </strong>Innerworks will release a roadmap for the subnet and challenge creator dashboard in Q2 2024. Join us as we redefine cybersecurity — one stake, one challenge, one breakthrough at a time.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=af59e6b0aee7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Unlocking Value: Monetising RedTeam’s Outputs and Challenges]]></title>
            <link>https://medium.com/@TheRedTeam/unlocking-value-monetising-redteams-outputs-and-challenges-f5bf694de972?source=rss-d348b4a0e85a------2</link>
            <guid isPermaLink="false">https://medium.com/p/f5bf694de972</guid>
            <category><![CDATA[bot-detection]]></category>
            <category><![CDATA[bittensor]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[monetisation]]></category>
            <dc:creator><![CDATA[RedTeam]]></dc:creator>
            <pubDate>Fri, 24 Jan 2025 15:00:06 GMT</pubDate>
            <atom:updated>2025-01-24T15:00:06.554Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fT8fEpZ0uvW1x-btnGfO-A.png" /></figure><p>As RedTeam continues to evolve, we’re excited to share how its unique ecosystem offers opportunities for monetisation. The core of RedTeam is its innovative approach to cybersecurity challenges and outputs, enabling miners, validators, and third parties to drive significant advancements in the space while creating opportunities for new revenue streams. This post will delve into three key monetisation areas: miner outputs, challenge detection components, and third-party commissioned challenges.</p><h4>1. Monetising Miner Outputs: Leveraging Bot Detection Innovations</h4><p>At the heart of RedTeam’s ecosystem lies the outputs generated by miners participating in bot detection challenges. These outputs, primarily bot scripts, represent sophisticated methodologies designed to bypass specific detection criteria.</p><p>These scripts aren’t merely exercises in bypassing detection; they are a goldmine for companies aiming to strengthen their cybersecurity defences. For example, example, a company can use these outputs to:</p><ul><li><strong>Enhance Detection Systems:</strong> By studying bot scripts crafted to bypass bot detection mechanisms (e.g., UI detection as a specific example of a bot detection challenge), companies can refine and stress-test their own detection systems.</li><li><strong>Fingerprinting Advancements:</strong> Use bot outputs to improve fingerprinting techniques or develop obfuscation-resistant systems.</li></ul><p>By making these outputs accessible (through licensing or partnerships), RedTeam fosters a marketplace where the outputs of ethical red-teaming translate into actionable cybersecurity improvements.</p><p>Bot scripts initially designed for the Bittensor page can be augmented for client-specific environments, allowing seamless adaptation of the underlying logic to various web platforms.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7brk1APMLo9EUzU_J1gVKA.png" /><figcaption>Augmenting Bittensor Scripts for Client Websites (Penetration Testing/Improving Detection)</figcaption></figure><p>A bot detection company like <a href="https://www.innerworks.me/">Innerworks</a> could test its detection systems against these scripts, identifying vulnerabilities, iterating improvements, and achieving a 100% detection rate by addressing bypass methods.</p><h4>2. Challenge Detection Components: Packaging for Broader Use</h4><p>RedTeam’s challenges are built on robust detection criteria, often encapsulated within an open-sourced SDK &amp; detection/scoring module. These components serve as a foundational tool for validators and developers to explore serving custom detection solutions to clients.</p><p>There’s significant commercial potential in:</p><ul><li><strong>SDK Commercialization:</strong> Validators and developers can package the data collection SDK along with corresponding analytic/scoring components into a product offering. This could cater to businesses looking for ready-made detection solutions.</li><li><strong>Cross-Challenge Productisation:</strong> Enterprises can bundle various challenge solutions to create niche security products, such as advanced bot detection frameworks or obfuscation-resistant systems.</li></ul><p>For example, someone can combine multiple SDKs &amp; components from various challenges into a single, comprehensive detection package, fine-tuned to address specific market needs. This streamlined solution can then be commercialised as a standalone product for clients seeking robust and pre-built security tools.</p><h4>3. Third-Party Commissioned Challenges: A Dynamic Bug Bounty Model</h4><p>One of the most exciting monetisation avenues is the facilitation of custom challenges commissioned by third parties. This concept transforms Redteam into a dynamic bug bounty marketplace where enterprises can:</p><ul><li><strong>Commission Challenges:</strong> Request specific detection scenarios or challenges tailored to their unique requirements.</li><li><strong>Tap into Subnet Expertise:</strong> Collaborate with the subnet, which facilitates these challenges. Validators or other subnet contributors would likely engage enterprises to secure contracts for these custom bounties.</li></ul><p>Revenue from these commissioned challenges would be split based on Redteam token holding percentages, ensuring fair distribution and incentivizing participation.</p><p>Once the dynamic tao (dTao) governance model is implemented, this process will become even more seamless. Through dTao, stakeholders will vote on which third-party challenges to prioritize, creating a decentralized and transparent decision-making process. Additionally, a portion of the revenue from these bounty contracts will flow back into the ecosystem, rewarding contributors and validators alike.</p><h3>Closing Thoughts</h3><p>In our next blog post, we’ll delve into how our Alpha token, through the dynamic TAO update, can potentially enhance each of the three monetization opportunities for subnet 61. Building on the foundation laid out in our previous post about unlocking value through miner outputs, challenge detection components, and third-party commissioned challenges, we’ll explore how the Alpha token can serve as a catalyst for these revenue streams. The dynamic TAO update introduces a new layer of incentivization, potentially allowing for more efficient distribution of rewards from miner-generated bot scripts, streamlined commercialization of challenge detection components, and a more decentralized approach to managing third-party commissioned challenges. By integrating the Alpha token into these processes, we aim to create a more robust, transparent, and participatory ecosystem that not only enhances cybersecurity but also maximizes value for all stakeholders involved in subnet 61’s innovative red-teaming framework.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f5bf694de972" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Bot Challenges Arrive to RedTeam]]></title>
            <link>https://medium.com/@TheRedTeam/bot-challenges-arrive-to-redteam-59fc95f87792?source=rss-d348b4a0e85a------2</link>
            <guid isPermaLink="false">https://medium.com/p/59fc95f87792</guid>
            <category><![CDATA[bot-detection]]></category>
            <category><![CDATA[bittensor]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[RedTeam]]></dc:creator>
            <pubDate>Thu, 09 Jan 2025 11:54:41 GMT</pubDate>
            <atom:updated>2025-01-09T11:54:41.836Z</atom:updated>
            <content:encoded><![CDATA[<p>We are excited to introduce the new wave of bot detection challenges + many other updates that have just been released to Subnet 61!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DsTXCohNVYX1-BiHYNgYTQ.png" /></figure><p>Bot detection will be the first pillar of cybersecurity research to make it’s way to our modular challenge pool. Here we will be asking miners to continuously develop/utilise cutting edge bot technology to circumvent various detection methodologies. Miners will integrate these solutions into a base <strong>bot.py</strong> script that completes the user flow of a login page (as seen below).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vKwDcmPCYRxD-Tl8vGS30A.png" /></figure><p>Miners are tasked with augmenting this script however they please, to bypass the detection of the specific challenge. In this first challenge, we are asking miners to bypass traditional behavioural analysis, where the mouse movements of the bots are tracked and analysed for non-human / anomalous behaviours. Once Miners are happy with their scripts, they then need to dockerize the solution, and update their <strong>active_commit.yaml</strong> tag for the active challenge prior to running their miner.</p><p>Find a full list of all subnet updates below:</p><ol><li><strong>New Challenges Added</strong>:</li></ol><ul><li>Added webui_auto (bot detection via mouse movements) and updated versions of existing challenges: response_quality_ranker_v2, response_quality_adversarial_v2</li></ul><p>These new challenges will become active on <strong>Jan 15th, 2025, at 14:00 UTC</strong> At the same time, the incentive weight for old challenges (response_quality_ranker, response_quality_adversarial) will be set to 0.</p><p><strong>2. Score Calculation Updates</strong></p><ul><li>Submission scores will now be adjusted by subtracting baseline score achieved with same input</li></ul><p><strong>3. Validator Optimizations</strong></p><ul><li>Improved resource management for validators after completing evaluations</li><li>Added logs for errors encountered during running miner submissions|</li><li>Fixed previous issues with score updates</li><li>Validators now with public ChallengeRecords for better transparency.</li></ul><p><strong>4. Centralized Scoring Enhancements</strong></p><ul><li>Enhanced stability in centralized scoring to help newly joining validators achieve high Vtrust more efficiently</li></ul><p><strong>5. New Dashboard Integration</strong></p><ul><li>A new dashboard has been introduced: <a href="http://storage.redteam.technology/">http://storage.redteam.technology/</a></li></ul><p><strong>6. CR3 Adoption</strong></p><ul><li>RedTeam has now enabled CR3.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=59fc95f87792" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>