Links, alerts and overlays.
The team’s software connects creator identity, receiving-wallet details, a personal donation link, messages, alert media and the stream overlay.
PRODUCT & TECHNICAL WHITEPAPER
Stream donations.
A clear software role.
STEN — Stream Earnings Network connects creator links, SOL/STEN donations and configurable overlays. Product explanation revised 15 October 2026, based on the team’s technical description.
THE PRODUCT
A clear donation model.
A personal streaming moment.
Solana (SOL) or STEN coins.
The agreed options are SOL and STEN on Solana. The direct route does not require an automatic STEN purchase or conversion inside STEN.
97% / 3%.
97% of the donated token amount is allocated to the streamer and 3% to the platform. Network costs, possible token-account funding and external crypto costs are separate.
TECHNICAL RESPONSIBILITIES
The connection is ours.
The approval is yours.
- 01 / PREPARE
STEN prepares the proposal.
Your asset, amount and message become an unsigned Solana transaction proposal, including the streamer/platform split.
- 02 / REVIEW
The viewer decides.
Check the request in your wallet. Approve or reject it. Change your amount or message in STEN before requesting a new proposal.
- 03 / SIGN & SEND
Your wallet submits.
Phantom or Solflare signs and sends the approved transaction, according to the team’s described implementation.
- 04 / PROCESS
Solana confirms.
The network processes the transfers to the streamer and platform. The full donation does not first pass through a STEN holding wallet.
- 05 / DISPLAY
Your overlay responds.
STEN uses confirmation for the stream alert. The creator’s configured overlay must be active for viewers to see the notification.
This describes the team’s implementation. Wallet authorisation, network confirmation and the overlay are separate steps. STEN prepares transactions and facilitates the alert workflow; it is not the viewer’s wallet.
TRANSACTION PREPARATION
An unsigned proposal.
A decision in the viewer’s wallet.
According to the team’s description, STEN prepares an unsigned Solana transaction server-side with the streamer/platform split. The full donation does not first pass through a STEN-controlled holding wallet, and STEN does not manage users’ private keys.
The viewer builds the amount and message in STEN. Their wallet provides the review and approval/rejection step, then signs and sends according to the described implementation. Do not assume that the fee split is freely editable in the wallet. A change in amount or message belongs before a fresh proposal.
These are implementation statements supplied by the team, not findings from an independent code or security audit. They do not establish a licensing exemption or an approval by a regulator or wallet provider.
IF YOUR WALLET SHOWS A WARNING
Check the message before continuing.
Stop and contact the team if your wallet flags a security concern. The exact warning and its current status need checking; do not override it to complete a donation.
Read the wallet warning guide →NETWORK AND CONFIRMATION
Solana processes.
STEN displays the result.
Solana fees are paid in SOL, including when the transferred donation asset is STEN. A base fee and optional priority fee can apply. A new token account may also need a separate minimum storage balance; who funds it must match the deployed application.
Confirmed transaction data can be checked using the transaction signature. The amount, addresses, status, network fee and any included on-chain text may be public. That does not make all identities, off-chain data or the full software stack transparent.
STEN uses confirmation for the overlay workflow. Network success, application feedback and alert display are different checks. The creator’s overlay must be active. No guaranteed universal completion or alert time is stated.
MESSAGES AND COSTS
State the limits
before the viewer approves.
Text placed on-chain is public and cannot simply be removed by STEN. The team must confirm what is stored, the actual input/display limits, truncation and Unicode handling. Discussed 120/200-character figures are product questions, not general Solana limits.
The standard 97/3 split concerns donated token units. At 100 STEN, the model allocates 97 STEN to the streamer and 3 STEN to the platform, with other costs separate. This is a calculation, not a demonstrated transaction or a guaranteed euro return.
Review the fee explanation →CURRENT PRODUCT AND DEVELOPMENT
Keep product evidence
separate from ambitions.
The existing creator environment and supplied developer screenshots describe Twitch account setup, links, overlays, alert media, an OBS guide and test alerts. The public app entry is visible without sign-in; the authenticated donation-to-OBS flow was not tested in this website revision.
Reported issues include overlay disconnections and donation attempts without clear feedback. They remain development checks. The agreed acceptance proposal covers both wallets/assets, success/cancellation/errors and a longer overlay run.
Card/Apple Pay payments, automated fiat conversion, a Twitch extension, extra languages and further notification features remain research or backlog unless separately implemented and tested.
The existing site publishes a 66% market / 34% founders-and-developers token allocation. This is a published claim requiring dated chain evidence; liquidity actions do not guarantee security or price stability.
SOURCE BASIS
Product claims and technical references.
Based on the owner’s 13 October meeting notes, the website briefing supplied on 15 October, the team’s technical description, the existing site and developer screenshots. The website revision is not an independent app-code or security audit.