Ecosystem metrics
- New Repos
- 25
- up 1150.0%
- Commits
- 381
- down 16.4%
- Releases
- 2
- up 100.0%
- Contributors
- 33
- down 2.9%
- Merges
- 11
- up 83.3%
Activity Overview
Commits and releases over time
- Commits
- Releases
- Authors
Repository Explorer
No repositories match that filter.
8005 commits in all time
Aug 19, 2026 23:35 – Nov 17, 2026 23:35 UTC
Merge 93ef58d0f689471da368e5acf2bc43d7c721b27b into 31883696f74799aa501420f226b9c442d395c0d5
45c42492
pull/473/merge
4/37 ++ 6 --
Merge 40f83c8942fb82bde166d26286a02fc5978d7daa into c55e01fd7aa3b1fc90916c036d6153f832f7f379
5d391a53
pull/264/merge
1/3 ++ 0 --
docs: archive notice in readme
40f83c89
docs/archive_notice
1/3 ++ 0 --
Merge e40a2306d620f2e972e255af6667f553d9103037 into e46aea5466a1152af6e08f83555ed16cfcd89f49
2096fb1c
pull/6752/merge
14/6,640 ++ 24 --
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.
e40a2306
feat/state_override
7/26 ++ 23 --
refactor: allow downstream app to set iOS chain
93ef58d0
feat/keychain-access-group
4/37 ++ 6 --
Merge 5844bef1fa0a6cb6bf24adee5340b0b08aa92bf3 into c2384e895f6f24251f2fc880c7335658cab2b42e
1ab6ecae
pull/37/merge
7/79 ++ 74 --
Merge remote-tracking branch 'upstream/main' into refactor/v2-noble-sync
5844bef1
pull/37/head
3/18 ++ 3 --
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>
0a67749e
feat/state_override
4/205 ++ 6 --
Merge f01e124e7c3a95b26cf318fecc530e6e00815e17 into 361d3066ffaca4241991cc6563403417bf562ecf
25235b28
pull/17/merge
4/3,335 ++ 1,988 --
fix(deps): update all non-major dependencies
f01e124e
renovate/all-minor-patch
4/3,335 ++ 1,988 --
Merge 0a4088760bfa11316fce38a219165ae3c1dc96a7 into cfe2e364b80e466defbb7e066f63e7c9a9ca6717
65a8d779
pull/203/merge
1/1 ++ 0 --
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>
5e44e138
feat/state_override
4/119 ++ 134 --
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>
640f280b
feat/state_override
8/188 ++ 94 --
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>
64446a58
feat/state_override
5/244 ++ 37 --
refactor: allow downstream app to set iOS chain
2a2e3834
feat/keychain-access-group
4/37 ++ 6 --
refactor: fix iOS warnings (#471)
31883696
main
83/265 ++ 175 --