Skip to content

[234] Guidance on Ambiguous Signatures  #2030

Open
@near-dx

Description

@near-dx

Title:
Guidance on Ambiguous Signatures
Description:
"This can be solved by having different keys for any chains that you can't prove could have ambiguous transactions."

To help devs know when to ensure distinct keys for ambiguous chains, can we enumerate a top 10-20 list of chains where these ambiguous transactions could occur?

Info

Reported by: charles ([email protected]) - Open in Gleap
Location: US
Type: 💡 FEATURE REQUEST

🔗 Open share link
🌍 Open ticket in Gleap

Metadata

browserName: Chrome(125.0.0.0)
userAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/125.0.0.0 Safari/537.36
browser: Chrome
systemName: MacOS
sessionDuration: 5465
devicePixelRatio: 2
screenWidth: 1512
screenHeight: 982
innerWidth: 1284
innerHeight: 823
currentUrl: https://docs.near.org/build/chain-abstraction/wallet
language: en-US
sdkVersion: 10.1.0
sdkType: javascript
environment: prod

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    Status

    No status

    Status

    Backlog 📖

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions