Cortensor
  • Home
  • Abstract
    • Value Proposition
    • Whitepaper
      • Page 1: Introduction and Vision
      • Page 2: Architecture and Technical Overview
      • Page 3: Incentive Structure and Tokenomics
      • Page4: Development Roadmap and Phases
      • Page5: Summary
  • Introduction
    • What is Cortensor?
    • Key Features & Benefits
    • Vision & Mission
    • Team
  • Getting Started
    • Quick Start Guide
    • System Requirements
    • Installation & Setup
      • Getting Test ETH
      • Setup Own RPC Endpoint
      • Router Node Setup
        • Router API Reference
  • Core Concepts
    • Decentralized AI Inference
      • Community-Powered Network
      • Gamification and Quality Control
      • Incentive Structure
    • Universal AI Accessibility
    • Multi-layer Blockchain Architecture
  • Technical Architecture
    • Design Principles
    • Node Roles
    • Node Lifecycle
      • Ephemeral Node State
    • Node Reputation
    • Network & Flow
    • Type of Services
    • Coordination & Orchestration
      • Multi-Oracle Node Reliability & Leadership Rotation
    • AI Inference
      • Open Source Models
        • Centralized vs Decentralized Models
      • Quantization
      • Performance and Scalability
    • Consensus & Validation
      • Proof of Inference (PoI) & Proof of Useful Work (PoUW
      • aka Mining
      • Proof of Useful Work (PoUW)
      • Proof of Useful Work (PoUW) State Machine
        • Miner & Oracle Nodes in PoUW State Machine
      • Sampling in Large Distributed Systems
      • Parallel Processing
      • Embedding Vector Distance
    • Multi-Layered Blockchain Architecture
    • Modular Architecture and Smart Contract Interactions
      • Session Queue
      • Node Pool
      • Session Payment
    • Mining Overview
    • User Interaction & Node Communication
      • Session, Session Queue, Router, and Miner in Cortensor
    • Data Management
      • IPFS Integration
    • Security & Privacy
    • Dashboard
    • Development Previews
      • Multiple Miners Collaboration with Oracle Node
      • Web3 SDK Client & Session/Session Queue Interaction
    • Technical Threads
      • AI Agents and Cortensor's Decentralized AI Inference
    • Infographic Archive
  • Community & Ecosystem
    • Tokenomics
      • Network Incentive Allocation
      • Token Allocations & Safe Wallet Management
    • Staking Pool Overview
    • Contributing to Cortensor
    • Incentives & Reward System
    • Governance & Compliance
    • Safety Measures and Restricted Addresses
    • Buyback Program
    • Liquidity Additions
    • Partnerships
      • Partnership Offering for Demand-Side Partnerships
    • Community Testing
      • Closed Alpha Testing Phase #1
        • Closed Alpha Testing Phase #1 Contest: Closing & Winners Announcement
      • Closed Alpha Testing Phase #2
      • Closed Alpha Testing Phase #3
      • Discord Roles & Mainnet Privileges
      • DevNet Mapping
      • DevNet Modules & Parameters
    • Jobs
      • Technical Writer
      • Communication & Social Media Manager
      • Web3 Frontend Developer
      • Distributed Systems Engineer
  • Integration Guide
    • Web2
      • REST API
      • WebSocket
      • Client SDK
    • Web3
      • Web3 SDK
  • Use Cases
  • Roadmap
    • Technical Roadmap: Launch to Next 365 Days Breakdown
    • Long-term Vision: Beyond Inference
  • Glossary
  • Legal
    • Terms of Use
    • Privacy Policy
    • Disclaimer
    • Agreement for Sale of Tokens
Powered by GitBook
On this page
  • Why Restricted Addresses are Necessary
  • Permanently Restricted Addresses
  • How to Check Restricted Addresses
  • Sybil Attempt
  1. Community & Ecosystem

Safety Measures and Restricted Addresses

To ensure the security and fairness of the Cortensor network, certain addresses have been restricted due to their involvement in activities such as launch sniping, scams, stolen funds, or other malicious behaviors. These addresses are permanently restricted from interacting with the Cortensor ecosystem.

Why Restricted Addresses are Necessary

Restricting addresses is an essential security measure to safeguard the network from harmful activities that can undermine the fairness and integrity of the ecosystem. Addresses that engage in malicious actions, such as launch sniping, scamming, or stealing funds from original owners, create an unfair environment for legitimate users and can put the project at risk.

Permanently Restricted Addresses

Once an address has been restricted, it will remain on the restricted list permanently. There will be no opportunity for unblocking, so users are advised to verify addresses before engaging in transactions, particularly in Over-The-Counter (OTC) trades. Always ensure the address you are dealing with is not restricted.

How to Check Restricted Addresses

Before completing any transaction, especially OTC deals, it is strongly recommended to check whether the address is restricted. This precaution helps protect you from the risks associated with dealing with compromised addresses.

Please make sure that transactions are carried out with reputable and verified parties to avoid issues related to restricted addresses.

"0x2e763440fCe758D76d7DB2bA2163CEE63fd3bFa5",
"0x6f4DeE8Ce5aC69018C7488DD04F5DbF12D20C2E4",
"0x5d0e39F33b233015a10A827EFe0bF96bD7Ea8760",
"0x1090040bA44Bbbc6a125bA22A27cAd2ba954E88b",
"0x6813cec8AE3B7b0F09D2Db373711B99a5E0a7349",
"0x09d2C018113be78A5eC519b20d423c71bb43c4f7",
"0x049D774d5b0d6C2eb62DfF70c6d59dfc75997e6E",
"0xB368838eBA51351C7c28e5b8dcaf891Ce7F09F7B",
"0xE6596c8Dd1EF8d15AFe32AE11b7d4Ff21313A542",
"0xc839e20311b8a53B969D4F48A6Fc93b9cEd5fD24",
"0x79A25D23121d1cD6C0C3b02ed0faB3fA84ac013F",
"0x8b5b054B93b643D1C215A55cEC4165cAE8704aCf",
"0x7043D633bfB41d8B944C162081ef15715e1C130A",
"0x718EA569643Ffe0AF92052d6C2BC3Cc15d9da18D",
"0x3B4ABC43B9A4466003B623bc523297e5e28bF4Bd",
"0x570d46B4080f5763B221fc69D79e860ECf948af1",
"0xe11d2724e0DC92AA4Ed723c851b83eD0a660Bf13",
"0xF22fa45Cf9b5ceB55beD23735f013c6F270F91B7",
"0x0660b47b4fe3D0E6647856fa8bf57D04166821A1",
"0x5F72163e4Ab6C6C46B66041c9C66CbD0fb95BA70",
"0xB874224f6B143Baa434Aa83AE9B85Fa8418a789E",
"0x4b71fC86B473C2Cf93524734809370B3B4C19fF8",
"0x9047E57AFdD493cD93b4178F0e46e066CCCF4aA7",
"0x71263912633CB4e5c858937B2427805AA82343B3",
"0xDe4972DA3dc0dB29D7a515fEC426B243b9Fc8746",
"0xdAA9529d844D1E7dFc6d207af0D60a695acD7fA9",
"0xDEc64Ff1d5033e47a8DaCf19144a9BfE55cd3B9e",
"0xeFAa223baf7ad3245bdfAd2a758B41Bb68398C1d",
"0x95cc98B3AF2d5d0E91A35A3C9c4053D4C383b5dA",
"0xae7Edd7C8314e0c46E6bB5AA52631a1cE65c3763",
"0xb9Cf9220fCe538c100f7b08034E80B83E736756C",
"0x3E0B27282a0aDe96048C62196d103d439F9ceA7c",
"0x0cb991c8d88fef1406964b0c100E9C411F2a25E9",
"0x402Cf0CAC36C6FaA342B8379D77111e158Fe75D0",
"0xB9ab779CE12CEd9C4D9196F6C01547bAd040FA8D",
"0x198A173bFD8356eFccd39eaD9bDa4Bea142a4498",
"0xC64375bee6A73EeDe40b27ff082CDe9c632baA53",
"0x4c5C2D83FA0e86e9A0a83fcDB46a3EAd91Afb581",
"0x019605cEf7791F0D4D61356BC699C471f2bdca5E",
"0x3DCcAE0d4AE52199F78Bc9386E632cA47Fef2c81",
"0x3DD39E8dd2b8be0A8bAc98074E4a88F9773f7640",
"0xa82eB4d285dCbb4a1577C175A21d79392463798A",
"0x0aa4c74ac0F5e8b2C90db2790CC4084096f78C1e",
"0x26761616A0e89Dc8A0CB10c0eC7E5f8C4808Fb1D",
"0xe9A1A28245c631846f27fc649C5E81845C634c5d",
"0xe21C660079Bf776A2E00734eb11FeBbe1813C259",
"0x233af0449ff4a6FA7025024F4f8d1483A0621e6A",
"0x95CaEA27e1e15E396d95E598F4DC1c0A0d1ef943",
"0xFE1864A317CE994C24F1b41d39C8Aea717b57323",
"0x5E2CaD5DF240E78a0BcB112adCAac2144D242020",
"0x87a06c3a0D74025403E39f226f95dc43dB16Ef25",
"0x4b9D261a9F637F570b74b89e81F1Fa283923021d",
"0xd29aF9eB6E37301292b6da4B7eC9FB948607b93a",
"0x6cb0866f4Fa54d9a1044B4b18Aa9276734705577", //Stolen Funds - Scam
"0x2d82BE7EBB20030b8f0d35CDAc91945044860ADe", //Stolen Funds - Scam
"0x1Db03Ae4609b1BB8B20713C5c209b86033a5F8A0", //Stolen Funds - Scam
"0x33b297c50c20effc79b4aa513dd55c6dad75a865", //Stolen Funds - Scam

Sybil Attempt

PreviousGovernance & ComplianceNextBuyback Program

Last updated 12 days ago

https://docs.google.com/document/d/1Dl8aJjhadVhG1ziAu-ZnZzAETuXOMgwCa3EB1tgeaiA