kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Get all kandi verified functions for this library.
Powerful structure NFTs are grouped by collections rather than their author, which allows for flexible authorizations. Schemas give NFTs an extensible data structure, which is used for the serialization. Templates store data and can be referenced by assets. This allows grouping similar assets together and saving RAM by not having to store the same data for each asset individually. Templates can also make NFTs non-transferable or non-burnable. Assets always belong to a collection and a schema, and can optionally reference a template.
Data Serialization AtomicAssets uses a custom built serialization inspired by Protobuf, which significantly reduces RAM costs compared to traditional methods (e.g. JSON strings). Serialization is done within the contract, which guarantees that no corrupt data enters the blockchain state.
No RAM Costs for users The RAM cost is paid fully by the dapps that create the assets. Even when transfering assets, this stays the same. The maximum an end user will ever have to pay are 112 bytes for their own scope, and even that will likely only rarely be necessary. This also means that AtomicAssets works without claims. Transfers are instant and no further user action is required.
Minimal fixed RAM costs Creating an asset only costs 151 bytes (112 of which are for the necessary index). Additionally, each token owner needs to have a scope, which costs 112 bytes.
Notifications for Smart Contracts Smart Contracts can get notified automatically about any relevant events related to their assets. This enables them to make the assets an integral part of their game rather than just a static token.
Backing assets with Fungible Tokens Assets can be backed by standard fungible tokens (e.g. EOS / WAX). Those tokens can only be freed by burning the asset, thus allowing dapps to give their asset a guaranteed intrinsic value.
Powerful Trade Offers AtomicAssets features a native implementation of two sided trade offers (similar to Steam or WAX Express Trade). This allows creating and accepting offers with a single action. The implementation of the offers also allows for peer to peer marketplaces that don't require transferring ownership to a market contract.
No Code Snippets are available at this moment for atomicassets-contract.
Why Metamask if web3.js can interact directly with ganache?Asked 2022-Mar-30 at 17:55
I am new to blockchain app development, I saw a project where ganache accounts are imported into Metamask, then web3.js is used to access and print those accounts and balances on Frontend (user interface).
If web3.js can directly access ganache blockchain accounts and balances, why do we need Metamask in between?
ANSWERAnswered 2022-Feb-08 at 09:11
If web3.js can directly acccess ganache blockchain accounts and balances, why we need metamask in between?
In this case, you don't need MetaMask to sign the transaction, as the node (Ganache) holds your private key.
But in a public environment (testnets and mainnet), the node doesn't hold your private key, so you'd need to sign the transaction using MetaMask (or any other tool that holds the private key).
No vulnerabilities reported