Code:
Name: LRP - Luke
Term: 3 Cycles
Cycle Amnt: 28,500
Total Amnt: 85,500
Author: JSKitty
Receiver: Luke
Address: DNkAdmxHiGvYvMV3Cvtb4FFYhJMUTc8oR2
Created: 10-07-2025
Status: Active
Vote Hash: f7c593d56cfe01726861458ca8d2460af142ff26fff953d179fee3ec3fe6efbeRole and Introduction
Progress Report
PIVX Promos Redeemer: Finished!
Luke's work on Redeemer system is complete: with an extended amount of time being spent on infrastructure assistance with Cryptech to support the additional coins integrated with the PIVX Promos Redeemer app - this was not expected, but Luke's assistance in helping setup the various Nodes and Blockbook Explorers has greatly sped up the work in getting PIVX Promos integrated in to it's first ever "DApp-style" game mod.
The Redeemer app is now live and ready for use at: https://pivxla.bz/redeemer
PIVCards Refactor: Finished!
Luke's has spent a substantial amount of time refactoring the backend systems for PIVCards; primarily catching up with some well-needed stability improvements, bug fixing, extensive code documentation, and a testing suite that enables us to more reliably test PIVCards for regressions, performance bottlenecks and weaknesses.
This upgrade also improves the backend's modularity, with the aim of being able to "plug-and-play" with additional card providers in an easier manner.
The PIVCards Refactor was deployed today! With this now live, you should have a more reliable experience using PIVCards, with less order issues encountered, and faster support!
Proposal Plans
The Vector Bot SDK: R&D
One of Luke's most prominent tasks, with PIVCards improvements out of the way; will be research and development in to building the Rust Vector Bot SDK, a simple Rust SDK that allows developers to create bots on Vector with incredible ease - no knowledge of the underlying protocol will be necessary to build a bot on Vector, with the most critical components handled on the developer's behalf.
With a Vector Bot SDK, we'll be able to onboard developers to build on the Vector platform to offer their own services, with zero censorship; why would bot developers care about that? Because millions of bots are at threat!
The following example is the platform "BotGhost", a Discord Bot hosting and development platform under threat of shutdown by Discord (you can read about the situation more at https://update.botghost.com/), not only is this platform at threat, but the millions of other bots by innocent developers looking to build their userbase, all at the whim of a single centralised entity.
On the contrary, Vector Bots are unstoppable - you'd need every node on the network to collude against a bot's operation via community consensus, or the seizure of the server operating the bot's code (a first-party attack), in essense, this entire situation is impossible on Vector's architecture, by design.
A solid Bot SDK will enable developers to build their integrations, applications, and services upon Vector with great ease - with this, we could run Bot Developer Onboarding campaigns, Bot Dev Competitions, and more, building the foundations of an app that services are sold on, users are protected on, and developers are welcomed to.
In addition to building the Vector Bot SDK; Luke will be building various small, open-source "example" bots that can be used as templates for developers to experiment, run and modify - speeding up the onboarding process by giving the community immediate real-world, practical example codebases for running their own bot services on the Vector platform - more news to come on what flavours of bots are inbound.
Maintenance and Supervision
While Luke primarily focuses on the SDK, he'll continue handling maintenance tasks for PIVCards, Redeemer, and keeping an eye on the recent infrastructure setup with the Cryptech team for Redeemer's altcoin Blockbook APIs, all of these are unlikely to take a significant amount of time, given all of them are at a complete, recently-updated state.
Additionally, if we acquire API partnerships for PIVCards, then another potential task-shift is starting the integration process for PIVCards to integrate the catalogues of said partners - but this relies entirely on BizDev and partner compliance with our non-custodial needs, making this an uncertain possibility.
Last edited: