The problem SolSignal.xyz solves

SolSignal.xyz allows you to configure alerts for Solana onchain events, such as a wallet transacting, a wallet balance falling below or rising above a certain amount, an NFT being minted etc.

There is a real market need for monitoring wallets and being notified of transactions as consumers and businesses want to be able to follow certain onchain activity. Consumers want to follow whales, friends, family, etc and businesses often need to monitor the walllets in their portfolios. An example of this is at my current employer, fan3, where we need to monitor the various wallets we use for gas sponsorred minting to ensure the balances don't get too low and users can no longer mint NFTs. There are some products that try to do this for the Solana ecosystem, but they are mostly targetted at traders (i.e. sniper bots), and are hard to use, often requiring regex or even coding knowledge. SolSignal.xyz will always be the simplest, easiest and fastest way to configure Solana alerts, largely targetted at non-technical people.

SolSignal is fully functional now and live at SolSignal.xyz. It currently supports email alerts and will be extended to SMS, push notifications, WhatsApp and more. While currently only supporting wallet transaction alerts, further alert types will be introduced in time. As well, SolSignal wlll introduce an API so that other developers can make use of it.

SolSignal.xyz has been built during late 2024 and is still in development, despite being live and functional. An early version of SolSignal was submitted to the Radar Hackathon but that did not include QuickNode Functions or QuickNode Streams. This latest version of SolSignal has evolved considerably and now is making use of QuickNode Functions, and QuickNode Streams is currently in development. Given the vast improvements and newly included QuickNode functionality, I am hopeful this latest version of SolSignal will be considered valid and accepted for the QN Build On Hackathon.

Challenges I ran into

Despite being a really cool backend technology, QN Functions lack support for many packages that I would find useful, particuarly Firebase. Also the interface is quite rigid.. It would be nice to be able to access HTTP headers and the query string of requests that hit a QN function so that these can be used for authorisation, parameterisation of function behaviour, etc.