Files
zeekay f4ee7a0525 Publish under the org, not a person
Bylines, paper authorship, correspondence addresses and the founder blurb under
each post named an individual. They name the organisation that published the
work instead: the brand on posts and pages, the research byline on papers, and
research@ in place of a personal address. Both are what these repositories
already used elsewhere — nothing new was coined.

Co-authors are untouched. Where a paper named someone else alongside, they stay
named; only the one byline changed. Bibliography entries, running heads,
PDF metadata and affiliations move with it, so a citation still resolves to
whoever the cited paper names.

Sample and fixture data uses the placeholder name these tests already use
elsewhere, so no assertion changed meaning.
2026-09-01 08:58:10 -07:00

100 lines
3.4 KiB
BibTeX

@misc{p3q-verifier,
author = {Lux Industries, Inc.},
title = {p3q-verifier: Audit-gated Rust verifier crate for the
strict-PQ STARK proof backend},
year = {2026},
howpublished = {github.com/luxfi/p3q/crates/p3q-verifier}
}
@techreport{pulsar,
author = {Lux Research},
title = {{LP-073}: Pulsar --- Module-{LWE} Rank-$k$ Threshold {ML-DSA}
for Permissionless Validator Sets},
number = {LP-073},
institution = {Lux Industries, Inc.},
year = {2026},
howpublished = {\url{https://github.com/luxfi/pulsar}},
note = {Lux's own threshold {ML-DSA} (FIPS~204) over Module-{LWE} at
general rank~$k$; canonical {LP-073}. Distinct from Corona
(rank~1) and from Ringtail (\cite{ringtail}).}
}
@misc{ringtail,
author = {Cecilia Boschini and Darya Kaviani and Russell W. F. Lai and
Giulio Malavolta and Akira Takahashi and Mehdi Tibouchi},
title = {Ringtail: Practical Two-Round Threshold Signatures from {LWE}},
year = {2024},
howpublished = {Cryptology ePrint Archive, Paper 2024/1113;
IEEE Symposium on Security and Privacy (S\&P) 2025},
url = {https://eprint.iacr.org/2024/1113},
note = {Academic two-round lattice threshold (IACR ePrint 2024/1113, IEEE S\&P 2025).
Not a Lux artifact; do not relabel as "Corona" or "Pulsar".}
}
@techreport{fri-paper,
author = {Eli Ben-Sasson and Iddo Bentov and Yinon Horesh and
Michael Riabzev},
title = {Fast {Reed-Solomon} Interactive Oracle Proofs of
Proximity},
number = {TR17-134},
institution = {Electronic Colloquium on Computational Complexity},
year = 2017
}
@misc{plonky3-bench,
author = {The Plonky3 contributors},
title = {{Plonky3}: A library for building efficient
zero-knowledge proofs},
year = 2024,
howpublished = {github.com/Plonky3/Plonky3}
}
@misc{ethereum-stark,
author = {Justin Drake and Vitalik Buterin and Dankrad Feist},
title = {Post-quantum {Ethereum} roadmap notes: {STARK}
precompiles and the verification surface},
organization = {Ethereum Foundation Research},
year = 2025
}
@misc{fips204,
author = {{NIST}},
title = {{FIPS} 204: Module-Lattice-Based Digital Signature
Standard},
month = {August},
year = 2024
}
@misc{eip-2929,
author = {Vitalik Buterin and Martin Holst Swende},
title = {{EIP-2929}: Gas cost increases for state access
opcodes},
howpublished = {Ethereum Improvement Proposal},
year = 2020
}
@inproceedings{bgl,
author = {Gilles Barthe and Beno{\^i}t Gr{\'e}goire and
Vincent Laporte},
title = {Secure compilation of side-channel countermeasures:
The case of cryptographic constant-time},
booktitle = {CSF 2018},
year = 2018
}
@inproceedings{dudect,
author = {Oscar Reparaz and Josep Balasch and
Ingrid Verbauwhede},
title = {Dude, is my code constant time?},
booktitle = {DATE 2017},
year = 2017
}
@misc{libjade,
author = {Formosa Crypto project},
title = {libjade: A formally verified library of
cryptographic algorithms},
year = 2024,
howpublished = {github.com/formosa-crypto/libjade}
}