The methodology behind CORE3’s crypto project risk assessment — security, financial, operational, reputational, compliance, and dependency risks.
The methodology behind CORE3’s crypto project risk assessment consists of the following risk areas: security, financial and operational sustainability, dependency, reputational, compliance and regulatory risks.
Security risks — smart contract audits, bug bounties, and monitoring
The Security Risks category evaluates a project’s resilience against direct technical exploitation and adversarial attacks, which remain one of the most dominant loss vectors in the crypto market. Smart contract vulnerabilities, protocol misconfigurations, and insufficient monitoring continue to be responsible for a significant share of catastrophic losses, often materializing suddenly and without warning.The combined assessment of token and product audits, active bug bounty programs, and continuous third-party monitoring allows CORE3 to distinguish between projects that treat security as a one-time compliance exercise and those that approach it as an ongoing operational discipline. Audits reduce known and classifiable risks, bug bounties incentivize adversarial testing under real-world conditions, and monitoring systems provide early detection of anomalous behavior post-deployment.
Together, these metrics mitigate the structural challenge of immutable code and composability risk by lowering both the probability and severity of security incidents. Within the Project PoL framework, this category primarily addresses tail-risk events that can lead to immediate and irreversible loss. This makes it a core component of any digital asset security assessment.
Financial risks — token economics, treasury, and liquidity analysis
The Financial Risks category assesses the economic sustainability, capital structure, and incentive alignment of a crypto project. In an environment where many failures stem not from exploits but from flawed token economics, liquidity shocks, or treasury mismanagement, financial risk represents a critical but often under-disclosed threat vector.By evaluating revenue sources, token inflation dynamics, TVL quality, active address activity, and treasury composition, CORE3 measures whether a project’s economic model is durable beyond short-term market cycles. Circulating supply analysis, locker structures, and unlock schedules further reveal dilution risks, liquidity cliffs, and insider exit dynamics that can materially impact users without violating any technical constraints.
This category directly mitigates the market-wide challenge of opacity in token economics and treasury. Within Project PoL, Financial Risks influence both gradual value erosion and event-driven liquidity failures, helping users distinguish between growth backed by fundamentals and growth driven by unsustainable financial engineering. This level of financial risk analysis is a key differentiator in CORE3’s approach to crypto due diligence.
Operational risks — governance, development activity, and market integrity
The Operational Risks category evaluates whether a project can reliably function, evolve, and govern itself over time. Many crypto failures occur not because of malicious intent or flawed code, but due to weak operational capacity, poor governance practices, or misaligned internal incentives.Metrics such as wash trading detection, GitHub activity, founder track record, and documentation quality provide insight into whether a project is actively developed, transparently managed, and operationally mature. Certifications and liquidity risk analysis further indicate whether internal processes and market operations meet baseline professional standards.
This category addresses the systemic problem of surface-level legitimacy masking fragile internal operations. Within Project PoL, Operational Risks affect the continuity of the protocol, the reliability of its markets, and its ability to respond effectively to stress, upgrades, or market disruptions. These factors are central to any meaningful crypto risk management framework.
Reputational risks — incident history, social manipulation, and stakeholder quality
The Reputational Risks category captures behavioral, historical, and relational risk signals that are often ignored by purely technical or financial models but have repeatedly preceded major failures in the crypto ecosystem. Market trust in crypto is highly reflexive, and reputational breakdowns can rapidly translate into liquidity loss, user exits, or regulatory attention.By analyzing responses to past incidents, audit firm reputation, social manipulation, and the presence of insurance coverage, CORE3 evaluates how a project behaves under pressure and whether it has credible external accountability. Project and protocol longevity, along with market maker and investor red flag identification, help detect patterns of extractive behavior, short-termism, or coordinated exit risk.
This category mitigates the challenge of asymmetric information around project intent and stakeholder quality. In Project PoL, Reputational Risks often act as early-warning indicators, signaling elevated loss probability before technical or financial stress becomes visible.
Compliance & regulatory risks — crypto compliance and jurisdictional exposure
The Compliance & Regulatory Risks category assesses a project’s exposure to legal, regulatory, and enforcement-related loss vectors. As regulatory scrutiny increases globally, non-compliance has become a leading cause of operational shutdowns, asset freezes, and forced delistings, even for technically sound projects.Metrics such as disclaimers, public registration, team transparency, regulatory surface controls, jurisdictional exposure, and formal compliance alignment help determine whether a project understands and actively manages its regulatory footprint. This category does not assess legal certainty, but rather the degree of regulatory awareness, preparedness, and cooperation.
Within the Project PoL framework, Compliance & Regulatory Risks mitigate the growing systemic risk of sudden market access loss caused by enforcement actions. This category primarily influences non-technical loss events that originate outside the protocol but have direct financial impact on users. As regulatory frameworks mature globally, this dimension of digital asset risk management becomes increasingly decisive.
Dependency risks — Bridges, oracles, infrastructure, and centralization vectors
The Dependency Risks category evaluates external systems, services, and counterparties upon which a crypto project relies but does not fully control. As composability and modular infrastructure become standard, failures increasingly propagate across protocols through shared dependencies rather than isolated weaknesses.By assessing bridges and cross-chain mechanisms, custody and admin wallet controls, L2, DA, and sequencer dependencies, oracles and market data sources, and infrastructure providers, CORE3 maps the project’s external attack and failure surface. Additional metrics such as web and DNS control, third-party SaaS and CI/CD pipelines, extended dependency scoring, and owner private key rotation practices further expose centralized choke points and governance risks.
This category addresses the core challenge of hidden centralization and transitive trust in decentralized systems. Within Project PoL, Dependency Risks account for systemic and cascading failure scenarios, which have historically produced some of the largest losses in the crypto market.
The methodology consists of 98 metrics and sub-metrics that together form the final score.
Different metrics are updated at different intervals, ranging from weekly to quarterly (or upon updates of the scored protocol, like new security audit), depending on their importance in keeping the score as fresh as possible and on the typical timeframe in which meaningful changes are expected to occur.
Project PoL Scoring Logic
Learn how these risk domains combine into a single PoL score
⌘I
{"docsConfig":{"theme":"linden","$schema":"https://mintlify.com/docs.json","name":"CORE3 Docs","colors":{"primary":"#000000","light":"#FFFAE6","dark":"#191917"},"logo":{"light":"https://mintcdn.com/hacken-efd4870a/019EJ2CsBtvgXXxs/images/Group2.svg?fit=max\u0026auto=format\u0026n=019EJ2CsBtvgXXxs\u0026q=85\u0026s=ef93b1dcc617ff497dbba2ef296145be","dark":"https://mintcdn.com/hacken-efd4870a/019EJ2CsBtvgXXxs/images/Group1.svg?fit=max\u0026auto=format\u0026n=019EJ2CsBtvgXXxs\u0026q=85\u0026s=61f56a4599382e9e73725abdbc011b8a"},"favicon":"https://mintcdn.com/hacken-efd4870a/JOB5au_cL23J_BQw/images/WebsiteFavicon.png?fit=max\u0026auto=format\u0026n=JOB5au_cL23J_BQw\u0026q=85\u0026s=874a14816efe6637c94c1b0ea76be280","navbar":{"links":[{"href":"https://app.core3.io/","label":"CORE3 Platform"},{"href":"https://app.core3.io/blog","label":"Blog"}]},"fonts":{"family":"Inter"},"styling":{"latex":false},"background":{"color":{"light":"#f7f7f7","dark":"#101012"}},"navigation":{"pages":[]}},"deployment":{"deploymentMetadataValue":{"subdomain":"hacken-efd4870a","hasAudioNarration":false,"actualSubdomain":"hacken-efd4870a","customDomains":["docs.core3.io"],"gitSource":{"type":"github","owner":"hai-group","repo":"core3-docs","deployBranch":"main","contentDirectory":"","isPrivate":true,"mountPath":"","label":""},"entitlements":{},"buildId":"6ae947306cb575c06c4d0fe8:success","clientVersion":"0.0.4124","searchFilterCounts":[{"language":"default","tag":"CORE3 for You","count":6},{"language":"default","tag":"Getting Started","count":3},{"language":"default","tag":"MCP","count":3},{"language":"default","tag":"CEX PoL","count":2},{"language":"default","tag":"Trust \u0026 Transparency","count":2},{"language":"default","tag":"API Reference","count":2},{"language":"default","tag":"Project PoL","count":2},{"language":"default","tag":"Probability of Loss (PoL)","count":1},{"language":"default","tag":"About CORE3","count":1}]},"assistantConfig":{"enableAskAiButton":false,"enableStarterQuestions":false,"enableAskAiSearchBar":true},"basePath":"","hasChatPermissions":false,"hasWebMcpPermissions":false,"toggles":[{"name":"kill-isr","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"custom-rbac-roles","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"agent-mintlify-slack","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"agent-integrations-settings","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"rbac-expansion","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"automations-pr-grouping","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"custom-prefix","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"analytics-v7","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"user-flows-analytics","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"no-publish-flow","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"workos-onboarding","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"snapshot-serving-live","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"stripTemperatureMiddleware","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"support-platform-pylon-zendesk","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"snapshot-serving","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"instant-rollback","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"granular-notifications-server","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"granular-notifications","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"automations-fable","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"fixed-ai-action-pricing","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"automation-resolve-merge-conflict","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"scoped-publishing","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"mintql","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"page-level-analytics","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"editor-version-history-v2","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"billing-page-v2","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"full-page-search","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"workspace-projects","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"assistant-v5","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"fork-pr-previews","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"revalidation-jwt","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"workos-sso-scim","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"hobby-abuse-scan","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"dashboard-inbox","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"workos-signup","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"turbopuffer-dual-write","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"workos-enabled","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"approve-review-flow","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"editor-metadata","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"sso-setup-deadline-banner","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"turbopuffer-serve","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"live-agents","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"llms-txt-v2","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false}],"googleFontsInlined":false},"customCss":[],"page":{"pagePath":"project-pol-methodology","slug":"/project-pol-methodology","pageMetadata":{"title":"Project PoL Methodology","description":"The methodology behind CORE3's crypto project risk assessment — security, financial, operational, reputational, compliance, and dependency risks.","icon":"flask-vial","href":"/project-pol-methodology"},"description":{"compiledSource":"\"use strict\";\nconst {jsx: _jsx} = arguments[0];\nconst {useMDXComponents: _provideComponents} = arguments[0];\nfunction _createMdxContent(props) {\n const _components = {\n p: \"p\",\n ..._provideComponents(),\n ...props.components\n };\n return _jsx(_components.p, {\n children: \"The methodology behind CORE3’s crypto project risk assessment — security, financial, operational, reputational, compliance, and dependency risks.\"\n });\n}\nfunction MDXContent(props = {}) {\n const {wrapper: MDXLayout} = {\n ..._provideComponents(),\n ...props.components\n };\n return MDXLayout ? _jsx(MDXLayout, {\n ...props,\n children: _jsx(_createMdxContent, {\n ...props\n })\n }) : _createMdxContent(props);\n}\nreturn {\n default: MDXContent\n};\n","frontmatter":{},"scope":{}},"pageType":"default","mdx":{"mdxSource":{"compiledSource":"\"use strict\";const{Fragment:_Fragment,jsx:_jsx,jsxs:_jsxs}=arguments[0];const{useMDXComponents:_provideComponents}=arguments[0];function _createMdxContent(props){const _components={p:`p`,strong:`strong`,..._provideComponents(),...props.components},{Callout,Card,Danger,Heading,Note,Tab,Tabs,Tip,Warning}=_components;if(!Callout)_missingMdxReference(`Callout`,true);if(!Card)_missingMdxReference(`Card`,true);if(!Danger)_missingMdxReference(`Danger`,true);if(!Heading)_missingMdxReference(`Heading`,true);if(!Note)_missingMdxReference(`Note`,true);if(!Tab)_missingMdxReference(`Tab`,true);if(!Tabs)_missingMdxReference(`Tabs`,true);if(!Tip)_missingMdxReference(`Tip`,true);if(!Warning)_missingMdxReference(`Warning`,true);return _jsxs(_Fragment,{children:[_jsx(_components.p,{children:`The methodology behind CORE3’s crypto project risk assessment consists of the following risk areas: security, financial and operational sustainability, dependency, reputational, compliance and regulatory risks.`}),`\n`,_jsxs(Tabs,{children:[_jsxs(Tab,{title:`Security`,id:`security`,\"data-child-heading-ids\":`[\"security-risks-%E2%80%94-smart-contract-audits%2C-bug-bounties%2C-and-monitoring\"]`,children:[_jsx(Heading,{level:`2`,id:`security-risks-—-smart-contract-audits-bug-bounties-and-monitoring`,children:`Security risks — smart contract audits, bug bounties, and monitoring`}),_jsx(_components.p,{children:`The Security Risks category evaluates a project’s resilience against direct technical exploitation and adversarial attacks, which remain one of the most dominant loss vectors in the crypto market. Smart contract vulnerabilities, protocol misconfigurations, and insufficient monitoring continue to be responsible for a significant share of catastrophic losses, often materializing suddenly and without warning.`}),_jsxs(_components.p,{children:[`The combined assessment of `,_jsx(_components.strong,{children:`token and product audits`}),`, `,_jsx(_components.strong,{children:`active bug bounty programs`}),`, and `,_jsx(_components.strong,{children:`continuous third-party monitoring`}),` allows CORE3 to distinguish between projects that treat security as a one-time compliance exercise and those that approach it as an ongoing operational discipline. Audits reduce known and classifiable risks, bug bounties incentivize adversarial testing under real-world conditions, and monitoring systems provide early detection of anomalous behavior post-deployment.`]}),_jsx(Tip,{children:_jsxs(_components.p,{children:[`Together, these metrics mitigate the structural challenge of immutable code and composability risk by lowering both the probability and severity of security incidents. Within the Project PoL framework, this category primarily addresses `,_jsx(_components.strong,{children:`tail-risk events`}),` that can lead to immediate and irreversible loss. This makes it a core component of any digital asset security assessment.`]})})]}),_jsxs(Tab,{title:`Financial`,id:`financial`,\"data-child-heading-ids\":`[\"financial-risks-%E2%80%94-token-economics%2C-treasury%2C-and-liquidity-analysis\"]`,children:[_jsx(Heading,{level:`2`,id:`financial-risks-—-token-economics-treasury-and-liquidity-analysis`,children:`Financial risks — token economics, treasury, and liquidity analysis`}),_jsx(_components.p,{children:`The Financial Risks category assesses the economic sustainability, capital structure, and incentive alignment of a crypto project. In an environment where many failures stem not from exploits but from flawed token economics, liquidity shocks, or treasury mismanagement, financial risk represents a critical but often under-disclosed threat vector.`}),_jsxs(_components.p,{children:[`By evaluating `,_jsx(_components.strong,{children:`revenue sources`}),`, `,_jsx(_components.strong,{children:`token inflation dynamics`}),`, `,_jsx(_components.strong,{children:`TVL quality`}),`, `,_jsx(_components.strong,{children:`active address activity`}),`, and `,_jsx(_components.strong,{children:`treasury composition`}),`, CORE3 measures whether a project’s economic model is durable beyond short-term market cycles. `,_jsx(_components.strong,{children:`Circulating supply analysis`}),`, `,_jsx(_components.strong,{children:`locker structures`}),`, and `,_jsx(_components.strong,{children:`unlock schedules`}),` further reveal dilution risks, liquidity cliffs, and insider exit dynamics that can materially impact users without violating any technical constraints.`]}),_jsx(Note,{children:_jsxs(_components.p,{children:[`This category directly mitigates the market-wide challenge of opacity in token economics and treasury. Within Project PoL, Financial Risks influence both `,_jsx(_components.strong,{children:`gradual value erosion`}),` and `,_jsx(_components.strong,{children:`event-driven liquidity failures`}),`, helping users distinguish between growth backed by fundamentals and growth driven by unsustainable financial engineering. This level of financial risk analysis is a key differentiator in CORE3’s approach to crypto due diligence.`]})})]}),_jsxs(Tab,{title:`Operational`,id:`operational`,\"data-child-heading-ids\":`[\"operational-risks-%E2%80%94-governance%2C-development-activity%2C-and-market-integrity\"]`,children:[_jsx(Heading,{level:`2`,id:`operational-risks-—-governance-development-activity-and-market-integrity`,children:`Operational risks — governance, development activity, and market integrity`}),_jsx(_components.p,{children:`The Operational Risks category evaluates whether a project can reliably function, evolve, and govern itself over time. Many crypto failures occur not because of malicious intent or flawed code, but due to weak operational capacity, poor governance practices, or misaligned internal incentives.`}),_jsxs(_components.p,{children:[`Metrics such as `,_jsx(_components.strong,{children:`wash trading detection`}),`, `,_jsx(_components.strong,{children:`GitHub activity`}),`, `,_jsx(_components.strong,{children:`founder track record`}),`, and `,_jsx(_components.strong,{children:`documentation quality`}),` provide insight into whether a project is actively developed, transparently managed, and operationally mature. `,_jsx(_components.strong,{children:`Certifications`}),` and `,_jsx(_components.strong,{children:`liquidity risk analysis`}),` further indicate whether internal processes and market operations meet baseline professional standards.`]}),_jsx(Warning,{children:_jsxs(_components.p,{children:[`This category addresses the systemic problem of surface-level legitimacy masking fragile internal operations. Within Project PoL, Operational Risks affect the `,_jsx(_components.strong,{children:`continuity of the protocol`}),`, the reliability of its markets, and its ability to respond effectively to stress, upgrades, or market disruptions. These factors are central to any meaningful crypto risk management framework.`]})})]}),_jsxs(Tab,{title:`Reputational`,id:`reputational`,\"data-child-heading-ids\":`[\"reputational-risks-%E2%80%94-incident-history%2C-social-manipulation%2C-and-stakeholder-quality\"]`,children:[_jsx(Heading,{level:`2`,id:`reputational-risks-—-incident-history-social-manipulation-and-stakeholder-quality`,children:`Reputational risks — incident history, social manipulation, and stakeholder quality`}),_jsx(_components.p,{children:`The Reputational Risks category captures behavioral, historical, and relational risk signals that are often ignored by purely technical or financial models but have repeatedly preceded major failures in the crypto ecosystem. Market trust in crypto is highly reflexive, and reputational breakdowns can rapidly translate into liquidity loss, user exits, or regulatory attention.`}),_jsxs(_components.p,{children:[`By analyzing `,_jsx(_components.strong,{children:`responses to past incidents`}),`, `,_jsx(_components.strong,{children:`audit firm reputation`}),`, `,_jsx(_components.strong,{children:`social manipulation`}),`, and the presence of `,_jsx(_components.strong,{children:`insurance coverage`}),`, CORE3 evaluates how a project behaves under pressure and whether it has credible external accountability. `,_jsx(_components.strong,{children:`Project and protocol longevity`}),`, along with `,_jsx(_components.strong,{children:`market maker and investor red flag identification`}),`, help detect patterns of extractive behavior, short-termism, or coordinated exit risk.`]}),_jsx(Tip,{children:_jsxs(_components.p,{children:[`This category mitigates the challenge of asymmetric information around project intent and stakeholder quality. In Project PoL, Reputational Risks often act as `,_jsx(_components.strong,{children:`early-warning indicators`}),`, signaling elevated loss probability before technical or financial stress becomes visible.`]})})]}),_jsxs(Tab,{title:`Compliance`,id:`compliance`,\"data-child-heading-ids\":`[\"compliance-%26-regulatory-risks-%E2%80%94-crypto-compliance-and-jurisdictional-exposure\"]`,children:[_jsx(Heading,{level:`2`,id:`compliance-\u0026-regulatory-risks-—-crypto-compliance-and-jurisdictional-exposure`,children:`Compliance \u0026 regulatory risks — crypto compliance and jurisdictional exposure`}),_jsx(_components.p,{children:`The Compliance \u0026 Regulatory Risks category assesses a project’s exposure to legal, regulatory, and enforcement-related loss vectors. As regulatory scrutiny increases globally, non-compliance has become a leading cause of operational shutdowns, asset freezes, and forced delistings, even for technically sound projects.`}),_jsxs(_components.p,{children:[`Metrics such as `,_jsx(_components.strong,{children:`disclaimers`}),`, `,_jsx(_components.strong,{children:`public registration`}),`, `,_jsx(_components.strong,{children:`team transparency`}),`, `,_jsx(_components.strong,{children:`regulatory surface controls`}),`, `,_jsx(_components.strong,{children:`jurisdictional exposure`}),`, and `,_jsx(_components.strong,{children:`formal compliance alignment`}),` help determine whether a project understands and actively manages its regulatory footprint. This category does not assess legal certainty, but rather the `,_jsx(_components.strong,{children:`degree of regulatory awareness, preparedness, and cooperation`}),`.`]}),_jsx(Danger,{children:_jsxs(_components.p,{children:[`Within the Project PoL framework, Compliance \u0026 Regulatory Risks mitigate the growing systemic risk of sudden market access loss caused by enforcement actions. This category primarily influences `,_jsx(_components.strong,{children:`non-technical loss events`}),` that originate outside the protocol but have direct financial impact on users. As regulatory frameworks mature globally, this dimension of digital asset risk management becomes increasingly decisive.`]})})]}),_jsxs(Tab,{title:`Dependency`,id:`dependency`,\"data-child-heading-ids\":`[\"dependency-risks-%E2%80%94-bridges%2C-oracles%2C-infrastructure%2C-and-centralization-vectors\"]`,children:[_jsx(Heading,{level:`2`,id:`dependency-risks-—-bridges-oracles-infrastructure-and-centralization-vectors`,children:`Dependency risks — Bridges, oracles, infrastructure, and centralization vectors`}),_jsx(_components.p,{children:`The Dependency Risks category evaluates external systems, services, and counterparties upon which a crypto project relies but does not fully control. As composability and modular infrastructure become standard, failures increasingly propagate across protocols through shared dependencies rather than isolated weaknesses.`}),_jsxs(_components.p,{children:[`By assessing `,_jsx(_components.strong,{children:`bridges and cross-chain mechanisms`}),`, `,_jsx(_components.strong,{children:`custody and admin wallet controls`}),`, `,_jsx(_components.strong,{children:`L2, DA, and sequencer dependencies`}),`, `,_jsx(_components.strong,{children:`oracles and market data sources`}),`, and `,_jsx(_components.strong,{children:`infrastructure providers`}),`, CORE3 maps the project’s external attack and failure surface. Additional metrics such as `,_jsx(_components.strong,{children:`web and DNS control`}),`, `,_jsx(_components.strong,{children:`third-party SaaS and CI/CD pipelines`}),`, `,_jsx(_components.strong,{children:`extended dependency scoring`}),`, and `,_jsx(_components.strong,{children:`owner private key rotation practices`}),` further expose centralized choke points and governance risks.`]}),_jsx(Warning,{children:_jsxs(_components.p,{children:[`This category addresses the core challenge of hidden centralization and transitive trust in decentralized systems. Within Project PoL, Dependency Risks account for `,_jsx(_components.strong,{children:`systemic and cascading failure scenarios`}),`, which have historically produced some of the largest losses in the crypto market.`]})})]})]}),`\n`,_jsx(Heading,{level:`2`,id:`how-often-are-crypto-risk-metrics-updated`,children:`How Often Are Crypto Risk Metrics Updated?`}),`\n`,_jsx(Callout,{icon:`clock`,color:`#FFC107`,children:_jsxs(_components.p,{children:[`The methodology consists of `,_jsx(_components.strong,{children:`98 metrics and sub-metrics`}),` that together form the final score.`]})}),`\n`,_jsx(_components.p,{children:`Different metrics are updated at different intervals, ranging from weekly to quarterly (or upon updates of the scored protocol, like new security audit), depending on their importance in keeping the score as fresh as possible and on the typical timeframe in which meaningful changes are expected to occur.`}),`\n`,_jsx(Card,{icon:`calculator`,href:`/project-pol-scoring-logic`,cta:`See how scores are calculated`,title:`Project PoL Scoring Logic`,children:_jsx(_components.p,{children:`Learn how these risk domains combine into a single PoL score`})})]})}function MDXContent(props={}){const{wrapper:MDXLayout}={..._provideComponents(),...props.components};return MDXLayout?_jsx(MDXLayout,{...props,children:_jsx(_createMdxContent,{...props})}):_createMdxContent(props)}return{default:MDXContent};function _missingMdxReference(id,component){throw new Error(`Expected `+(component?`component`:`object`)+\" `\"+id+\"` to be defined: you likely forgot to import, pass, or provide it.\")}","frontmatter":{},"scope":{"config":{},"pageMetadata":{"title":"Project PoL Methodology","description":"The methodology behind CORE3's crypto project risk assessment — security, financial, operational, reputational, compliance, and dependency risks.","icon":"flask-vial","href":"/project-pol-methodology"}}},"mdxSourceWithNoJs":null},"mdxExtracts":{"tableOfContents":[{"title":"Security risks — smart contract audits, bug bounties, and monitoring","slug":"security-risks-—-smart-contract-audits-bug-bounties-and-monitoring","depth":2,"children":[],"tabId":"security"},{"title":"Financial risks — token economics, treasury, and liquidity analysis","slug":"financial-risks-—-token-economics-treasury-and-liquidity-analysis","depth":2,"children":[],"tabId":"financial"},{"title":"Operational risks — governance, development activity, and market integrity","slug":"operational-risks-—-governance-development-activity-and-market-integrity","depth":2,"children":[],"tabId":"operational"},{"title":"Reputational risks — incident history, social manipulation, and stakeholder quality","slug":"reputational-risks-—-incident-history-social-manipulation-and-stakeholder-quality","depth":2,"children":[],"tabId":"reputational"},{"title":"Compliance \u0026 regulatory risks — crypto compliance and jurisdictional exposure","slug":"compliance-\u0026-regulatory-risks-—-crypto-compliance-and-jurisdictional-exposure","depth":2,"children":[],"tabId":"compliance"},{"title":"Dependency risks — Bridges, oracles, infrastructure, and centralization vectors","slug":"dependency-risks-—-bridges-oracles-infrastructure-and-centralization-vectors","depth":2,"children":[],"tabId":"dependency"},{"title":"How Often Are Crypto Risk Metrics Updated?","slug":"how-often-are-crypto-risk-metrics-updated","depth":2,"children":[]}],"codeExamples":{}},"jsLinks":[],"subdomain":"hacken-efd4870a","siteName":"CORE3 Docs","title":"Project PoL Methodology - CORE3 Docs","navMaps":{"firstHrefInVersion":{},"firstHrefInLanguage":{}},"lastModified":"2026-02-25T14:13:28.897Z","originalFileLocation":"project-pol-methodology.mdx"},"headHtml":"\u003cscript data-mint-head>(function(){var d=document.documentElement,p=null;if(!p){try{p=localStorage.getItem(\"isDarkMode\")}catch(e){}if(p==='true')p='dark';else if(p==='false')p='light';if(p!=='light'\u0026\u0026p!=='dark'\u0026\u0026p!=='system')p=\"system\"}var r=p==='system'?(matchMedia(\"(prefers-color-scheme: dark)\").matches?'dark':'light'):p;d.classList.remove(r==='dark'?'light':'dark');d.classList.add(r);d.setAttribute(\"data-theme-preference\",p)})();\u003c/script>\u003cmeta data-mint-head name=\"description\" content=\"The methodology behind CORE3\u0026#x27;s crypto project risk assessment — security, financial, operational, reputational, compliance, and dependency risks.\">\u003cmeta data-mint-head name=\"application-name\" content=\"CORE3 Docs\">\u003cmeta data-mint-head name=\"generator\" content=\"Mintlify\">\u003clink data-mint-head rel=\"icon\" type=\"image/png\" sizes=\"192x192\" href=\"/mintlify-assets/_mintlify/favicons/hacken-efd4870a/Ju-jvz4z49rvQHoL/_generated/favicon/android-chrome-192x192.png\" media=\"(prefers-color-scheme: light)\">\u003clink data-mint-head rel=\"apple-touch-icon\" type=\"image/png\" sizes=\"180x180\" href=\"/mintlify-assets/_mintlify/favicons/hacken-efd4870a/Ju-jvz4z49rvQHoL/_generated/favicon/apple-touch-icon.png\">\u003clink data-mint-head rel=\"icon\" type=\"image/png\" sizes=\"16x16\" href=\"/mintlify-assets/_mintlify/favicons/hacken-efd4870a/Ju-jvz4z49rvQHoL/_generated/favicon/favicon-16x16.png\" media=\"(prefers-color-scheme: light)\">\u003clink data-mint-head rel=\"icon\" type=\"image/png\" sizes=\"32x32\" href=\"/mintlify-assets/_mintlify/favicons/hacken-efd4870a/Ju-jvz4z49rvQHoL/_generated/favicon/favicon-32x32.png\" media=\"(prefers-color-scheme: light)\">\u003clink data-mint-head rel=\"shortcut icon\" type=\"image/x-icon\" href=\"/mintlify-assets/_mintlify/favicons/hacken-efd4870a/Ju-jvz4z49rvQHoL/_generated/favicon/favicon.ico\" media=\"(prefers-color-scheme: light)\">\u003clink data-mint-head rel=\"icon\" type=\"image/png\" sizes=\"192x192\" href=\"/mintlify-assets/_mintlify/favicons/hacken-efd4870a/Ju-jvz4z49rvQHoL/_generated/favicon-dark/android-chrome-192x192.png\" media=\"(prefers-color-scheme: dark)\">\u003clink data-mint-head rel=\"icon\" type=\"image/png\" sizes=\"16x16\" href=\"/mintlify-assets/_mintlify/favicons/hacken-efd4870a/Ju-jvz4z49rvQHoL/_generated/favicon-dark/favicon-16x16.png\" media=\"(prefers-color-scheme: dark)\">\u003clink data-mint-head rel=\"icon\" type=\"image/png\" sizes=\"32x32\" href=\"/mintlify-assets/_mintlify/favicons/hacken-efd4870a/Ju-jvz4z49rvQHoL/_generated/favicon-dark/favicon-32x32.png\" media=\"(prefers-color-scheme: dark)\">\u003clink data-mint-head rel=\"shortcut icon\" type=\"image/x-icon\" href=\"/mintlify-assets/_mintlify/favicons/hacken-efd4870a/Ju-jvz4z49rvQHoL/_generated/favicon-dark/favicon.ico\" media=\"(prefers-color-scheme: dark)\">\u003cmeta data-mint-head property=\"og:title\" content=\"Project PoL Methodology - CORE3 Docs\">\u003cmeta data-mint-head property=\"og:description\" content=\"The methodology behind CORE3\u0026#x27;s crypto project risk assessment — security, financial, operational, reputational, compliance, and dependency risks.\">\u003cmeta data-mint-head property=\"og:site_name\" content=\"CORE3 Docs\">\u003cmeta data-mint-head property=\"og:url\" content=\"https://docs.core3.io/project-pol-methodology\">\u003cmeta data-mint-head property=\"og:type\" content=\"website\">\u003cmeta data-mint-head property=\"og:image\" content=\"https://hacken-efd4870a.mintlify.site/_mintlify/api/og/v2?division=Project+PoL\u0026amp;title=Project+PoL+Methodology\u0026amp;description=The+methodology+behind+CORE3%27s+crypto+project+risk+assessment+%E2%80%94+security%2C+financial%2C+operational%2C+reputational%2C+compliance%2C+and+dependency+risks.\u0026amp;theme=5b1c102f66710bcb6f17d128\u0026amp;signature=6e5ddcd2562e44563517b55e4d16e739ace265b1399bb4cfe5245400ebd516e9\">\u003cmeta data-mint-head property=\"og:image:width\" content=\"1200\">\u003cmeta data-mint-head property=\"og:image:height\" content=\"630\">\u003cmeta data-mint-head name=\"twitter:card\" content=\"summary_large_image\">\u003cmeta data-mint-head name=\"twitter:title\" content=\"Project PoL Methodology - CORE3 Docs\">\u003cmeta data-mint-head name=\"twitter:description\" content=\"The methodology behind CORE3\u0026#x27;s crypto project risk assessment — security, financial, operational, reputational, compliance, and dependency risks.\">\u003cmeta data-mint-head name=\"twitter:image\" content=\"https://hacken-efd4870a.mintlify.site/_mintlify/api/og/v2?division=Project+PoL\u0026amp;title=Project+PoL+Methodology\u0026amp;description=The+methodology+behind+CORE3%27s+crypto+project+risk+assessment+%E2%80%94+security%2C+financial%2C+operational%2C+reputational%2C+compliance%2C+and+dependency+risks.\u0026amp;theme=5b1c102f66710bcb6f17d128\u0026amp;signature=6e5ddcd2562e44563517b55e4d16e739ace265b1399bb4cfe5245400ebd516e9\">\u003cmeta data-mint-head name=\"twitter:image:width\" content=\"1200\">\u003cmeta data-mint-head name=\"twitter:image:height\" content=\"630\">\u003cmeta data-mint-head name=\"msapplication-config\" content=\"/mintlify-assets/_mintlify/favicons/hacken-efd4870a/Ju-jvz4z49rvQHoL/_generated/favicon/browserconfig.xml\">\u003cmeta data-mint-head name=\"apple-mobile-web-app-title\" content=\"CORE3 Docs\">\u003cmeta data-mint-head name=\"msapplication-TileColor\" content=\"#000000\">\u003clink data-mint-head rel=\"canonical\" href=\"https://docs.core3.io/project-pol-methodology\">\u003clink data-mint-head rel=\"alternate\" type=\"application/xml\" href=\"/sitemap.xml\">\u003clink data-mint-head rel=\"alternate\" type=\"text/markdown\" href=\"/project-pol-methodology.md\">\u003cscript data-mint-head type=\"application/ld+json\">{\"@context\":\"https://schema.org\",\"@graph\":[{\"@type\":\"Organization\",\"@id\":\"https://docs.core3.io/#organization\",\"name\":\"CORE3 Docs\",\"url\":\"https://docs.core3.io\",\"logo\":{\"@type\":\"ImageObject\",\"url\":\"https://mintcdn.com/hacken-efd4870a/019EJ2CsBtvgXXxs/images/Group2.svg?fit=max\u0026auto=format\u0026n=019EJ2CsBtvgXXxs\u0026q=85\u0026s=ef93b1dcc617ff497dbba2ef296145be\"}},{\"@type\":\"WebSite\",\"@id\":\"https://docs.core3.io#website\",\"name\":\"CORE3 Docs\",\"url\":\"https://docs.core3.io\",\"publisher\":{\"@id\":\"https://docs.core3.io/#organization\"}},{\"@type\":\"WebPage\",\"@id\":\"https://docs.core3.io/project-pol-methodology#webpage\",\"url\":\"https://docs.core3.io/project-pol-methodology\",\"name\":\"Project PoL Methodology\",\"description\":\"The methodology behind CORE3's crypto project risk assessment — security, financial, operational, reputational, compliance, and dependency risks.\",\"dateModified\":\"2026-02-25T14:13:28.897Z\",\"isPartOf\":{\"@id\":\"https://docs.core3.io#website\"},\"breadcrumb\":{\"@id\":\"https://docs.core3.io/project-pol-methodology#breadcrumb\"}},{\"@type\":\"BreadcrumbList\",\"@id\":\"https://docs.core3.io/project-pol-methodology#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"CORE3 Docs\",\"item\":\"https://docs.core3.io\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Project PoL Methodology\",\"item\":\"https://docs.core3.io/project-pol-methodology\"}]},{\"@type\":[\"Article\",\"TechArticle\"],\"@id\":\"https://docs.core3.io/project-pol-methodology#article\",\"headline\":\"Project PoL Methodology\",\"name\":\"Project PoL Methodology\",\"description\":\"The methodology behind CORE3's crypto project risk assessment — security, financial, operational, reputational, compliance, and dependency risks.\",\"url\":\"https://docs.core3.io/project-pol-methodology\",\"mainEntityOfPage\":{\"@id\":\"https://docs.core3.io/project-pol-methodology#webpage\"},\"dateModified\":\"2026-02-25T14:13:28.897Z\",\"publisher\":{\"@id\":\"https://docs.core3.io/#organization\"},\"isPartOf\":{\"@id\":\"https://docs.core3.io#website\"}}]}\u003c/script>\u003cscript data-mint-head type=\"application/ld+json\">{\"@context\":\"https://schema.org\",\"@type\":\"WebSite\",\"name\":\"CORE3 Docs\",\"publisher\":{\"@type\":\"Organization\",\"name\":\"CORE3 Docs\"},\"provider\":{\"@type\":\"Organization\",\"name\":\"Mintlify\",\"url\":\"https://mintlify.com\"}}\u003c/script>","agentPointerHref":"/project-pol-methodology.md","siteName":"CORE3 Docs","nav":{"global":null,"groups":[{"group":"Getting Started","pages":[{"title":"What is CORE3","icon":"shield-halved","href":"/what-is-core3"},{"title":"How CORE3 is Different","icon":"arrows-split-up-and-left","href":"/how-core3-is-different"},{"title":"CORE3 Platform Components","icon":"cubes","href":"/core3-components"}]},{"group":"API Reference","icon":"book-open","pages":[{"title":"Projects Data API","sidebarTitle":"Projects Data API (Beta)","icon":"database","href":"/projects-data-api"},{"title":"Exchanges Data API","sidebarTitle":"Exchanges Data API (Beta)","icon":"building-columns","href":"/exchanges-data-api"}]},{"group":"MCP","icon":"plug","pages":[{"title":"CORE3 MCP","sidebarTitle":"MCP overview","icon":"plug","href":"/mcp-overview"},{"title":"Getting started with CORE3 MCP","sidebarTitle":"Getting started","icon":"rocket","href":"/mcp-getting-started"},{"title":"CORE3 MCP tools reference","sidebarTitle":"Tools reference","icon":"list","href":"/mcp-tools-reference"}]},{"group":"Probability of Loss (PoL)","icon":"chart-line-down","pages":[{"title":"Probability of Loss (PoL)","description":"CORE3's unbiased, data-driven risk metric reflecting a project's risk exposure on a scale from 0 (Exceptional) to 100 (Critical risk).","icon":"chart-line-down","href":"/probability-of-loss"}]},{"group":"Project PoL","icon":"flask-vial","pages":[{"title":"Project PoL Methodology","icon":"flask-vial","href":"/project-pol-methodology"},{"title":"Project PoL Scoring Logic","description":"How CORE3 calculates the Project Probability of Loss score using baseline assessment and contextual adjustment modules.","icon":"calculator","href":"/project-pol-scoring-logic"}]},{"group":"CEX PoL","icon":"building-columns","pages":[{"title":"CEX PoL Methodology","icon":"building-columns","href":"/cex-pol-methodology"},{"title":"CEX PoL Scoring Logic","icon":"scale-balanced","href":"/cex-pol-scoring-logic"}]},{"group":"Trust \u0026 Transparency","icon":"certificate","pages":[{"title":"CORE3 Seals","icon":"certificate","href":"/core3-seals"},{"title":"Proof of Voice (PoV)","icon":"user-check","href":"/proof-of-voice"}]},{"group":"CORE3 for You","icon":"computer-mouse","pages":[{"title":"CORE3 for Retail Investors","icon":"user","href":"/core3-for-retail"},{"title":"CORE3 for Institutions","icon":"landmark","href":"/core3-for-institutions"},{"title":"CORE3 for Centralized Exchanges","icon":"arrow-right-arrow-left","href":"/core3-for-exchanges"},{"title":"CORE3 for Crypto Projects","icon":"rocket","href":"/core3-for-projects"},{"title":"CORE3 for Regulators","icon":"gavel","href":"/core3-for-regulators"},{"title":"CORE3 for Ecosystem Partners","icon":"puzzle-piece","href":"/core3-for-partners"}]},{"group":"About CORE3","icon":"compass","pages":[{"title":"Vision \u0026 Long-Term Direction","icon":"compass","href":"/vision"}]}]},"basePath":"","title":"Project PoL Methodology - CORE3 Docs","buildId":"dpl_8hoxaqFTU7hTr6A2fUraxAyjuiZo","deploymentId":"dpl_8hoxaqFTU7hTr6A2fUraxAyjuiZo","dynamics":[],"chunks":[]}