As far as the SMT question goes. This isn't a point by point replacement for SMTs. This costs aditional resources to run and provide token API, as well as Resource credits for the runners. SMTs were going to be run by all HIVE nodes, the cost of running these different tokens would have been reduced by limiting token functions... So in many ways these can be adapted to more uses, and if interested parties are running their token nodes mostly from their at home computers that are always on anyway it would only take a couple hundred HP per node for the Resource credits; while API is provided from a dedicated server(s) to the website(s) relying on the token architecture.
You are viewing a single comment's thread from: