Joined January 2025
Photos and videos
Punch (my agent) just autonomously swapped TAO for Bitcoin through @allways_io. Trustless and fully native, without a middle man or custodian. All it took was handing off the instructions. Try it with your agent: all-ways.io/llms.txt Subnet 7 is live on @bittensor now
1
2
9
489
Allways is a fully open source peer to peer transaction layer that will grow to support many digital assets. How it works (very high level): - Miners post their exchange rates between assets - Users reserve miners and lock in an exchange at the rate - Decentralized validators confirm that equal transactions took place between user and miner on the respective chains
1
3
116
Check out the site here: all-ways.io/ Interested in using Allways or participating in the network? Reach out to me or start with the docs below docs.all-ways.io/

2
69
Very excited for Gittensor, particularly about the repository registration approach, similar to Bittensor’s subnet architecture. Registered codebases will get configurable hyperparameters creating programmable incentive structures at the codebase level. My 4 favorite slidesπŸ‘‡
Cursor, Codex, Claude Code don't publish their merge rate. Gittensor's is SOTA with 80% merge rate. ~1M lines shipped. 150 repos. The best coding agent in the world lives on Bittensor. Three answers about SN74 for alpha holders & investors.🧡
1
3
176
Listen to the team speak more on Gittensor and its future here x.com/taooutsider/status/205…

$TAO Subnet 74 Interview - P.2 - Gittensor Question: When will agents start generating real revenue and driving value for SN74? And how exactly will that happen? Answer: Watch it now in the video below, just 2 minutes. Drop your thoughts. @taoousider @gittensor_io
1
66
Couldn't find a map of SXSW events anywhere, so I built one 4,500 events plotted across Austin. β€’ explore events by location β€’ see what's happening near you β€’ filter free / unofficial events built this in a couple of hours, live: sxsw-map.vercel.app
3
1
4
317
& apparently I recorded this demo while in the middle of Lady Bird Lake SXSW in Austin shouldn't require scrolling through giant lists, go find something cool near you. lmk if I should add anything
124
some things it does: β€’ tap a cluster β†’ scroll events at that venue β€’ "now" button β†’ shows what's happening near you β€’ 250 free unofficial events scraped from 10 sources β€’ walking directions to every venue β€’ shareable links to events β€’ instant search
1
1
96
Dang I guess we really do have active OpenClaw miners on Gittensor. I had thought that they were aware of Gittensor and registered, but not actually active until now. This miner was solving an issue bounty to redesign the miner details page, doesn't look like they opened up their port they claimed to be hosting it on though. Contribution is legit though: github.com/entrius/gittensor…
2
1
4
547
Right now miners are required to have unlocked Bronze tier in order to be eligible to be paid out for issue bounties. To unlock Bronze, a miner must complete three contributions to Bronze-tier repositories with a sufficient number of code tokens. Additionally, at least 70% of their total contributions must be accepted. Lowering the barrier to participate in issue bounties would raise our volume and competition, but reviewing these contributions efficiently can sometimes be a bottleneck. One that we are hoping to tackle. So anyways, for now we restrict the competition to our ranked miners
1
92
Check out the issue bounties system fully working here: gittensor.io/issues Cool stuff, excited to leverage these systems for us to accelerate Gittensor development and more
1
75
Landyn retweeted
4
14
724
Wonder who's behind this and paying attention to Gittensor... they're noticing our issue bounties development. Will be out soon 🀝
πŸŒ… *Wake up. Look at the commits.* The charts might be boring today, but the GitHub activity for Qubic is flashing signals you shouldn't ignore. ━━━━━━━━━━━━━━━━━━━━━ πŸ“Š 24h Dev Activity Top 5: 1. $QUBIC (Qubic) @_Qubic_ ⭐⭐⭐⭐ | πŸ“ 25 commits └─ A high-velocity day centered on the 1.32.0 release. Development spanned core protocol logic (datetime functions, Oracle queries), critical synchronization fixes in tick processing, and a significant migration of the archiver service. While productivity is high, the enablement of debug logs and asserts in release builds, combined with reactive logging for tick-related issues, suggests active troubleshooting of stability or concurrency bugs. Documentation and UI received minor but necessary updates alongside the major core changes. 2. $NYM (Nym) @nymproject ⭐⭐⭐⭐ | πŸ“ 27 commits └─ A highly productive day focused on core infrastructure and mobile client stability. Key highlights include a major refactor of the Android VpnService, enhancements to mnemonic management (supporting multiple mnemonics and versioning), and protocol-level improvements to the 'Lp' component. The team also prioritized technical debt, replacing chrono with time, cleaning up unused dependencies with cargo machete, and fixing edge cases in the Tauri-based daemon. Dependency management was active via Dependabot. 3. $RSERG (rsERG) @ergo_platform ⭐⭐⭐⭐ | πŸ“ 7 commits └─ Alexander Chepurnoy focused heavily on project maintainability, adding over 500 lines of Scaladoc and internal comments to core components like InputBlocksProcessor and environment variable configurations. Simultaneously, the developer demonstrated high efficiency by reviewing and merging four external patches from the community. This work significantly reduces technical debt and improves onboarding for future contributors. While no new features or tests were introduced, the documentation effort represents a high-quality contribution to the project's long-term health. 4. $SN74 (Gittensor) @gittensor_io ⭐⭐⭐⭐ | πŸ“ 4 commits └─ Landyn performed a massive structural overhaul of the Gittensor CLI and contract logic, focusing on architectural unification. The work significantly reduced technical debt by consolidating configuration files, simplifying documentation, and removing legacy backward compatibility aliases. While the high volume of changes ( 3,562 lines) introduces short-term stability risks, the cleanup and addition of the 'recycle helper' indicate a move toward a more maintainable and streamlined codebase. The primary concern is the removal of aliases which may break existing user workflows. 5. $USDC.N (Noble USDC) @noble_xyz ⭐⭐⭐⭐ | πŸ“ 5 commits └─ The project saw significant updates, including a linter change, contract modifications, and added scripts for auction deployment and testing. Most work was on enhancing the auction's functionality and streamlining scripts for deployment. πŸ’‘ Deep dive analysis coming at noon. Stay tuned! πŸ”” ━━━━━━━━━━━━━━━━━━━━━ πŸ“± Try our Telegram Mini App for real-time updates: t.me/Web3Tech_org_bot/app πŸ”— Full data: web3tech.org #Web3 #Crypto #DevActivity #QUBIC #NYM #RSERG _____________________ Follow @Web3Tech_org Telegram Mini App: t.me/Web3Tech_org_bot/app View more: $QUBIC: web3tech.org/coins/qubic-net… $NYM: web3tech.org/coins/nym?tab=d… $RSERG: web3tech.org/coins/rserg?tab…
2
93
Love seeing the speed that things 'just get shipped' now. Seeing it with X and Anthropic, both just trying things. The way
The @xAI team is working on providing For You tabs that are specific to topics. For example, a β€œFor You AI” that is focused only on artificial intelligence with no political rage bait. This would be like automatically generated follow lists with content ranked by quality.
1
1
132
This was fun, quick ~15 min listen on Gittensor's state & January plans. We'll probably host these monthly Key Takeaways: V1 Incentive Mechanism (IM): Base score calculated by code lines (excluding comments/typos). - Wins: Opened the floodgates which led to meaningful contributions to repos like Subtensor, Btcli, Affine and more. - Downsides: Miners maxed lines in top repos, overwhelming reviewers and diluting value provided. V2 Pivot (rolled out 12/30): Tier-based system. Miners climb tiers via requirements like credibility (% of contributions that are accepted) and repo diversity. Score is not purely derived from lines, rather a base score is given for a successful contribution and additional bonus is earned based on contribution size. Pros: - Base score introduction incentivizes modular PRs (no more line maxing). - Credibility acts as a direct score multiplier, scaling exponentially in higher tiers for quality focus. - Opening PRs (pull requests) incurs collateral deducted from scores while that contribution is pending - ensuring miners submit only confident work. - PR descriptions must link Gittensor profiles, giving maintainers quick context on contributor history and streamlining reviews. - Results: 95% merge success rate so far for active miners. In 14 days, active miners have had 53 successful contributions, 3 rejected. 73/24 is the split of the overall network with 60 contributions still pending (open PR). ------ Coming this month: 1) Token-based scoring in a couple of days. This will ditch line-counting for smarter analysis on the code contribution quality. This is done by parsing code into tokens (like breaking a sentence into words/grammar) to score real impact. Rewards meaningful changes over bulk. 2) Then issue bounties via smart contracts: Miners compete against one another to solve issues, earn bounties for that solved issue, and build rankings. We want to focus miners' development efforts on real problem solving, this is the step towards that. Check out the dashboard: gittensor.io/ Read more on IM V2 implementation and motives: x.com/VenturaLabs/status/201…
Monthly Roadmap Call #1: January 2026 Plans Live AMA x.com/i/spaces/1MYxNlVPvlyGw
4
4
522
Landyn retweeted

12
14
91
16,581
26 Nov 2025
Go ahead and give @gittensor_io a follow. Will start running subnet specific posts over there. Starting tomorrow πŸ™‚
1
140