mirror of
https://github.com/lux-apps/papers.git
synced 2026-10-30 18:15:21 +00:00
zeekay
6d75dc0464
Lux Partners Limited is not the entity behind this work. Every place the old name stood — copyright lines, site footers, brand config, legal and compliance text — now names the company that actually holds it. lux.fund is the exception and is not renamed to match: that site belongs to Lux Assets Management LLC, a different company, and it says so. Two kinds of line were left for a person rather than rewritten. A dated news item recording that Lux Partners Limited was established in the Isle of Man is a historical fact, and renaming it would falsify the record. And a sentence asserting that the company is domiciled in the Isle of Man is a claim about a jurisdiction, not a name — an Inc or an LLC is not an Isle of Man company, so swapping the name there would assert something untrue.
94 lines
3.1 KiB
TeX
94 lines
3.1 KiB
TeX
\section{Conclusion}
|
|
|
|
%% ============================================================================
|
|
|
|
ZAP achieves the highest single-core serialization throughput (42M encode ops/sec, 156M decode ops/sec) and lowest tail latency (19.8$\mu$s p99) of any protocol tested. The zero-allocation design eliminates GC-induced consensus timeouts, which remain a measurable risk with gRPC ($1.7 \times 10^{-6}$ per million rounds) and a significant risk with JSON-RPC ($2.8 \times 10^{-3}$).
|
|
|
|
For blockchain consensus transport---where schemas are fixed, nodes are pre-authenticated, and tail latency determines finality---ZAP is the optimal choice. For general-purpose RPC requiring schema evolution, FlatBuffers is the best zero-copy alternative.
|
|
|
|
\vspace{1em}
|
|
\noindent\textbf{Availability.} The ZAP implementation is available at \texttt{github.com/luxfi/zap}. The benchmark suite is in \texttt{zap/bench/} and \texttt{zap/*\_test.go}.
|
|
|
|
\bibliographystyle{plain}
|
|
\begin{thebibliography}{12}
|
|
|
|
\bibitem{zapwire}
|
|
Kelling, Z.
|
|
\textit{ZAP: Zero-Allocation Binary Wire Protocol for Consensus Transport}.
|
|
Lux Industries Inc, 2023.
|
|
|
|
\bibitem{quasar}
|
|
Kelling, Z.
|
|
\textit{Quasar Consensus: Dual-Certificate Quantum-Secure Finality}.
|
|
Lux Industries, Inc., 2025.
|
|
|
|
\bibitem{grpc}
|
|
Google.
|
|
\textit{gRPC: A High-Performance, Open-Source Universal RPC Framework}.
|
|
\url{https://grpc.io}, 2015.
|
|
|
|
\bibitem{protobuf}
|
|
Google.
|
|
\textit{Protocol Buffers: Language-Neutral, Platform-Neutral Extensible Mechanism for Serializing Structured Data}.
|
|
\url{https://protobuf.dev}, 2008.
|
|
|
|
\bibitem{capnp}
|
|
Varda, K.
|
|
\textit{Cap'n Proto: Insanely Fast Data Interchange Format}.
|
|
\url{https://capnproto.org}, 2013.
|
|
|
|
\bibitem{flatbuf}
|
|
Google.
|
|
\textit{FlatBuffers: Memory Efficient Serialization Library}.
|
|
\url{https://flatbuffers.dev}, 2014.
|
|
|
|
\bibitem{Protobuf-mux}
|
|
Protocol Labs.
|
|
\textit{Protobuf-mux: Protobuf Serialization with Stream Multiplexing}.
|
|
\url{https://protobuf.dev}, 2017.
|
|
|
|
\bibitem{quic}
|
|
Iyengar, J. and Thomson, M.
|
|
\textit{QUIC: A UDP-Based Multiplexed and Secure Transport}.
|
|
RFC 9000, IETF, 2021.
|
|
|
|
\bibitem{zapdb}
|
|
Jain, M. et al.
|
|
\textit{BadgerDB: Fast Key-Value Store in Go}.
|
|
Dgraph Labs, 2017.
|
|
|
|
\bibitem{goruntime}
|
|
The Go Authors.
|
|
\textit{A Guide to the Go Garbage Collector}.
|
|
\url{https://tip.golang.org/doc/gc-guide}, 2022.
|
|
|
|
\bibitem{epyc}
|
|
AMD.
|
|
\textit{AMD EPYC 7003 Series Processors Software Optimization Guide}.
|
|
AMD Publication 56665, Rev 3.00, 2022.
|
|
|
|
\bibitem{mpc}
|
|
Kelling, Z. and Seesahai, V.
|
|
\textit{Universal Threshold Signatures}.
|
|
Lux Industries Inc, 2021.
|
|
|
|
% --- Named-competitor scaffold (Apr 2026) ---
|
|
|
|
\bibitem{kcchubuffer}
|
|
Chu, K.C. (2024).
|
|
\textit{buffer-benchmarks: Benchmarking Protobuf, FlatBuffers, and Cap'n Proto on Go and Rust}.
|
|
\url{https://github.com/kcchu/buffer-benchmarks}
|
|
|
|
\bibitem{chronoxorbench}
|
|
chronoxor. (2024).
|
|
\textit{CppSerialization: Performance comparison of C++ serialization protocols (Cap'n Proto, FBE, Flatbuffers, Protobuf, JSON)}.
|
|
\url{https://github.com/chronoxor/CppSerialization}
|
|
|
|
\bibitem{grpcperformance}
|
|
gRPC Authors. (2024).
|
|
\textit{gRPC Performance Benchmarks}.
|
|
\url{https://grpc.io/docs/guides/benchmarking/}
|
|
|
|
\end{thebibliography}
|
|
|