Is there any plans to support EIP-7212/4521? Literally supports passkey signature on TRON

[giki0318]

Background
EIP-4521 is an Ethereum Improvement Proposal designed to provide native support for secp256r1 (P-256) signature verification. Since Passkey signatures are based on the FIDO2 and WebAuthn standards, which rely on secp256r1 as their cryptographic foundation, supporting EIP-4521 is crucial for enabling Passkey-based on-chain interactions.

Rationale
Why should this feature exist?
Cross-chain compatibility:

Passkey is at the core of modern passwordless authentication technologies. Supporting EIP-4521 would enhance TRON's integration capabilities within both the Web3 and Web2 ecosystems.
Many Web2 services, such as Google, Apple, and Microsoft authentication systems, have already widely adopted Passkey technology.
User experience improvement:

Users can seamlessly interact with on-chain applications using Passkey signatures, reducing the complexity of traditional key management.
It increases user security by minimizing risks associated with private key mismanagement.
Future compatibility:

EIP-4521 provides a standardized way to verify secp256r1 signatures, making it highly relevant for TRON-supported use cases such as DApps and wallets.
Use cases
Identity authentication: Users can authenticate themselves with Passkey signatures, enabling on-chain decentralized identity (DID) functionalities.
Authorization requests: Users can authorize transactions or resource access on-chain using Passkey signatures.
Cross-chain interactions: Supporting secp256r1 will enhance TRON's compatibility in multi-chain ecosystems.
Specification
EIP-4521 proposes introducing a new opcode to efficiently verify secp256r1 signatures. Does TRON plan to implement a similar mechanism to facilitate on-chain verification of Passkey signatures?

Test Specification
Is there any plan to introduce secp256r1 verification support within TRON’s smart contract framework?
Will TRON support new opcodes to simplify secp256r1 signature verification?
Can existing TRON node APIs be extended to enable secp256r1 signature verification?
Scope of Impact
Impact on TRON:

Enhances support for modern cryptographic standards such as WebAuthn and FIDO2.
Strengthens TRON’s competitiveness in terms of user experience and security.
Impact on existing projects:

It is essential to confirm whether adding secp256r1 support would affect TRON's current signature verification logic.
Implementation
Are there any plans to implement this feature?
Is there a roadmap for integrating secp256r1 support into TRON’s smart contract and verification framework?
Are there plans to provide functionalities similar to those proposed in EIP-4521?
Are we willing to assist in implementing this feature?
We are more than willing to collaborate and support TRON in implementing secp256r1 signature verification, especially for enabling Passkey-based on-chain interactions.

[endiaoekoe]

hi, @giki0318
1.do you mean RIP-7212( now it is moved from EIP to RIP category and renamed RIP-7212)?
2. EIP-4521 seems like to be a proposal about NFT standards.
can you confirm the 2 things above？

[DongDongSunny]

Not sure for Tron's security plan. But from security prospective, from my investigation, now Tron link use SM2 and secp256k1 the same as Ethereum, in terms of secp256r1, I would say all of them have comparable security.

[GrothenDI]

Not sure for Tron's security plan. But from security prospective, from my investigation, now Tron link use SM2 while Ethereum use secp256k1, in terms of secp256r1, I would say all of them have comparable security.

Tron link vs Ethereum? Did you mean a Ethereum wallet?

[DongDongSunny]

@GrothenDI I mean the Tron blockchain. And Tron wallet use secp256k1 to add signature, thus Tron chain support both secp256k1 and sm2 crypto now.