DAGWatch

Flowchart

What is DAGWatch

DAGWatch is a wallet abstraction provider for the Constellation network. It lets developers create applications with DAGWatch API and manage users' DAG wallets on their server, without a need for interaction with Blockchain.

How we built it

We've built a REST API for developers and created a DAGWatch API documentation. Also, we created an interface for developers to visibly manage their apps.

How it works

From a developer perspective, you should read DAGWatch API docs to learn how to integrate DAGWatch into your project. But don't worry, it's so simple.

As a developer, the first thing you should do is create an app on DAGWatch. You can use /sign-application endpoint for that.

Then, save your app ID and access token, now you are ready to manage your users' wallets.

From the user perspective, on the other hand, all you need to do is sign in with your favorite OAuth2 provider, like Google, Discord, etc.

A DAG wallet will be generated off-chain, and it'll be related to your email and login method. Now you have your DAG wallet generated by your app provider without needing to install a wallet extension or learn anything about the blockchain ecosystem. That's the beauty of wallet abstraction providers.

Wallet Endpoints

These endpoints are available for your own app, you can't call API requests for other apps. To learn more, read DAGWatch API docs.

/user

Returns the user info using the wallet address.

/balance

Returns the ordinal and balance of the user's DAG wallet.

/send-transaction

Starts a transaction from one DAG wallet to another. The receiver wallet does not have to be a part of the app, it can be any DAG wallet. As body parameters, needs the sender address, receiver address, and an amount.

Technologies we use

Interface

React
Sass
Zustand
react-router-dom

API

Node.js
Express.js
Passport
MongoDB

Challenges we ran into

We've faced some problems during the Metagraph Node setup. Some Python modules were unable to install on our Ubuntu server, however, we've solved this challenge by modifying config files from the original repository.