Skip to content

Integrate agg changes on crypto#978

Closed
ssd04 wants to merge 1 commit intorc/supernovafrom
integrate-crypto-aggregate-updates
Closed

Integrate agg changes on crypto#978
ssd04 wants to merge 1 commit intorc/supernovafrom
integrate-crypto-aggregate-updates

Conversation

@ssd04
Copy link
Contributor

@ssd04 ssd04 commented Jan 27, 2026

No description provided.

@ssd04 ssd04 self-assigned this Jan 27, 2026
@codecov
Copy link

codecov bot commented Jan 27, 2026

Codecov Report

❌ Patch coverage is 66.66667% with 4 lines in your changes missing coverage. Please review.
✅ Project coverage is 37.64%. Comparing base (05006fc) to head (ce29749).

Files with missing lines Patch % Lines
crypto/signing/bls/bls.go 66.66% 2 Missing and 2 partials ⚠️
Additional details and impacted files
@@               Coverage Diff                @@
##           rc/supernova     #978      +/-   ##
================================================
+ Coverage         36.23%   37.64%   +1.41%     
================================================
  Files                87       87              
  Lines             20589    17573    -3016     
================================================
- Hits               7460     6616     -844     
+ Misses            12462    10287    -2175     
- Partials            667      670       +3     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

// VerifyAggregatedSig verifies aggregated signature of BLS MultiSig
func (b *bls) VerifyAggregatedSig(pubKeysSigners [][]byte, message []byte, aggSig []byte) error {
return b.multiSigner.VerifyAggregatedSig(pubKeysSigners, message, aggSig)
pubKeys, err := b.convertBytesToPubKeys(pubKeysSigners)
Copy link
Contributor Author

Choose a reason for hiding this comment

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

this should behave as before, until now this convert was done in crypto multi signer

Copy link
Contributor Author

Choose a reason for hiding this comment

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

we can analyse to cache here pubkeys and avoid conversion (which takes quite some time ~60ms)

Choose a reason for hiding this comment

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

yes... it will add some overhead here... the 60 ms...

github.com/mitchellh/mapstructure v1.5.0
github.com/multiversx/mx-chain-core-go v1.4.0
github.com/multiversx/mx-chain-crypto-go v1.3.0
github.com/multiversx/mx-chain-crypto-go v1.3.1-0.20260127130843-3c6c4667127e

Choose a reason for hiding this comment

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

do not forget actual release

// VerifyAggregatedSig verifies aggregated signature of BLS MultiSig
func (b *bls) VerifyAggregatedSig(pubKeysSigners [][]byte, message []byte, aggSig []byte) error {
return b.multiSigner.VerifyAggregatedSig(pubKeysSigners, message, aggSig)
pubKeys, err := b.convertBytesToPubKeys(pubKeysSigners)

Choose a reason for hiding this comment

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

yes... it will add some overhead here... the 60 ms...

@ssd04
Copy link
Contributor Author

ssd04 commented Jan 28, 2026

This will be on hold for now. Changed multiversx/mx-chain-crypto-go#53 to add new methods for the signing methods.

@ssd04 ssd04 marked this pull request as draft January 28, 2026 09:17
@ssd04 ssd04 closed this Jan 30, 2026
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.

2 participants