Files
zeekay 7cf87b230b node-unified is the node
The module already called itself github.com/luxfi/node while containing no node
in Go: cmd/luxd was twenty-one lines that printed the size of a few types, and
the Go column of the matrix measured a VM plugin. A repo that fetches the thing
it claims to be has not replaced it, so the Go sources move in — 1515 files,
the daemon and everything under it — and the build reaches outside this module
for nothing.

Rust and C++ sit beside it unchanged and are still measured against it by the
differential. That is the point of one repo: the reference implementation and
the two ports are the same checkout, so parity is a thing you can run rather
than a thing you assert.

Verified: builds, and the closure carries no lux-private — checked at build time
rather than believed. The daemon starts twelve chains on a local network
(P X C Q Z A B G K M F, plus D through its plugin) and reports healthy.
2026-09-07 16:15:25 -07:00

25 lines
868 B
Go

// Copyright (C) 2019-2025, Lux Industries Inc. All rights reserved.
// See the file LICENSE for licensing terms.
// Package sender provides p2p.Sender implementations over ZAP and gRPC transports.
//
// ZAP is the default transport with zero-copy serialization and minimal overhead.
// gRPC support can be added with the grpc build tag for testing compatibility.
//
// Build tags:
//
// go build # ZAP only (default, production)
// go build -tags=grpc # gRPC support (for testing/compatibility)
//
// Usage:
//
// // ZAP transport (default)
// s := sender.ZAP(zapConn)
//
// // gRPC transport (requires -tags=grpc)
// s := sender.GRPC(senderpb.NewSenderClient(grpcConn))
//
// Both return p2p.Sender with identical behavior, just different wire protocol.
// ZAP provides ~5-10x faster serialization and ~30-50% lower CPU usage.
package sender