# NFT Game Assets API

{% tabs %}
{% tab title="March Updates" %}

### <mark style="color:orange;">3/22/22 Report:</mark>

**Previous Milestone:**

As a brief recap of the focus of this proposal - Revelar is building an NFT Game Engine to quickly integrate games on-chain. This NFT Game Asset API is the core backend API to interacting through Cardano nodes to the blockchain & data queries. This is the first report for this proposal, we have onboarded, and have made progress on our first sprint milestone listed below.&#x20;

**Progress:**

High reliability is key for these core API services, and we have spent this sprint reviewing data structures that exist with Cardano's GraphQL and how other projects have approached creating API's (particularly Blockfrost). We have defined our core architecture and will be deploying a hybrid cloud approach with the majority of services running in Google Cloud, with development nodes running on site on bare metal deployments. \
&#x20;\
We believe this gives us the best balance of speed to delivery, global coverage, and decentralized local nodes as a fallback. \
\
Part of this proposal is scripts for asset generation (stacking layers) which we have completed 70%. The next step is to deploy in our cloud instances and test via some of the beginning endpoints. API documentation will begin next sprint, and will likely be available for first review late April. \
\
Developers looking to be early testers should reach out to <mark style="color:blue;"><ben@revelar.co></mark> to join our API Key waitlist. <br>

**Next Steps:**

The next sprint will be finalization of our asset generation script & continued documentation on our APIs and cloud deployment. <br>

**Roadblocks:**

None

**Status:**

On Time
{% endtab %}

{% tab title="April Updates" %}

### <mark style="color:orange;">4/5/22 Report:</mark>

**Previous Milestone:**

As a brief recap of the focus of this proposal - Revelar is building an NFT Game Engine to quickly integrate games on-chain. This NFT Game Asset API is the core backend API to interacting through Cardano nodes to the blockchain & data queries. This is the first report for this proposal, we have onboarded, and have made progress on our first sprint milestone listed below.&#x20;

**Progress:**

Building upon the documentation for our Data Structures and High Level Design for this system:&#x20;

{% embed url="<https://docs.google.com/document/d/1nVJvOd9ObufXeoFVAkKtmJwo4Nf16qvJPzhnBIp08sI/edit?usp=sharing>" %}

After discussing with devs from current leaders in NFT minting platforms, we noticed an opportunity to prototype a Multi-Minter during our API standup and thus reprioritized the finalization of our asset generation script to the next sprint. The multi-minting approach will allow for an expanded API with lower costs with consolidation of Min UTxO requirements and faster delivery times with batching transactions. This is a vast improvement on current minting options in market. \
\
The Revelar Multi-Minting has been successfully tested on mainnet and will be deployed to production infrastructure in the coming weeks.\
\
Developers looking to be early testers should reach out to <mark style="color:blue;"><ben@revelar.co></mark> to join our API Key waitlist. <br>

**Next Steps:**

The next sprint will be finalization of our asset generation script.&#x20;

**Roadblocks:**

None

**Status:**

On Time
{% endtab %}

{% tab title="May Updates" %}

{% endtab %}

{% tab title="Final Update" %}

{% endtab %}
{% endtabs %}

###


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://catalyst.revelar.co/catalyst-updates/fund-7-updates/nft-game-assets-api.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
