Trustless Work DEMO | API Documentation
A minimal dApp example to demonstrate how to interact with the Trustless Work API, deploy escrows, and submit signed transactions to the Stellar network.
Maintainers | Telegram
Tech Rebel | Product Manager techrebelgit Telegram |
Joel Vargas | Frontend Developer JoelVR17 Telegram |
Armando Murillo | Full Stack Developer armandocodecr Telegram |
Caleb Loría | Smart Contract Developer zkCaleb-dev Telegram |
Follow the steps below to get started with this project:
- Install dependencies.
- Format code.
- Set enviroment variables.
- Run the project!
- Fork the repo.
- Clone the repo locally.
- Execute
npm i. - Setup .env according to the information below.
- et the API Key from the htpps://dapp.dev.trustlesswork.com -> https://docs.trustlesswork.com/trustless-work/developer-resources/authentication/request-api-key
- Run the project.
-
Install dependencies:
npm i
-
Format the code using Prettier: (This is for avoid eslint errors)
npx prettier --write . -
Start the development server:
npm run dev
Make sure to set up the following environment variable in your .env file:
# TRUSTLESS WORK -> See API KEY Video
NEXT_PUBLIC_API_KEY=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJ3YWxsZXQiOiJHRE42SUpMUzVCUjNXN1FCM1NBRTNNWU5CRzZINFpXRFVHWURNRVVRWEU2RjJRSFhXSFlNNU1MWCIsImlhdCI6MTc0NTcwMzQzM30.M1gr85EXzUl7JRZ82yOORtVTGmGRL_DxN2C2Cl486lY
To use this project, you must have one of the following wallets installed:
- Freighter
These wallets are required to interact with the platform.
You should use Chrome, Brave or Firefox browser, please install any of the wallets that were listen before. Important Note: If you're having problems to use Freighter, make sure that you have the wallet in "test net", and also if even you couldn't be able to use because it shows you "Not Available". Try going to: Security > Manage Connected Wallet > Remove the "localhost". If the problem persist, please contact us. This mistake happens for the wallet, not our product.
It's important to note that we are using Husky. This means that when you run a git push, Husky will automatically execute npm run format and npm run lint. If either of these commands throws an error, the push will not be successful, and you will see a Husky error. When this happens, make sure to resolve any format and lint errors before trying the push again.





