[use our mintDarkblockUpgrade endpoint(https://docs.darkblock.io/openapi/core/tag/Darkblock-API/#tag/Darkblock-API/operation/mint-upgrade-darkblock)]
Make sure you select the dev endpoint to hit as seen here:
We added a new parameter “type” where you can pass in a string. You can name it something descriptive for your protocol, or really whatever you want.
You will need to pass in the address of the person uploading the content as the creator_address and then ask them to generate a signature as shown in the docs on that page.
Once Darkblock unlockable content is detected we need to construct a session token to access the content. This session token is a combination of the epoch timestamp (milliseconds), the signature of the concatenation of the current epoch timestamp and the wallet address of the user, and the chain.
One session token is needed per chain, and can be cached, as they do not currently expire. They will be prone to expiration in the future, the rules around this will be coming soon based on partner feedback.
Here is the format of the session token:
Signature of 16529845012790x438cba7e454b59a9f897d4731fd3eaef37160c0a
The ArtId can be taken from the Darkblock info response and combined with the session token, owner wallet address, NFT Contract and Token Id, and platform to construct a Gateway request. https://gateway.darkblock.io/proxy?artid=&session_token=&token_id=&contract=&platform=
For Ethereum compatible chains you can use this handy-dandy signature tool that allows you to paste in some arbitrary text and create a signature with Metamask: https://random-crap-public.s3.amazonaws.com/sign.html