Welcome to the official minting vault for the TEN_FanClub (TENFC) NFT collection.
This is a sovereign smart contract deployed on the Ethereum Classic network. By entering the vault, you will be interacting directly with the decentralized blockchain.
Minting Parameters:
Total Supply: Strictly capped at 4,701 tokens.
Mint Price: 10 ETC per token.
Transaction Limit: Maximum 47 tokens per transaction.
Please ensure you have a Web3 wallet (like MetaMask) installed and sufficient ETC to cover the mint and standard network gas fees.
** The connection to the Minting Vault on the Ethereum Classic Mainnet is connected to the IPFS protocol**
The InterPlanetary File System (IPFS) is a decentralized, peer-to-peer (P2P) protocol designed to change how data is stored and accessed on the internet. Unlike the traditional web (HTTP), which finds files based on where they are (location-based), IPFS finds them based on what they are (content-based).Â
Core Meaning and Purpose
Meaning: IPFS is a distributed file system that connects all computing devices with the same system of files. Every piece of content is assigned a unique Content Identifier (CID), which is a cryptographic hash of the data itself.
Purpose: The primary goal is to make the web more efficient, resilient, and open. It aims to move away from centralized "cloud" servers owned by a few large companies toward a model where users directly share data with each other.Â
Â
Key Benefits
Censorship Resistance: Because data is distributed across many nodes, no single entity can easily block or take down content.
Data Integrity: Since the address (CID) is derived from the content, you can be certain that the file you download hasn't been altered. Any change to the file would result in a completely different CID.
Speed and Efficiency: IPFS can retrieve data from the nearest node that has a copy, reducing latency and saving up to 60% of bandwidth for high-volume content like video.
Resilience: It eliminates "single points of failure." If one server goes down in the HTTP world, the data is gone; in IPFS, as long as at least one node in the network has the data, it remains accessible.
Data Permanence: It helps prevent "link rot" by ensuring content can be archived and retrieved as long as anyone in the network thinks it is valuable enough to store.Â
Â
Security and Privacy Needs for Users
Users must understand that IPFS is public by design and requires proactive steps to secure sensitive data.Â
Content Encryption: By default, files on IPFS are not encrypted. If you are storing sensitive information, you must encrypt the file before adding it to the network.
Anonymity Risks: Your node’s ID and the CIDs you request are visible to other nodes in the network. This means your activity can potentially be tracked or profiled.
Gateway Trust: If you access IPFS through a public HTTP gateway (like ipfs.io) rather than your own node, you are trusting that gateway not to monitor your traffic or alter the content before it reaches you.
Data Persistence (Pinning): Data is not automatically stored forever. To ensure your files stay online, you must "pin" them on your own node or use a pinning service.
Immutability: Once a file is on the public network, it is virtually impossible to "delete" it if other nodes have cached or pinned it.