...
- Can this infrastructure be flexible enough to define and issue different kinds of NFTs that conform to different standards?
- Can a multi-protocol approach work (this is considerably more difficult as it involves creating smart contracts in different protocols)- What about WASM approaches (investigate Solang HL Lab)
- Interoperability of NFTs can NFT issued on one protocol move to another? Be paid for in another
- Oracles that underlie NFTs.
- Submarining- Is this relevant for non-IPFS storage mechanisms?
- Other damping mechanisms- A governor or clamping mechanism with a circuit breaker for extreme events
- Incorporate AI and XR in the stack
Handle Current limitations of Web3 implementations (Moxie M)
- "Design systems that can distribute trust without having to distribute infrastructure." . All data to be in distributed infrastructure (In Fabric this can be Private Data Collections)
- "Reduce the burden of building software." - No code platform....A smart contract generator, for Go implementations first.
- A generic issuer front end.
- A wallet front end for transfers (not tied to a particular access point)
- Platforms vs Protocols.
- Avoid the worst of both worlds: "centralize to control, decentralize to reduce speed of change".
- Wallets need to do complex things, beyond being only a view onto centralized datainterfaces to decentralized data without having to rely on a centralized intermediary.