Lightning settlement for games and creators

Split payments for Bitcoin-native games, marketplaces and tournaments.

Noderunners routes Lightning payments, unlocks game sessions, validates scores, funds jackpots and prize pools, pays creators, and keeps a configurable platform fee flowing to the operator.

API Game config, sessions, scores and payment status.
LNURL Entry payments, player notes and withdraw payouts.
Splits Platform, developer, prize, jackpot and seller shares.
Nostr Official arcade leaderboard publishing.

Core Flows

The platform starts with games, but the settlement model also fits creator products, events, bounties, paywalls and marketplace orders.

Games

Paid arcade entries

Create a LNURL entry payment, capture the player name, unlock a session, submit a score, and publish leaderboards.

Tournaments

Prize pool settlement

Entry fees split into product fee, prize pool, operator share and reserve before winners receive LNURL-withdraw payouts.

Marketplace

Seller payouts

Orders can split to platform fees and one or more sellers using wallet aliases, Lightning Address or LNURL-pay.

Creators

Revenue share

Game developers, asset creators, affiliates and sponsors can all become payment destinations in a future split rule.

Jackpots

Game-funded rewards

Paid credits can contribute to jackpot wallets while keeping platform fees and operator shares separate.

Nostr

Public score signal

Leaderboards can be published as official Noderunners Arcade events without requiring players to log in with Nostr.

Payment Split

The recommended first product mode is custodial settlement: Noderunners receives the payment, verifies it, then distributes sats.

player payment -> Noderunners invoice -> product/platform fee -> developer or seller payout -> prize pool, jackpot, reserve -> session unlock, webhook, leaderboard

Why this mode matters

  • Payment status is reliable before a game session starts.
  • Platform fees can be applied consistently.
  • Partner payouts can use Lightning Address or LNURL-pay.
  • Retries, logs and manual review can live in one backend.

Developer Endpoints

Base URL: https://lightning.druts.nl/api

Game Discovery

GET /api/games GET /api/game/config/{slug} GET /api/game/pricing/{slug}

Lightning Entries

POST /api/lightning/create-invoice GET /api/lightning/entry-lnurl/{id} GET /api/lightning/payment-status/{id}

Scores

POST /api/game/session/start POST /api/game/highscore/submit GET /api/game/leaderboard/{slug}

Tournaments

POST /api/tournament/create POST /api/tournament/join-invoice GET /api/tournament/status/{id}

Marketplace

POST /api/marketplace/invoices POST /api/marketplace/payout-destination/validate GET /api/marketplace/payments/{id}

Product Fee Config

product.gameFeeEnabled=true product.gameFeePercent=5 product.gameFeeDestination=wallet_bitcoinblitz_operator

Roadmap

This backend is moving toward a full split-payments product with partner onboarding and third-party paid games.

1. Product Fee Foundation

Global product fee config for paid game credits and tournament entries.

2. Generic Split Engine

Reusable payment intents, split rules, settlement records, retries and event logs.

3. Partner Platform

Partner API keys, game ownership, payout destinations, dashboards and webhooks.

Docs

The markdown docs are part of the backend repo and describe the API, root page plan and split-payments product direction.

Open API Explorer Live Endpoint Tester Open Games API Open Human Slacker Test Game Command Test Marketplace Command The Rabbit Hole Leaderboard Open Arcade Slack API Docs