|
About the L1/L2 category
|
|
0
|
389
|
December 2, 2024
|
|
Pruning safety in the vProgs architecture
|
|
1
|
300
|
September 26, 2025
|
|
Data Availability Concerns
|
|
6
|
796
|
September 17, 2025
|
|
A Basic Framework For Proofs Stitching
|
|
2
|
671
|
August 24, 2025
|
|
# On transaction scopes and the visibility of the object DAG
|
|
0
|
290
|
August 20, 2025
|
|
Zoom-in: A formal backbone model for the vProg computation DAG
|
|
7
|
903
|
August 19, 2025
|
|
Concrete proposal for a synchronously composable verifiable programs architecture
|
|
3
|
3444
|
August 17, 2025
|
|
On the inherent tension between multileader consensus and inclusion-time proving
|
|
2
|
586
|
May 27, 2025
|
|
On the design of based ZK rollups over Kaspa's UTXO-based DAG consensus
|
|
8
|
3762
|
February 23, 2025
|
|
Additional practical considerations re hash function and zk opcodes
|
|
22
|
1777
|
February 12, 2025
|
|
Thoughts about covenant and async message standardization
|
|
0
|
467
|
January 31, 2025
|
|
Subnets sequencing commitments
|
|
5
|
718
|
January 31, 2025
|
|
L1<>L2 canonical bridge (entry/exit mechanism)
|
|
1
|
1140
|
January 28, 2025
|
|
Conflicting Proofs Policy
|
|
1
|
359
|
January 24, 2025
|
|
Fees and throughput regulation dynamics
|
|
3
|
1252
|
January 22, 2025
|
|
Updateable list of L1<>L2 topics to flesh out before finalizing design
|
|
0
|
1142
|
December 23, 2024
|
|
Atomic Composability and other considerations for L1/L2 support
|
|
0
|
6431
|
November 12, 2024
|