A protocol and an account boundary.
1soft is a research-stage independent native ledger with account and permission software around it. The web experience is a separate, static project; it is not the chain client.
No public SDK package, RPC URL, faucet, explorer API or mainnet endpoint is advertised. The private development repository is not linked as a public download.
The intended integration flow.
These stages have distinct responsibilities. Preparing or signing a payment is not settlement. A responding server does not replace cryptographic verification. A stale snapshot cannot prove the latest balance.
Task identity before transaction identity.
The local payment-job prototype preserves an exact request under a stable task ID. Compatible runtimes should resume it after interruption, rather than inventing a replacement purchase.
This is local workspace coordination, not on-chain idempotency. Cross-device recovery and external payment routes require further design.
Integrate standards where they help.
The architecture should evaluate existing payment and agent-authorization interfaces rather than invent an incompatible alternative to every checkout protocol. Support for a named standard must be demonstrated by an implemented and tested adapter.
x402, MPP, AP2 and multi-asset access are research directions, not supported production endpoints in this release.
A bounded public surface.
The first website contains public research, a roadmap and a clearly labelled browser model. It has no financial backend, no analytics integration and no secret material.
Public SDK releases, network parameters, safe examples and verified support channels will require their own release process. A domain being active is not evidence that those systems are ready.