# Confidential Treasuries Source: https://docs.trezu.org/confidential-treasuries Manage assets and payroll without exposing your financial data At Trezu, we understand that some teams need to manage their crypto assets securely, but do not want to expose their financial data publicly. To help them, we have built **confidential treasuries**, a new type of treasury where all financial data **is visible only** to **team members**. Confidential Treasuries All transactions and actions on a confidential treasury are private. If you need to handle public funds or want to make your transactions public, you will need to use a public treasury instead. *** ## How do confidential treasuries work? Confidential treasuries are built on top of the same core technology as public treasuries, meaning they are multisig wallet smart contracts deployed on NEAR Protocol. Confidential Treasuries The main difference is that confidential treasuries are deployed on a **private shard** on NEAR. This allows us to use the same technology that secures public treasuries while keeping all financial data away from the public's eyes. While NEAR Protocol is a single blockchain, it is actually composed of multiple small chain instances called shards, which run in parallel. Each shard is in charge of certain accounts and smart contracts and operates in parallel, with all shards aggregating to form the NEAR blockchain. In NEAR, all shards are public by default, which means that anyone can see all the funds and transactions happening on them. However, NEAR also allows the creation of private shards, which run on the same technology as the public ones, but with the main difference of **not exposing any data to the public**. This makes private shards an ideal solution for confidential treasuries, as they provide all the security and functionality of a public shard, but with the added privacy of not exposing any financial data to the public. *** ## Public vs Confidential overview Confidential treasuries share all the core features of public treasuries, such as multi-member management and a secure proposal and voting system. The key difference is in how funds are handled. | Feature | Public Treasuries | Confidential Treasuries | | ---------------------------------------------- | ----------------------------------------- | ----------------------------------------------------------- | | Member List | 🌐 Visible to anyone | 🌐 Visible to anyone | | Member votes on proposals | 🌐 Visible to anyone | 🌐 Visible to anyone | | Treasury balances | 🌐 Visible to anyone | πŸ”’ Visible only to the team | | Proposals | 🌐 Proposals and their content are public | πŸ”’ Only the team can see the proposal's content (see below) | | View payment requests (current and historical) | 🌐 Visible to anyone | πŸ”’ Visible only to the team | | Swap requests (current and historical) | 🌐 Visible to anyone | πŸ”’ Visible only to the team | | Deposits and Payments | 🌐 Made on the public blockchain | πŸ”’ Made through a private shard | *** ## Deposits Because confidential treasuries run on a private shard, funding them and paying from them requires moving funds between the private shard and public blockchains. Trezu supports two ways to do that, depending on how your team wants to operate.
**Automatic bridging through temporary deposit addresses** Your treasury can receive public funds on a temporary account and automatically bridge them to the private. This allows you to fund your treasury from any external wallet just as you would with a public treasury. Furthermore, using a unique deposit address for each transfer makes it harder for external observers to link multiple deposits, wallets, or counterparties to the same treasury, which provides additional privacy. deposit through temporary address Temporary deposit addresses are single-use and remain valid for 72 hours. If the address expires, create a new one before sending funds.
**Deposits through confidential accounts on near.com** If your team already uses a confidential account on [near.com](https://near.com/), you can fund the treasury by transferring assets directly to the treasury account ID. We have detailed guides on how to [**fund confidential treasuries through near.com**](/guides/funding-confidential-treasuries). *** ## Proposals In a public treasury, anyone can see both the existence and the contents of proposals. In a confidential treasury, anyone can see that a proposal exists and how members voted, but only team members can see the proposal details. For example, if a team member creates a proposal to pay `10 USDC` to `alice.near`, the public can see that a proposal was created and whether it was approved or rejected, but only team members can see that it was a *payment* proposal, as well as the amount, token, and recipient. *** ## Payments Confidential treasuries can create payments in all supported assets, and the recipient can be either a confidential [near.com](https://near.com/) accounts or a public wallet addresses. Payments to [near.com](https://near.com/) confidential accounts will be executed within the private shard, so the recipient will need to log in to [near.com](https://near.com/) to access and withdraw the funds. When making payments to public wallets, Trezu will automatically bridge the funds from the private shard to the recipient's address on the selected chain. In this case, the public recipient will see the funds arriving from the near.com settlement account, as that is the account used to bridge funds from the private shard to the public one. *** ## Frequently Asked Questions No, when creating a treasury you need to choose whether you want it to be public or confidential, as this will determine how the treasury is deployed and how it handles funds. If you want some of your funds and transactions to be public and others to be private, we recommend creating two separate treasuries, one public and one confidential, and managing your funds accordingly. While NEAR Protocol is a single blockchain, it is actually composed of multiple small chain instances called shards, which run in parallel. Each shard is in charge of certain accounts and smart contracts and operates in parallel, with all shards aggregating to form the NEAR blockchain. Almost all shards on NEAR are public, which means that anyone can see all the funds and transactions happening on them. However, NEAR also allows the creation of private shards, which run on the same technology as the public ones, but with the added security of being private and encrypted. This is how confidential treasuries work: they are deployed on their own private shard, which is not accessible to anyone outside the team, thus keeping all financial data private. To deposit funds into a confidential treasury, you can either use [**near.com**](https://near.com/) and [fund the treasury's account](/guides/funding-confidential-treasuries) through a confidential account there, or let Trezu handle the bridging process for you automatically through a temporary deposit address. Yes, all payments from a confidential treasury are private, as they are executed within the private shard. This means that the details of the payment, such as the amount, recipient, and token, are only visible to team members and not to the public. Recipients of confidential payments can either [receive the funds in a near.com confidential account](/guides/confidential-payments) or receive them directly in their public wallet. For recipients who receive payments directly in their public wallet, the sender will appear as the general NEAR Intents account. Yes, all swaps from a confidential treasury are private, as they are executed within the private shard. This means that the details of the swap, such as the amount, tokens involved, and exchange rate, are only visible to team members and not to the public. Yes, you can still connect with your Ledger wallet to manage a confidential treasury. The process of connecting your wallet and signing transactions is the same as with a public treasury, as both types of treasuries are built on the same core technology. The main difference is that with a confidential treasury, all transactions and actions are executed within the private shard, so while you can use your Ledger to sign transactions, the details of those transactions will not be visible to the public. *** ## Ready to get started? [Create your treasury now](https://trezu.app/) and start managing your team's crypto assets securely and collaboratively! # Handling Governance Requests Source: https://docs.trezu.org/governance/handling-requests Manage governance requests in your treasury Once a request is created - either to change a [team member's role](/governance/members-and-roles) or to [change a voting threshold](/governance/voting-settings) - it is listed as a `Pending` request in the `Requests` section of the left sidebar. Request Navigate to the `Requests` section in the left sidebar to see all pending governance requests. You can filter and sort requests to find the one you want to review and vote on. *** ## Voting on a Request Click on a request to review its details, including the type of request, the proposed changes, and any comments added by the requester. After reviewing the request, you can cast your vote to either approve or reject it. Request Details Only team members with the **[Governance](/governance/members-and-roles#governance) role** can review request details and cast a vote to either **approve** or **reject**. *** ## Filtering Governance Requests You can filter governance requests by the following fields: `Request Type`, `Created Date`, `Recipient`, `Token`, `Requester`, `Approver`, `My Vote Status`. To filter governance requests, click on the **`Filter`** icon: Request Then simply add as many filters as needed: Request To see only governance requests, filter by `Request Type` -> `Change Policy` # Members and Roles Source: https://docs.trezu.org/governance/members-and-roles Discover how to manage your treasury's team members and their roles In Trezu, each treasury is a shared multisig account, where multiple members collectively control the treasury's assets and actions. No single member has unilateral control over the treasury, and to perform any action the team needs to reach consensus. Members You can manage your team members and their roles in the **`Members`** section in the left sidebar. *** ## Members A member in Trezu represents a wallet address that can participate in the treasury. Each member: * Connects using their own wallet (e.g. a browser wallet, mobile wallet, or hardware wallet) * Signs proposals and votes using that wallet * Acts independently from other members This is the core multisig concept: multiple wallets collectively control one treasury. No single member has unilateral control over the treasury's funds, and to perform any action the team needs to reach consensus. *** ## Roles & Permissions Roles define what actions a member’s wallet is allowed to perform within the treasury. There are three roles in a treasury: [**Requestor**](#requestor), [**Finance**](#finance), and [**Governance**](#governance). Each role has specific permissions that determine what actions members can perform within the treasury. Members can have multiple roles assigned, and will have the combined permissions granted by each of their assigned roles *** ### Requestor Allows members to create requests related to the treasury's funds (e.g. treasury transaction requests). #### Can * βœ… Create payment requests * βœ… Create staking, unstaking, and withdraw requests * βœ… Create asset exchange requests * βœ… Delete their own pending requests #### Cannot * ❌ Vote on any request *** ### Finance Responsible for voting on treasury transaction requests - those created by [Requestors](#requestor). #### Can * βœ… Vote to approve or reject requests created by Requestors #### Cannot * ❌ Create, edit or delete requests * ❌ Manage members or treasury settings *** ### Governance Responsible for configuring the treasury's settings and member configuration. Exercise caution when assigning the Governance role, as this role has extensive control over the treasury's settings. [Read More](#governance-is-the-highest-trust-role) #### Can * βœ… Create requests to add, edit, or delete members * βœ… Create requests to update the voting duration * βœ… Create requests to update the treasury's theme and logo * βœ… Set the treasury's voting threshold * βœ… Vote on any treasury configuration requests * βœ… Delete their own requests #### Cannot * ❌ Create financial requests (e.g., payments, staking) * ❌ Vote on financial requests created by Requestors *** ## Governance is the Highest-Trust Role The Governance role controls who has power in the system. Because Governance controls membership and voting rules, it should be treated as the highest-trust role in the treasury. Governance is intentionally powerful and not meant for day-to-day use. Best practice is to: * Assign Governance to highly secure wallets * Use high voting thresholds * Share Governance across multiple trusted members when possible Treasury safety comes from isolating and sharing authority, not from weakening permissions *** ## Permission Matrix The following table shows the actions each role can perform: | Action | Requestor | Finance | Governance | | --------------------------------------------------------- | --------- | ------- | ---------- | | Create Payment Requests | βœ… | ❌ | ❌ | | Create Stake Delegation Requests (Stake/Unstake/Withdraw) | βœ… | ❌ | ❌ | | Create Asset Exchange Requests | βœ… | ❌ | ❌ | | Vote on Treasury Transaction Requests | ❌ | βœ… | ❌ | | Create Add/Edit/Delete Member Requests | ❌ | ❌ | βœ… | | Create Voting Duration Update Requests | ❌ | ❌ | βœ… | | Create Theme/Logo Update Requests | ❌ | ❌ | βœ… | | Create Voting Thresholds Requests | ❌ | ❌ | βœ… | | Vote on Configuration Requests | ❌ | ❌ | βœ… | | Delete Own Pending Requests | βœ… | ❌ | βœ… | | Delete Others' Pending Requests | ❌ | ❌ | ❌ | *** ## Best Practices When assigning roles and permissions within your treasury, consider the following best practices: * **Use least privilege**: Grant only the roles needed for each member’s responsibilities * **Separate duties**: Maintain a clear separation between financial operations and treasury configuration, do not assign the Governance role to Requestors or Finance members * **Use voting thresholds intentionally**: Higher-risk actions (like configuration changes) should require more approvals * **Do regular reviews**: Periodically review assigned roles and permissions to ensure they align with your treasury's current needs * **Governance caution**: Exercise caution when assigning the Governance role, as this role has extensive control over the treasury's settings # Voting Rules Source: https://docs.trezu.org/governance/voting-settings Keep your treasury secure through voting rules When creating a treasury, you will be able to set up the `Voting Threshold` for all requests in the treasury. This voting threshold represents the minimum number of approvals required for a proposal to be approved. Creating Treasury Voting thresholds prevent any single member from acting alone. Proceed with caution when setting up voting thresholds. *** ## Updating Voting Rules Once the treasury is created, team members with the [Governance](/governance/members-and-roles#governance) role can present proposals to change the treasury's configuration, including its voting thresholds and voting period. Creating Treasury Only members with the [Governance](/governance/members-and-roles#governance) role can create proposals to update the treasury's voting settings. Governance proposals can change how decisions are made, thus having significant impact on the treasury's security and operations. Do not lower the governance threshold unless necessary. [Read More](/governance/members-and-roles#governance-is-the-highest-trust-role) *** ## Voting Settings Explained There are two main configurations that can be updated through proposals: [Voting Thresholds](#voting-thresholds), and the [Voting Duration](#voting-duration). *** ### Voting Thresholds A voting threshold is the **minimum number of votes required for a proposal to be approved**. For example, if the treasury has a voting threshold of 2, it means that at least **2 votes in favor are needed for the proposal to pass**. Treasuries separately configure voting thresholds for Governance and Finance proposals, which means that the required number of votes for a proposal to be approved can differ based on the type of proposal being voted on. ### Governance Threshold How many [Governance](/governance/members-and-roles#governance) approvals are required for: * [Editing Team Members](#) * [Updating Voting Settings](#) ### Finance Threshold How many [Finance](/governance/members-and-roles#finance) approvals are required for: * [Making Payments](#) * [Swapping Assets](#) * [Handling Staked Assets](#) *** ### Voting Duration The voting duration is the **time period during which team members can cast their votes on a proposal**. For example, if the voting duration is set to 3 days, it means that team members will have 3 days to vote on a proposal after it has been created. If the required number of votes is reached within the voting duration, the proposal is approved and executed immediately. However, if not enough members vote in favor of the proposal within the voting duration, the proposal then expires and is automatically rejected by the system. In contrast to voting thresholds, which can be configured separately for Governance and Finance proposals, the voting duration is a single setting that applies to all proposals in the treasury, regardless of their type. *** ## What's Next? After a governance request is submitted, it is ready for team members with the [Governance](/governance/members-and-roles#governance) role to review and [vote on the request](/governance/handling-requests). Head to [Handling Governance Requests](/governance/handling-requests) to learn how to review and vote on governance requests. # Receiving a Payment on near.com Source: https://docs.trezu.org/guides/confidential-payments Withdraw payments received from a confidential treasury Just like public treasuries, [confidential treasuries](/confidential-treasuries) can [send payments](/payments/single-payment) in all [assets and chains](/what-is#chains--assets) supported by Trezu. Confidential treasuries can send payments to both [near.com](https://near.com/) accounts and public wallet addresses, but in both cases the payment details and the sender's information are hidden from the public. In this guide we will explain how to access and withdraw a confidential payment received on a [near.com](https://near.com/) account, and how to transfer it to an external wallet. *** ## Accessing and Withdrawing a Confidential Payment Navigate to [near.com](https://near.com/) and log in with the **wallet where you received the payment** (`near.com` supports a wide range of wallets, from multiple ecosystems). Once logged in, use the top left switch to enable confidential mode. You should see your private balance update to reflect the funds received from the confidential treasury. confidential mode enabled Click on `Transfer` and select the `To Main` option, this will allow you to transfer the funds to your main near.com balance, making them available for withdrawal to an external wallet. Transfer to main account Once the transfer is complete, go back to the home screen, disable confidential mode using the top left switch, and click on `Send` to transfer the funds to your external wallet. Withdrawing funds Make sure to disable confidential mode before sending the funds to your external wallet. Select the token you want to send, the destination network, and the recipient address, then confirm the transfer. withdraw funds You can swap the funds to any other asset supported by `near.com` before withdrawing them. The same asset can also be sent across multiple networks, so you can choose the option that best fits your needs. Once the transfer completes, you will see the funds available in your selected external wallet. withdraw completed # Funding through near.com Source: https://docs.trezu.org/guides/funding-confidential-treasuries Learn how to fund a confidential treasury using near.com [Confidential treasuries](/confidential-treasuries) run on a private shard on NEAR, so assets need to be bridged from public blockchains to the private shard through [near.com](https://near.com/). For teams that want to manage the bridging process themselves, this guide explains how to fund a confidential treasury through [near.com](https://near.com/). If you do not want to interact with [near.com](https://near.com/) or manage private accounts, Trezu can handle the bridging process for you automatically. Simply use the `Deposit` button in your confidential treasury's dashboard to generate a temporary deposit address, then send the funds from any external wallet to that address. Remember that temporary deposit addresses are single-use and remain valid for 72 hours, so make sure to create a new one if the address expires before you send the funds. *** ## Moving Funds into near.com Navigate to [near.com](https://near.com/) and connect with any of the supported wallets. Once connected, you will see the main dashboard where you can deposit and manage your assets. near.com dashboard Use the `Receive` option to deposit funds into your main [near.com](https://near.com/) balance. Receive funds screen In this example, we want to deposit some USDC from the NEAR wallet we used to log in, so we will select "Wallet or Exchange" as the source and deposit directly from that wallet. `near.com` allows you to log in with multiple wallets across different chains and supports multiple popular assets. You can also deposit funds into your `near.com` by direct transfer from any external wallet. Deposit funds screen *** ## Transferring Funds to the Confidential Treasury Now that the funds are in your main `near.com` balance, the next step is to move them into your confidential balance. Use the top-left switch to enable confidential mode, then click `Transfer`. This moves the funds from your main `near.com` balance to your confidential `near.com` balance. confidential mode enabled Select `To Confidential`, then choose which token and how much of it you want to transfer into your confidential balance. Transfer to confidential account Once that transfer is complete, go back to the home screen and send the funds to the treasury. Click `Send` and select **another near.com account** as the destination. Sending funds to another near.com account As [confidential treasuries](/confidential-treasuries) are deployed on `near.com`'s private shards, they are effectively `near.com` accounts. Make sure to select **another near.com account** on the `Send` screen. If you send the funds anywhere else, they will not arrive in the confidential treasury. Select the token you want to send and enter the treasury's account ID as the destination. You can find the treasury's account ID by using the `Deposit` button in your private treasury's [dashboard](https://trezu.app/). getting address from trezu Make sure to copy the correct account ID, remember that confidential treasuries can only receive funds from `near.com` accounts. Confirm the transfer. Once it completes, you will see the funds in your confidential treasury's [dashboard](https://trezu.app), ready to use for payments and swaps. deposit completed At this point, the treasury is funded and ready for confidential payment and swap proposals. confidential treasury dashboard # Using a Ledger Source: https://docs.trezu.org/guides/ledger Learn how to set up and use a Ledger hardware wallet with Trezu on NEAR Hardware wallets are one of the most secure ways to manage your account. While you do not need a hardware wallet to use Trezu, it is highly recommended to use one β€” especially for your most critical operational roles, such as `Finance` and `Governance`. Learn more on how to keep your treasury safe using a Ledger device in our [**blog post**](https://trezu.org/blog/how-to-use-ledger-hardware-wallet). *** ## Setting Up Ledger with NEAR 1. Download and install [Ledger Live](https://www.ledger.com/ledger-live) 2. Connect your Ledger via USB or Bluetooth 3. Open the **Ledger Live** application and ensure your device firmware is up to date 4. In **Ledger Live**, install the **NEAR app** from the *App Catalog* 5. Open the NEAR app on your Ledger device (the screen should display *Application is ready*) NEAR app installed in Ledger Live

*NEAR app (v2.4.3) installed in Ledger Live*

Your Ledger is now set up, so you can readily use it to join a treasury in Trezu or create a new one. *** ## 1. Log in to Trezu Go to [trezu.app](https://trezu.app) and click **Login** 1. Select the **Ledger** option 2. Choose between **USB** or **Bluetooth** connection depending on your device 3. Your device will prompt you to **confirm the connection** β€” approve it on the device *** # 2. Select a Derivation Path At this point, you will be prompted to select a `Derivation Path`, which determines which private key you want the Ledger to use when signing transactions in Trezu. Derivation path selection If you are **unsure** which one to select, do not worryβ€”simply **select the first one** (`Account 1`). Approve the selection on your Ledger device before proceeding to the next step. *** ## 3. Select an Account Now that you have selected which `private key` you want to use, it is time to manually enter the `account` you want to log in with: AccountID Selection You can either use the `implicit account` derived directly from the selected `derivation path`, or input any other `accountId` of your choice. After confirming, you will see one of the following outcomes: 1. **Logged in successfully** β€” the account exists and matches the selected Ledger `private key` 2. **Create account option** β€” the account does not exist yet, so you can create it immediately 3. **Error message** β€” the account exists, but it is linked to a different Ledger `private key` To avoid key mismatch errors, use the same derivation path that was originally used with that `accountId`. **Advanced** In NEAR, it is possible to add your Ledger `public key` to accounts that already exist; however, to do this you will need to use an external tool, such as the [NEAR CLI](https://docs.near.org/tools/near-cli). *** ## 4. You are in! That's it! You are now logged in to Trezu using your Ledger hardware wallet. Do not worry if you do **not have funds** in the account yet β€” Trezu sponsors creating the treasury, as well as interacting with proposals. You can simply use Trezu as you normally would, but now with the added security that all your actions will require physical confirmation on your Ledger device. Go ahead and [create a new treasury](https://trezu.app/app/new), or ask your team to add you as a member to an existing one! # Proposing Multiple Payments Source: https://docs.trezu.org/payments/bulk-payment Request payments for multiple recipients at once Besides being able to create [requests for single payments](/payments/single-payment), you can also create bulk payment requests to pay multiple recipients at once. This is especially useful when you need to pay a large number of recipients with the same token, as it allows you to request all payments in a single request, saving you from having to create them separately. Payment requests can only be created by team members with the [Requestor](/governance/members-and-roles#requestor) role, and they require approval from team members with the [Finance](/governance/members-and-roles#finance) role before they can be executed. *** ## Bulk Payment Request Navigate to the **`Payments`** section in the left sidebar, then click **`Bulk Payments`**. Bulk Payment Button You will need to specify in which token you want to pay the recipients - all recipients will be paid in the same token. Then, you will need to manually enter the payment details for each recipient or upload a `.csv` file with the information. Bulk Payment Request
The expected format is a list of recipients with their wallet address and the amount to be paid, e.g. if we want to pay `10.50 USDC` to `alice.near` and `21.34 USDC` to `bob.near`, you can manually provide the payment data in the **Provide Data** section as follows: ``` alice.near, 10.50 bob.near, 21.34 ``` Or download our template and fill in the payment details, then upload the file in the **Upload File** section. *** ## Reviewing the Request Make sure to review the bulk payment request before submitting it. You can also add a comment to provide more context to the approvers. Bulk Payment Review After the bulk payment is approved and executed, you will be able to produce a [receipt](/payments/handling-requests). Make sure to select the right blockchain and enter the correct wallet addresses, as payments are irreversible. *** ## What's Next? After submitting the payment request, it will be ready for the [Finance](/governance/members-and-roles#finance) team members to review and vote on the request. Head to [Handling Payment Requests](/payments/handling-requests) to learn how to review and vote on payment requests. # Handling Payment Requests Source: https://docs.trezu.org/payments/handling-requests Manage payment requests in your treasury Once a payment request is created - either for a [single payment](/payments/single-payment) or to pay [multiple recipients at once](/payments/bulk-payment) - it gets listed as a `Pending` request in the `Requests` section. Request Navigate to the `Requests` section in the left sidebar to see all pending payment requests. You can filter and sort requests to find the one you want to review and vote on. Only team members with the **[Finance](/governance/members-and-roles#finance) role** can review request details and cast a vote to either **approve** or **reject**. *** ## Voting on a Request Click on a request to review its details, including the recipient, the amount, the token, and any comments added by the requester. After reviewing the request, you can cast your vote to either approve or reject it. Request Details Only team members with the **[Finance](/governance/members-and-roles#finance) role** can review request details and cast a vote to either **approve** or **reject**. If the treasury does not have enough funds to cover the payment request, you will need to top up the treasury with the required tokens before the request can be approved. *** ## Receipts Once a payment request is approved and executed, you can generate a PDF receipt to share with the recipient as a proof of payment. Simply click on the payment you want to generate a receipt for, and then click on the **`Generate PDF Receipt`** button. Generate Receipt For **non-confidential** treasuries you can also share a receipt link with the recipient, so they can view the receipt online. Confidential treasuries do not allow sharing receipt links, but you can still generate a PDF receipt and share it with the recipient. *** ## Filtering Payment Requests You can filter payment requests by the following fields: `Request Type`, `Created Date`, `Recipient`, `Token`, `Requester`, `Approver`, `My Vote status`. To filter payment requests, click on the **`Filter`** icon: Request Then simply add as many filters as needed: Request To see only payment requests, filter by `Request Type` -> `Payments`. # Proposing a Payment Source: https://docs.trezu.org/payments/single-payment Request a payment to an external account The treasury funds can be used to send payments to an external account. You can request payments to any wallet address on any blockchain, even if the treasury does not have the required tokens to cover the payment - your team can top up the treasury with the required tokens later on. Need to request multiple payments at once? Check the [Proposing Multiple Payments](/payments/bulk-payment) section. Payment requests can only be created by team members with the [Requestor](/governance/members-and-roles#requestor) role, and they require approval from team members with the [Finance](/governance/members-and-roles#finance) role before they can be executed. *** ## Requesting a Payment Navigate to the **`Payments`** section in the left sidebar, then simply fill in the required details: the recipient's **wallet address**, the **token** and **amount** you want to send, and the recipient's **network**. Payments Screen You can create a payment request even if the treasury does not have the necessary tokens. This allows you to request payments, and the team can top-up the treasury with the required tokens later on. Use the [Address Book](#address-book) to save frequently used wallet addresses and easily select them when creating payment requests ### πŸ”’ Private Treasuries [Confidential treasuries](/confidential-treasuries) can create payments to [near.com](https://near.com/) accounts, or directly to public wallet addresses. Payments sent to [near.com](https://near.com/) accounts are private, as the recipient will need to [log in to near.com](/guides/confidential-payments) to access and withdraw the funds. In that case, the sender will appear as the confidential treasury's account on [near.com](https://near.com/). Payments sent directly to public wallet addresses are also private, as they are executed within the private shard. However, in that case, the sender will be the near.com settlement account, as the funds are bridged from the private shard to the public one before being sent to the recipient. *** ## Reviewing the Payment Request After filling in the payment details, you can review the payment request before submitting it. Feel free to add a comment to the payment to provide more context to the approvers. Review Payment After the payment is approved and executed, you can generate a [receipt](/payments/handling-requests). Make sure to select the right blockchain and enter the correct wallet address, as payments are irreversible. *** ## Address Book Trezu allows you to save frequently used wallet addresses in an address book, making it easier to select the correct recipient when creating payment requests. Address Book Addresses can be linked to multiple blockchains, so you can save a recipient's wallet address once and use it for payments across different networks Simply navigate to the **`Address Book`** section in the left sidebar, then click on **`Add Recipient`** to save a new wallet address. *** ## Frequently Asked Questions Here is a list of frequently asked questions about creating payment requests. If you have any other questions, feel free to reach out to your team or contact us! No, once a payment request is submitted, it cannot be edited. If you need to make changes to a payment request, you will need to delete the existing request and create a new one with the correct details. If the payment request is approved and executed with an incorrect wallet address, the funds will be sent to the wrong address and may be unrecoverable. Always double-check the wallet address before submitting the payment request to avoid any mistakes. *** ## What's Next? After submitting the payment request, it will be ready for the [Finance](/governance/members-and-roles#finance) team members to review and [vote on the request](/payments/handling-requests). Head to [Handling Payment Requests](/payments/handling-requests) to learn how to review and vote on payment requests. # Swapping Assets Source: https://docs.trezu.org/swap Swap assets across blockchains directly from Trezu If your team needs to [make a payment](/payments/single-payment) in a token that the treasury currently does not have, or if you simply want to rebalance the treasury's portfolio, you can create a swap request to exchange one token for another. Swapping Trezu allows you to swap assets directly from the platform, making it easy to manage your treasury's portfolio and access liquidity when needed. *** ## Creating a Swap Request To swap assets, simply navigate to the **Exchange** section in the left sidebar, select the asset you want to swap from and the asset you want to swap to, enter the amount, and review the swap details before confirming the request. Swapping Only team members with the [Request](/governance/members-and-roles#request) role can create swap requests. ### Swap Fee We currently charge a 0.7% fee on the amount being swapped, which is included in your swap quote. This fee covers the fee costs of the underlying swap protocol - NEAR Intents - and the Trezu widget fee Trezu swap are built on NEAR Intents, a platform for multi-chain asset swaps, that provides competitive rates and low fees for swapping assets across different blockchains *** ## What's Next? Swap requests remain open for **24 hours**. During this time, members with the [Finance](/governance/members-and-roles#finance) role can vote on them. If the request does not receive enough votes - as determined by the treasury's [voting configuration](/governance/voting-settings) - within the 24-hour period, it will be automatically rejected. # What is a Treasury? Source: https://docs.trezu.org/what-is Learn how treasuries can help teams to securely manage all their assets A treasury is a shared wallet that allows teams to securely manage crypto assets across multiple blockchains. Treasuries are designed to be flexible and customizable, allowing teams to set their own rules and permissions for managing their funds. More technically, a treasury is a multisig wallet, where each member controls their own wallet and is assigned a specific role. To perform any action, team members need to create proposals - limited by their role - and submit them for voting. If a proposal reaches the required voting threshold, then it gets executed automatically by the system. Trezu is a non-custodial solution, which means we do not have access to your private keys or funds. Your team retains full control over your assets. *** ## Public & Confidential Treasuries Trezu currently offers two types of treasuries, each designed to meet different needs regarding financial data visibility and how transactions are handled: 1. **Public** treasuries, built for open organizations handling public funds 2. **Confidential** treasuries, designed for teams that want to keep their financial data private | Feature | Public Treasury | Confidential Treasury | | ---------------------------------------------- | ------------------------ | -------------------------- | | Team members | 🌐 Visible to anyone | 🌐 Visible to anyone | | View the treasury funds | 🌐 Visible to anyone | πŸ”’ Only the team | | View payment requests (current and historical) | 🌐 Visible to anyone | πŸ”’ Only the team | | View swap requests (current and historical) | 🌐 Visible to anyone | πŸ”’ Only the team | | How transactions are handled | 🌐 Through public chains | πŸ”’ Through a private shard | Learn more about confidential treasuries in the [**Confidential Treasuries documentation**](/confidential-treasuries). *** ## Chains & Assets Treasuries can hold crypto assets on multiple chains, helping teams to manage all their funds from a **single platform**, thus **without needing to use multiple wallets**. New chains and assets are being added regularly, so if you don't see a specific chain or asset supported, please reach out to us and let us know! *** ## Team Members & Roles A treasury is composed of multiple members, and each member can be assigned multiple [roles and permissions](/governance/members-and-roles). There are three main roles in a treasury: Manages team members and configuration, without handling day-to-day fund requests Creates fund-related proposals such as payments and swaps, with no voting power Reviews and votes on fund-related proposals, cannot manage governance settings Team members can be assigned multiple roles, for example a member can be both Governance and Finance, which means they can manage team members and also vote on proposals. *** ## Governance & Proposals In a treasury, nobody can take unilateral decisions regarding the management of funds or team members. Instead, each treasury defines a minimum number of members that need to be in agreement to perform a certain action - this is called the voting threshold. All actions - be it making a payment, swapping tokens, or managing team members - need to be **first proposed**, and relevant team members get to vote on them. If a proposal reaches the required voting threshold, then it gets executed automatically by the system. This way, treasuries ensure that all decisions are made collectively, thus minimizing risks and maximizing security. *** ## Security Model Treasury security in Trezu is enforced through three mechanisms: 1. **Multiple members** – actions require approvals from more than one wallet 2. **Roles** – limit what actions each wallet can perform 3. **Voting thresholds** – define how many approvals are required for an action to be executed *** ## Frequently Asked Questions A treasury is a wallet on its own, so you would need to deposit funds into the treasury to be able to use them. Once the funds are in the treasury, they can be managed by the team according to the defined roles and voting rules. Your funds are held by the treasury, which is a multisig wallet smart contract on NEAR. The treasury is controlled by your team members through governance. The Trezu team does not custody your keys or funds, nor has any kind of access to them. Your funds remain on-chain and under the treasury control. Team members can use alternative interfaces or command-line tooling to keep managing the treasury. If you previously created a `.sputnikdao.near` DAO, just sign in with the same account that created it and your treasury will be there, ready to use. For other treasury types, we do not currently offer a migration tool. Feel free to contact us so we can discuss your specific case and see how we can help. *** ## Ready to get started? [Create your treasury now](https://trezu.app/) and start managing your team's crypto assets securely and collaboratively!