SW4P

SW4P is an intelligent routing and settlement system for moving value across the internet. A payment, transfer or exchange starts with an intended outcome. SW4P selects a route and coordinates the authorisation, fees, gas and execution needed to carry it through settlement. It tracks what completed, what failed and what requires recovery. These capabilities are programmable and composable. Software can call them directly and combine them across multiple steps, making value movement part of how an application operates.

​

Value at the speed of thought

SW4P’s vision is to make moving value as natural as expressing intent. The ambition is dependable completion with less effort, cost and delay, wherever value needs to move. A payment involves more than sending an instruction. The application needs to know what is being moved, who should receive it, which costs apply, whether it arrived, and what to do if the operation stops partway through.

​

The Settlement Lifecycle

​

Define the Instruction

Identify the asset, amount, recipient, source, and intended destination. Connect the payment to its purpose: for example, funding work, paying a provider, or settling an amount owed to a collaborator.

​

Select a Route and Review Costs

A route describes how the asset will reach its destination. The quote needs to account for the available route, applicable fees, execution costs, and any gas requirements.

​

Authorise the Operation

The person or agent initiating the payment must have authority to use the relevant funds. The requested operation, spending limits, and required approvals belong to the application or programme’s terms.

​

Execute and Confirm

Execution carries out the selected route. Confirmation establishes the result on the relevant network and connects it to the original instruction.

​

Recover Interrupted Work

A failure can occur before funds move or after part of a route has executed. Recovery needs to account for that difference, preserve the transaction’s state, and avoid treating an unresolved operation as complete.

​

Reconcile the Result

Reconciliation connects the instruction, incurred costs, receipts, recipient outcome, and remaining obligations. It explains what was paid, what remains owed, and which costs belong to the activity.

​

Routes, Assets, and Fees

Route selection depends on the asset, source and destination networks, available liquidity or transfer mechanism, and the requirements of the application. Before authorising a transfer, use the selected SW4P application’s route and quote information to confirm:

• The asset and networks.
• The recipient and destination address.
• The amount, fees, execution costs, and gas arrangements.
• The supported execution method and the instructions for following its progress.
• The recovery and support path if the operation does not finish.

Different routes can use different transfer mechanisms. A native burn-and-mint route, for example, burns the source asset, obtains the required attestation, and mints on the destination. Other routes have different steps and dependencies. Use the current application’s route and quote information to determine the transfer being offered.

​

Application and Agent Workflows

SW4P’s role extends to applications that need to coordinate several economic actions: fund an activity, cover provider costs, pay collaborators, and account for the remaining balance. An agent can prepare or carry out a settlement within its assigned authority. The application needs to distinguish a proposed instruction from an authorised payment and a confirmed result. Recurring purchases, price-triggered orders, batches, portfolio changes, and solver-based execution are specialised workflows described in the wider SW4P design. Each requires its own execution rules and available integration.

​

SW4P and SW4P Earn

SW4P coordinates settlement. SW4P Earn extends SW4P’s economic model into source-aware allocation, claims, rewards, payout schedules, reserves, and reconciliation. Sponsor funding, service fees, settlement revenue, token-related revenue, and reserves have different purposes. The applicable programme determines which costs must be covered, who receives an allocation, and what remains reserved or unpaid. Current status: SW4P Earn is not yet publicly available. No staking, liquidity, reward, or claim programme is currently open.

​

Integration Within RNDRNTWRK

RNDRNTWRK’s operating model uses SW4P to close the payments associated with work. Other applications can use the settlement role while keeping their own user experience and business model. AGG describes payment aggregation and routing within the protocol model. Hyperlink describes programmable payment interactions. Their integration with settlement needs to preserve the payment’s purpose, recipient, and result. $555 is RNDRNTWRK’s coordination asset. Any product-specific use of the token has its own rules.

​

Interfaces and Operating Responsibilities

Applications may connect through a user interface, an agent integration, or a service interface. @sw4p/kit introduces the agent integration project. An integration needs to account for authentication, spending authority, route availability, fees, transaction state, error handling, and records. Operators also need controls for rate limits, interrupted execution, monitoring, and responding to incidents. Use the selected component’s documentation for its concrete interfaces and operating requirements. Security reviews describe the exact source and version assessed.

​

Technical Documentation

The SW4P documentation is the separate technical destination. Use it for the component and integration you are working with.

​

Go Deeper