Closed arnetheduck closed 4 years ago
Currently we have two "adapters" (https://github.com/status-im/nim-eth/blob/master/eth/keys/secp.nim and https://github.com/status-im/nim-libp2p/blob/master/libp2p/crypto/secp.nim) of the raw interface found in this repo - to join them together, I'd like to:
secp256k1_abi.nim
secp256k1
nim-eth
nim-libp2p
Plan B would be to create a separate ABI repo and a nice repo on top, but this seems overkill.
Also, we have some modifications to upstream (https://github.com/status-im/secp256k1/pull/2/commits/4afc920fe79fc5c853fc76638ada8101e9aba377 and https://github.com/status-im/secp256k1/pull/2/commits/1766dc808621f8a6e91282a321ddabce4352e624) - these could potentially be moved into this repo so that we rely on a "clean" upstream repo.
Currently we have two "adapters" (https://github.com/status-im/nim-eth/blob/master/eth/keys/secp.nim and https://github.com/status-im/nim-libp2p/blob/master/libp2p/crypto/secp.nim) of the raw interface found in this repo - to join them together, I'd like to:
secp256k1_abi.nim
in line with https://github.com/arnetheduck/nim-sqlite3-abi/blob/master/sqlite3_abi.nim as it exports the raw C ABI to nimsecp256k1
in this reponim-eth
andnim-libp2p
Plan B would be to create a separate ABI repo and a nice repo on top, but this seems overkill.
Also, we have some modifications to upstream (https://github.com/status-im/secp256k1/pull/2/commits/4afc920fe79fc5c853fc76638ada8101e9aba377 and https://github.com/status-im/secp256k1/pull/2/commits/1766dc808621f8a6e91282a321ddabce4352e624) - these could potentially be moved into this repo so that we rely on a "clean" upstream repo.