Author: VandyILL
Status: Draft for Community Discussion
Scope: X (@RadixDLT), Telegram (Radix Official), Reddit (r/Radix), Bluesky (new — bsky.radixdlt.com)
Proposed Term: Upon approval through December 31, 2026
Why This Proposal Exists
As the Radix Foundation prepares to sunset and governance transitions to DAO-led community structures, the project’s official social accounts need a new custodian. These accounts — X, Telegram, Reddit — currently sit under foundation control. Without a defined handover plan, they go dormant.
This proposal offers a time-bound stewardship model: I take custody of these accounts, stand up a content and moderation framework, and put the community in control of whether I keep doing it. If the community decides I’m not the right person, the proposal includes clear mechanisms to replace me. If nobody steps up, the accounts don’t disappear — they enter a minimal custodianship mode until someone does.
This isn’t a request for permanent ownership. It’s a proposal to keep the lights on, turn them up, and hand the community the dimmer switch.
Scope of Accounts
Transferred from Foundation
Three accounts transfer via direct credential handover from the Radix Foundation:
-
X (formerly Twitter) — @RadixDLT
-
Telegram — Radix Official community channel
-
Reddit — r/Radix
Newly Created
- Bluesky — Official Radix account at
bsky.radixdlt.com, created and hosted on the quack.space PDS (Personal Data Server) on the AT Protocol network. This account does not currently exist and will be established as part of this mandate.
Hosting the official Bluesky presence on Radix-ecosystem infrastructure is an intentional demonstration of the principle at the heart of this proposal: the official Radix social presence should run on what the Radix community builds.
Sub-System Accounts
Credential transfers are messy. Admin structures may result in incidental custodianship of sub-system accounts — developer channels, ambassador channels, regional Telegram groups, or other accounts tied to the same credential chain.
Any sub-system accounts that transfer incidentally with the primary credentials will be:
-
Catalogued and published to the Radix Accountability Council (RAC) within 30 days of transfer.
-
Held in custodianship-only mode — no editorial changes, no policy changes.
-
Open to re-delegation proposals from the community. Any community member may submit a proposal to the RAC to take custodianship of a sub-system account.
I will not make unilateral editorial or structural decisions about accounts outside my core four-platform mandate.
Custodianship vs. Stewardship
This proposal draws a hard distinction between two roles:
Custodianship is holding the credentials securely. It is a responsibility, not a privilege. It carries personal liability. It does not end until credentials are physically transferred to a successor.
Stewardship is the active work: setting editorial direction, defining moderation policy, integrating tools, producing and curating content, and building the content pipeline. It is the value-add. It ends when the community says it ends.
A recall vote ends stewardship. It does not end custodianship. Custodianship ends only when a successor receives the credentials.
This distinction matters because it sets honest expectations about what happens after a recall — addressed in the Recall & Succession section below.
Mandate & Term
Duration
This mandate runs from the date of credential transfer through December 31, 2026.
Retention
At the end of the term, the RAC conducts a retention vote. If retained, a new term begins under whatever conditions the community sets at that time. Retention is not automatic — it requires an affirmative vote.
Recall
At any point during the term, the community may initiate a recall vote via the Radix Consultation dApp (on-chain, free, accessible to all XRD holders). A successful recall immediately ends stewardship.
What Happens After Recall
If the community recalls me, the following changes take effect immediately:
-
X: Content production stops. No new posts, threads, or engagement.
-
Reddit: Editorial content production stops. No new posts under the official account.
-
Telegram & Reddit: Moderation continues, but in restrictive mode — I moderate only to the extent necessary to protect my personal liability as credential holder. This means removing illegal content, credible threats, doxxing, and scam/phishing links. Community tone policing, off-topic enforcement, and nuanced moderation judgments stop.
-
Tool integrations (bots, agentic pipelines, Radix-native tools): Shut down or paused.
This is not a threat or leverage. It is an honest accounting of what an unpaid, recalled custodian will and won’t do. I’m not going to actively manage community spaces after the community votes to remove me from that role. But I’m also not going to abandon credential security or leave the community exposed to illegal content.
This restrictive mode persists until:
-
A RAC member takes control of the credentials, or
-
A new steward is appointed and credentials are transferred.
The community should factor this transition cost into any recall decision. Having a successor identified before initiating recall is strongly recommended.
Credential Security & DM Policy
Phased Access Model
-
Phase 1 (Immediate): Single-custodian credential transfer. I hold all passwords, 2FA, and recovery keys. This is necessary because the foundation handover has a timeline and cannot wait for a multi-sig infrastructure to be designed.
-
Phase 2 (Within 60 days): Onboard a small group of trusted backup credential holders — selected in consultation with the RAC — with clearly defined access protocols.
-
Phase 3 (By mid-year review): Full multi-sig or community-approved access list, if the infrastructure and trust model supports it.
DM Wipe Policy
All DMs in transferred accounts will be wiped upon credential transfer to me. This is non-negotiable. Foundation-era private messages may contain sensitive information that I should not inherit and cannot be responsible for.
The same DM wipe will occur at any future custodianship transfer. This should be a standing policy: every custodianship transfer includes a full DM wipe. No custodian should inherit another custodian’s private conversations.
Governance: Two Separate Policies
This proposal governs four platforms that serve two different functions. Telegram and Reddit are participation spaces where the community talks. X and Reddit are publishing platforms where editorial content goes out under the Radix name. Reddit serves both functions.
Because of this, two separate policy documents govern the accounts:
1. Community Moderation Policy
Applies to: Telegram and Reddit (community-generated content)
This policy governs what community members can and cannot post in Radix-managed spaces.
Governance:
-
Moderation policies are subject to community vote via the Radix Consultation dApp.
-
I retain a liability veto — if a community-approved policy creates personal legal exposure for me as credential holder, I may override it. This veto is narrow: it applies only to liability, not to editorial or taste preferences. If exercised, I will publicly explain my rationale.
-
I am not retaining a legal team for this role. In ambiguous situations, moderation may lean conservative. This is an honest tradeoff of an unpaid stewardship model.
Moderators:
-
All existing moderators are assumed to retain their roles unless impeached by the community or removed by me.
-
New moderators are selected by me.
-
Community impeachment: Any moderator may be impeached via the Radix Consultation dApp. This is intended to be a lower-friction process than a full steward recall — the stakes are lower and the mechanism should reflect that.
-
Future microproposal: Token-weighted moderator votes via Flock Commander are proposed as a future governance upgrade, to be submitted as a separate microproposal for community consideration.
-
Removal by steward: I may remove a moderator at my discretion. If I do, I must provide my rationale to the removed moderator directly. The moderator then has the right to make that rationale public. This ensures I cannot quietly purge moderators without reputational accountability.
2. Editorial Policy
Applies to: X and Reddit (content published under the official accounts)
This policy governs what I publish — or approve for publication — under the official Radix account name.
Governance:
-
Editorial decisions are at my discretion as steward. This is not a community vote matter — it is what the community is evaluating me on at retention time.
-
Editorial direction is informed by the agentic SEO strategy and content pipeline described below.
The Price Talk Question
The legacy “no price talk” rule served the foundation era. It does not serve a community-governed project that needs to have adult conversations about markets, competition, and opportunity sizing.
This proposal replaces “no price talk” with a nuanced framework:
What’s Allowed
-
Price post-mortems: Discussing what happened after a price movement and why. “XRD dropped 15% after the broader market correction — here’s what on-chain data shows about the sell pressure.” This is analysis, not speculation.
-
Market assessment and opportunity sizing: Analyzing competitor market caps, DeFi TVL comparisons, total addressable market for specific use cases, and what growth in those metrics would mean for the Radix ecosystem. “If Radix captured 5% of the cross-chain DeFi market, here’s what that looks like in TVL terms.”
-
Strategic market context: Discussing how macro conditions, competitor launches, or industry trends affect Radix’s competitive position.
What’s Not Allowed
-
Price forecasting: No “$XRD to $X by [date]” predictions. No technical analysis price targets. No “this is going to pump.”
-
Calls to action based on price: No “buy the dip,” “last chance under $X,” “don’t miss this entry point,” or any language that frames price movement as a reason to take trading action.
Scope
This framework applies to the Community Moderation Policy (Telegram and Reddit user-generated content) and the Editorial Policy (X and Reddit published content), though editorial content will naturally operate with more analytical depth and nuance.
Content Strategy: Agentic SEO & Radix-Native Tools
The Thesis
The internet is bifurcating. Content is increasingly consumed not just by humans scrolling feeds, but by AI agents scraping platforms for knowledge. Reddit, X, and increasingly Bluesky are primary sources for LLM training data and agent retrieval pipelines. If Radix isn’t present — clearly, accurately, and frequently — in those information streams, it doesn’t exist to the next generation of discovery.
Agentic SEO means optimizing content for both human readers and AI agents: structured claims, clear technical comparisons, factual ecosystem data, and accessible explanations of what makes Radix different. This isn’t keyword stuffing — it’s making Radix legible to machines as well as people.
The Practice
The content pipeline will operate on two tracks:
AI-Assisted Content Production: AI tools — including but not limited to the Radix Intelligence Engine, Flock Commander, and other community-built agents — will generate draft content, research briefs, competitive analyses, and structured data posts. These will be reviewed and published with human editorial oversight. The pipeline will evolve over time as tools mature and community contributors scale.
Human-Written Content: Community members, ambassadors, developers, and ecosystem projects will contribute content through a submissions and approval process. Human expertise and community voice remain central — AI augments the pipeline, it doesn’t replace the community.
Agents as audience and agents as infrastructure are both first-class priorities. We’re not just writing for agents — we’re using agents to write, optimize, distribute, and measure.
Dogfooding Radix
This is the core differentiator of this proposal. The official Radix social presence will not just promote Radix-native tools — it will use them.
-
Community coordination bots built on Radix.
-
Raid and engagement tools from the ecosystem.
-
Intelligence and research from the Radix Intelligence Engine.
-
The official Bluesky account hosted on the quack.space PDS.
-
Flock Commander for community intel gathering and moderation governance.
If we’re telling the world to build on Radix, the official accounts should be built on Radix. Every tool integration is a live case study. Every bot interaction is a proof of concept. The accounts become a flywheel: they create demand for Radix-native tools, which improves those tools, which makes the accounts more effective, which demonstrates the ecosystem’s capability to new builders and users.
Branding
Editorial discretion on account branding (names, bios, profile images, pinned content) rests with the steward. However, the intent is to remain aligned with universal Radix project branding as managed by the RAC for flagship properties (RadixDLT.com, Meta accounts, Discord, etc.).
Changes to visual identity or messaging will be made in service of the content strategy, not for personal expression. If branding changes are significant enough to be controversial, I’ll flag them to the community proactively.
Platform Expansion
This proposal covers four platforms: X, Telegram, Reddit, and Bluesky.
Any community member may submit a separate proposal to create and manage an official Radix presence on other platforms (Farcaster, YouTube, TikTok, LinkedIn, etc.). Those proposals are independent of this mandate and do not require my approval.
Compensation
I am proposing this as an unpaid stewardship for the initial term. There is no stipend, no salary, and no automatic funding attached to this role.
If specific features, services, or deliverables require funding — tool integrations, paid promotional campaigns, design work, infrastructure costs — I may submit funding requests to the RAC. These requests will be evaluated on their own merits. The burden of justification is mine.
If, at retention time, the scope of the role warrants compensation, that is a conversation for the community to have and for me to make the case for. It is not an entitlement of this proposal.
Accountability & Reporting
Success Metrics
For this initial term, evaluation is qualitative. The community judges whether the accounts are more alive, more useful, and more representative of the Radix ecosystem than they were before. There is no pretense that meaningful KPIs can be set before we know what normal operations look like under community governance.
In future terms — whether under my stewardship or a successor’s — the community and RAC should develop quantitative KPIs informed by the baseline established during this period.
Reporting
The RAC may request a stewardship report up to twice per month, with a cap of 12 reports total for the remainder of the calendar year. This provides meaningful oversight without enabling audit fatigue as a soft recall mechanism.
Reports will be made available to the community unless they contain information that would compromise credential security.
Summary of Governance Mechanisms
| Mechanism | Platform | Authority |
|---|---|---|
| Retention vote | End of term | RAC |
| Recall vote | Anytime | Community via Radix Consultation dApp |
| Moderation policy changes | Telegram, Reddit | Community vote, steward liability veto |
| Moderator appointment | All platforms | Steward |
| Moderator impeachment | All platforms | Community via Consultation dApp (future: Flock Commander token-weighted vote) |
| Editorial decisions | X, Reddit, Bluesky | Steward discretion |
| Branding changes | All platforms | Steward discretion, aligned with RAC flagship branding |
| Funding requests | As needed | Steward proposes, RAC approves |
| Sub-system re-delegation | Incidental accounts | Community proposal to RAC |
| DM wipe | All transfers | Mandatory |
| Reporting | As requested | RAC, max 2x/month, max 12x/year |
What I’m Asking the Community
Approve the transfer of X, Telegram, and Reddit credentials from the Radix Foundation to me. Approve the creation of an official Radix Bluesky account hosted on quack.space. Grant me a stewardship mandate through December 31, 2026, subject to recall at any time. Trust the process — and hold me to it.
This proposal is a living document for community discussion. Feedback, amendments, and counterproposals are welcome. The goal is not to get this exactly right on the first pass — it’s to get it right enough to move forward, with governance mechanisms that let the community course-correct as we learn.