From b9e0e0486e66a551b82674013315227852c975cd Mon Sep 17 00:00:00 2001
From: Pana <pana.wang@outlook.com>
Date: Fri, 16 Jan 2026 10:02:53 +0800
Subject: [PATCH] add cip 166

---
 CIPs/cip-167.md | 55 +++++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 55 insertions(+)
 create mode 100644 CIPs/cip-167.md

diff --git a/CIPs/cip-167.md b/CIPs/cip-167.md
new file mode 100644
index 0000000..e863289
--- /dev/null
+++ b/CIPs/cip-167.md
@@ -0,0 +1,55 @@
+---
+CIP No.: 167
+Title: Precompile for secp256r1 Curve Support
+Author: PanaW (@PanaW)
+Status: Draft
+Type: Spec Breaking
+Created: 2026-01-07
+Required CIPs: 
+---
+
+## Simple Summary
+
+Add precompiled contract for secp256r1 ECDSA signature verification with proper security checks
+
+## Abstract
+
+Introduce the `secp256r1` precompile as [EIP-7951](https://eips.ethereum.org/EIPS/eip-7951), which can efficiently perform ECDSA signature verification over the secp256r1 elliptic curve (also known as P-256 or prime256v1).
+
+## Motivation
+
+The secp256r1 elliptic curve is a NIST-standardized curve widely supported in modern secure hardware and authentication systems. Adding native support for secp256r1 signature verification to Ethereum enables several important use cases that are currently impossible or prohibitively expensive.
+
+Modern secure hardware devices, including Apple Secure Enclave, Android Keystore, HSMs, TEEs, and FIDO2/WebAuthn authenticators, use secp256r1 for key storage and signing operations. Native secp256r1 support enables sophisticated account abstraction patterns like device-native signing, multi-factor authentication, and simplified key management - ultimately reducing friction for mainstream adoption through familiar authentication flows.
+
+The secp256r1 curve is already widely supported across blockchain networks and protocols, including Layer 2 networks, enterprise blockchains, and interoperability protocols. This broad compatibility enables seamless integration with existing infrastructure while maintaining security through hardware-backed signing capabilities.
+
+This EIP supersedes RIP-7212 by implementing the same functionality with the same interface, but without the vulnerability.
+
+## Specification
+
+Same as [EIP-7951](https://eips.ethereum.org/EIPS/eip-7951). 
+
+## Rationale
+
+N/A
+
+## Backwards Compatibility
+
+This CIP is Spec Breaking.
+
+## Test Cases
+<!--Test cases for an implementation are mandatory for CIPs that are affecting consensus changes. Other CIPs can choose to include links to test cases if applicable.-->
+N/A
+
+## Implementation
+<!--The implementations must be completed before any CIP is given status "Final", but it need not be completed before the CIP is accepted. While there is merit to the approach of reaching consensus on the specification and rationale before writing code, the principle of "rough consensus and running code" is still useful when it comes to resolving many discussions of API details.-->
+N/A
+
+## Security Considerations
+<!--All CIPs must contain a section that discusses the security implications/considerations relevant to the proposed change. Include information that might be important for security discussions, surfaces risks and can be used throughout the life cycle of the proposal. E.g. include security-relevant design decisions, concerns, important discussions, implementation-specific guidance and pitfalls, an outline of threats and risks and how they are being addressed. CIP submissions missing the "Security Considerations" section will be rejected. a CIP cannot proceed to status "Final" without a Security Considerations discussion deemed sufficient by the reviewers.-->
+N/A
+
+## Copyright
+
+Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/).
\ No newline at end of file