Menu
What's new

  • Due to abuse, self-registration is disabled.

    Registration is only required for posting topics or replies. To register, make a request on any of the PIVX social media or chat channels.

    NOTE: To enhance forum security, new accounts that have no posts within a 30-day period are subject to being deleted.

Active LRP - Luke

PIVX Labs

PIVX Labs

Administrator
Staff member
Code: 
Name: LRP - Luke
Term: 3 Cycles
Cycle Amnt: 28,500
Total Amnt: 85,500
Author: JSKitty
Receiver: Luke
Address: DRCftD2Xqmoud7x5EdhnBnMjof5qfE4rEn
Created: 10-10-2025
Status: Active
Vote Hash: 19adc2138e863ce15d9934df0919a9f186afaac3b0d4719658fa40fbfbfd028f


Role and Introduction
Luke is the primary backend developer across the majority of central Labs Platforms under JSKitty, he develops PIVCards, Labs Oracle, our Node Maintenance systems, and assists 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.
Click to expand...


Progress Report

Vector Bot SDK: Launched!
Luke's work on the Vector Bot SDK has lead to the launch of Vector SDK v0.2.0, a simple SDK that allows the creation of Vector Bots (essentially, Nostr Bots with all of the complex network and cryptographic stack hidden behind a simplified, Discord-API-like interface).

This SDK empowers developers to easily utilise Vector as a service platform, i.e: to build, offer and grow services and businesses with autonomy over our decentralised network, a true Agorist network.

As of v0.2.0, the SDK already supports the majority of in-chat features of Vector, making it easy for bot developers to utilise the platform to the fullest.

Already, several bots have been developed via the Vector SDK, many of such are used as open-source examples for the community to clone, template, and build their own bots upon, here's a rundown of some existing projects utilizing the Vector SDK:
  1. Vector LLM: https://github.com/JSKitty/Vector-LLM - A chatbot-style LLM interface for Vector, plug-and-play with all popular OpenAI style APIs, Vector LLM powers Viktor, our official Vector AI Chatbot.
  2. Vecord: https://github.com/JSKitty/Vecord - The bridge bot for Vector and Discord, Vecord allows you to connect a Discord community and be able to speak to them through Vector bi-directionally, similar in function to Discord <--- Telegram bridges, Vecord could ease the transition from Discord to Vector by providing a middleground to weary users.
  3. Cat Bot: https://github.com/Luke-Larsen/Vector-SDK-Example/tree/main/ImageResponse - Arguably the most important bot, a bot that sends you on-demand cat images, in privacy.
  4. A series of small example bots: https://github.com/Luke-Larsen/Vector-SDK-Example - Luke maintains a "Vector SDK Examples" repo, showing various templated examples of how to utilize the SDK for different purposes and usecases, as well as showcasing its capabilities.
In private, Luke is also developing his very own bots using the Vector SDK to provide services to the community, when ready, these bots will be announced to the community.

The official Vector AI Chatbot, Viktor, is powered by the Vector SDK, and based on the above open-source repository: Vector LLM.
1760128087763.png
​


Labs Pulse: Notification System
Luke assisted with the development of a Notification System for Labs Pulse, built with the ability to DM admins via Vector when issues are detected, and the ability to ping a Discord Webhook in addition.

Pulse Notifier is written in Rust, granting it the ability to utilise the Rust Vector SDK for over-network Vector notifications.

github.com

GitHub - Luke-Larsen/Pulse-Notifier: A bot that listens to pivx pulse and sends a message if anything goes wrong

A bot that listens to pivx pulse and sends a message if anything goes wrong - Luke-Larsen/Pulse-Notifier
github.com github.com


PIVCards: general maintenance
As usual, Luke has been involved in maintaining PIVCards and ensuring smooth operation - tweaking cards, handling support tickets and technical issues, as well as fulfilling user requests for well-intentioned card removals (Roblox cards), PIVCards continues to run smoothly with no necessity for heavy work.


Proposal Plans

The Vector Bot SDK: MLS support and further refinement
Luke will primarily continue his work on the Vector SDK, with the main goal being to integrate Vector's MLS implementation (Marmot), which would allow Vector Bots to be fully compatible with Group Chats - when this is complete, Bots gain a massive amount of utility, for example: Vecord could be used to bridge entire communities between Vector and Discord, rather than a Discord community to each Vector user's DMs - additionally, chatbots like Viktor could be added to Group Chats for multi-user conversations, and any other style of service built on Vector could be deployed in Group Chats, small and large, for infinite possibilities, powered by scalable, truly next-generation encryption protocols.

Aside from Vector MLS integration, his work on refining the SDK will continue; making it easier to use, adding new features, and slowly compounding the SDK's mission to onboard the world of developers and businesses to Vector as a platform.


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.
 
Last edited:
You must log in or register to reply here.
Top