This is great news, I didn't know you planned to deliver general use lite accounts as part of this too. 😀
Since you mention template code for the creation of tokens, do you have any thoughts on the format and compatibility of these? Is there any chance that they will be incorporated into Hive Engine, for example? Or perhaps following Inleo's lead with Thorchain integration? Having this auto created for all new tokens would be a real game changer in so many ways.
Also interested as to whether you think these token templates could include rewards pools in the vein of Hive's L1 pool and Hive Engine's L2 pools?
I haven't seen any mention of fees anywhere - are there any? Do you know how that will work yet?
Due to contracts being WebASsembly. It's not possible to directly make them work with Hive engine. However, data standards could be aligned for interop. I have some limited plans for doing VSC -> EVM/Thorchain bridging and making it universal for all tokens, but nothing concrete. I will keep that in mind.
Yes, nothing stopping that from being developed.
No fees (yet), but VSC will eventually use staked HBD for lite account fee payments in a similar way to Hive RCs.
I am mainly thinking of how future breakaway communities will be presented to the world and be made tradable. Simplicity is always preferable and if we don't have pure 'SMTs' on L1 Hive - the simplest option - then it would be nice to avoid having more than one structure and format for L2 tokens on Hive. However, I appreciate that this may be unavoidable.
I guess that as long as there is a way for external services, such as coin tracker apps and exchanges, to be able to identify the protocol/service being used to run the L2 coin and they code their systems to denote that and treat them accordingly, then there's no real problem other than ensuring end users are aware of exactly what is going on when they use a community's L2 token on Hive.
That's great to hear! There is huge potential in this imo. Hive Engine tokens have never really been customisable enough to allow us to test different approaches to their functioning.. Being able to custom create contracts for L2 tokens on Hive could be the solution.
Also great! Thanks for explaining
I agree. I plan on building a single interface for token-like contracts that inherit the standard VSC Asset spec for tokens. Any other arbitrary logic can be added on the side of that such as custom mint function, supply cap, etc.