| Orange Line - New Media |
Information: 
The virtual inworld blockchain at
Toronto.uk.com
Network Type: Polygon Network (Sidechain of Ethereum); Polygon Mainnet; (Gas: Polygon Matic);
Compatible Wallet: MetaMask (Non-Custodial Wallet)
Contract Address (Restrictions Apply) on 0xf29DaDcED973AE292d475A5CF6bFeC73bf52533B
Creator
0x19cA9756061E4004D6e56Cd0a660
Supply: 300M (Transaction History)
Purpose and Intention: To test the innovative potential of blockchain.
Limits of Use: Restrictions apply to comply with OSC rules and regulations regarding blockchain technology usage in Ontario, Canada.
Identification Notes: The name of the contract is not the key to identifying the correct contract. What ultimately matters is the contract address (above) and tracing its history to the creator (above).
Technical Explanation: contracts may share the same or similar names but are totally different and unrelated to each other. Contract names are not protected or regulated by any centralized "naming" authority - so relying on a name is the incorrect way of checking a contract's authenticity. This is a potential area of confusion if someone confuses one contract for another because they may have the same or similar names or symbols. Therefore, it is crucial to find and identify the correct contract by its address. Here, the contract address, or origin is: 0xf29DaDcED973AE292d475A5CF6bFeC73bf52533B. For this particular contract type on the Polygon Mainnet Network, use polygonscan.com for the purpose of checking contract information, its address, and its history (Click on the "Polygon Scan" Button - Upper Left of this screen). However, Polygon Scan is not used to search all blockchains that are in existence. This is because specific search techniques are dependent on the specific type of blockchain being checked, each contract type with its own particularly designed search tool(s). In some ways, the layman's term of "pedigree" serves as a useful analogy when it comes to understanding blockchain contract address tracing. That is to say, the search parameters for contract identification are ultra-specific to its address and its creator when verifying for authenticity, each with unique checks and tools for that pedigree. The tracing process must be done precisely to determine the contract's origins and history. So it is good practice to be in the habit of tracing. When a token is transferred between MetaMask wallets, ensure that the token has a specific origin point from contract address: 0xf29DaDcED973AE292d475A5CF6bFeC73bf52533B. Otherwise, any other token being passed off as such is not authentic or valid in the toronto.uk.com metaverse. Click here for screenshots.
Transfers (on the blockchain): Computer end-user applications such as the "MetaMask Wallet" app (owned by a company named ConsenSys) or browser add-ons are designed for token transfers (such as Polygon Matic) through its 'non-custodial' wallet. Each Metamask wallet address is the unique address of the owner. Just as the creator of the contract has an address (who may be using MetaMask), so do the users who want to execute a token transfer with another party (who may also be using MetaMask). The MetaMask wallet contains a secret passphrase which acts as a password to a transaction, so it is important to know the difference between the "publicly viewable" wallet address and the secret passphrase (which should be protected and not shared with anyone). Caution: Keep the secret passphrase in a safe place because if it is lost, then there is no other way to recover tokens through a "password reset". Contextually, the idea of a 'wallet' is not completely analogous to the true operational nature of the blockchain technology described herein because there are no actual "digital" tokens stored in a MetaMask Wallet. To be more precise, the "MetaMask Wallet" software functions as a computer end-user program which assists in recording transactions on the blockchain's electronic ledger - records which are publicly readable on Polygon Scan. Any "transfer" does not occur with the actual exchange of a token but the record of their transfer, in unit terms, on the blockchain's ledger. So what can be potentially stolen is not the token itself but a compromise in security in having a secret passphrase stolen or a hack on the blockchain itself (such as a 51% attack) leading to change in the ledger. Transfers are performed by paying "gas fees" to miners, which in this case, are paid in Polygon Matic on the Polygon Network, the sidechain of Ethereum. Polygon Matic can be purchased on a cryptoexchange and are also stored on apps such as MetaMask wallet. But in reality, there are no actual "digital tokens" stored in a 'non-custodial' wallet such as MetaMask Wallet - it is just transaction information stored decentrally on several nodes (computers) which validate transactions (consensus) to maintain the ledger. For more introductory reading into the subject, refer to Laura Shin's book: "The Cryptonians: Idealism, Greed, Lies, and the Making of the First Big Cryptocurrency Craze"
Restrictions on Value, Transfer, and Ownership: The specified blockchain (herein referred to as "contract"), at the contract address of 0xf29DaDcED973AE292d475A5CF6bFeC73bf52533B of Polygon Scan, is not intended for trading as a security or security-like instrument. There is no monetary value, stated or implied, in the aforementioned contract. There is no underlying asset class or asset conversion right attached to said contract. The contract is not listed on any cryptoexchange and has no marketable value. The contract is limited to in-world virtual online use on the website(s) and metaverse server(s) of toronto.uk.com to enhance transaction security and anti-fraud measures in e-commerce. The contract is only available to designated beta test users who legally agree (in writing) to abide by restrictions on use, transfer, and ownership rights. The contract is subject to any and all other further restrictions and controls under Ontario law in Canada. The owners of 'Polygon Network', 'Ethereum', 'MetaMask' and 'Polygon Matic' are third parties unrelated to Blackhorse Motorcycles Inc. and www.toronto.uk.com
Non-Unique Symbol (unprotected): SIG1 Token (SIG1); see above notes for explanation about why a symbol is not adequate.
Metaverse Beta Testing Contact: SigniumX (Second Life)
|