module alias for secp256k1

[Syn-McJ]

What context is your feature request related to?

Some web3 projects use secp256k1.swift library and adding them together with web3swift causes the "multiple targets named 'secp256k1'" error.

What solution would you like?

I'm not sure if there is a way to fix it on my side yet, but perhaps it's worth renaming secp256k1 target or using a module alias or something. Migrating to secp256k1.swift would probably work too, but obviously is more effort and might not be worth it.

Any additional context?

No response

[yaroslavyaroslav]

We're discussed this request a long time ago actually.

We're definitely should migrate to any external and actively maintained implementation of it. But unfortunately there's no straight timeline about that that we can share with you.