LRP - Duddino

Name: LRP - Duddino
Term: 3 Cycles
Cycle Amount: 30,000
Total Amount: 90,000
Author: JSKitty, Duddino
Receiver: Duddino
Address: DShxa9sykpVUYBe2VKZfq9dzE8f2yBbtmg
Created: 12-5-2025
Status: Active
Vote Hash: 7c2c8da375daef967e5030847d0f64ebea3b9a6f8ce2fe4ea96b52fcb4f37407

This is a continuation of my previous proposals, the last one being here.

My PIVX Wallet
These past cycles were mostly focused on implementing Multi Account on MPW, which is the task that took the most amount of effort and time.
Other work includes memo support and other bug fixes and improvements.

The PRs are as follows:

• Change submodule URL to self hosted one - https://github.com/PIVX-Labs/MyPIVXWallet/pull/529 - Self host git lfs to prevent the e2e tests to using all the github quotas
• Add form component to Proposal Form - https://github.com/PIVX-Labs/MyPIVXWallet/pull/534 - Add form component, this also provides a better UX to prevent users from accidentally sending a proposal with an invalid URL.
• Abstract shield sync fetching - https://github.com/PIVX-Labs/MyPIVXWallet/pull/536 - Refactor shield sync and abstract it, this is mainly for MPW tauri to allow it to switch to a different shield sync source
• Prevent double import - https://github.com/PIVX-Labs/MyPIVXWallet/pull/537 - Prevent double wallet imports, which could potentially cause issues.
• Don't use Request::bytes - https://github.com/PIVX-Labs/MyPIVXWallet/pull/538 - Older version of chromium based browser didn't have this API
• Fix e2e test for forks - https://github.com/PIVX-Labs/MyPIVXWallet/pull/539 - Forks needed access to secrets to run e2e tests, since git lfs requires authentication.
• Translate hard coded strings - https://github.com/PIVX-Labs/MyPIVXWallet/pull/540
• Multi account - https://github.com/PIVX-Labs/MyPIVXWallet/pull/542 - This adds multi account support to MPW. It allows to import different accounts per seed as per BIP44, as well as add different seeds or private keys.
• Localize events - https://github.com/PIVX-Labs/MyPIVXWallet/pull/543 - Mainly needed for multi account
• Store shield sync data on DB - https://github.com/PIVX-Labs/MyPIVXWallet/pull/545 - This prevents MPW from downloading the shield data over and over, by storing it on the db the first time (This only applies when deleting accounts or adding accounts on the multi account branch)
• Move cold stake address in the settings - https://github.com/PIVX-Labs/MyPIVXWallet/pull/546
• Add masternode translation - https://github.com/PIVX-Labs/MyPIVXWallet/pull/547
• Refactor activity - https://github.com/PIVX-Labs/MyPIVXWallet/pull/548 - This makes the activity component use the wallet composable instead of relying on the parent component to call update
• Masternode reward list - https://github.com/PIVX-Labs/MyPIVXWallet/pull/549 - Add a reward list to masternode
• Send and receive memos - https://github.com/PIVX-Labs/MyPIVXWallet/pull/551 - Add the ability to send and receive shield memos.

PIVX Shield Library
Most improvements on PIVX shield are also related to multi account and memos.

• Make rust request static - https://github.com/PIVX-Labs/pivx-shield/pull/99 - Instead of creating a worker for each PIVX-Shield instance, use the same one. This is useful for multi account.
• Fix error when uuid is undefined - https://github.com/PIVX-Labs/pivx-shield/pull/100
• Improve worker init - https://github.com/PIVX-Labs/pivx-shield/pull/101 - Multiple instances of PIVX-Shield could get stuck if created at once.
• Add load seed function - https://github.com/PIVX-Labs/pivx-shield/pull/102
• Fix fee calculation - https://github.com/PIVX-Labs/pivx-shield/pull/103 - the library would sometimes give a slightly off fee when creating a tx with low amounts, causing it to be rejected by PIVX nodes. This fixes it.
• Add option to send of receive memo - https://github.com/PIVX-Labs/pivx-shield/pull/104

MPW Tauri Full Node

• Add a primitive shield sync - https://github.com/PIVX-Labs/MPW-Tauri/pull/36
• Kill pivxd when already running - https://github.com/PIVX-Labs/MPW-Tauri/pull/38

PIVX Core

We decided that the best way to keep ongoing development is to start testnet6 and start testing it to find any potential bugs and areas of improvement. Liquid has created a proposal regarding this, which I invite everyone to check out:
https://forum.pivx.org/threads/testnet6-funds.2835fe/

• Make install-params script work when called from other dirs - https://github.com/PIVX-Project/PIVX/pull/2966

PIVX Crawler

Made with the help of @liquid, this is a tool to monitor PIVX's network size and health by crawling nodes.
https://github.com/PIVX-Labs/PIVX-Crawler