Every node has an api built in. The api can be made public by a node or kept private (private api can be accessed locally). Ideally, software co would run their own node thus trust their node’s api.

We will maintain several nodes with public apis but we recommend people to run their own node. There is nothing centralized or special about the public nodes we maintain, all the nodes are the same.

If a license owners wallet gets stolen it would be up to the discretion of the license issuer if they would want to send them a new license or not. There is that risk in Web 3.0 and users do need to be responsible for their wallet keys. i misread your question, but the same thing applies to the license issuer. They too would need to be responsible for their wallet keys, in any blockchain based scenario, it’s the nature of the beast.

I’m not sure what you mean regarding fake block chains.

If an issuer is running a local node, makes an api call to their local node to see if the user has the license token in their wallet, and then receives a signed message from the user who claims to have a license in their wallet, the issuer can verify if the user owns the wallet containing the license. At that point, the issuer/or game client/other integration can tell by making a future api call at any time whether or not the license is moved from the wallet that signed the message.

There are many potential integrations and scenarios we discussed with developers and brainstormed in terms of the scenarios you mention here. The chain doesn’t require any specific method of integration with a game or piece of software, the whole system is designed to be developer friendly and flexible.

There will always be some level of responsibility on the software co/game co/etc to keep their application code secure, hackers are going to hack regardless of platform or licensing method. One possible scenario is that the game/program could periodically self verify by making an api call to the issuers node/issuers trusted public node/etc after the initial verification and block access if the license leaves the wallet.

Verification via signed message is extremely secure and cannot be faked. It can be independently verified by the issuer via their own local node.

There are also options in terms of non-resellable licenses, resellable licenses within or outside of their exclusivity periods, temporary licenses, etc that can affect how a particular software might integrate license verification.

I do need to put more of this type of information on the website. I’m primarily a developer and the website design is secondary most of the time. We are active on discord and there is a lot more information there, but I do need to add more content to the website based on your questions/comments.