Take a look at how Dungeon Krawler (DK) uses Blockery
DK wants to accept $DJED tokens in exchange for NFTs representing in-game items. They implement Blockery which streams data concerning their metaverse wallets in real time. When Alice sends some $DJED tokens to Dungeon Krawler, it reacts instantly releasing NFTs to Alice and providing her items in-game.
DK allows players to own in-game equipment as NFTs. When a player obtains a new NFT from a third party, Dungeon Krawler is immediately informed by Blockery of the event. The game then grants the player access to the item in their inventory. Similarly, when a player transfers one of their items out of their wallet, Blockery let's DK know in real-time to remove that item from the player's inventory.
Mint Assets on Demand
DK rewards players with NFTs representing in-game equipment. When a player is rewarded equipment, the mmo tells Blockery (via simple http request) to mint an NFT. Blockery does so, and then delivers it the player.
DK lacks the desire to run their own servers on their own hardware; a step which must be taken to ensure security of cryptographic keys. Previously DK used a virtual server at a web services provider, but was concerned the engineers at that provider could access their signing keys at will with no audit trail!
Blockery's security strategy is designed specifically for its use case ensuring only trusted operators can access critical systems, and no individual operator can gain access to cryptographic keys!
Integration is Easy
Integration with Blockery consists of simple http requests to RESTful resources in order to execute commands. Inbound data is read by subscribing to event-based publish/subscribe channels using the SDK.
You're a few lines of code away from minting nfts, reacting to on-chain activity, and thriving in the metaverse.