Skip to content

Conversation

@CluEleSsUK
Copy link
Contributor

dir

@CluEleSsUK CluEleSsUK requested a review from AnomalRoil February 9, 2023 10:47
@CluEleSsUK CluEleSsUK force-pushed the feature/include-version-at-compile branch from 8e1776c to d6527b6 Compare February 9, 2023 12:19
@CluEleSsUK CluEleSsUK merged commit 0afea01 into master Feb 9, 2023
@CluEleSsUK CluEleSsUK deleted the feature/include-version-at-compile branch February 9, 2023 12:55
let chainToUse
for (const chain of chains) {
const info = await chain.info()
if (info.schemeID === 'pedersen-bls-chained' || info.schemeID === 'pedersen-bls-unchained') {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What if it's "bls-unchained-on-g1" ??

Copy link
Contributor Author

@CluEleSsUK CluEleSsUK Feb 9, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We don't test it because we don't support it. This test started breaking because it previously assumed chains[0] was one that it could process. Since we added testnet-g, it is now chains[0] and blows up.
Once we merge a fix for the g1 swap, we can revert this (and just test against all the networks)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants