Add support for data encoding with unit tests and update Solidity interfaces #1
Conversation
…mple ganache test
najienka
changed the title
…public key data type
| ```js | ||
| import { ethers, getBytes } from "ethers"; | ||
| import { Blocklock, SolidityEncoder, encodeCiphertextToSolidity } from "blocklockjs"; | ||
| import { MockBlocklockReceiver__factory } from "../types"; // Generated by Typechain |
There was a problem hiding this comment.
mockblocklock - sounds funny ;p
There was a problem hiding this comment.
I'm thinking for consistency with our website and blogs, we might need to stop using the name blocklock and use timelock throughout in all our code bases.
There was a problem hiding this comment.
yeah I think this makes sense - the time vs chainheight differentiation for drand vs decrypt won’t matter for most users
There was a problem hiding this comment.
Okay, I've added to the list of items for the next release.
| @@ -7,5 +7,5 @@ export default { | |||
| useESM: true, | |||
| }], | |||
| }, | |||
| testTimeout: 50000, | |||
There was a problem hiding this comment.
jesus that's a long test :p
There was a problem hiding this comment.
That's right. The local ganache integration takes some time to start and stop. Worth revisiting and seeing if it can be switched to using Anvil programmatically.
| out.setZ(z) | ||
| return out | ||
| } | ||
|
|
||
| public deserialiseFp2([x, y]: [bigint, bigint]): Fp2 { | ||
| const xx = new mcl.Fp() |
There was a problem hiding this comment.
as elsewhere, we should consider nuking mcl if possible
Co-authored-by: Robin Müller <33422394+azixus@users.noreply.github.com>
Co-authored-by: Robin Müller <33422394+azixus@users.noreply.github.com>
…into refactoring
Co-authored-by: PM <3749956+CluEleSsUK@users.noreply.github.com>
Co-authored-by: PM <3749956+CluEleSsUK@users.noreply.github.com>
Co-authored-by: PM <3749956+CluEleSsUK@users.noreply.github.com>
Co-authored-by: PM <3749956+CluEleSsUK@users.noreply.github.com>
No description provided.