Fork lwsf for Wownero

- Rename project to lwsf-wow
- Update mixin_default from 15 to 21 (Wownero ring size 22)
- Update README for Wownero documentation and links
- Add Wownero copyright notices alongside Monero
- Change XMR -> WOW in ledger output
- Add upstream sync instructions

CMakeLists.txt

@@ -1,4 +1,5 @@
 # Copyright (c) 2024-2025, The Monero Project
+# Copyright (c) 2024-2025, The Wownero Project
 #
 # All rights reserved.
 #
@@ -27,7 +28,7 @@
 # THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
 cmake_minimum_required(VERSION 3.5.0)
-project(lwsf)
+project(lwsf-wow)
 
 enable_language(CXX)
 set(CMAKE_CXX_STANDARD 17)
@@ -46,7 +47,7 @@ if(NOT LWSF_SANITIZER STREQUAL "OFF")
 endif()
 
 if (NOT MONERO_SOURCE_DIR)
-  message(FATAL_ERROR "The argument -DMONERO_SOURCE_DIR must specify a location of a monero source tree")
+  message(FATAL_ERROR "The argument -DMONERO_SOURCE_DIR must specify a location of a wownero source tree")
 endif()
 
 cmake_path(CONVERT "${MONERO_SOURCE_DIR}" TO_CMAKE_PATH_LIST MONERO_SOURCE_DIR_CONVERTED)

README.md

@@ -1,7 +1,6 @@
-# lwsf
+# lwsf-wow
 
-> This project is **NOT** a part of the official monero "core" code, but _may_
+> Wownero fork of lwsf - Light Wallet Server Frontend
-> be merged into that project.
 
 > This project is correctly incomplete, so the instructions here are for
 > the truly adventurous.
@@ -11,61 +10,45 @@
   - [Introduction](#introduction)
   - [About this project](#about-this-project)
   - [License](#license)
-  - [Compiling lwsf from source](#compiling-lwsf-from-source)
+  - [Compiling lwsf-wow from source](#compiling-lwsf-wow-from-source)
     - [Dependencies](#dependencies)
     - [Cloning the repository](#cloning-the-repository)
     - [Build Instructions](#build-instructions)
-  - [Running lwsf](#running-lwsf)
+  - [Running lwsf-wow](#running-lwsf-wow)
 
 
 ## Introduction
 
-Monero is a private, secure, untraceable, decentralised digital currency. You are your bank, you control your funds, and nobody can trace your transfers unless you allow them to do so.
+Wownero is a privacy-focused, CPU-mineable, decentralized cryptocurrency based on Monero. This is the Wownero fork of lwsf (Light Wallet Server Frontend).
-
-**Privacy:** Monero uses a cryptographically sound system to allow you to send and receive funds without your transactions being easily revealed on the blockchain (the ledger of transactions that everyone has). This ensures that your purchases, receipts, and all transfers remain absolutely private by default.
-
-**Security:** Using the power of a distributed peer-to-peer consensus network, every transaction on the network is cryptographically secured. Individual wallets have a 25 word mnemonic seed that is only displayed once, and can be written down to backup the wallet. Wallet files are encrypted with a passphrase to ensure they are useless if stolen.
-
-**Untraceability:** By taking advantage of ring signatures, a special property of a certain type of cryptography, Monero is able to ensure that transactions are not only untraceable, but have an optional measure of ambiguity that ensures that transactions cannot easily be tied back to an individual user or computer.
-
-**Decentralization:** The utility of monero depends on its decentralised peer-to-peer consensus network - anyone should be able to run the monero software, validate the integrity of the blockchain, and participate in all aspects of the monero network using consumer-grade commodity hardware. Decentralization of the monero network is maintained by software development that minimizes the costs of running the monero software and inhibits the proliferation of specialized, non-commodity hardware.
 
 
 ## About this project
 
 The tl;dr is that you if you import this project into your wallet,
-you can choose at runtime between a Monero "full" wallet that does
+you can choose at runtime between a Wownero "full" wallet that does
-all of the transaction scanning locally, or a Monero "light" wallet
+all of the transaction scanning locally, or a Wownero "light" wallet
 that does all of the scanning remotely. A single C++ `virtual`
-interface has two different implementations for Monero wallet
+interface has two different implementations for Wownero wallet
 processing.
 
 **The longer version -**
 
-This is a client library for the [Monero light-wallet REST API](https://github.com/monero-project/meta/blob/master/api/lightwallet_rest.md)
+This is a client library for the [Wownero light-wallet REST API](https://codeberg.org/wownero/wownero-lws)
-(i.e. MyMonero compatible) that implements the [`wallet2_api.h`](https://github.com/monero-project/monero/blob/3b01c490953fe92f3c6628fa31d280a4f0490d28/src/wallet/api/wallet2_api.h)
+that implements the `wallet2_api.h` interface. Downstream projects/wallets can write code that calls into
-interface. Downstream projects/wallets can write code that calls into
+the `wallet2_api.h` functions to manage a Wownero wallet, and select
-the `wallet2_api.h` functions to manage a Monero wallet, and select
+a "standard" wownero wallet by calling
-a "standard" monero wallet by calling
 `Monero::WalletManagerFactory::getWalletManager()` or select a
 light-wallet by calling `lwsf::WalletManagerFactory::getWalletManager()`.
 
-[`lwcli` illustrates how this works](https://github.com/cifro-codes/lwcli/blob/4a6793608c46f05d959336ea55dd106e0b0339bd/src/main.cpp#L281).
+The `lwsf` manager requires the user to specify a [wownero-lws](https://codeberg.org/wownero/wownero-lws) server,
-The main function calls a different "factory" function depending on the
+whereas the `Monero` manager requires a wownerod RPC. The
-CLI arguments. The `lwcli` TUI "draw" code is then given a single
-`Monero::WalletManager` interface object that can be one of two
-implementations. The `lwsf` manager requires the
-user to specify a [LWS](https://github.com/vtnerd/monero-lws) server,
-whereas the `Monero` manager requires a monero daemon RPC. The
 light-wallet implementation can have quicker sync time, whereas the
-monerod implementation will have better privacy guarantees. If you
+wownerod implementation will have better privacy guarantees. If you
 run your own LWS server, the privacy is identical.
 
 The projects use different file formats for storing data, so
-you have to manully import a wallet via seed if you want to
+you have to manually import a wallet via seed if you want to
-change backends. The files output by the `Monero` factory function
+change backends.
-are compatbile with `monero-gui` and `monero-wallet-cli`, as it
-uses the same code.
 
 
 ## License
@@ -84,7 +67,7 @@ The following table summarizes the tools and libraries required to build.
 | GCC          | 7             | NO       | `build-essential`    | `base-devel` | `base-devel`       | `gcc`               | NO       |                 |
 | CMake        | 3.5           | NO       | `cmake`              | `cmake`      | `cmake`            | `cmake`             | NO       |                 |
 | Boost        | 1.66          | NO       | `libboost-all-dev`   | `boost`      | `boost-devel`      | `boost-devel`       | NO       | C++ libraries   |
-| monero       | master branch | NO       |                      |              |                    |                     | NO       | Monero libraries|
+| wownero      | master branch | NO       |                      |              |                    |                     | NO       | Wownero libs    |
 | OpenSSL      | basically any | NO       | `libssl-dev`         | `openssl`    | `libressl-devel`   | `openssl-devel`     | NO       | sha256 sum      |
 | libzmq       | 4.2.0         | NO       | `libzmq3-dev`        | `zeromq`     | `zeromq-devel`     | `zeromq-devel`      | NO       | ZeroMQ library  |
 | libunbound   | 1.4.16        | NO       | `libunbound-dev`     | `unbound`    | `unbound-devel`    | `unbound-devel`     | NO       | DNS resolver    |
@@ -92,53 +75,53 @@ The following table summarizes the tools and libraries required to build.
 | Doxygen      | any           | NO       | `doxygen`            | `doxygen`    | `doxygen`          | `doxygen`           | YES      | Documentation   |
 | Graphviz     | any           | NO       | `graphviz`           | `graphviz`   | `graphviz`         | `graphviz`          | YES      | Documentation   |
 
-Follow the guide from the [Monero projdect](https://github.com/monero-project/monero/blob/master/README.md#dependencies) for
+Follow the guide from the [Wownero project](https://git.wownero.com/wownero/wownero) for
-dependency installation and cloning the Monero repository. Stop
+dependency installation and cloning the Wownero repository. Stop
-after you've finished the cloning section for Monero, as `lwsf`
+after you've finished the cloning section for Wownero, as `lwsf-wow`
-will build Monero separately for you.
+will build Wownero separately for you.
 
 ### Cloning the repository
 
 Clone recursively to pull-in needed submodule(s):
 
 ```bash
-git clone --recursive https://github.com/vtnerd/lwsf.git
+git clone --recursive https://codeberg.org/wownero/lwsf-wow.git
-cd monero-lws && git submodule init && git submodule update
+cd lwsf-wow && git submodule init && git submodule update
 ```
 
 ### Build instructions
 
-Monero uses the CMake build system. Create a folder for the build,
+Wownero uses the CMake build system. Create a folder for the build,
-and specify both the Monero source directory and
+and specify both the Wownero source directory and
-lwsf source directory:
+lwsf-wow source directory:
 
 ```bash
 mkdir build_lwsf && cd build_lwsf
-cmake -DCMAKE_BUILD_TYPE=Release -DMONERO_SOURCE_DIR=/home/user/monero_source /home/user/lwsf_source
+cmake -DCMAKE_BUILD_TYPE=Release -DMONERO_SOURCE_DIR=/home/user/wownero_source /home/user/lwsf-wow_source
-cmake --build
+cmake --build .
 ```
 
-## Running lwsf
+## Running lwsf-wow
 
 When complete, you should have `lwsf-ledger` executable in
 `/home/user/build_lwsf/src` and a `lwsf-api.a` file in the
 same folder. Run the `-h` option on `lwsf-ledger` to test
-against a LWS server.
+against a wownero-lws server.
 
 ### lwsf-api.a
 
 This file is a little tricky to use outright as it doesn't
 contain the entire code needed. The remainder of the code
-is in `.a` files in the Monero source directory. The best
+is in `.a` files in the Wownero source directory. The best
-way to include `lwsf` into another project is to use Cmake
+way to include `lwsf-wow` into another project is to use Cmake
-with the [`FetchContent` function](https://github.com/cifro-codes/lwcli/blob/4a6793608c46f05d959336ea55dd106e0b0339bd/CMakeLists.txt#L40).
+with the [`FetchContent` function](https://cmake.org/cmake/help/latest/module/FetchContent.html).
 After running those few lines, you will have a `lwsf-api`
 target in Cmake:
 
 ```cmake
 project(your_project)
 include(FetchContent)
-FetchContent_Declare(lwsf SOURCE_DIR "${your_project_SOURCE_DIR}/external/lwsf")
+FetchContent_Declare(lwsf SOURCE_DIR "${your_project_SOURCE_DIR}/external/lwsf-wow")
 
 if (NOT lwsf_POPULATED)
   FetchContent_MakeAvailable(lwsf)
@@ -148,5 +131,17 @@ add_library(your_library ...)
 target_link_libraries(your_library lwsf-api)
 ```
 
+## Syncing with Upstream
+
+This project tracks the upstream [lwsf](https://github.com/vtnerd/lwsf) repository.
+To sync changes from upstream:
+
+```bash
+git fetch upstream
+git merge upstream/main
+# Resolve any conflicts if needed
+git push origin main
+```
+
 
 

include/lws_frontend.h

@@ -1,4 +1,5 @@
 // Copyright (c) 2025, The Monero Project
+// Copyright (c) 2025, The Wownero Project
 // 
 // All rights reserved.
 // 

src/CMakeLists.txt

@@ -1,4 +1,5 @@
 # Copyright (c) 2024, The Monero Project
+# Copyright (c) 2024, The Wownero Project
 #
 # All rights reserved.
 #

src/ledger_main.cpp

@@ -268,14 +268,14 @@ namespace
       const std::string& account = label.empty() ? std::to_string(info->subaddrAccount()) : label;
       if (info->direction() == Monero::TransactionInfo::Direction_In)
       { 
-        std::cout << "    Assets:Monero:" << account << "      " << cryptonote::print_money(info->amount()) << " XMR" << std::endl;
+        std::cout << "    Assets:Wownero:" << account << "      " << cryptonote::print_money(info->amount()) << " WOW" << std::endl;
         std::cout << "    Income" << std::endl;
       }
       else
       {
-        std::cout << "    Expenses             " << cryptonote::print_money(info->amount()) << " XMR " << std::endl;
+        std::cout << "    Expenses             " << cryptonote::print_money(info->amount()) << " WOW " << std::endl;
-        std::cout << "    Expenses:Monero:Fee  " << cryptonote::print_money(info->fee()) << " XMR" << std::endl;
+        std::cout << "    Expenses:Wownero:Fee  " << cryptonote::print_money(info->fee()) << " WOW" << std::endl;
-        std::cout << "    Assets:Monero:" << account << std::endl;
+        std::cout << "    Assets:Wownero:" << account << std::endl;
       }
     }
   }

src/lwsf_config.h

@@ -1,4 +1,5 @@
 // Copyright (c) 2024, The Monero Project
+// Copyright (c) 2024, The Wownero Project
 // 
 // All rights reserved.
 // 
@@ -57,7 +58,7 @@ namespace lwsf { namespace config
   constexpr const std::size_t max_ring_size_in_rpc = 128;
   constexpr const std::size_t max_txes_in_rpc = 2048;
   constexpr const std::size_t min_outputs = 2;
-  constexpr const std::uint32_t mixin_default = 15;
+  constexpr const std::uint32_t mixin_default = 21; // Wownero ring size 22 (mixin + 1)
   constexpr const std::chrono::seconds refresh_interval{30};
   constexpr const std::chrono::seconds refresh_interval_min{5};
   constexpr const std::chrono::seconds rpc_timeout{30};