Skip to content

Navigation Menu

Explore
By company size
By use case
By industry
View all solutions
Topics
- AI
- DevOps
- Security
- Software Development
- View all
Explore
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Dismiss alert

AntelopeIO / leap Public

Notifications You must be signed in to change notification settings
Fork 73
Star 118

Code
Issues 114
Pull requests 3
Actions
Projects
Wiki
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Actions
Projects
Wiki
Security
Insights

Replace hacky version of `calculate_max_depth` with simpler one.#2320

Merged

greg7mdp merged 4 commits intomainAntelopeIO/leap:mainfrom incr_merkleAntelopeIO/leap:incr_merkleCopy head branch name to clipboard

Mar 18, 2024

+8-50

Conversation Commits4 (4)Checks Files changed

Commits

Commits on Mar 18, 2024

Replace hacky version of calculate_max_depth with simpler one.
greg7mdp
committed
Use Matt's non-floating point implementation of calculate_max_depth.
greg7mdp
committed
Update comment.
greg7mdp
committed
Use improved version from Matt.
greg7mdp
committed

Footer

© 2025 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Docs
Contact

You can’t perform that action at this time.