Skip to main content
WEN clients target shared, versioned contracts with separate economy accounts, assets, budgets and obligations. Use the accepted generated interfaces and exact deployment descriptor; do not reproduce monetary formulas in a browser client. Retail and Fased must reconcile the same ownership, fees, reservations, settlement and claims. A browser may close or a submission reply may be lost: durable action identity and chain readback must prevent duplicate execution. Keepers submit permitted work using their own fee-payer wallets and RPC. They cannot change recipients, allocation rules or owner spending limits. Account inclusion, bounded processing, concurrent windows, cancellation and recovery need contract-level proof. Protocol repositories own authoritative versioned interfaces. A documentation example or private workspace path is not a deployable SDK. Accepted interface versions and public source links will accompany a release; repository visibility must not be confused with product readiness.