Hello friend! We both wrote Pure Swift ECC SDKs this summer

[Sajjon]

We seem to have been working on the same thing :D

Have a look at EllipticCurveKit. My goal is to finish my rewrite using EquationKit, I have got it working already in the equations branch which allows for pretty cool syntax:

///
/// Elliptic Curve on Short Weierstrass form (`𝑆`)
/// - Covers all elliptic curves char≠𝟚,𝟛
/// - Mixed Jacobian coordinates have been the speed leader for a long time.
///
///
/// # Equation
///      𝑆: 𝑦² = 𝑥³ + 𝑎𝑥 + 𝑏
/// - Requires: `𝟜𝑎³ + 𝟚𝟟𝑏² ≠ 𝟘`
///
public struct ShortWeierstraßCurve: CurveForm {


    private let a: Number
    private let b: Number
    public let galoisField: Field
    public let equation: Polynomial

    private let 𝑥＇: Polynomial
    private let 𝑦＇: Polynomial

    public init?(
        a: Number,
        b: Number,
        galoisField: Field
        ) {

        let 𝑝 = galoisField.modulus

        guard 𝟜𝑎³ + 𝟚𝟟𝑏² ≢ 𝟘 % 𝑝 ↤ [ 𝑎 ≔ a, 𝑏 ≔ b ] else { return nil }

        self.a = a
        self.b = b
        self.galoisField = galoisField
        self.equation = EllipticCurveForm.Weierstraß.short.substitute() {[ 𝑎 ≔ a, 𝑏 ≔ b ] }
        self.𝑥＇ = equation.differentiateWithRespectTo(𝑥)!
        self.𝑦＇ = equation.differentiateWithRespectTo(𝑦)!
    }
}

I have also begun implemented other curve forms than ShortWeierstraß, such as TwistedEdwards and Montgomery.

I saw you PR in CryptoSwift adding support for Scrypt which I am also working on currently.

I'm in need of it in the Zilliqa Swift SDK I am developing, for the export wallet function.

[shamatar]

Hello @Sajjon

I'll start wit the last question: Scrypt for CryptoSwift is unfortunately delayed, I couldn't make it fast enough and fight copy of write.

The purpose of the library was to

• Use for signatures as a replacement to secp256k1 and other C libs
• Use for fancy stuff like confidential transaction, lib
• Implement pairings and BLS signatures (for future Ethereum releases)
• Implement zkSNARK verification and proving for small circuits

There was no intention to make it abstract and based on some general underlying math package like "Sage", but more like pure EC arithmetics packages in other languages.

Regarding the curve forms - I'd focus on a twisted edwards first. Montgommery form is more interesting only for ECDH.

Sincerely, Alex

[Sajjon]

What is your goal time for a release build (using optmization) of Scrypt?

I forked your repo and fixed support for iOS yesterday. I also added a public iOS scheme to support Carthage and it works fine. I might do a PR if you want?

Regardign EC, I too think BLS would be pretty cool to have native support for. I might support it in EllipticCurveKit in the future. I have implemented Schnorr signatures appart form ECDSA.

Yes I wanted to support ECDH that is why I did Montgomery, with Montgomery ladder multiplication(using "mladd-1987-m-3")

@hyugit have also been developing some EllipticCurve Swift SDK. It would be nice for the community with one standard EllipticCurve SDK in Swift. As CryptoSwift is a standard for hashing algorithms. It would also be cool to move all Swift crypto repos into an organisation.

[shamatar]

How much did you get for one Scrypt operation? It should ideally be below 0.1 second for “weak” parameters (N=4096). I think C implementation has something like 0.016, while debug scheme I had was about 2.5. Please make a PR, I’ll check what’s going on and may be finally update it for CryptoSwift. One library sounds cool! Also there is huge room for improvement, for example, hashing to Edwards is completely different, and there is an alternative signature scheme on x25519 curve by Bernstein. Sincerely, Alex

…

________________________________ From: Alexander Cyon <[email protected]> Sent: Monday, September 24, 2018 1:19:16 PM To: shamatar/EllipticSwift Cc: Alexander; Comment Subject: Re: [shamatar/EllipticSwift] Hello friend! We both wrote Pure Swift ECC SDKs this summer (#1) What is your goal time for a release build (using optmization) of Scrypt<https://github.com/shamatar/scrypt-cryptoswift/>? I forked your repo and fixed support for iOS yesterday. I also added a public iOS scheme to support Carthage and it works fine. I might do a PR if you want? Regardign EC, I too think BLS would be pretty cool to have native support for. I might support it in EllipticCurveKit in the future. I have implemented Schnorr signatures appart form ECDSA. Yes I wanted to support ECDH that is why I did Montgomery, with Montgomery ladder multiplication<https://github.com/Sajjon/EllipticCurveKit/blob/equations/Source/EllipticCurve/Curve/CurveForms/MontgomeryCurve.swift#L164-L205>(using "mladd-1987-m-3"<http://www.hyperelliptic.org/EFD/g1p/auto-code/montgom/xz/ladder/mladd-1987-m.op3>) @hyugit<https://github.com/hyugit> have also been developing some EllipticCurve Swift SDK<https://github.com/hyugit/EllipticCurve>. It would be nice for the community with one standard EllipticCurve SDK in Swift. As CryptoSwift is a standard for hashing algorithms. It would also be cool to move all Swift crypto repos into an organisation. — You are receiving this because you commented. Reply to this email directly, view it on GitHub<#1 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AGKv9xVsJG0NUq9K1MpwIu9tJc5YdU8Tks5ueLGkgaJpZM4W1yxt>.

[Sajjon]

@shamatar I just tried it using N: 262144 (cost parameter) and that did not even complete in 20 minutes on iOS Simulator on my Macbook Pro 2016 (maxed hardware config) using optimization flags.

So yeah it is unfortunately too slow, even when using the C version of calculate. I tried to Profile the unit tests but got some errors, so no luck. Have you CPU time profiled calculate to see what takes time?

[hyugit]

pooling everything into one organization sounds good

[shamatar]

I’ll start working on a consolidation structure after finishing a work on extension fields and pairing operation

…

________________________________ From: Huang Yu <[email protected]> Sent: Saturday, September 29, 2018 12:43:16 PM To: shamatar/EllipticSwift Cc: Alexander; Mention Subject: Re: [shamatar/EllipticSwift] Hello friend! We both wrote Pure Swift ECC SDKs this summer (#1) pooling everything into one organization sounds good — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#1 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AGKv9yXbE1S2m_HN_jgvqvy6TEuWq3Oaks5uf0C0gaJpZM4W1yxt>.