Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(core, ffi): should accept bigint inputs #24
fix(core, ffi): should accept bigint inputs #24
Changes from all commits
6dfef64
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I imagine we have functions like
func serializeInputs(_ int32Array: [Int32]) -> [String]
// TODO: Add proper BigNumber library
// For now can mock with
struct BigNumber
and thenBigNumber("1532423423432")
func serializeInputs(_ BNArray: [BigNumber]) -> [UInt8]
Since Outputs and Inputs are symmetrical, and there's really no "output", perhaps we can just call this serializeInputs? If we think it is confusing to not have a serializeOutputs method we can just have it be identical / alias to serializeInputs.
Then similarly for deserialization
func deserializeInputs(_ strArray: [String]) -> [BigNumber]
That way the fact that we serialize to strings is an implementation detail (this could change in the future) and we can easily add serialization methods for various types
Use of BigNumber in Swift seems like a separate issue and more of an app concern for now, so just mocking this with a basic type wrapping string in app/tests seems OK for now
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we can compute over BigNumber before calling
generateProof
(there should be a
toString
like function in such library)but if we can handle
serialize_inputs
anddeserialize_inputs
in rust it could be more easier for swift developers?I prefer not to have these two functions
serializeInputs
anddeserializeInputs
in swift