Identity and Community Ownership

Profiles and communities in Bitsocial are controlled by keypairs, not by revocable platform accounts.

That changes the relationship between ownership and service providers. You can delegate uptime, hosting, or convenience to another service without giving that service permanent custody over the identity or community itself.

Why keys matter here

A hosted platform account is ultimately rented. It exists as long as the platform continues to honor it.

A key-controlled identity is different:

• the private key is the source of authority
• hosting can be replaced
• app choice can change
• ownership does not need to move with infrastructure

What delegation should mean

Delegation should mean help with availability, not surrender of control.

For example, a public RPC or hosting service can keep a node online, but that service should not need the power to permanently seize the profile or community. Assistance is useful. Custody should remain optional.

The broader point

This makes a Bitsocial identity feel closer to a wallet-controlled asset than to a username rented from a company. The service layer can be swapped out. The owner relationship should survive that swap.