Luke
New Pivian
Role and Introduction
What I Accomplished Last Quarter (Q1 2026)
PIVCards
This quarter threw some serious curveballs at us on the PIVCards front. Our payment provider made several unexpected changes to their system with little warning, and went offline briefly. These changes broke parts of our integration and put the platform at risk of extended downtime. I had to drop what I was doing and jump in with emergency API fixes, reworking how we communicate with the provider's endpoints and adapting our internal logic to match their updated system. It was a significant amount of work, not just patching things up, but properly re-engineering the affected components so we wouldn't be in a fragile state going forward. I'm happy to say the platform came through it stable.On top of the emergency work, I delivered everything I committed to in my Q1 proposal, as well as additional projects. The automated liquidity provider management system is done, which streamlines how we handle payments to our provider. The in-web support integration is also up and running, giving users a more direct path to get help without having to leave the platform. I also continued handling the day-to-day maintenance, monitoring, and user support that keeps PIVCards running reliably.
Infrastructure & Server Migration
Sparrow let us know that they could no longer host a server with many important services, including toolbox services, all of our marketing materials, and services for testnet. This wasn't something we had planned for, so I stepped in and migrated those services over to new infrastructure. It involved setting up the new environments, transferring data, testing everything, and making sure there was no disruption to those that depend on that server. It all went smoothly and nothing was lost in the process.On top of the migration, I kept all of our Labs infrastructure running smoothly throughout the quarter. All Labs services received regular maintenance and attention, including updates, monitoring, and quick responses whenever something needed fixing.
Cross-Platform Bot
I made solid progress on the cross-platform bot that bridges Discord, Vector, and Telegram. The goal is to give users the ability to send direct messages and transfer funds across all three platforms seamlessly. As of now, it's working locally and the Discord-to-Vector bridge is looking solid in my personal testing. I'm planning to release it this or the following week. Telegram support may take a bit longer to get live due to some platform-specific quirks.What I'll Be Working On (Q2 2026)
MyPIVXWallet (MPW) v3
This is my main focus for the quarter. I'll be working closely with JSkitty, Liquid, and Duddino to push MPW to version 3. This is a major release for the web wallet, and it's going to take a coordinated effort from all of us to get it across the finish line.Testnet & PIVX Core V6
After MPW v3, I'll be teaming up with Liquid, JSkitty, and others to push out the testnet and work toward the PIVX Core V6 release. This is a big milestone for the network, and I'm excited to be part of it.Coinbase x402 for PIVX
If time allows, I'd also like to explore setting up a branch of coinbase/x402 adapted for PIVX. For those unfamiliar, x402 is an open protocol that enables native payments over HTTP, essentially letting websites and APIs accept crypto payments directly without needing third-party payment processors. This matters for real-world adoption because it removes friction. Instead of going through exchanges or complicated checkout flows, a merchant or service could simply accept PIV as part of a standard web request.The AI side of this is just as interesting. x402 is being positioned as a protocol for AI agents to make autonomous payments on the web. As AI-driven services and commerce keep growing, having the ability for an AI agent to pay for an API call, a resource, or a service in PIV instantly and without human intervention is huge. Getting PIVX plugged into this kind of infrastructure early puts us ahead of most other projects.