L1/L2
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| About the L1/L2 category |
|
0 | 303 | December 2, 2024 |
| Data Availability Concerns |
|
2 | 80 | July 14, 2025 |
| On the inherent tension between multileader consensus and inclusion-time proving |
|
2 | 492 | May 27, 2025 |
| A Basic Framework For Proofs Stitching |
|
0 | 352 | April 2, 2025 |
| On the design of based ZK rollups over Kaspa's UTXO-based DAG consensus |
|
8 | 3414 | February 23, 2025 |
| Additional practical considerations re hash function and zk opcodes |
|
22 | 1618 | February 12, 2025 |
| Thoughts about covenant and async message standardization |
|
0 | 428 | January 31, 2025 |
| Subnets sequencing commitments |
|
5 | 622 | January 31, 2025 |
| L1<>L2 canonical bridge (entry/exit mechanism) |
|
1 | 968 | January 28, 2025 |
| Conflicting Proofs Policy |
|
1 | 324 | January 24, 2025 |
| Fees and throughput regulation dynamics |
|
3 | 1184 | January 22, 2025 |
| Updateable list of L1<>L2 topics to flesh out before finalizing design |
|
0 | 1047 | December 23, 2024 |
| Atomic Composability and other considerations for L1/L2 support |
|
0 | 6222 | November 12, 2024 |