@anywalletkit/wallet-ton 0.0.0-stage → 0.2.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/LICENSE +202 -0
- package/README.md +126 -2
- package/dist/chunk-BLWBC6L2.js +480 -0
- package/dist/chunk-BLWBC6L2.js.map +1 -0
- package/dist/history.cjs +499 -0
- package/dist/history.cjs.map +1 -0
- package/dist/history.d.cts +163 -0
- package/dist/history.d.ts +163 -0
- package/dist/history.js +25 -0
- package/dist/history.js.map +1 -0
- package/dist/index.cjs +1649 -0
- package/dist/index.cjs.map +1 -0
- package/dist/index.d.cts +704 -0
- package/dist/index.d.ts +704 -0
- package/dist/index.js +1185 -0
- package/dist/index.js.map +1 -0
- package/package.json +69 -3
package/LICENSE
ADDED
|
@@ -0,0 +1,202 @@
|
|
|
1
|
+
|
|
2
|
+
Apache License
|
|
3
|
+
Version 2.0, January 2004
|
|
4
|
+
http://www.apache.org/licenses/
|
|
5
|
+
|
|
6
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
7
|
+
|
|
8
|
+
1. Definitions.
|
|
9
|
+
|
|
10
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
11
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
12
|
+
|
|
13
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
14
|
+
the copyright owner that is granting the License.
|
|
15
|
+
|
|
16
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
17
|
+
other entities that control, are controlled by, or are under common
|
|
18
|
+
control with that entity. For the purposes of this definition,
|
|
19
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
20
|
+
direction or management of such entity, whether by contract or
|
|
21
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
22
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
23
|
+
|
|
24
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
25
|
+
exercising permissions granted by this License.
|
|
26
|
+
|
|
27
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
28
|
+
including but not limited to software source code, documentation
|
|
29
|
+
source, and configuration files.
|
|
30
|
+
|
|
31
|
+
"Object" form shall mean any form resulting from mechanical
|
|
32
|
+
transformation or translation of a Source form, including but
|
|
33
|
+
not limited to compiled object code, generated documentation,
|
|
34
|
+
and conversions to other media types.
|
|
35
|
+
|
|
36
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
37
|
+
Object form, made available under the License, as indicated by a
|
|
38
|
+
copyright notice that is included in or attached to the work
|
|
39
|
+
(an example is provided in the Appendix below).
|
|
40
|
+
|
|
41
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
42
|
+
form, that is based on (or derived from) the Work and for which the
|
|
43
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
44
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
45
|
+
of this License, Derivative Works shall not include works that remain
|
|
46
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
47
|
+
the Work and Derivative Works thereof.
|
|
48
|
+
|
|
49
|
+
"Contribution" shall mean any work of authorship, including
|
|
50
|
+
the original version of the Work and any modifications or additions
|
|
51
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
52
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
53
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
54
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
55
|
+
means any form of electronic, verbal, or written communication sent
|
|
56
|
+
to the Licensor or its representatives, including but not limited to
|
|
57
|
+
communication on electronic mailing lists, source code control systems,
|
|
58
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
59
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
60
|
+
excluding communication that is conspicuously marked or otherwise
|
|
61
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
62
|
+
|
|
63
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
64
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
65
|
+
subsequently incorporated within the Work.
|
|
66
|
+
|
|
67
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
68
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
69
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
70
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
71
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
72
|
+
Work and such Derivative Works in Source or Object form.
|
|
73
|
+
|
|
74
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
75
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
76
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
77
|
+
(except as stated in this section) patent license to make, have made,
|
|
78
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
79
|
+
where such license applies only to those patent claims licensable
|
|
80
|
+
by such Contributor that are necessarily infringed by their
|
|
81
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
82
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
83
|
+
institute patent litigation against any entity (including a
|
|
84
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
85
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
86
|
+
or contributory patent infringement, then any patent licenses
|
|
87
|
+
granted to You under this License for that Work shall terminate
|
|
88
|
+
as of the date such litigation is filed.
|
|
89
|
+
|
|
90
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
91
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
92
|
+
modifications, and in Source or Object form, provided that You
|
|
93
|
+
meet the following conditions:
|
|
94
|
+
|
|
95
|
+
(a) You must give any other recipients of the Work or
|
|
96
|
+
Derivative Works a copy of this License; and
|
|
97
|
+
|
|
98
|
+
(b) You must cause any modified files to carry prominent notices
|
|
99
|
+
stating that You changed the files; and
|
|
100
|
+
|
|
101
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
102
|
+
that You distribute, all copyright, patent, trademark, and
|
|
103
|
+
attribution notices from the Source form of the Work,
|
|
104
|
+
excluding those notices that do not pertain to any part of
|
|
105
|
+
the Derivative Works; and
|
|
106
|
+
|
|
107
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
108
|
+
distribution, then any Derivative Works that You distribute must
|
|
109
|
+
include a readable copy of the attribution notices contained
|
|
110
|
+
within such NOTICE file, excluding those notices that do not
|
|
111
|
+
pertain to any part of the Derivative Works, in at least one
|
|
112
|
+
of the following places: within a NOTICE text file distributed
|
|
113
|
+
as part of the Derivative Works; within the Source form or
|
|
114
|
+
documentation, if provided along with the Derivative Works; or,
|
|
115
|
+
within a display generated by the Derivative Works, if and
|
|
116
|
+
wherever such third-party notices normally appear. The contents
|
|
117
|
+
of the NOTICE file are for informational purposes only and
|
|
118
|
+
do not modify the License. You may add Your own attribution
|
|
119
|
+
notices within Derivative Works that You distribute, alongside
|
|
120
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
121
|
+
that such additional attribution notices cannot be construed
|
|
122
|
+
as modifying the License.
|
|
123
|
+
|
|
124
|
+
You may add Your own copyright statement to Your modifications and
|
|
125
|
+
may provide additional or different license terms and conditions
|
|
126
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
127
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
128
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
129
|
+
the conditions stated in this License.
|
|
130
|
+
|
|
131
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
132
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
133
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
134
|
+
this License, without any additional terms or conditions.
|
|
135
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
136
|
+
the terms of any separate license agreement you may have executed
|
|
137
|
+
with Licensor regarding such Contributions.
|
|
138
|
+
|
|
139
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
140
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
141
|
+
except as required for reasonable and customary use in describing the
|
|
142
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
143
|
+
|
|
144
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
145
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
146
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
147
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
148
|
+
implied, including, without limitation, any warranties or conditions
|
|
149
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
150
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
151
|
+
appropriateness of using or redistributing the Work and assume any
|
|
152
|
+
risks associated with Your exercise of permissions under this License.
|
|
153
|
+
|
|
154
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
155
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
156
|
+
unless required by applicable law (such as deliberate and grossly
|
|
157
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
158
|
+
liable to You for damages, including any direct, indirect, special,
|
|
159
|
+
incidental, or consequential damages of any character arising as a
|
|
160
|
+
result of this License or out of the use or inability to use the
|
|
161
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
162
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
163
|
+
other commercial damages or losses), even if such Contributor
|
|
164
|
+
has been advised of the possibility of such damages.
|
|
165
|
+
|
|
166
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
167
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
168
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
169
|
+
or other liability obligations and/or rights consistent with this
|
|
170
|
+
License. However, in accepting such obligations, You may act only
|
|
171
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
172
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
173
|
+
defend, and hold each Contributor harmless for any liability
|
|
174
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
175
|
+
of your accepting any such warranty or additional liability.
|
|
176
|
+
|
|
177
|
+
END OF TERMS AND CONDITIONS
|
|
178
|
+
|
|
179
|
+
APPENDIX: How to apply the Apache License to your work.
|
|
180
|
+
|
|
181
|
+
To apply the Apache License to your work, attach the following
|
|
182
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
|
183
|
+
replaced with your own identifying information. (Don't include
|
|
184
|
+
the brackets!) The text should be enclosed in the appropriate
|
|
185
|
+
comment syntax for the file format. We also recommend that a
|
|
186
|
+
file or class name and description of purpose be included on the
|
|
187
|
+
same "printed page" as the copyright notice for easier
|
|
188
|
+
identification within third-party archives.
|
|
189
|
+
|
|
190
|
+
Copyright [yyyy] [name of copyright owner]
|
|
191
|
+
|
|
192
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
193
|
+
you may not use this file except in compliance with the License.
|
|
194
|
+
You may obtain a copy of the License at
|
|
195
|
+
|
|
196
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
197
|
+
|
|
198
|
+
Unless required by applicable law or agreed to in writing, software
|
|
199
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
200
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
201
|
+
See the License for the specific language governing permissions and
|
|
202
|
+
limitations under the License.
|
package/README.md
CHANGED
|
@@ -1,3 +1,127 @@
|
|
|
1
|
-
#
|
|
1
|
+
# @anywalletkit/wallet-ton
|
|
2
2
|
|
|
3
|
-
|
|
3
|
+
TON accounts at `m/44'/607'/i'` (SLIP-10 ed25519) on Wallet V5R1 — the
|
|
4
|
+
derivation Trust Wallet and Ledger use for a BIP-39 phrase, pinned by
|
|
5
|
+
golden vectors in `@anywalletkit/conformance`. Runtime dependencies: `@ton/core`,
|
|
6
|
+
`@ton/crypto`, `buffer` (no `@ton/ton`: the V5R1 contract and the toncenter
|
|
7
|
+
client are implemented here, byte-for-byte checked against `@ton/ton` in tests).
|
|
8
|
+
|
|
9
|
+
```ts
|
|
10
|
+
import WalletManagerTon from '@anywalletkit/wallet-ton'
|
|
11
|
+
|
|
12
|
+
const wallet = new WalletManagerTon(seedPhrase, {
|
|
13
|
+
tonClient: [{ url: 'https://toncenter.com/api/v2/jsonRPC', secretKey }], // fails over in order
|
|
14
|
+
// emulate: {kind: 'tonapi'} is the default (tonapi.io/v2/wallet/emulate, then /traces/emulate);
|
|
15
|
+
// {kind: 'toncenter-v3', url} switches the emulator, false = estimateFee only.
|
|
16
|
+
tonApiKey, // optional: Bearer key for tonapi
|
|
17
|
+
})
|
|
18
|
+
const account = await wallet.getAccount(0)
|
|
19
|
+
|
|
20
|
+
account.describe({ to: 'UQ…', value: 100_000_000n, body: 'thanks' }) // offline: kind, items, warnings
|
|
21
|
+
await account.simulateTransaction({ to: 'UQ…', value: 100_000_000n }) // fees + emulation verdict + risk (what leaves the wallet)
|
|
22
|
+
await account.transfer({ recipient: 'UQ…', amount: 100_000_000n }) // 0.1 TON
|
|
23
|
+
await account.transfer({ token: USDT_MASTER, recipient: 'UQ…', amount: 1_000_000n, forwardPayload: 'hi' })
|
|
24
|
+
await account.sendTransaction([ // several messages, ONE external
|
|
25
|
+
{ to: 'EQ…', value: 50_000_000n, bodyBoc, stateInit }, // e.g. an Omniston escrow deploy
|
|
26
|
+
{ to: 'UQ…', value: 1n },
|
|
27
|
+
])
|
|
28
|
+
const receipt = await account.getTransactionReceipt(hash) // hash = body hash, via toncenter v3
|
|
29
|
+
wallet.dispose()
|
|
30
|
+
|
|
31
|
+
// Tonkeeper-style 24-word TON mnemonic (not BIP-39): one account, same surface.
|
|
32
|
+
const tk = await WalletManagerTon.fromTonMnemonic(words, { tonClient })
|
|
33
|
+
```
|
|
34
|
+
|
|
35
|
+
## Every send
|
|
36
|
+
|
|
37
|
+
1. Hard checks, before any network call: value > 0, workchain 0/-1 only,
|
|
38
|
+
friendly-address network flag matches `config.network`, `valid_until` =
|
|
39
|
+
now + `validUntilSeconds` (default 60, max 600).
|
|
40
|
+
2. Fresh seqno (never cached across sends).
|
|
41
|
+
3. Preflight on the zero-signed body: toncenter `estimateFee` (the fee cap)
|
|
42
|
+
and a trace emulation — tonapi by default (`POST /v2/wallet/emulate`,
|
|
43
|
+
falling back to `/v2/traces/emulate`), or a toncenter-v3 `emulateTrace`
|
|
44
|
+
endpoint via `emulate: {kind: 'toncenter-v3', url}`. A non-zero compute exit,
|
|
45
|
+
an aborted transaction, a failed action phase or a failed **first-hop**
|
|
46
|
+
internal message (the operation would bounce) throws `SimulationError`
|
|
47
|
+
**before signing**; failures deeper in the trace are `warnings`. tonapi's
|
|
48
|
+
`risk` is returned as `risk` and a body that would carry the whole balance
|
|
49
|
+
(send mode 128) is refused with `UnsafeTransactionError('drain')` unless
|
|
50
|
+
`allowDrainingTransactions`. `emulate: false` keeps only `estimateFee`;
|
|
51
|
+
`simulate: false` skips the preflight entirely.
|
|
52
|
+
4. noble ed25519 over the body hash; the 32-byte seed is the only key material
|
|
53
|
+
and `dispose()` zeroizes it.
|
|
54
|
+
5. `sendBoc` of the external (with StateInit when the wallet is not deployed).
|
|
55
|
+
|
|
56
|
+
## Signers
|
|
57
|
+
|
|
58
|
+
The account never holds a key. Every signature is a `signer.sign(bytes, {scheme: 'ed25519', context})`
|
|
59
|
+
call: `ton-external` over the hash of the V5R1 signing cell (after the preflight, which runs on a
|
|
60
|
+
zero-signed body), `ton-message` over raw message bytes (`sign()`, ton_proof). Seed wallets get a
|
|
61
|
+
`LocalSigner`; a hardware wallet, MPC node or backend is wrapped with `externalSigner()` from
|
|
62
|
+
`@anywalletkit/core`:
|
|
63
|
+
|
|
64
|
+
```ts
|
|
65
|
+
const signer = externalSigner({ curve: 'ed25519', publicKey, sign: (payload, { context }) => device.sign(payload) })
|
|
66
|
+
const manager = new WalletManagerTon(signer, { tonClient })
|
|
67
|
+
const account = await manager.getAccount() // path 'external'; other indexes throw
|
|
68
|
+
```
|
|
69
|
+
|
|
70
|
+
A derivable `SeedSigner` at `m/44'/607'` yields `getAccount(i)` children; a leaf signer (including
|
|
71
|
+
`fromTonMnemonic`) is one account. `WalletAccountTon.fromPrivateKey(priv, pub, path)` keeps the
|
|
72
|
+
raw-key shape for callers that derive themselves.
|
|
73
|
+
|
|
74
|
+
## Describe
|
|
75
|
+
|
|
76
|
+
`describeTransaction(tx)` / `account.describe(tx)` decode TON transfers (text
|
|
77
|
+
comments), jetton transfers (`0x0f8a7ea5`: amount, destination, forward
|
|
78
|
+
amount/payload, custom payload) and contract calls, also from a prebuilt V5R1
|
|
79
|
+
body, with warnings: `zero-value`, `non-bounceable-contract-call`,
|
|
80
|
+
`unknown-body`, `large-forward-amount`, `testnet-address` / `mainnet-address`,
|
|
81
|
+
`exotic-workchain`.
|
|
82
|
+
|
|
83
|
+
## Buffer
|
|
84
|
+
|
|
85
|
+
On import the package installs the `buffer` polyfill as `globalThis.Buffer` if
|
|
86
|
+
none exists (`@ton/core` requires the global). Node, and apps that already set
|
|
87
|
+
it, are untouched.
|
|
88
|
+
|
|
89
|
+
## React Native
|
|
90
|
+
|
|
91
|
+
`@ton/crypto-primitives` resolves its `react-native` build on Metro, which
|
|
92
|
+
requires `expo-crypto` (random bytes) at module load and
|
|
93
|
+
`react-native-fast-pbkdf2` for the TON-mnemonic import. Install `expo-crypto`
|
|
94
|
+
in the app (Expo projects already have it). BIP-39 wallets sign through noble
|
|
95
|
+
ed25519 and need neither.
|
|
96
|
+
|
|
97
|
+
## Activity history
|
|
98
|
+
|
|
99
|
+
`createTonHistory` is the chain's `HistorySource` (`@anywalletkit/core`): tonapi account events first, toncenter v3 as a reduced fallback.
|
|
100
|
+
|
|
101
|
+
```ts
|
|
102
|
+
import { createTonHistory } from '@anywalletkit/wallet-ton/history'
|
|
103
|
+
|
|
104
|
+
const history = createTonHistory({ apiKey: process.env.TONAPI_KEY })
|
|
105
|
+
const page = await history.listActivity('UQCbXJ1-Hd_CyyAt3TNgircduNIn5QH5dj1_LBNz__y4fQaq', { limit: 25 })
|
|
106
|
+
const older = await history.listActivity(address, { cursor: page.cursor })
|
|
107
|
+
const one = await history.getTransaction(page.items[0].hash, address)
|
|
108
|
+
history.explorerTxUrl(one.hash) // https://tonviewer.com/transaction/…
|
|
109
|
+
```
|
|
110
|
+
|
|
111
|
+
| option | default | notes |
|
|
112
|
+
|---|---|---|
|
|
113
|
+
| `tonapiUrl` | `https://tonapi.io` (`testnet.tonapi.io`) | `null` disables tonapi. |
|
|
114
|
+
| `apiKey` | none | tonapi Bearer key. Keyless tonapi allows ~1 request/s. |
|
|
115
|
+
| `toncenterUrl` | `https://toncenter.com` (`testnet.toncenter.com`) | v3 fallback; `null` disables it. |
|
|
116
|
+
| `toncenterApiKey` | none | `X-API-Key`. |
|
|
117
|
+
| `network` | `mainnet` | `ton:-239` / `ton:-3`. |
|
|
118
|
+
| `rateLimit` | 1 rps keyless, 10 with a key | tonapi requests per second (toncenter: 1 keyless, 10 with a key). |
|
|
119
|
+
| `fetch`, `timeoutMs` | global, 15 000 | |
|
|
120
|
+
|
|
121
|
+
**tonapi** (`GET /v2/accounts/{a}/events?limit=&before_lt=`, `GET /v2/accounts/{a}/events/{id}`): one event = one trace, with typed actions. `TonTransfer`, `JettonTransfer`, `JettonMint`, `JettonBurn`, `JettonSwap` (TON / jetton in and out against the DEX router), `SmartContractExec` (`ton_attached`), `DepositStake` / `WithdrawStake` (staker ↔ pool), `Subscribe`, `NftPurchase`, elections become transfers; jetton transfers carry the master as `token`, `standard: 'jetton'`, `symbol` and `decimals` from the action's jetton object. The first contract-level action is the `call`: `SmartContractExec` → `to` = contract, hex op in `data`, named op in `method`; `JettonSwap` → router / `swap`; a jetton sent to a contract with a forward payload → recipient / `jetton_transfer` with the op from tonapi's `Call: 0x…` comment; `DepositStake` → pool / `stake`, `WithdrawStakeRequest` → pool / `unstake`, `WithdrawStake` → pool / `withdraw_stake`. tonapi does not spell out the pool-token burn of an unstake request, so for those events the source fetches `/v2/events/{id}` once and turns the account's `value_flow` jetton deltas into transfers (`raw.valueFlow`). `from` is the first action's initiator, `nativeValue` the TON it sent, `fee` = `-extra` (tonapi's "what the account lost beyond its actions", so it includes forward fees the actions do not show), `status` = `pending` while `in_progress`, `failed` when every action failed, `block` = the event's `lt`, `hash` = the event id (the trace root; tonapi resolves any transaction hash of the trace to it). `is_scam` events are flagged `scam: true` (also in `raw.scam`). Addresses stay raw (`0:…`, lowercase) as tonapi returns them.
|
|
122
|
+
|
|
123
|
+
**toncenter v3** (`GET /api/v3/transactions?account=&limit=&sort=desc&end_lt=`): the account's own transactions only. An external message (the wallet acted) maps its outgoing messages to TON transfers and the first op code to `call` (`data` = `opcode`, `method` = `decoded_opcode`); an incoming message maps its value and op. Jettons are not visible here, `fee` = `total_fees`, `hash` = the transaction hash in hex.
|
|
124
|
+
|
|
125
|
+
**Cursor.** Base64 JSON `{ v: 1, b: 'tonapi' | 'toncenter', lt }`: an exclusive `lt` upper bound (`before_lt` for tonapi, `end_lt = lt − 1` for toncenter). A cursor from one backend resumes on the other; the backend that issued it is tried first. `since` is applied client-side and ends pagination.
|
|
126
|
+
|
|
127
|
+
Fixtures in `test/fixtures/history/` were captured on 2026-10-14 from `tonapi.io` and `toncenter.com` (keyless) for the test wallet: one events page, the account-scoped events of the Tonstakers stake / unstake request / payout and of the Omniston STON.fi swap and escrow order (the same transactions as those modules' activity fixtures), the full event with `value_flow` for the unstake, and a toncenter v3 page. `test/history.test.ts` checks that the Tonstakers and Omniston modules describe the rows this source builds (`stake`, `unstake`, `claim`, `swap`, `bridge`). Note: `@anywalletkit/protocol-swap2-core`'s `netTransfers` compares addresses verbatim, so `DescribeActivityContext.own` must contain the raw `0:…` form of the wallet for Omniston (Tonstakers normalizes itself).
|