History / Data Models

docs: publish version 14.0.0 reference and migration guidance Promote the approved development documentation to the version 14.0.0 release reference. Update version labels, source links, the sidebar, and the payment guide notice so users are directed to the released main-branch implementation rather than treating these APIs as unpublished dev-only behavior. Add an explicit migration section from version 13: batches now prepare every invoice before one wallet submission, oversized batches are rejected rather than silently split, TON preparation requires a real payer identity, invoice completion must correlate with the request id, and durable recovery/OS payer coordination are part of the default automatic-payment workflow. State the approved 1.5 percent native service fee separately from network fees and voluntary support. Retain exact accounting rules, the USDT/EVM exclusions, one combined native fee message, and independent downstream fulfillment for each invoice. Preserve the historical version 13 migration information without presenting its per-invoice broadcast behavior as the version 14 contract. Keep guidance for persistent journal storage, original-session reconciliation, operator evidence, process-crash recovery, and multi-host distributed adapters linked from the released overview. The full guide stays in the wiki, with no duplicate docs/payments.md reintroduced in the library repository.

S1qwy committed Oct 15, 2026

docs: document single-submission batches, durable recovery, and payer coordination on dev Move the complete payment integration guide into the project's dedicated wiki and add it to the sidebar and overview navigation. Keep full reference material in this repository, with the library README linking here rather than maintaining a parallel docs/payments.md file. Clearly identify new behavior as the current dev branch rather than implying that a new package has already been published. Replace obsolete per-invoice batch-broadcast descriptions with the restored single-wallet-submission contract. Explain validation of every input before invoice initialization, preparation of every invoice before sending, preservation of invoice messages, a summed native fee message, exact combined USDT requirements, the earliest expiration, one gas reserve, and rejection before send when wallet capacity is exceeded. Distinguish wallet submission from atomic downstream contract execution and independent Fragment fulfillment. Document the combined external-signing payload, component invoices for inspection, shared wallet-message identifiers, zero-based chunk index, accepted-broadcast counters, unknown item outcomes, and concrete result models. Require completion to correlate with the invoice id instead of accepting generic page completion. Explain preflight uncertainty versus an attempted provider send using the new BroadcastUncertainError operation_id and attempted attributes. Describe SQLitePaymentStorage, PaymentStorage, wallet_lock_factory, signed-intent persistence before network transmission, restart/cancellation recovery, and the get_payment/list_payments/reconcile_payment/resolve_payment APIs. Clarify that reconciliation never resends a blockchain payment and that operator settlement records require independently checked evidence without claiming fulfillment. Document sensitive signed BOCs, persistent deployment paths, local process locks, OS release after process exit, and shared store/distributed lock requirements for multiple hosts. Correct stale accounting and wallet guidance: explain configured basis points instead of the outdated 0.5% assertion, distinguish service fees from network fees and voluntary support, remove the shared auth wallet as a payer fallback, add Telegram WalletTg, and correct HighloadV3R1 capacity to 64,516 messages. Update constructor references, recovery models, public receipt operation ids, exception semantics, limits, examples, and migration notes consistently. Validation checks local wiki links and section targets, compares documented public fields and constructor parameters against the library source, scans for obsolete batch/fee/fallback statements, and verifies the library history no longer contains docs/payments.md in the rewritten development commits.

S1qwy committed Oct 15, 2026

docs: update documentation to version 13.0.0

S1qwy committed Oct 2, 2026

Created Data Models (markdown)

S1qwy committed Aug 22, 2026