---
# System prepended metadata

title: Stardust Architecture and APIs
tags: [Crypto]

---

# Stardust Architecture and APIs

In this document we will depict Use Cases and APIs of three microservices: NFT, Tokens, POI.

## Architecture

All the microservices need to act as a bridge for a web2 company to use the stardust technologies. In particular the microservices need to keep centralized information related to Tokens, NFT and POI (Data use case), profiling them using DID.

Since DID is not yet present in the Stardust network, we will use in first instance the capabilities of the current mainnet (Crysalis) 

![](https://i.imgur.com/7aQKW3u.png)

## Challenges

The main Challenge here is to enable browser interaction with a stronghold wallet in order to sign transactions.

We envision some Firefly/Stronghold agent running on the customer's machine (that aks like Metamask) that is able to receive signature requests.

This component is mandatory in order to allow interaction with backend microservice in a secure way.

## Implementation

Microservice will be written in Go (?)

# Stronghold Agent

Firefly is a complex software that enable simple tasks on the IOTA tangle. Unlikely it is a desktop/mobile application and has no possibility to enable frontend applications.

