Skip to content

Conversation

@Lchangliang
Copy link
Contributor

  • Restructure DKGSessionInfo to contain nested DKGSessionMetadata
  • Change ConfigV2Data threshold types from uint64 to uint128 for FixedPoint64 compatibility
  • Add getDKGState() view function returning 4 fields for debugging
  • Update DKGStartEvent to emit DKGSessionMetadata instead of full session info
  • Update spec documentation to reflect all structural changes

The DKGSessionInfo now contains:

  • metadata: DKGSessionMetadata (dealerEpoch, randomnessConfig, validator sets)
  • startTimeUs: uint64
  • transcript: bytes

This keeps the structure consistent with gravity-genesis-contract.

Description

Type of Change

  • 📚 Documentation (Non-breaking change; Changes in the documentation)
  • 🔧 Bug fix (Non-breaking change; Fixes an existing bug)
  • 🥂 Improvement (Non-breaking change; Improves existing feature)
  • 🚀 New feature (Non-breaking change; Adds functionality)
  • 🔐 Security fix (Non-breaking change; Patches a security issue)
  • 💥 Breaking change (Breaks existing functionality)

- Restructure DKGSessionInfo to contain nested DKGSessionMetadata
- Change ConfigV2Data threshold types from uint64 to uint128 for FixedPoint64 compatibility
- Add getDKGState() view function returning 4 fields for debugging
- Update DKGStartEvent to emit DKGSessionMetadata instead of full session info
- Update spec documentation to reflect all structural changes

The DKGSessionInfo now contains:
- metadata: DKGSessionMetadata (dealerEpoch, randomnessConfig, validator sets)
- startTimeUs: uint64
- transcript: bytes

This keeps the structure consistent with gravity-genesis-contract.
@github-actions
Copy link

🛡️ Security Audit Results

Security Audit Summary

Generated on: Thu Jan 15 14:08:06 UTC 2026
Commit: a07e9c0
Branch: 13/merge

Tools Executed

  • ✅ Slither: 1 reports
  • ✅ Mythril: 1 reports
  • ✅ 4naly3er: 1 reports
  • ✅ Aderyn: 0 reports

Next Steps

  1. Review all generated reports in the audit/ directory
  2. Prioritize High and Medium severity issues
  3. Address findings before deployment
  4. Consider additional manual security review

📁 Full reports available in GitHub Actions Artifacts

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