|
3 | 3 | ## 🚀 Features |
4 | 4 |
|
5 | 5 | - **Contract Creation** |
6 | | - Create and manage legally binding contracts with vendors. |
| 6 | + Create and manage legally binding vendor agreements. |
7 | 7 |
|
8 | 8 | - **Participant Invitation** |
9 | | - Invite all stakeholders to collaborate on the contract. |
| 9 | + Invite all stakeholders to collaborate on the contract (Buyer, Supplier, Third-Party) |
10 | 10 |
|
11 | 11 | - **E-signing of Contracts** |
12 | 12 | Sign contracts electronically, eliminating the need for physical paperwork. |
13 | 13 |
|
14 | 14 | - **Delivery Note Generation** |
15 | 15 | Automatically generate delivery notes as proof of delivery. |
16 | 16 |
|
17 | | -- **Invoice Generation** |
18 | | - Create invoices directly from contract or delivery data. |
| 17 | +- **Invoices** |
| 18 | + Create invoices and pay invoices directly from contract or delivery data. |
19 | 19 |
|
20 | 20 | - **Locking of Assets in Escrow** |
21 | | - Secure payment and asset exchange through escrow integration. |
| 21 | + Secure payments through escrow integration. |
22 | 22 |
|
23 | 23 | - **Flexible Payment Terms** |
24 | 24 | Supports various payment configurations: |
25 | 25 | 1. On Delivery |
26 | | - 2. Standard payment periods: 7, 14, 30 Day, Net 60/90 |
27 | | - 3. Custom payment periods |
| 26 | + 2. Custom payment periods |
28 | 27 |
|
29 | 28 | - **Discounts and Penalties** |
30 | 29 | Configure dynamic pricing based on early payment or late delivery. |
31 | 30 |
|
32 | 31 | - **Automatic Asset Transfer** |
33 | | - Transfer funds automatically on contract fulfillment. |
| 32 | + Transfer funds automatically on contract fulfillment. (On Delivery payment term) |
34 | 33 |
|
35 | 34 | - **Dispute Resolution** |
36 | 35 | Built-in mechanisms to manage and resolve disputes efficiently. |
|
39 | 38 | Connection to crypto wallet |
40 | 39 |
|
41 | 40 |
|
42 | | - |
43 | | -## Running the project locally |
44 | | - |
45 | | -If you want to test your project locally, you can use the following commands: |
46 | | - |
47 | | -```bash |
48 | | -# Starts the replica, running in the background |
49 | | -dfx start --background |
50 | | - |
51 | | -# Deploys your canisters to the replica and generates your candid interface |
52 | | -dfx deploy |
53 | | -``` |
54 | | - |
55 | | -Once the job completes, your application will be available at `http://localhost:4943?canisterId={asset_canister_id}`. |
56 | | - |
57 | | -If you have made changes to your backend canister, you can generate a new candid interface with |
58 | | - |
59 | | -```bash |
60 | | -npm run generate |
61 | | -``` |
62 | | - |
63 | | -at any time. This is recommended before starting the frontend development server, and will be run automatically any time you run `dfx deploy`. |
64 | | - |
65 | | -If you are making frontend changes, you can start a development server with |
66 | | - |
| 41 | +## 🚀 Running locally |
| 42 | +1. **Clone the repository** |
67 | 43 | ```bash |
68 | | -npm start |
| 44 | +git clone <repo-url> |
| 45 | +cd <repo-url> |
69 | 46 | ``` |
| 47 | +2. **Deploy** |
| 48 | +Run local_deploy.sh script. This will create identities and deploy all canisters. |
70 | 49 |
|
71 | | -Which will start a server at `http://localhost:8080`, proxying API requests to the replica at port 4943. |
| 50 | +In the CLM_backend candid interface: |
72 | 51 |
|
73 | | -### Note on frontend environment variables |
| 52 | +1. Fund escrow canister. Transfer dummy tokens to escrow canister using ```transfer``` function. These will be used to cover transfer fees for operations. |
74 | 53 |
|
75 | | -If you are hosting frontend code somewhere without using DFX, you may need to make one of the following adjustments to ensure your project does not fetch the root key in production: |
| 54 | +2. Once users are created in the frontend, use the ```transferToUsers``` function to allocate dummy tokens to user accounts. |
76 | 55 |
|
77 | | -- set`DFX_NETWORK` to `ic` if you are using Webpack |
78 | | -- use your own preferred method to replace `process.env.DFX_NETWORK` in the autogenerated declarations |
79 | | - - Setting `canisters -> {asset_canister_id} -> declarations -> env_override to a string` in `dfx.json` will replace `process.env.DFX_NETWORK` with the string in the autogenerated declarations |
80 | | -- Write your own `createActor` constructor |
| 56 | +This enables users to participate in transactions. |
0 commit comments