Skip to content
This repository was archived by the owner on Oct 21, 2025. It is now read-only.
This repository was archived by the owner on Oct 21, 2025. It is now read-only.

Cache NFT type id and NFT id after initial creation #67

@MastaP

Description

@MastaP

Currently the NFT type id is hardcoded. Upon startup the service checks if type has already been created (if not, creates it) and also looks up the NFT of this type (if the configured wallet does not have it, mints the token). There are several ways some things might go wrong.

  • If hardcoded type id is changed, upon restart/redeploy with the newer version, service will automatically switch to new NFT.
  • If for some reason there are several NFTs of same type owned by the wallet, the service might start using a different NFT from what it was using before.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions