A decentralized chat app governed by the people for the people

OpenChat

Catch-all w.r.t to following for non-critical proposals.

All non-critical topics

Side-effect-less proposals to set general governance direction.

Motion

Proposal to change the core parameters of SNS governance.

Manage nervous system parameters

Proposal to upgrade the wasm of an SNS controlled canister.

Upgrade SNS controlled canister

Proposal to add a new, user-defined, nervous system function: a canister call which can then be executed by proposal.

Add nervous system function

Proposal to remove a user-defined nervous system function, which will be no longer executable by proposal.

Remove nervous system function

Proposal to execute a user-defined nervous system function, previously added by an AddNervousSystemFunction proposal. A canister call will be made when executed.

Execute nervous system function

Proposal to upgrade the WASM of a core SNS canister.

Upgrade SNS to next version

Proposal to change the metadata associated with an SNS.

Manage SNS metadata

Proposal to transfer funds from an SNS Governance controlled treasury account

Transfer SNS treasury funds

Proposal to register a dapp canister with the SNS.

Register dapp canisters

Proposal to deregister a previously-registered dapp canister from the SNS.

Deregister Dapp Canisters

Proposal to mint SNS tokens to a specified recipient.

Mint SNS tokens

Proposal to change some parameters in the ledger canister.

Manage ledger parameters

Proposal to change canister settings for some dapp canisters.

Manage dapp canister settings

Proposal to advance the target version of this SNS.

Advance SNS target version

Proposal to set the topics for custom SNS proposals.

Set topics for custom proposals

Proposal to register a new SNS extension.

Register SNS extension

Proposal to execute an operation on a registered SNS extension.

Execute SNS extension operation

Proposal to upgrade the WASM of a registered SNS extension.

Upgrade SNS extension

This will upload the given WASM to the user_index and trigger a rolling upgrade of local_user_index canisters on each subnet.

Upgrade local_user_index canisters

This will upload the given WASM to the user_index which will in turn call c2c_upgrade_user_canister_wasm on the local_user_index on each subnet. These will each trigger a rolling upgrade of user canisters on their subnet.

Upgrade user canisters

This will add a reference to an uninstalled local_user_index canister on a new subnet.

Add new local_user_index canister

This will mark the local_user_index with the given canister_id as full so that no more users will be created on this subnet.

Mark local_user_index full

During a rolling user canister upgrade this controls how many user canisters can be upgraded concurrently. Setting a value of zero stops the upgrade altogether. Setting this value too high will slow down subnets during user upgrade.

Set max concurrent user canister upgrades

The user with the given user id will be given the role of platform moderator. These users have the authority to suspend users and freeze groups.

Add a platform moderator

The user with the given user id will have the role of platform moderator rescinded.

Remove a platform moderator

The user with the given user id will be given the role of platform operator. These users have the authority to call endpoints which affect rolling canister deployments such as setting the concurrency level.

Add a platform operator

The user with the given user id will have the role of platform operator rescinded.

Remove a platform operator

This will register a new external achievement which users can complete to earn CHIT

Register an external achievement

This will remove an existing bot from OpenChat

Remove a bot

This will publish a registered bot allowing it to be found and installed in OpenChat communities, groups and directly with users

Publish a bot

This will upload the given WASM to the group_index and trigger a rolling upgrade of local_group_index canisters on each subnet.

Upgrade local_group_index canisters

This will upload the given WASM to the group_index which will in turn call c2c_upgrade_group_canister_wasm on the local_group_index on each subnet. These will each trigger a rolling upgrade of group canisters on their subnet.

Upgrade group canisters

This will add a reference to an uninstalled local_group_index canister on a new subnet.

Add new local_group_index

This will mark the local_group_index with the given canister_id as full so that no more groups will be created on this subnet.

Mark local_group_index full

During a rolling group canister upgrade this controls how many group canisters can be upgraded concurrently. Setting a value of zero stops the upgrade altogether. Setting this value too high will slow down subnets during group upgrade.

Set max concurrent group canister upgrades

This will upload the given WASM to the group_index which will in turn call c2c_upgrade_community_canister_wasm on the local_group_index on each subnet. These will each trigger a rolling upgrade of community canisters on their subnet.

Upgrade community canisters

This proposal will mark the given public community as 'verified' (blue tick) if it passes. The proposal summary should be used to provide evidence that the given community legitimately represents the given name. Additionally, if a different name is provided for this community and this name is already used by an existing public community or group which isn't itself 'verified' then this proposal will rename that community/group by adding a random suffix like _436 and the given community will take on the given name. This is to address the scenario where a public community or group has been created for a name which it doesn't legitimately represent.

Set community verification

This proposal will mark the given public group as 'verified' (blue tick) if it passes. The proposal summary should be used to provide evidence that the given group legitimately represents the given name. Additionally, if a different name is provided for this group and this name is already used by an existing public group or community which isn't itself 'verified' then this proposal will rename that group/community by adding a random suffix like _436 and the given group will take on the given name. This is to address the scenario where a public group or community has been created for a name which it doesn't legitimately represent.

Set group verification

Revoke the verified status (blue tick) of the given community. This would be used if the given community no longer legitimately represents its name. The proposal summary should be used to provide evidence.

Revoke community verification

Revoke the verified status (blue tick) of the given group. This would be used if the given group no longer legitimately represents its name. The proposal summary should be used to provide evidence.

Revoke group verification

This will upload the given WASM to the notifications_index and trigger a rolling upgrade of notifications_canisters on each subnet.

Upgrade notifications canisters

This will add a reference to an uninstalled notifications canister on a new subnet.

Add notifications canister

This will create a new proposals group with the given details and sync it with proposals from the given SNS governance canister.

Add SNS proposals group

This will remove a proposals group linked to the given SNS governance canister id.

Remove SNS proposals group

For each given user, the proposals_bot will call into the group canister corresponding to the given governance canister, to set the user's role within the group to admin.

Appoint admins in proposals group

Import the specified proposals group into the specified community.

Import proposals group into community

This will add a reference to an uninstalled storage_bucket canister.

Add new storage_bucket canister

This will mark the storage_bucket with the given canister_id as full so that no more files will be uploaded to this bucket.

Mark storage_bucket full

This will upload the given WASM to the storage_index canister and trigger a rolling upgrade of the storage_bucket canisters.

Upgrade storage_bucket canisters

The cycles_dispenser will keep the added canister topped up with cycles.

Add canister to cycles_dispenser

This will update the configuration of the cycles_dispenser canister such as max_top_up_amount and min_cycles_balance.

Update cycles_dispenser config

This will add the specified token to the Registry, enabling users to send it within OpenChat messages.

Add token to Registry

This will update the specified token's details in the Registry, updating the value of each field provided in the payload.

Update token details in the Registry

This will instruct the Registry to expand OpenChat onto a new subnet, allowing it to scale to many more users, groups and communities

Expand OpenChat onto a new subnet

This will instruct the NeuronController canister to stake a new neuron with 1 ICP.

Subsequent 'ManageNnsNeuron' and 'TransferFromTreasury' proposals can be made to update the neuron's configuration and increase its stake.

Stake NNS neuron

This will instruct the NeuronController canister to call 'manage_neuron' on the NNS governance canister to manage one of the neurons it controls.

This can be used to configure the neuron, set up following, spawn a new neuron, etc.

Manage NNS neuron

This will instruct the OpenChatInstaller canister to upgrade the specified canister.

Upgrade canister

This will commit a newly prepared batch of assets which have been uploaded to the asset canister by a principal which has been granted the "Prepare" permission.

Update OpenChat frontend assets

This will grant the specified principal the permission to perform the specified action on the frontend assets canister.

Grant permission to manage frontend assets

This will revoke the permission of the specified principal to perform the specified action on the frontend assets canister.

Revoke permission to manage frontend assets

Call trade_tokens on the CHAT/CYCLES trading pair canister at the CYCLES-TRANSFER-STATION.

Cancel an open position/order on the CHAT/CYCLES trading pair canister at the CYCLES-TRANSFER-STATION.

This will enable the OpenChat SNS Governance canister to manage NNS neurons, allowing it to perform actions such as voting on NNS proposals

Call manage_neuron on the NNS Governance canister

Transfer tokens from the SNS treasury via icrc1_transfer

Transfer nICP

Proposals to set the direction of the DAO by tokenomics & branding, such as the name and description, token name etc

DAO community settings

Proposals to upgrade and manage the SNS DAO framework.

SNS framework management

Proposals to upgrade the registered dapp canisters and dapp upgrades via built-in or custom logic and updates to frontend assets.

Dapp canister management

Proposals that are custom to what the governed dapp requires.

Application Business Logic

Proposals that represent community polls or other forms of community opinion but don't have any immediate effect in terms of code changes.

Governance

Proposals to move and manage assets that are DAO-owned, including tokens in the treasury, tokens in liquidity pools, or DAO-owned neurons.

Treasury & asset management

Proposals to execute critical operations on dapps, such as adding or removing dapps from the SNS, or executing custom logic on dapps.

Critical Dapp Operations

# Proposal to execute nervous system function:

## Nervous system function:

NervousSystemFunction {
    id: 10000,
    name: "Update OpenChat frontend assets",
    description: Some(
        "This will commit a newly prepared batch of assets which have been uploaded to the asset canister by a principal which has been granted the \"Prepare\" permission.",
    ),
    function_type: Some(
        GenericNervousSystemFunction(
            GenericNervousSystemFunction {
                target_canister_id: Some(
                    6hsbt-vqaaa-aaaaf-aaafq-cai,
                ),
                target_method_name: Some(
                    "commit_proposed_batch",
                ),
                validator_canister_id: Some(
                    6hsbt-vqaaa-aaaaf-aaafq-cai,
                ),
                validator_method_name: Some(
                    "validate_commit_proposed_batch",
                ),
                topic: Some(
                    DappCanisterManagement,
                ),
            },
        ),
    ),
}

## Payload sha256: 

c1be2007d8a98482d7f4f26f2cf028c920c8fc9f0a26dfee3178db59cba00701

## Payload:

commit proposed batch 256 with evidence a506e3b19483836701c9690f2285f2eaa7083c7907cf53b304ccfb2fa89c620c

Upgrade website to 2.0.2041

# Description

This is a tiny release whose sole purpose is to serve an `apple-app-site-association` file from `https://oc.app/.well-known/apple-app-site-association`.

This file is Apple's standard mechanism for associating a website with a native app — the iOS counterpart of the `assetlinks.json` file we already serve for Android. It is required to unblock passkey support in the native iOS app we are currently developing: without it, iOS refuses to create or use passkeys with `oc.app` as the relying party, so shipping it now unblocks that work.

It has no effect on the web app, the Android app, or existing passkeys — it simply declares which native app is allowed to use `oc.app` credentials.

## Changed

- Serve apple-app-site-association for iOS passkeys ([#9241](https://github.com/open-chat-labs/open-chat/pull/9241))