Ecosystem metrics

New Repos
18
down 99.0%
Commits
899
down 0.3%
Releases
3
down 70.0%
Contributors
50
up 0.0%
Merges
48
up 60.0%

Repository Explorer

6631 commits in all time May 29, 2026 20:50 – Aug 27, 2026 20:51 UTC
Ganainmtech devportal
Merge pull request #657 from algorandfoundation/main
Nav and throughput fixes: main -> main-dist
Git Commit 4cb7c04a Branch main-dist Document 5/15 ++ 35 --
Ganainmtech devportal
Merge 7276a8e301c92c6feb21e94c647ac7c780074148 into 137e52932bd16bcf04774e43901c79ad68891b7b
Git Commit fe8a088c Branch pull/657/merge Document 5/15 ++ 35 --
Ganainmtech devportal
Merge pull request #656 from algorandfoundation/docs/fix-block-size-param
Git Commit 7276a8e3 Branch main Document 1/1 ++ 1 --
algorandskiy go-algorand
Merge 59cba6cba2031ec7cfeecd641d2254cb48d5b71c into 8284e3ff259d591042b2c10038ea9f8a19be6d46
Git Commit 17699c79 Branch pull/6711/merge Document 4/621 ++ 38 --
algorandskiy go-algorand
add verifiedTxnCtx size assertion
Git Commit 59cba6cb Branch pull/6711/head Document 1/13 ++ 0 --
Ganainmtech devportal
Merge ce21ed4e9204d649fc70046e548884fbf7325efa into 9929271cd64f2d0256973943a683c9131823a1a8
Git Commit f7310101 Branch pull/656/merge Document 1/1 ++ 1 --
Ganainmtech devportal
style: prettier formatting
Git Commit ce21ed4e Branch docs/fix-block-size-param Document 1/1 ++ 1 --
Ganainmtech devportal
docs: correct block size limit to 5242880 bytes
Git Commit 7362a444 Branch docs/fix-block-size-param Document 1/1 ++ 1 --
algorandskiy go-algorand
Merge 9f7df394a827988932c31f0c808ca843085da86a into 8284e3ff259d591042b2c10038ea9f8a19be6d46
Git Commit c31c31ef Branch pull/6711/merge Document 4/608 ++ 38 --
algorandskiy go-algorand
by-value cache maps with verifiedTxnCtx entries
Git Commit 9f7df394 Branch pull/6711/head Document 2/79 ++ 12 --
gabrielkuettel vibekit
docs: drop the unreferenced explore gif and mp4
2 MB of media nothing links to. AGENTS.md says docs/ holds exactly the two
canonical design documents; this restores that.
Git Commit 4bd06ea3 Branch main Document 2/0 ++ 0 --
gabrielkuettel vibekit
docs: the one upstream change post-quantum accounts need
Falcon keypairs work today and PQ signatures are live on chain (algod 5.0.0,
v42). The address half is already solved -- algosdk 3.7.0 exports
addressFromPQKey, verified byte-identical to a hand-rolled derivation of the
spec. The gap is that keystore-node feeds a BIP39 seed straight into Falcon
generateKey, skipping the PQK domain separation the SDK applies to a 25-word
mnemonic, so the same words yield a different key.

Records why deriving an address on top of today's key is a footgun rather
than a shortcut, and what to ask the keystore team for.
Git Commit 018ad96a Branch main Document 1/32 ++ 0 --
gabrielkuettel vibekit
skills(use-vibekit): PQ signatures are live, correct the claim
MainNet and TestNet both report algod 5.0.0 AVAIL, which carries v42. The
previous note said networks reject post-quantum signatures until the upgrade
lands -- wrong, and it was shipping inside the CLI binary. The remaining
blocker is the keystore's key derivation, not the chain.
Git Commit 4034234a Branch main Document 2/4 ++ 3 --
gabrielkuettel vibekit
skills(use-vibekit): warn against deriving a PQ address with algosdk
algosdk 3.7.0 already exports addressFromPQKey and returns a well-formed
address for a keystore Falcon key -- verified identical to a hand-rolled
derivation of the spec. It is a trap: the SDK derives the keypair from a
25-word mnemonic via pq25WordMnemonicToSeed (the PQK step), the keystore
derives it from a BIP39 seed. Same words, different key, different address,
and funds at that address would not be recoverable in any other wallet.
Git Commit 9e26c897 Branch main Document 2/11 ++ 1 --
jannotti go-algorand
Merge ffdc4ff53d4a83af310cafe14645ef006e433ff8 into 8284e3ff259d591042b2c10038ea9f8a19be6d46
Git Commit 7f9cd35e Branch pull/6703/merge Document 49/2,826 ++ 950 --
jannotti go-algorand
Merge remote-tracking branch 'upstream/master' into f512-support
Git Commit ffdc4ff5 Branch f512-support Document 60/2,866 ++ 3,931 --
jannotti go-algorand
CR Review
Git Commit 3fb73ccc Branch f512-support Document 2/87 ++ 41 --
gabrielkuettel vibekit
skills(use-vibekit): document key derivation, and that falcon is not an account
vibekit keystore passes everything through to the Foundation keystore, whose
generate subcommands were undocumented -- so an agent asked for a
post-quantum account reaches for 'generate falcon' and reports success. It
mints a real Falcon-1024 keypair, but the keystore implements none of the
account derivation in the Algorand PQ spec: no PQK seed step, no
canonical-salt search, no PQA address. The key has no address, never appears
in keystore accounts, and without the PQK step the same mnemonic yields a
different keypair than a spec-compliant wallet. Post-quantum signatures also
need the v42 consensus upgrade before any network accepts them.

Also warns never to run 'generate seed' unannounced or echo the phrase.
Git Commit 390c1843 Branch main Document 2/41 ++ 1 --
jannotti go-algorand
comment about seeds
Co-authored-by: Cosimo Bassi <65770425+cusma@users.noreply.github.com>
Git Commit 208da7a6 Branch f512-support Document 1/2 ++ 1 --
Ganainmtech devportal
Merge pull request #655 from algorandfoundation/docs/block-throughput
Git Commit 9929271c Branch main Document 2/6 ++ 4 --
algorandskiy go-algorand
apply interning for addresses and consensus version
Git Commit 78d7d2b8 Branch pull/6711/head Document 2/97 ++ 10 --
Ganainmtech devportal
Update src/content/docs/getting-started/why-algorand.mdx
Co-authored-by: JBScaled <164410456+JBScaled@users.noreply.github.com>
Git Commit c6c1a0f2 Branch main Document 1/1 ++ 1 --
Ganainmtech devportal
Merge cd09941172a0f78a5fef611017d89b371ed30938 into 522755619852833e282c35eb841e062d03142814
Git Commit b0be8793 Branch pull/655/merge Document 2/6 ++ 4 --
Ganainmtech devportal
Update src/content/docs/getting-started/why-algorand.mdx
Co-authored-by: JBScaled <164410456+JBScaled@users.noreply.github.com>
Git Commit cd099411 Branch docs/block-throughput Document 1/1 ++ 1 --