Ecosystem metrics

New Repos
8
New
Commits
673
down 13.3%
Releases
5
up 0.0%
Contributors
51
up 2.0%
Merges
21
down 8.7%

Repository Explorer

8484 commits in all time Jul 16, 2026 18:55 – Oct 14, 2026 18:55 UTC
jannotti go-algorand
Merge 249fc923bf1190d69d92fd9a78e353cc4f86fe91 into 95f79d3770cf6cbe656512b0d8aa5f48e2a14504
Git Commit 6dedd36c Branch pull/6774/merge Document 30/4,965 ++ 19,966 --
jannotti go-algorand
Upgrade msgp to 1.1.66
Git Commit 249fc923 Branch pull/6774/head Document 30/4,965 ++ 19,966 --
github go-algorand
add Go Benchmark (go) benchmark result for 95f79d3770cf6cbe656512b0d8aa5f48e2a14504
Git Commit 6870a58a Branch gh-pages Document 1/445 ++ 1 --
lempira algokit-core
Merge 452ef7209b98568bdd33196ac90cf3c69327119f into 591f8771e8c06b916e29f6223e27af728780063a
Git Commit 53b65de2 Branch pull/357/merge Document 25/850 ++ 13 --
vividvisit go-algorand
nodecontrol: clarify LaggedStdIo comments (#6730)
Signed-off-by: vividvisit <vividvisit@outlook.com>
Git Commit 95f79d37 Branch master Document 1/3 ++ 3 --
lempira algokit-core
feat(transact): v42 size limits and heartbeat challenge discount
Raises the transaction limits consensus v42 relaxed, and adds the heartbeat
field that claims the challenge fee discount.

Two of the existing limits were not merely stale, they were rejecting
transactions the network accepts: extra program pages was capped at 3 against
v42's 7, and total app args at 2048 against 16384. The program-size check
derives from the page count, so it was wrong through the same root. Both now
carry the absolute value, with the old number kept alongside as BASE_ to mark
where the per-byte surcharge begins rather than where rejection does. Note and
logicsig limits follow the same pairing. Every value is taken from
config/consensus.go at v5.0.0-stable.

Heartbeat gains challenge_discount on codec tag "c". It is a request, not an
assertion: the node grants it only if the account is genuinely under challenge.
Declining it has to encode identically to omitting it, or the transaction ID
would change for a heartbeat that asked for nothing, so it follows the
Option<bool> plus is_false_opt convention already used by non_participation.

estimate_size is deliberately unchanged. Falcon-1024 is not priced by byte
count: signatureFeeContribution dispatches a flat 2e6 factor per scheme
regardless of signature length. Inflating the size estimate would feed
calculate_fee, which still multiplies size by fee_per_byte, and produce a fee
that does not match the network. The fee factor constants are added here so the
usage-based engine can apply them correctly.

One existing test used 17 args of 700 bytes as both too many and too large.
That total is legal under the new cap, so it is resized to keep its meaning.
Git Commit 452ef720 Branch feat/transact-v42-constants Document 4/145 ++ 4 --
lempira algokit-core
feat(transact): pqsig wire format and PQ address derivation
Adds the consensus v42 post-quantum signature envelope and the address
derivation that goes with it.

PQSignature carries the scheme, salt, public key, and signature under the
codec tags go-algorand uses ("sch"/"slt"/"pk"/"sig"), all omitempty. It can
sit at the top of a SignedTransaction as "pqsig", or one level down inside a
LogicSignature to delegate a program; both slots count toward the existing
single-delegation rule, so a transaction still cannot carry two.

A post-quantum address is the hash of the public key plus a salt, resampled
until the result is not a valid Edwards25519 point. That keeps the new
addresses from colliding with real ed25519 public keys. The point check lands
in algokit_crypto and deliberately matches go's permissive decoder: it accepts
non-canonical encodings and small-order points, because a stricter predicate
would reject salts that the network accepts and derive the wrong address.

The crate does not bundle a Falcon-1024 implementation. PQKeyAndSigner lets a
caller supply one, mirroring the existing Ed25519KeyAndSigner shape.

Signature fields now omit all-zero values as well as absent ones, since an
unsigned envelope and a zero-filled one must encode identically.

Test data is vendored under algokit_test_artifacts/pq with secret keys
stripped; it gets re-pointed at the shared fixtures in a later phase.
Git Commit bfa24220 Branch feat/transact-v42-constants Document 22/705 ++ 9 --
jannotti go-algorand
Merge 4d8f71d946363eefb1771a94dcf57c40171323b2 into be1fdce17d32d4a4909adb9895c1ad9d9d08c592
Git Commit 83c88d6b Branch pull/6741/merge Document 36/1,479 ++ 179 --
Merge 3077806171555c1f9ae5cb13907bfc3b0ebfbfd8 into 361d3066ffaca4241991cc6563403417bf562ecf
Git Commit 3c285183 Branch pull/17/merge Document 4/3,363 ++ 1,957 --
fix(deps): update all non-major dependencies
Git Commit 30778061 Branch renovate/all-minor-patch Document 4/3,363 ++ 1,957 --
jannotti go-algorand
Txn: add the ls post-quantum account scheme for LogicSigs
Git Commit 4d8f71d9 Branch pull/6741/head Document 36/1,479 ++ 179 --
github go-algorand
add Go Benchmark (go) benchmark result for be1fdce17d32d4a4909adb9895c1ad9d9d08c592
Git Commit 7029f1f9 Branch gh-pages Document 1/445 ++ 1 --
jannotti go-algorand
Txn: collect each PQ scheme's description into one table (#6772)
Git Commit be1fdce1 Branch master Document 18/298 ++ 235 --
joe-p go-algorand
Merge ba3bc00a84dd50c18a7b10d06bff9a882954d4a6 into e3be5c1706832d938cb6e95a6c8997c6f241c744
Git Commit cb2c6552 Branch pull/6773/merge Document 10/456 ++ 10 --
PhearZero ARCs
Merge a0bdb48336b379e3b7623048ab8c4eb65748829e into 750f8a3065a96f9a6e27711d72c92c59255dda7f
Git Commit a61362c5 Branch pull/488/merge Document 19/44 ++ 2,619 --
PhearZero ARCs
chore: migrate arc-87 reference
Git Commit a0bdb483 Branch pull/488/head Document 19/44 ++ 2,619 --
jannotti go-algorand
Merge 1b5c24e1519be376121d6345a714470dff6c2193 into e3be5c1706832d938cb6e95a6c8997c6f241c744
Git Commit 740934e2 Branch pull/6772/merge Document 18/298 ++ 235 --
jannotti go-algorand
Address review: tighten PQ scheme table tests
Check every pqSchemes entry for nil fields rather than only those reached
through PQTestSchemes, and drop assertions that held by construction.
PQTestSchemes no longer carries MaxSignatureSize; the one test that needed
it reads the bound from the scheme table instead.
Git Commit 1b5c24e1 Branch pull/6772/head Document 4/23 ++ 27 --