Luke
New Pivian
Name: Luke (Q1 2026)
Term: 3 Cycles
Cycle Amnt: 28,500
Total Amnt: 85,500
Author: Luke
Receiver: Luke
Address: DRCftD2Xqmoud7x5EdhnBnMjof5qfE4rEn
Created: 1-10-2026
Status: Active
Vote Hash: a336383c2327164a511b5d9ba238d8f15f5c0b441df01d35c6e2424828ef69af
NOTE: Due to recent internal changes in PIVX labs, I will be posting my own proposals from now on.
Role and Introduction
Luke is the primary back-end developer across the majority of central Labs Platforms, he develops PIVCards, Labs Oracle, our Node Maintenance systems and more. Assisting with architectural work and code-reviews for other parts of Labs - Overall, he's a core member of Labs' infrastructure, keeping everything running smoothly while adding new features and expanding the ecosystem.
Due to the recent changes in how the proposal is being made, I’d like to briefly go over a general history of my contribution to PIVX and PIVX labs, just to keep the continuity with the previous proposal forum posts.
Previous Work:
MyPIVXWallet (MPW)
- Code reviews for faster PR merging
- Quality control assistance
- A number of small aspects that needed to be done such as the language switcher backend code
PIVCards Platform
- Reduced delivery times from 30+ minutes to under 5 minutes
- Achieved 1% error rate (industry-leading reliability)
- Full conversion to SHIELD service
- Implemented Catalog system and internal search engine
- Built cashback system (back-end complete)
- Database migration to MongoDB
- Created templating system for easy card provider integration across multiple providers
- Extensive refactoring for stability and scalability
- PIVCards now handles higher volumes with lower costs
Ongoing Responsibilities for PIVCards:
- Platform maintenance and monitoring
- Support ticket resolution
- Technical issue handling
- User request fulfillment
Labs Oracle
- Replaced unreliable CoinGecko
- Open-source development
- Database optimizations for faster chart loading
- Integration of additional data sources
- Historical price data implementation
- Public launch with web interface
- Powers MyPIVXWallet and other Labs back-ends, as well as provides a consistent price API for anyone to use
Labs Pulse Notifier
- Notification system development (Rust-based)
- Vector integration for admin alerts
- Discord webhook support for alerting admins
- Infrastructure monitoring
Labs Node Checker
- Automatic node stability monitoring
- Fork detection and correction
- Peer optimization
- Email alerts for admins
- Bootstrapping capability
- Auto-restart on instabilities
PIVX Promos/Redeemer
Universal multi-coin redeemer with a focus on PIVX for use in allowing quick and easy payments and gifts
- Complete back-end development
- Live deployment at https://pivxla.bz/redeemer
- Infrastructure setup with Cryptech partnership
- Node and Blockbook Explorer configuration
- Integration into Project Zomboid game mod
- Enables broader PIVX adoption by allowing easy sending and receiving of funds even when an end user doesn’t yet have a wallet
Vector Bot SDK (Recent Focus)
- Released Vector SDK v0.2.0 (Rust-based)
- Created multiple example bots and templates
- Powers Viktor (official Vector AI chat-bot)
- Developed Vecord (Discord-Vector bridge)
- Built Pulse Notifier for Labs infrastructure monitoring
- Open-source repositories for community development
Progress Report
My work on the Vector Bot SDK has progressed. It now includes creating a bot capable of being in group chats and using all the normal functions that users can do in these groups. During this time there was also some work on the closed source bot (more information can be found in the “proposal plans” section for this proposal.) Once merged (early January 2026) a new version of the Vector Bot SDK will be released.
The main SDK work was done on a branch in the vector-sdk located here: https://github.com/VectorPrivacy/Vector-SDK/tree/mls-groups
You can find a ton of example bot systems on my repo : https://github.com/Luke-Larsen/Vector-SDK-Example (This uses the SDK from above)
During this time there was also some work making sure that PIVCards orders got filled and dealing with liquidity provider issues, more is described in this proposal’s “Proposal Plans” section.
There was also the creation of the Pulse Notifier, a tool used to alert for any 'downed' services. This works with our Pulse system to make sure that nothing silently fails. You can find the repo here: https://github.com/Luke-Larsen/Pulse-Notifier
Proposal Plans:
PIVCards – Liquidity provider management, and in-web support
Due to some recent issues that have affected a great number of those in the PIVX community we have begun to realize that some of our liquidity providers are not as reliable as once thought. To fix this we need to create an automated system by which we can quickly detect issues from our providers and switch to other ones, and adjust fees, with minimal human intervention. Previously we had systems in place in the event that one provider went down, but these systems did not account for if those provider’s systems did not give proper errors.
We also need better systems for managing fees as the liquidity providers fees can change drastically. These different fees effecting the overall liquidity and viability of PIVCards as a whole. These changes are required so that we can continue to provide reliable, cheap and timely gift-cards.
Beyond that point it has been brought up that an in-web support system would be a useful tool. To that end I will be looking into different solutions and choosing one that works the best for everyone involved. My current plan is to set up a web based Vector plugin for ticketing support but if time doesn't allow it, or there is some other major road block, I will integrate another system that will provide support directly on the website rather than relying on discord.
PIVX Promos – Continued work to help with integrations
The PIVX promos system is here to help adoption of PIVX. Using promos people are able to get paid in PIVX without even having an address at the time. Currently, this is being utilized in games as rewards, and also work is currently being done to utilize this in Vector as an easy way to get people adopted into the PIVX ecosystem. We will need continued development of these systems to provide for smooth adoption and utilization
Custom Cross Platform Bot
This is my solution to the issue of multiple communities across multiple platforms not being able to communicate. This is a project I have been working on the back burner for a bit of time, and now that the vector bot SDK is getting finalized I am finally getting to the point of releasing it for public use. The following features are planned to be completed by the end of the proposal time, with more coming in the future.
- Cross platform communication in “Direct messages” and a contact book.
This allows a user on discord to “DM” a user on vector for instance. This system allows users to register with the bot and connect their npubs, Telegram handles, Discord handles, PIVX wallets etc. together so that someone could find their names on a different platform. While this limits the privacy, and security of such communications it increases adoption and allows for users to communicate when one might not want to talk directly on one platform for whatever reason.
- Sending funds, using our promos system, across platforms.
This allows a user to send PIVX across platforms utilizing the promos system.
- Swapping coins
By using providers and systems developed side by side for PIVCards. I will be enabling the bot to swap coins using our providers APIs.
Maintenance and Supervision
As with most previous proposals I’d like to mention, I will also be handling maintenance tasks for PIVX labs services, helping review MPW proposals, and building any in between projects that need to be built to get to the goals listed above.
## Appendix: For more information you can view my previous proposals here:
1. Jan 2024: https://forum.pivx.org/threads/lrp-luke.1903/
2. Apr 2024: https://forum.pivx.org/threads/lrp-luke.2018/
3. Jul 2024: https://forum.pivx.org/threads/lrp-luke.2181/
4. Oct 2024: https://forum.pivx.org/threads/lrp-luke.2409/
5. Jan 2025: https://forum.pivx.org/threads/lrp-luke.2707/
6. Apr 2025: https://forum.pivx.org/threads/lrp-luke.2830/
7. Jul 2025: https://forum.pivx.org/threads/lrp-luke.2867/
8. Oct 2025: https://forum.pivx.org/threads/lrp-luke.2910/
Last edited: