Create Project

As a user, the first step to using TreSori is creating a project. A project acts as the foundational unit where all configurations and resources are grouped.

Step-1: Clicks on Create Project Tab on the main screen or click on +New project as shown in the image below.

Step-2: As soon as user click on it they will be redirected to the Project Creation screen as shown below.

Step-3: Here user need to provides basic details:

• Project Name(mandatory)

• Project Description

Step-4: Wallet Configuration

When creating a new project in TreSori, users are required to choose a wallet type that best fits their application’s security, compliance, and user-experience requirements.

User need to selects a wallet type which they want to associate and configure with this specific project:

• Self-Custodial

• Custodial

• MPC

The platform also provides a comparative view of different wallet types, helping users quickly understand which wallet model best suits their project requirements. By default, the wallet type is set to Self-Custodial, ensuring full control and ownership for the user. However, users can easily reconfigure this setting and switch to an alternative wallet type based on their operational, security, or compliance needs.

Wallet Confuguration

Custodial Wallet Configuration

This helps you decide who manages private keys for your application and which infrastructure provider will be responsible for secure key storage and transaction signing.

By selecting a custodial wallet:

• Platform (a trusted provider) manages private keys on behalf of users

• End users get a simpler, Web2-like experience

• Security, compliance, and operational responsibility are handled at the infrastructure level

Available Providers

1. Kalp Studio (Default / Managed)

2. Fireblocks

3. BitGo

4. HashiCorp Vault

5. Nitro Enclaves

6. Google Cloud HSM

Coming Soon Providers : This gives users visibility into TreSori’s future enterprise custody roadmap.

1. Coinbase Custody

2. Anchorage Digital

3. Copper

4. Gemini Custody

Once user select any platform other than Kalp Studio the following screen will be displayed.

Here we have selected "Fireblocks" and this configuration enables secure wallet creation, transaction signing, and asset management using Fireblocks’ infrastructure. All fields in this modal define how TreSori authenticates and communicates with the Fireblocks APIs.

API Key (Required)

The API Key is the primary identifier issued by Fireblocks for your workspace. TreSori uses this key to authenticate every request made to Fireblocks on behalf of your project. This field is mandatory, and without a valid API key, the integration cannot be established.

Base Path (Required)

The Base Path specifies the Fireblocks API endpoint that TreSori should use. This usually depends on your Fireblocks environment (for example, production or sandbox). Providing the correct base path ensures that all wallet operations, transaction requests, and status updates are routed to the correct Fireblocks environment.

API Secret Key (Optional)

The API Secret Key is an optional but recommended field used for enhanced security. When provided, it enables stronger request signing and verification between TreSori and Fireblocks. This adds an extra layer of protection for sensitive operations such as transaction approvals and wallet management.

Once User provide all the mandatory detials Click Save Configuration button securely stores the provided Fireblocks credentials for the selected project. Once saved, TreSori can start using Fireblocks as the custodial provider for wallet creation, transaction execution, and asset custody.

MPC Wallet Configuration

When setting up a new project in TreSori, this screen allows you to configure your project using an MPC (Multi-Party Computation) Wallet. This option is designed for applications that require advanced security, distributed key management, and institutional-grade controls.

MPC (Multi-Party Computation) enables distributed key management, where cryptographic key shares are generated, stored, and used independently.

Integration Type (Key Storage & Security Providers)

This section Provides multiple option to the users to choose where and how MPC key shares are stored and protected.

1. KS Providers (Kalp Studio – Managed)

2. AWS KMS

3. AWS S3 (Encrypted Storage)

4. HashiCorp Vault

5. Nitro Enclaves

6. Google Cloud HSM

Coming Soon Providers : This gives users visibility into TreSori’s future enterprise roadmap and indicate future support.

1. Azure Key Vault

2. Google Cloud KMS

Once user select any platform other than Kalp Studio the following screen will be displayed.

Here we have selected AWS KMS, and this configuration enables secure key management, cryptographic signing, and encryption operations using Amazon Web Services Key Management Service. All fields in this modal define how TreSori securely identifies, accesses, and interacts with AWS KMS APIs to perform key-related operations within the selected project.

ARN Key (Required)

The ARN Key refers to the Amazon Resource Name (ARN) of the AWS KMS key that will be used by TreSori. This uniquely identifies the KMS key within your AWS account. TreSori relies on this ARN to locate and securely invoke the correct key for cryptographic operations such as transaction signing or data encryption.

Region (Required)

The Region specifies the AWS region where the KMS key is hosted (for example, us-east-1, eu-west-1, etc.). AWS KMS keys are region-specific, so this value must exactly match the region of the provided ARN.

Once User provide all the mandatory detials Clicking Save Configuration securely stores the AWS KMS details for the selected project. Once saved, TreSori can begin using the specified AWS KMS key for secure key management and cryptographic workflows within that project.

After finalizing the wallet configuration, users can seamlessly configure transaction costing using a one-click setup. This feature automatically determines and applies the appropriate transaction cost parameters, simplifying the onboarding process and reducing configuration complexity.

Step-5: Enable/ Disable Gasless transactions

While creating a new project in TreSori, users are given the option to enable Gasless Transactions. This option allows the project to sponsor blockchain transaction fees on behalf of end users, removing the need for users to hold or manage native gas tokens.

This option is a part of the project configuration step, indicating that gas sponsorship is a project-level capability, not a per-transaction toggle.

Note: Its an optional action while creating the new project

Once enabled Gas Tank is automatically associated with the project and all supported transactions initiated under this project can be gas-sponsored

Step-6:Project status

It represents the operational state of a project in TreSori that determines whether a project is allowed to perform actions such as wallet creation, API access, transaction execution, and gas sponsorship.

From a user’s perspective, Project Status acts as an on/off control for an entire project environment.

Step-6: Complet project Creation

Final step is to click on “Create Project” Button for copletion of project.