Pudgy Penguins 백서

Pudgy Penguins

원문

bitpro가 원문에서 글자만 모은 내용이에요. 표·그림·수식은 빠지거나 깨질 수 있어요. 전체 3쪽 중 3쪽

, or compatibility challenges that affect the asset’s continuity or utility. Legal ownership risk: Depending on jurisdiction and platform terms, holders may not acquire legal ownership or enforceable rights with respect to the crypto-asset, which could affect recourse options in the event of fraud, misrepresentation, or loss. Network usage risk: A decline in activity or utility on the associated network may reduce the economic relevance of the crypto-asset, diminishing its value and undermining its role as a medium of exchange or utility token. Compliance risk: Holders may be subject to local obligations related to tax reporting, anti-money laundering (AML), or sanctions compliance. Failure to meet these obligations could result in penalties or legal consequences. Cross-border risk: Transactions involving the crypto-asset may span multiple jurisdictions, creating uncertainty around applicable laws, conflict-of-law issues, or barriers to enforcement and regulatory clarity. Incentive misalignment risk: The crypto-asset’s economic model may depend on incentives for participants such as validators, developers, or users. If these incentives become insufficient or distorted, network participation and security may decline. Token distribution concentration risk: A disproportionate concentration of token supply in the hands of a small number of holders (“whales”) may enable price manipulation, governance capture, or coordinated sell-offs that impact market stability and community trust. Misuse risk: The crypto-asset may be used for illicit purposes (e.g., money laundering, ransomware payments), exposing the project to reputational harm or regulatory scrutiny, even if such activity is beyond the issuer’s control. Utility risk: The expected utility of the token within its ecosystem may fail to materialise due to low adoption, under-delivery of promised features, or technical incompatibility, undermining its value proposition. Inflation or deflation risk: The token’s supply mechanics (minting, burning, vesting, etc.) may introduce inflationary or deflationary dynamics that affect long-term holder value and purchasing power within the network. Secondary market dependence risk: The ability of users to access, trade, or price the token may depend entirely on secondary markets. If such platforms restrict or delist the asset, liquidity and discoverability may be severely impacted. Taxation risk: The treatment of crypto-assets for tax purposes may vary by jurisdiction and change over time. Holders may face unanticipated tax liabilities related to capital gains, income, or transaction activity. Bridging risk: If the crypto-asset exists on multiple blockchains via bridging protocols, vulnerabilities in those bridges may lead to de-pegging, duplication, or irrecoverable losses affecting token integrity and user balances. Incompatibility risk: The crypto-asset may become technically incompatible with evolving wallets, smart contracts, or infrastructure components, limiting its usability and support within the broader crypto ecosystem. Network governance risk: If governance decisions (e.g., protocol upgrades, treasury usage) are controlled by a limited set of actors or are poorly defined, outcomes may not align with broader user interests, leading to fragmentation or disputes. Economic abstraction risk: Users may be able to interact with the network or ecosystem without using the crypto-asset itself (e.g., via gas relayers, fee subsidies, or wrapped tokens), reducing demand for the token and weakening its economic role. Page 25 Dust and spam risk: The crypto-asset may be vulnerable to dust attacks or spam transactions, creating bloated ledgers, user confusion, or inadvertent privacy exposure through traceability. Jurisdictional blocking risk: Exchanges, wallets, or interfaces may restrict access to the crypto-asset based on IP geolocation or jurisdictional policies, limiting user access even if the asset itself remains transferable on-chain. Environmental or ESG risk: The association of the crypto-asset with energy-intensive consensus mechanisms or unsustainable tokenomics may conflict with emerging environmental, social, and governance (ESG) standards, affecting institutional adoption. I.4 Project implementation-related risks Development risk: The project may experience delays, underdelivery, or changes in scope due to unforeseen technical complexity, resource constraints, or coordination issues, impacting timelines and stakeholder expectations. Funding risk: The continued implementation of the project may depend on future funding rounds, revenue generation, or grants. A shortfall in available capital may impair the project’s ability to execute its roadmap or retain key personnel. Roadmap deviation risk: Strategic shifts, pivots, or reprioritization may result in deviations from the originally published roadmap, potentially leading to dissatisfaction among community members or early supporters. Team dependency risk: The project’s success may be heavily dependent on a small number of core contributors or founders. The departure, unavailability, or misconduct of these individuals could significantly impair execution capacity. Third-party dependency risk: Certain components of the project (e.g., infrastructure providers, integration partners, oracles) may rely on external entities whose performance or continuity cannot be guaranteed, introducing operational fragility. Talent acquisition risk: The project may face challenges recruiting and retaining qualified professionals in highly competitive areas such as blockchain development, AI engineering, security, or compliance, slowing implementation or reducing quality. Coordination risk: As decentralised or cross-functional teams grow, internal coordination and alignment across engineering, product, legal, and marketing domains may become difficult, leading to delays, errors, or strategic drift. Security implementation risk: Insufficient diligence in implementing security protocols (e.g., audits, access controls, testing pipelines) during development may introduce critical vulnerabilities into the deployed system. Scalability bottleneck risk: Architectural decisions made early in the project may limit performance or scalability as usage grows, requiring resource-intensive refactoring or redesign to support broader adoption. Vendor lock-in risk: Reliance on specific middleware, cloud infrastructure, or proprietary tools may constrain the project’s flexibility and increase exposure to price shifts, service outages, or licencing changes. Compliance misalignment risk: Product features or delivery mechanisms may inadvertently breach evolving regulatory requirements, particularly around consumer protection, token functionality, or data privacy, necessitating rework or geographic limitations. Community support risk: The project’s success may rely on active developer or user participation. If the community fails to engage or contribute as anticipated, ecosystem momentum and resource leverage may decline. Governance deadlock risk: If project governance (e.g., DAO structures or steering committees) lacks clear decision-making processes or becomes fragmented, the project may face delays or paralysis in critical strategic decisions. Page 26 Incentive misalignment risk: Implementation plans may fail to maintain consistent alignment between stakeholders such as developers, token holders, investors, and users, undermining cooperation or long-term sustainability. Marketing and adoption risk: Even with timely technical delivery, the project may fail to gain market traction, user onboarding, or brand recognition, reducing the effectiveness of its deployment. Testing and QA risk: Inadequate testing coverage, staging environments, or quality assurance processes may allow critical bugs or regressions to reach production, causing service degradation or user loss. Scope creep risk: Expanding project objectives without adequate resource reallocation or stakeholder alignment may dilute focus and overextend the development team, compromising quality or deadlines. Interoperability risk: Implementation plans involving cross-chain or cross-platform integration may encounter compatibility issues, protocol mismatches, or delays in third-party upgrades. Legal execution risk: If foundational legal structures (e.g., entities, IP assignments, licencing) are not finalised or enforceable across key jurisdictions, the project may face friction during scaling, partnerships, or fundraising. I.5 Technology-related risks Smart contract risk: The crypto-asset may rely on smart contracts that, if improperly coded or inadequately audited, can contain vulnerabilities exploitable by malicious actors, potentially resulting in asset loss, unauthorised behaviour, or permanent lock-up of funds. Protocol risk: The underlying blockchain protocol may contain unknown bugs, suffer from unanticipated behaviour, or experience edge-case failures in consensus, finality, or synchronisation, leading to disruptions in network operation. Bridge risk: If the crypto-asset is deployed across multiple chains via bridging infrastructure, the underlying bridge may be vulnerable to exploit, misconfiguration, or oracle manipulation, threatening asset integrity across networks. Finality risk: Some blockchains may exhibit probabilistic or delayed finality, making transactions theoretically reversible within short windows. This can lead to issues in cross-chain settlements or operational reliability. Node centralization risk: If the network depends on a small number of validators or infrastructure providers to maintain consensus or data availability, it may be susceptible to downtime, censorship, or coordinated manipulation. Data integrity risk: In decentralised environments, reliance on off-chain data (e.g., oracles or external feeds) introduces the possibility of incorrect or manipulated information entering the system and triggering undesired outcomes. Versioning and upgrade risk: Protocol upgrades, forks, or version mismatches between nodes and clients can introduce compatibility issues or destabilise service availability, particularly if coordination or governance processes are insufficient. Storage and archival risk: The technical infrastructure supporting the crypto-asset may be vulnerable to data loss or corruption, particularly in cases involving third-party storage solutions, partial nodes, or decentralised file systems. Interoperability risk: Integration with third-party tools, blockchains, or application layers may rely on APIs, SDKs, or interfaces that change without notice or suffer from inconsistencies, potentially breaking user functionality or asset movement. Scalability risk: The underlying technology may not scale effectively under high usage conditions, leading to network congestion, transaction delays, fee spikes, or degraded user experience. Cryptographic risk: The system relies on current cryptographic standards for key generation, digital signatures, and hashing. Advances in computing (e.g., quantum computing) or undiscovered flaws may undermine these protections in the future. Page 27 Permissioning or access control risk: If token behaviour or network features are governed by privileged roles (e.g., admin keys, multisigs), improper key management, role abuse, or governance capture could impact fairness or security. Decentralization illusion risk: Despite being labelled “decentralised,” critical components (e.g., governance, token distribution, node operation) may be technically or operationally centralised, concentrating risk and reducing resilience. Latency and synchronisation risk: Distributed networks may experience propagation delays, inconsistent state views, or latency in consensus confirmation, introducing unpredictability in transaction ordering and agent coordination. Frontend dependency risk: End users may rely on centralised interfaces (e.g., websites, wallets, APIs) to interact with the asset, which if compromised or taken offline, can block access despite the network itself being operational. Misconfiguration risk: Errors in smart contract deployment, token configuration, permission settings, or network parameters can result in unintended behaviour, including frozen assets, incorrect balances, or bypassed restrictions. Monitoring and observability risk: Insufficient logging, alerting, or metrics may prevent the timely detection of technical issues, exploits, or usage anomalies, limiting the project’s ability to respond to emergent threats. Software dependency risk: Core components may depend on open-source libraries or packages that are unmaintained, vulnerable, or deprecated, exposing the asset to cascading failures or inherited security flaws. Time drift and clock sync risk: Distributed ledgers that rely on timestamping may face issues if nodes do not maintain consistent system time, impacting consensus, block ordering, or event sequencing. Blockchain immutability risk: Once deployed, certain design flaws or oversights may be difficult or impossible to correct due to the immutable nature of smart contracts or protocol rules, necessitating workarounds or forks. I.6 Mitigation measures Risk mitigation comprises open source developments, partial reliance on audited third-party blockchains like Ethereum and Solana, and ongoing improvements based on community feedback. Project expansion into real-world partnerships further stabilises the ecosystem against some volatility risks. Page 28 Part J – Information on the sustainability indicators in relation to adverse impact on the climate and other environment-related adverse impacts J.1 Adverse impacts on climate and other environment-related adverse impacts Mandatory Information on principal adverse impacts on the climate S.1 Name Simple Action Limited S.2 Relevant legal entity identifier 6EH6 S.3 Name of the crypto-asset PENGU S.4 Consensus Mechanism See H.4 S.5 Incentive Mechanisms and Applicable Fees See H.5 S.6 Beginning of the period to which the disclosure relates 2025-10-15 S.7 End of the period to which the disclosure relates 2026-10-15 S.8 Energy consumption 6,110.24 kWh / a S.9 Energy consumption sources and methodologies www.archax.com/dlt-sustainability-assessment Supplementary Information on the principal adverse impacts on the climate and other environment- related adverse impacts of the consensus mechanism As the project is under the 500,000 kWh threshold for energy consumption, this section is not required. Page 29
프로젝트로 돌아가기