The mQuark API logic
THIS PAGE IS DEPPRICATED
If you have reviewed our Smart Contract docs, you are already aware that mQuark v.0.1-alpha is based on a data pattern contract. the protocol is handled based on two smart-contracts, one to control the financial logic, and the other for the storage for the NFT data. The Control contract is also the gateway for developers to connect with the data contract.
The mQuark subgraph recieves events data from both of the aformentioned smart contracts, and all data are openly accessible for the public to query.
let's take a look at the categories of data each of these sub-graphs can provide:
- Control Endpoints: recieves logged events about accounting activities e.g. fund transfers and withdrawals from projects.
- Data Endpoints: gets logged events about NFT Data activity of projects and their users
its important to pay attention to Reuqest URLs as in API Reference section, as endpoints are related to either of the contracts mentioned above.