Ecosystem metrics
- New Repos
- 52
- New
- Commits
- 715
- down 3.6%
- Releases
- 4
- up 0.0%
- Contributors
- 47
- down 17.5%
- Merges
- 25
- up 25.0%
Activity Overview
Commits and releases over time
- Commits
- Releases
- Authors
Repository Explorer
No repositories match that filter.
10730 commits in all time
May 07, 2026 17:31 – Aug 05, 2026 17:31 UTC
Merge 2130c2fd0826b5e8b15d16979455b15a4a5e8a19 into fbc74d4f89bf4f7600c9f80f94f8da21c971b4d5
66bd56dd
pull/596/merge
8/345 ++ 63 --
Merge 876d9719628a1c06eafb4a2a026e0105c9d815b5 into 95d55a9b81145fcbc0a09023680b96b684f57b64
fbc74d4f
pull/595/merge
20/1,764 ++ 9 --
types: narrow post-quantum scheme identifiers to a Literal union
876d9719
feat/pq
2/8 ++ 4 --
Merge d32cbaa36fc66ad3449f4fd685ed4ff44ff724b4 into da0a0f56530ee6a406a5f4fcbcb7bc7ac373fb71
23babb5c
pull/381/merge
123/3,180 ++ 492 --
feat: switch to entropy instead of private key
c46c9a9e
falcon25
16/151 ++ 155 --
refactor: add more fnet reference updates
87b55447
falcon25
14/62 ++ 24 --
feat: switch to seed for SignFalconBundle
0f85ca35
falcon25
37/669 ++ 78 --
docs: add in falcon25 to mermaid diagram
9f402478
falcon25
1/7 ++ 0 --
feat: add in falcon25 support
affe8c4f
falcon25
73/1,985 ++ 277 --
refactor: add in onboarding and developer setting fixes for Falcon25
aeffe7c2
falcon25
9/125 ++ 11 --
refactor: update structure of file
d32cbaa3
falcon25
1/50 ++ 15 --
Merge ffd0657c6c8db9e612ca713966b2393bcb2d03c5 into dda085879f1868c14ccb115fb5f92f2b4f75c741
d61511fb
pull/6690/merge
38/2,518 ++ 3,923 --
Doc: Derive txn Note size limit from consensus bounds
The Note field doc hardcoded 1024 bytes, which went stale when v42 raised MaxAbsoluteTxnNoteBytes to 4096. Build it with Sprintf from bounds.MaxTxnNoteBytes, the same cross-version maximum the decoder uses, so the generated docs cannot drift again. Unlike the limits derived from evaluator constants, this changes generated output: 1024 becomes 4096 everywhere the Note doc appears.
ffd0657c
pull/6690/head
27/78 ++ 76 --
Merge 573f35ca525792c41bfcb0daad0bf5641f61856e into b8f983bbc7ec0565bb02686dff661b8d694c3ae5
884c341e
pull/594/merge
2/159 ++ 307 --
Merge e3967c6814e681eb68c57079d47a393387b7e948 into dda085879f1868c14ccb115fb5f92f2b4f75c741
09e3ca90
pull/6696/merge
7/10 ++ 10 --
agreement: bump sortition dependency to v1.1.1
e3967c68
pull/6696/head
7/10 ++ 10 --
docs: rewrite assets concept page around the runnable examples
573f35ca
feat/docs-assets
2/159 ++ 307 --
Doc: Correct README, tutorial, and jsonspec
These files are hand-maintained, not generated, and had drifted from the implementation: - tutorial.md described the pre-v41 LogicSig world. It now covers the four signature methods including post-quantum signatures, the LMsig and PQsig LogicSig fields and how they bind the authorizer's address into the signed message, that at most one delegation signature may be present, that validation is against the authorizer (AuthAddr when rekeyed), and that legacy Msig is rejected from consensus v41 onward, with goal's --legacy-msig escape hatch. Also fixes the "LogicSic" typo. - jsonspec.md conflated rules that json_ref enforces while parsing the whole text with rules enforced only on the extracted value. Classify each rule as whole-text or extraction. In particular, the old "Raw non-unicode characters not accepted" claim was wrong: invalid utf-8 parses, and becomes U+FFFD when a string value containing it is extracted. A \u escape with non-hex digits parses but errors on extraction (it becomes U+FFFD only in a key), and a null value parses but always errors on extraction. - TestParseRawNonUnicodeChar never tested invalid utf-8 (its input was valid utf-8 and its error cases failed for other reasons). It now feeds a genuine invalid byte through parse and extraction and asserts the U+FFFD replacement. - README.md points at the generated stack-types table and lists the assembler pseudo-ops (int, byte, addr, method) that appear in no opcode table.
fa5cc851
pull/6690/head
4/84 ++ 25 --
Doc: Correct and expand opcode descriptions
Document behavior that the descriptions omitted or got wrong: - The v13 box opcodes: shared boxAccessExtra text states the name length rule (1-64 bytes, MaxAppKeyLen), the availability rule, and the ClearState ban for every box opcode, not only those whose short description mentioned them. foreignBoxExtra spells out the app_box_* authorization matrix (AppForeignBoxReads for reads, AppFamilyBoxAccess plus same creator for everything else) and the family reentrancy rule; boxFamilyExtra applies the same reentrancy rule to an app's own boxes once it opts in. app_params_set explains what setting each flag grants. - itxn_begin's Fee description matched neither the group-based fee logic nor when fees are checked. Describe the actual default: the amount that would make the group's fees sufficient so far, with the new transaction counted as one base fee, and note that the real check happens at itxn_submit. - bnz documents the v13 varint offset encoding (previously it described only the two-byte form), including the forward/back reference points and that a branch to the start of its own instruction cannot be encoded. callsub points at bnz for the encoding. - State failure conditions: shl/shr fail if B > 63, divmodw fails on a zero divisor, bzero fails above 4096. - balance/min_balance params claimed an application id argument they do not take. voter_params_get and online_stake answer as of the balance round (320 rounds back), not the agreement round. - json_ref links to the JSON spec by URL (the relative link only worked in the repo) and assorted typo/spacing fixes, including the ec_multi_scalar_mul naming note that compared the opcode to itself.
fa60387d
pull/6690/head
27/832 ++ 497 --
opdoc: Return docVersion to a hand-bumped constant
Deriving docVersion from the current consensus LogicSigVersion meant new opcodes could not be documented or checked in CI until their consensus version was released. Make it a manually bumped package constant again, as it was before, so in-progress opcodes can be documented during development. The LogicSigVersion field in the langspec files stays consensus-derived, since it reports what the chain currently accepts, which can lag docVersion. Generated output is unchanged.
5090bc5e
pull/6690/head
1/8 ++ 4 --