Ecosystem metrics

Commits
382
down 16.6%
Releases
2
up 100.0%
Contributors
32
down 5.9%
Merges
11
up 83.3%

Repository Explorer

7988 commits in all time Aug 19, 2026 21:37 – Nov 17, 2026 21:37 UTC
joe-p go-algorand
Merge e40a2306d620f2e972e255af6667f553d9103037 into e46aea5466a1152af6e08f83555ed16cfcd89f49
Git Commit 2096fb1c Branch pull/6752/merge Document 14/6,640 ++ 24 --
JBScaled devportal
Merge pull request #695 from algorandfoundation/docs/lora-naming
docs: use "LORA" consistently on hand-written pages
Git Commit ccce1b81 Branch main Document 10/35 ++ 35 --
joe-p go-algorand
simulate: report override failures as requests and finish the API docs
Return only "simulation panicked" when a panic is recovered in Simulate,
so the 500 body no longer echoes the recovered Go value; the value still
goes to the log. Fix the StartEvaluator comment to list LatestTotals
instead of the always-erroring LookupLatest.

Report an account whose pending rewards cannot be settled as an invalid
override rather than a 500, matching the other checks that reject state
the evaluator cannot handle. The "params not found for creator" cases
keep returning internal errors: both sides of the comparison read the
raw ledger, so an override cannot be responsible.

Document the 1024 item limit, and move the semantics that were attached
to $ref siblings (delta shape, box names as keys, allowed box actions,
local-state-schema scope) into the parent type descriptions, which
survive the oas2 to oas3 conversion.

Drop required from SimulateBlockOverride.round and set x-omitempty: false
instead. The generated type keeps the round without omitempty, so an
explicit round 0 survives go-codec's empty-value omission, while the
spec no longer marks an optional field as both required and nullable.
Git Commit e40a2306 Branch feat/state_override Document 7/26 ++ 23 --
acfunk xHD-Wallet-API-ts
Merge 5844bef1fa0a6cb6bf24adee5340b0b08aa92bf3 into c2384e895f6f24251f2fc880c7335658cab2b42e
Git Commit 1ab6ecae Branch pull/37/merge Document 7/79 ++ 74 --
acfunk xHD-Wallet-API-ts
Merge remote-tracking branch 'upstream/main' into refactor/v2-noble-sync
Git Commit 5844bef1 Branch pull/37/head Document 3/18 ++ 3 --
JBScaled devportal
Merge bbdc899610522d26f877b731b17875f01524f3c6 into d01651fef55be744794d876e7f2fa155eed779c5
Git Commit cbe7e652 Branch pull/695/merge Document 10/35 ++ 35 --
JBScaled devportal
Merge branch 'main' into docs/lora-naming
Git Commit bbdc8996 Branch docs/lora-naming Document 99/99 ++ 39 --
JBScaled devportal
Merge pull request #694 from algorandfoundation/docs/frontmatter-descriptions
docs: update frontmatter descriptions on hand-written pages
Git Commit d01651fe Branch main Document 100/100 ++ 40 --
joe-p go-algorand
simulate: prevent panics and bound work under state overrides
Settle rewards in buildStateOverlay at the start header's rewards level
only, check each ledger account with checkPendingRewards before any call
that panics on overflow, and recover panics in Simulate.

Report StartEvaluator and GenerateBlock failures as invalid requests
only when an empty block evaluates from the ledger's own state, so that
ledger faults are not blamed on the overrides.

Limit a request to MaxStateOverrides overridden items, since each one is
looked up on the ledger before the transaction group is checked.

Advance a round in TestStateOverrideBlockValidation, which failed when
the test environment started at genesis.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Git Commit 0a67749e Branch feat/state_override Document 4/205 ++ 6 --
Merge f01e124e7c3a95b26cf318fecc530e6e00815e17 into 361d3066ffaca4241991cc6563403417bf562ecf
Git Commit 25235b28 Branch pull/17/merge Document 4/3,335 ++ 1,988 --
fix(deps): update all non-major dependencies
Git Commit f01e124e Branch renovate/all-minor-patch Document 4/3,335 ++ 1,988 --
Merge 0a4088760bfa11316fce38a219165ae3c1dc96a7 into cfe2e364b80e466defbb7e066f63e7c9a9ca6717
Git Commit 65a8d779 Branch pull/203/merge Document 1/1 ++ 0 --
ETHURAM awesome-algorand
Add Fluid to Wallet Providers
Git Commit 0a408876 Branch pull/203/head Document 1/1 ++ 0 --
joe-p go-algorand
simulate: report evaluator failures under overrides as invalid requests
Errors from eval.StartEvaluator and BlockEvaluator.GenerateBlock are
reported as InvalidRequestError when state is overridden, so an
overridden Bonus that overflows the proposer payout no longer returns a
500. This replaces checkRewards, which repeated the evaluator's rewards
arithmetic to the same end.

Bound an overridden timestamp only on the start round, using the
MaxTimestampIncrement of the simulated block's protocol as MakeBlock
does. Earlier rounds have no later timestamp derived from them.

Document that creating an app at the ID of a deleted one keeps the
boxes and local states that outlived the deletion.

Share the fixed-size byte and address conversions in the API layer,
inline validateAppParams, and re-read the start round header only when
there is an overlay.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Git Commit 5e44e138 Branch feat/state_override Document 4/119 ++ 134 --
joe-p go-algorand
simulate: tighten state override validation
Require the round of a block override. The generated field was a plain
value, so an omitted round was taken to be round 0. It is now nullable
in the spec, which makes it a pointer that can be checked.

Reject overrides from which the simulated round's rewards cannot be
paid, instead of letting the evaluator fail with an internal error.

Store the zero address for an auth-addr override equal to the account's
own address, as apply.Rekey does.

Convert override lists with a shared helper, and drop a duplicated
comment about rewards overflow.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Git Commit 640f280b Branch feat/state_override Document 8/188 ++ 94 --
joe-p go-algorand
simulate: patch balance round agreement data per overridden field
An override of Balance or a participation field replaced the account's
agreement data at the balance round with its overridden state at the start
round, except that a Balance override of an account not online at the start
round was ignored. Neither is right for an account whose status changed since
the balance round. One that has gone offline kept its old stake under a
Balance override, and lost its stake and keys under any participation field
override. One that registered after the balance round gained stake that
agreement does not yet count.

Without a Status override, keep the account's status at the balance round. If
it was online then, replace only the overridden fields of its online data
there. If it was not, it has no online data. A Status override still applies
as of the balance round, using the start round state.

GetKnockOfflineCandidates read the same data, which is now as of the balance
round, so derive candidate data from the overridden account at the start
round.

Cover accounts that went offline or came online after the balance round, and
unchanged circulation for a Balance override of an offline account.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Git Commit 64446a58 Branch feat/state_override Document 5/244 ++ 37 --
algolog ff-py-sdk
Add support for quantum accounts
* Folks-Finance/algorand-js-sdk@e5eba1d
Git Commit bc3aba50 Branch main Document 28/294 ++ 131 --
ipaleka frontend
Updated API page
Git Commit d832a562 Branch main Document 2/10 ++ 3 --
Merge a46ad2182ffc41b6e66d02a47b0586b2257fe6e3 into 859b511f3342b0107897305e79819de9fa573ecf
Git Commit c183cfcc Branch pull/470/merge Document 4/30 ++ 7 --
Merge 5ae77ca8c4026717acb4b898e1a8cc06bcda2695 into 51522a1bd373f68d1af03dfac8ef3e1ea278cc80
Git Commit 6f9bc5a3 Branch pull/76/merge Document 3/133 ++ 263 --