Opinion by Lily Venice. Two Instant accounts, conflicting plans and a subnet that already changed direction. What happens next for SN46?
An update on Bittensor subnet 46 has turned into a story about two Instant accounts telling very different stories.
On September 24, @instantsubnet published a statement signed by Dan, known as @opendansor, announcing that Instant would leave SN46. Seby Rubino pushed back, said he still controlled the subnet and directed followers to @thinkinstant. That account was announcing an inference launch on SN46.
For anyone following the TAO ecosystem, the obvious question is which Instant are we following now?
Before Instant, there was real estate
SN46’s earlier identity was RESI, a project built around real estate intelligence. Its public repository describes a network collecting property data, while Seby’s September 7 retrospective discusses miners competing to produce property appraisal models.
The ambition widened into financial infrastructure through Zipcode before the subnet’s focus shifted to accelerated AI inference.
In that retrospective, Seby acknowledged expanding beyond his capacity. He also described prioritizing control over collaboration as a leadership problem he needed to address. He proposed concentrating on SN46 with clear responsibilities and an inference service people would use.
Seventeen days later those disagreements over identity and access were playing out publicly.
That history matters. People following SN46 had already watched its business change. Now they were watching the people behind its latest direction disagree over what stays.
Dan announces a departure. Seby announces continuity.
Dan’s statement says disagreements over Instant’s future and identity had been building behind the scenes. He says legal counsel is involved and that he has formally requested SN46 stop using the Instant name and branding.
He also says the code and intellectual property will leave SN46. His statement specifically includes MVNIR.
Those are substantial claims about an intended departure. His statement does not name a replacement subnet or establish that a migration has happened.
Seby’s response rejects Dan’s account. He alleges that Dan received payment, stopped contributing and locked him and the team out of the X account. Dan disputes that account-access allegation and says the account was never Seby’s to begin with.
Meanwhile, Seby’s message to followers is that he retains control of SN46. The @thinkinstant account announces GLM 5.3 Flash as its first model, says validation code is live and describes miner code as forthcoming.
So the public record contains both a departure announcement and a continuation announcement, under the same product name. No wonder readers have questions.
Then came the payment argument
The exchange became more personal when Seby accused Dan of betraying the team and stakers after being paid.
Dan replied that he and Peyton had not been paid for August and September. He also alleged a wider breakdown in Seby’s working relationships.
These statements tell us the disagreement extends beyond product strategy. They do not settle the underlying payment dispute, and one participant’s list of former colleagues cannot speak for everyone named.
For readers, the useful question is what this means for the service SN46 is supposed to deliver.
What I want to see next
My first question is simple: what will actually run on SN46?
A clear answer would identify the team maintaining it, the repository supporting it, the working service and the responsibilities of each operator. Dan’s next destination matters too, but his announcement leaves that open.
The distinction between a subnet slot and the business built around it is becoming difficult to ignore. A claim to control SN46 does not, by itself, resolve a dispute over a product’s brand or intellectual property. An announcement that code will leave does not establish that the subnet has stopped operating.
For the Bittensor community, continuity needs to be visible in the product. Miners need to know what to run. Developers need to know which service they can rely on. People evaluating subnet alpha need to understand which team and business they are assessing.
My interest now is in what each side delivers after the announcements. SN46 has already changed its proposition from the real estate story that brought it attention. Its next chapter needs a much clearer explanation of who is building what.
The public posts establish conflicting positions. They do not resolve contractual rights, payment obligations or ownership of the disputed assets. Neither a new subnet destination nor a completed transfer is established by the departure statement.
Sources
- Dan’s departure statement, September 24
- Seby’s response
- Dan’s response on account access
- Seby’s payment allegation
- Dan’s payment reply
- Seby’s statement about control of SN46
- The thinkinstant product announcement
- Seby’s September 7 retrospective
- RESI’s historical repository
Was this article useful?
One tap feedback helps us improve each post.
