Stewardship & administration

Bittrees TLD

A shared administration desk with explicit responsibility.

Open websitetld.bittrees.org
Access: Authorized wallet
For
Authorized Bittrees controllers, signers and administrators
Access details
Current Safe membership or assigned TLD access
Purpose
Infrastructure
On this page
Public entrance to Bittrees TLD
Public page preview · 17 October 2026 · Sign-in entrance; private workspace not shown.

Purpose

Bittrees TLD provides an administration workspace around the Bittrees domain identity and its organizational Safes. The public entrance offers Ethereum wallet sign-in, with separate controller and contract-wallet options. Workspace details remain hidden until access is authorized. Its purpose is to make operational responsibility visible and structured for authorized people, rather than offer a general-purpose domain marketplace.

The product

The workspace is organized around Safes, controller policies, shared workspace information, roles, members, permissions and activity. Its documentation describes balances, owners, signing thresholds, pending transactions and transaction history, alongside proposals and review flows. These are tools for carrying out and inspecting administration, with the connected wallet remaining responsible for signing actions.

Community and accountability

Access requires current Safe membership or assigned TLD administration, with a separate route for the root controller. Membership and permissions are checked by the service; connecting a wallet alone does not open the workspace. A website role does not make someone a Safe owner or remove a Safe’s signature threshold. The community benefit is a clearer chain of responsibility around who can propose, approve and activate changes.

Integration and scope

TLD connects to Ethereum and Safe, and its documented controller policies can govern explicitly enrolled operations across Bittrees applications. Those integrations are scoped and activated through their own approval process; the existence of the workspace does not mean every application function is centrally controlled. Wallet sign-in proves identity, while role changes and Safe actions require the appropriate subsequent approvals.

A good place to start

Connect an authorized wallet and review the selected Safe or policy scope before proposing an administrative change.

Browse all 17 sites