In addition to the core Lightning Network Daemon software and end-user applications, the Lightning Network ecosystem includes supporting systems like watchtowers (a form of backup), peer availability/network monitoring, advanced liquidity provisioning tools, automated channel management, and other services. We’re looking for a systems-oriented engineer to design and build out the key components that will support the initial bootstrapping and growth of the network. These tools will lower the barrier to entry for operating routing nodes[1] and enable existing routing node operators to more effectively manage their infrastructure.
An ideal candidate would have a strong passion for Bitcoin and a desire to make using Bitcoin cheap, fast, and simple for everyone.Roles:- Write advanced software tooling for automated channel management and initial client channel selection (autopilot)- Implement algorithms for ongoing capital management and optimization (fee maximization and capital efficiency)- Design and maintain a suite of monitoring and alert infrastructure for routing nodes- Develop and collect metrics to passively analyze of the health of the network based on graph and node level signals- Design and build novel systems designed to help nodes/users acquire and manage liquidity on the Lightning NetworkSkills:- Experience building and operating secure, scalable, highly-available systems- Experience developing and supporting publicly available APIs- Familiarity contributing to open source projects preferred- Experience in systems programming languages such as Go, C or C++- Security and adversarially-oriented mindset- Knowledge of Bitcoin and applied cryptography; understanding of the Lightning Network protocol preferredCheck out our Github repos at:https://github.com/lightningnetwork/lndhttps://github.com/lightninglabs/poolhttps://github.com/lightninglabs/neutrinohttps://github.com/lightninglabs/faradayhttps://github.com/lightninglabs/lndmonhttps://github.com/lightninglabs/aperture[1] https://blog.lightning.engineering/posts/2018/05/30/routing.html