Paloma Lightnodes enable Proof of Work mining on the Proof of Stake Cosmos-SDK Paloma Chain, allowing users to earn staking rewards without needing significant hash power. They provide a lightweight, efficient way to engage with the network, eliminating the need to run a full validator and making decentralized participation more accessible.
Paloma Lightnodes lets users earn staking rewards without needing high hash power or deep technical knowledge. It runs on the Proof of Work mechanism within the Proof of Stake Cosmos-SDK Paloma Chain, making it an easy and efficient way for users to get involved in the network and support decentralization. As Lead Product Designer, I simplified the whole process of onboarding, purchasing, installing, and activating so anyone, even with no tech background, could jump in. By collaborating with a cross-functional team, I turned complex engineering details into a straightforward experience, helping boost network participation, keep error rates low, and drive growth in the Paloma ecosystem.
> sh $HOME/Downloads/setup.sh automate — LightNode Console delegation view initialized.
How could we provide software without a front-end to non-developer users? The challenge was to create an intuitive onboarding experience that welcomed users with minimal blockchain knowledge. We needed to simplify purchasing and running Lightnodes while ensuring fair token distribution and promoting network decentralization.
Lightnodes expand access to network rewards beyond traditional validators, allowing new users to participate and further decentralize the chain. The Lightnode pricing model follows an increasing price systeLightnodes broaden access to network rewards beyond just traditional validators, enabling new users to participate and further decentralize the blockchain. The pricing model for Lightnodes follows a tiered system, offering early adopters the opportunity to purchase them at a more favorable rate using GRAIN, Paloma’s native token. This approach generates revenue while promoting sustainable growth through software upgrades. Additionally, users can own an unlimited number of Lightnodes, creating opportunities for both new and existing participants to expand their holdings.
LightNode Download Instructions — Console output and web interface interaction displayed. The console guides the download process, while the web interface provides real-time status and configuration options.
The design process consisted of four phases: research, development of instructional content, purchase flow design, and ongoing improvement.
We took an iterative, hands-on approach to improve the installation process for Paloma Lightnodes, focusing on users without technical backgrounds. I started as the first test user—guided by the CEO and Head Protocol Engineer—going through the entire setup from downloading the package to using the terminal. This session helped us create the first draft of our installation guide.
We then tested the guide with non-technical team members and later with friends and family. Watching them in real time revealed confusion around the console, unclear steps, and a lack of feedback during long command executions.
Key insights included:
We worked closely with engineers to update the flow, write clearer instructions, and document pain points using screen recordings. This process made setup easier, reduced errors, and ensured accessibility for users of all backgrounds.
User feedback highlighted key setup challenges, leading to clearer instructions and a smoother process.
After gathering enough research and testing insights, we created final instructions for both the website and command line. The last round of testing with users from MacOS, Windows, and Linux confirmed everything was smooth and bug-free. We felt confident knowing the instructions were clear enough for anyone to follow.
However, post-launch, we received a user request regarding setting up the Lightnode on a Virtual Private Server (VPS). We quickly updated our documentation to include this new use case, expanding access to more users.
Final installation instructions - Updated based on testing and user feedback, now include a VPS setup guide.
After downloading and installing the Lightnode, users needed to activate it by linking it to their EVM wallet (the same wallet used to purchase the node). The process required users to return to the interface and paste the Paloma Wallet address into the required field, linking their EVM wallet to the Paloma Address and completing the activation.
Lightnode Activation Flow – After installation, users link their EVM wallet to the Paloma Wallet address generated by the Lightnode to complete activation and connect their nodes.
Once we had the installation process dialed in, it was time to tackle the purchase flow. The goal was to create a smooth, intuitive experience where users could easily buy their Lightnode—without feeling lost in the process.
Purchase Flow – Final screens of the LightNode purchase process, including error states and registration.
During testing, we discovered something key: each slot could only hold a specific number of nodes. This meant that when users bought multiple Lightnodes, we needed to show them multiple slots to keep things clear and avoid any confusion. It was a small but crucial tweak that made a big difference in the overall experience.
.gif)
To make it easier for non-crypto users to buy and install a Lightnode, we integrated Transak and Coinbase Wallet. These integrations allowed users to purchase Lightnodes using deposit or credit cards. This was a game-changer for non-crypto users, making the transaction process feel just like any other online purchase. It removed the complexity of crypto transactions, making it super easy for new users to get started with Paloma Lightnodes.
To further assist users, we created video walkthroughs demonstrating the node installation process. These videos provided clear, step-by-step guidance, helping reduce errors and ensuring users had the support they needed to complete the setup successfully.
It took us three months from the start of user research to launch. By the time we released, our improved interface and onboarding flow resulted in just a 1% error rate, measured through customer support tickets. 80% of these tickets led to refinements in our installation instructions. We sold 4,000 Lightnodes in the first month. Email marketing played a key role in keeping users engaged and encouraging repeat purchases, where the memorability and clarity of the interface proved essential.
Designing Paloma Lightnodes was a hands-on, iterative process where we had to get creative with limited resources. From being the first test user myself to watching friends and team members navigate the install flow, it taught me how much power there is in simple, clear design, especially when the tech is complex. This project pushed me to think like a user, not just a designer. I learned a lot about decentralized infrastructure, node activation, and the small details that can make or break an onboarding experience. Seeing the Lightnodes go from concept to 4,000+ sold in the first month made all the effort worth it.
Thank you for reading through this Product Design case study.
