mirror of
https://github.com/luxdao/app.git
synced 2026-10-30 18:14:05 +00:00
zeekayandHanzo Dev
5c1562944c
lux.vote was served by an interface derived from Decent DAO under AGPL-3.0. This is a fresh app on @hanzo/gui with no Decent lineage — the replaced app's route table was read to enumerate what the interface must do, and nothing else. No Tailwind anywhere. @luxfi/ui is not a dependency: its prebuilt components carry arbitrary-utility class strings and are the only reason the exchange scans for them. Dropping it means replacing two things it provided — createGui, which GuiProvider alone does not call and without which the tree throws and the document is blank, and luxUi()'s aliases, now read from node_modules/@hanzogui at config time so an upgrade cannot leave a package undeduplicated. Twelve screens over the Governor, the votes token, the Timelock, the work market, Roles, Karma and the gauges, wired to luxfi/standard's Foundry artifacts rather than to its stale ABI barrel. The contracts are not what the prose says: Bounty has no escrow, arbiter or dispute state; MultiDAOGovernor swaps Executed and Expired; Karma emits no Transfer so no holder list exists. The Governor's clock is mode=timestamp, which is asked for rather than assumed because 96369 produces blocks on demand and reading seconds as blocks turns one day into months. Every read reports one of four outcomes — deployed, not deployed, not read, no record. A contract with no code answers with empty data rather than an error, so an absent contract and an idle one arrive identically at the call site; only one of them is a statement about governance. /deployment asks eth_getCode for every address on every chain on load, because the written records disagree with the chain and with each other. Endpoints are the /v1/bc/C/rpc form. The bare host serves the same chain to curl and refuses a browser — 405 on preflight, no allow-origin header — which would report every Governor unreadable while the Governor was fine. Wallet login is @luxwallet/connect, imported by subpath: its root barrel pulls a connector factory naming all seven chains, and a bundler follows every branch into optional peers the dev server never resolves. It signs a CAIP-122 message and offers no provider, transactions or chain switching, so viem is built over our own EIP-6963 discovery for the calls that write. Telemetry off: the design system posts to api.hanzo.ai on load by default, and who reads a proposal is not this interface's to report. Gates ported and made real. The class check ran against the Suspense fallback until a negative control caught it passing on a route with an injected utility class; every gate now waits for the screen's own h1. 22 unit tests, 135 browser tests against the built output. Co-authored-by: Hanzo Dev <[email protected]>
123 lines
4.1 KiB
Plaintext
123 lines
4.1 KiB
Plaintext
Lux Ecosystem License
|
|
Version 1.2, December 2025
|
|
|
|
Copyright (c) 2020-2025 Lux Industries Inc.
|
|
All rights reserved.
|
|
|
|
TECHNOLOGY PORTFOLIO - PATENT APPLICATIONS PLANNED
|
|
Contact: [email protected]
|
|
|
|
================================================================================
|
|
TERMS AND CONDITIONS
|
|
================================================================================
|
|
|
|
1. DEFINITIONS
|
|
|
|
"Lux Primary Network" means the official Lux blockchain with Network ID=1
|
|
and EVM Chain ID=96369.
|
|
|
|
"Authorized Network" means the Lux Primary Network, official testnets/devnets,
|
|
and any L1/L2/L3 chain descending from the Lux Primary Network.
|
|
|
|
"Descending Chain" means an L1/L2/L3 chain built on, anchored to, or deriving
|
|
security from the Lux Primary Network or its authorized testnets.
|
|
|
|
"Research Use" means non-commercial academic research, education, personal
|
|
study, or evaluation purposes.
|
|
|
|
"Commercial Use" means any use in connection with a product or service
|
|
offered for sale or fee, internal use by a for-profit entity, or any use
|
|
to generate revenue.
|
|
|
|
2. GRANT OF LICENSE
|
|
|
|
Subject to these terms, Lux Industries Inc grants you a non-exclusive,
|
|
royalty-free license to:
|
|
|
|
(a) Use for Research Use without restriction;
|
|
|
|
(b) Operate on the Lux Primary Network (Network ID=1, EVM Chain ID=96369);
|
|
|
|
(c) Operate on official Lux testnets and devnets;
|
|
|
|
(d) Operate L1/L2/L3 chains descending from the Lux Primary Network;
|
|
|
|
(e) Build applications within the Lux ecosystem;
|
|
|
|
(f) Contribute improvements back to the original repositories.
|
|
|
|
3. RESTRICTIONS
|
|
|
|
Without a commercial license from Lux Industries Inc, you may NOT:
|
|
|
|
(a) Fork the Lux Network or any Lux software;
|
|
|
|
(b) Create competing networks not descending from Lux Primary Network;
|
|
|
|
(c) Use for Commercial Use outside the Lux ecosystem;
|
|
|
|
(d) Sublicense or transfer rights outside the Lux ecosystem;
|
|
|
|
(e) Use to create competing blockchain networks, exchanges, custody
|
|
services, or cryptographic systems outside the Lux ecosystem.
|
|
|
|
4. NO FORKS POLICY
|
|
|
|
Lux Industries Inc maintains ZERO TOLERANCE for unauthorized forks.
|
|
Any fork or deployment on an unauthorized network constitutes:
|
|
|
|
(a) Breach of this license;
|
|
(b) Grounds for immediate legal action.
|
|
|
|
5. RIGHTS RESERVATION
|
|
|
|
All rights not explicitly granted are reserved by Lux Industries Inc.
|
|
|
|
We plan to apply for patent protection for the technology in this
|
|
repository. Any implementation outside the Lux ecosystem may require
|
|
a separate commercial license.
|
|
|
|
6. DISCLAIMER OF WARRANTY
|
|
|
|
THIS SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
|
|
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
|
|
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
|
|
|
|
7. LIMITATION OF LIABILITY
|
|
|
|
IN NO EVENT SHALL LUX INDUSTRIES INC BE LIABLE FOR ANY CLAIM, DAMAGES
|
|
OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
|
|
ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE.
|
|
|
|
8. TERMINATION
|
|
|
|
This license terminates immediately upon any breach, including but not
|
|
limited to deployment on unauthorized networks or creation of forks.
|
|
|
|
9. GOVERNING LAW
|
|
|
|
This License shall be governed by the laws of the State of Delaware.
|
|
|
|
10. COMMERCIAL LICENSING
|
|
|
|
For commercial use outside the Lux ecosystem:
|
|
|
|
Lux Industries Inc.
|
|
Email: [email protected]
|
|
Subject: Commercial License Request
|
|
|
|
================================================================================
|
|
TL;DR
|
|
================================================================================
|
|
|
|
- Research/academic use = OK
|
|
- Lux Primary Network (Network ID=1, Chain ID=96369) = OK
|
|
- L1/L2/L3 chains descending from Lux Primary Network = OK
|
|
- Commercial products outside Lux ecosystem = Contact [email protected]
|
|
- Forks = Absolutely not
|
|
|
|
================================================================================
|
|
|
|
See LP-0012 for full licensing documentation:
|
|
https://github.com/luxfi/lps/blob/main/LPs/lp-0012-ecosystem-licensing.md
|