Go over backend integration with TftC #8

New Issue

timur · 2025-07-08T19:27:56Z

timur commented

2025-07-08 19:27:56 +00:00

Hugo reached out:

Could we hop on a call in the next few days to compare our OS versions?
There may be components you developped we could re use and vice versa.


Also what do you suggest from a data perspective?
OWZ shall have all relevant uaer data - in which repository shall we connect ?

to which I responded:

As OWZ, i’m told we need to regulate certain user data (financials etc) and i need to know the scope of that, mainly from Chris and Matthew.

I assume it would be:

Legal:

- User legal name and email
- the id of the user within your platform
- access to your kyc account and and a map of user id’s to their kyc identifiers, so if needed OWZ can access their kyc details.

Financial:
- wallet addresses
- accounting data (if your platform supports something like marking an outgoing transaction as am expense or creating an invoice corresponding to an incoming tx.

If your platform has within it a scope of digital asset issuance or trading, then also we might need other stuff.


I guess you could use entirely our backend, but assuming that will be less desirable for your project, I think it makes sense that we provide you api endpoints that correspond to the data scopes we require.

Hugo reached out: ``` Could we hop on a call in the next few days to compare our OS versions? There may be components you developped we could re use and vice versa. Also what do you suggest from a data perspective? OWZ shall have all relevant uaer data - in which repository shall we connect ? ``` to which I responded: ``` As OWZ, i’m told we need to regulate certain user data (financials etc) and i need to know the scope of that, mainly from Chris and Matthew. I assume it would be: Legal: - User legal name and email - the id of the user within your platform - access to your kyc account and and a map of user id’s to their kyc identifiers, so if needed OWZ can access their kyc details. Financial: - wallet addresses - accounting data (if your platform supports something like marking an outgoing transaction as am expense or creating an invoice corresponding to an incoming tx. If your platform has within it a scope of digital asset issuance or trading, then also we might need other stuff. I guess you could use entirely our backend, but assuming that will be less desirable for your project, I think it makes sense that we provide you api endpoints that correspond to the data scopes we require. ```

timur added this to the Zanzibar Digital Freezone project 2025-07-08 19:28:00 +00:00

timur self-assigned this 2025-07-08 19:28:06 +00:00

Sign in to join this conversation.

No Label

No Milestone

No project

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: herocode/freezone#8