-
Notifications
You must be signed in to change notification settings - Fork 4
Expand file tree
/
Copy pathbasic-data-types.html
More file actions
464 lines (411 loc) · 27.5 KB
/
basic-data-types.html
File metadata and controls
464 lines (411 loc) · 27.5 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width">
<title>Basic Data Types - XAG Ledger Dev Portal</title>
<!-- favicon -->
<link rel="apple-touch-icon" sizes="180x180" href="assets/favicons/apple-touch-icon.png">
<link rel="icon" type="image/png" sizes="16x16" href="assets/favicons/favicon-16x16.png">
<link rel="icon" type="image/png" sizes="32x32" href="assets/favicons/favicon-32x32.png">
<link rel="manifest" href="assets/favicons/site.webmanifest">
<link rel="shortcut icon" href="favicon.ico">
<meta name="msapplication-TileColor" content="#25A768">
<meta name="msapplication-config" content="assets/favicons/browserconfig.xml">
<meta name="theme-color" content="#25A768">
<!-- jQuery -->
<script src="assets/vendor/jquery-1.11.1.min.js"></script>
<!-- Stylesheet -->
<link href="assets/css/devportal.css" rel="stylesheet" />
<link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/docsearch.js@2/dist/cdn/docsearch.min.css" />
<!-- syntax highlighting -->
<link rel="stylesheet" href="assets/vendor/docco.min.css" />
<script src="assets/vendor/highlight.min.js"></script>
<!-- expandable code samples -->
<script src="assets/js/expandcode.js"></script>
<!-- multi-code selection tabs -->
<script src="assets/js/multicodetab.js"></script>
<script>
$(document).ready(function() {
$(".multicode").minitabs();
hljs.initHighlighting();
make_code_expandable();
});
</script>
</head>
<body class="xrp-ledger-dev-portal sidebar-primary lang-en ">
<nav class="navbar fixed-top navbar-expand-lg navbar-light bg-white">
<a href="index.html" class="navbar-brand"><img src="assets/img/logo.png" class="logo" height="44" alt="XAG Ledger Dev Portal" /></a>
<button class="navbar-toggler" type="button" data-toggle="slide-collapse" data-target="#navbarHolder" aria-controls="navbarNav" aria-expanded="false" aria-label="Toggle navigation">
<span class="navbar-toggler-icon"></span>
</button>
<div class="collapse navbar-collapse justify-content-end" id="navbarHolder">
<ul class="nav navbar-nav">
<li class="nav-item">
<a class="nav-link" href="dev-tools.html">Dev Tools</a>
</li>
<li class="nav-item">
<a class="nav-link" href="http://xagfans.com/" target="blank">BBS</a>
</li>
</ul>
<div class="nav navbar-nav language-selector">
<div class="dropdown">
<button class="btn btn-outline-secondary dropdown-toggle" type="button" id="language_selector_header_btn" data-toggle="dropdown" aria-haspopup="true" aria-expanded="false">
English
</button>
<div class="dropdown-menu" aria-labelledby="language_selector_header_btn">
<a class="dropdown-item" href="/basic-data-types.html">English</a>
<a class="dropdown-item" href="/cn/basic-data-types.html">中文</a>
</div><!--/.dropdown-menu-->
</div><!--/.dropdown-->
</div><!--/.language-selector-->
</div><!--/#navbarHolder-->
<div class="menu-overlay"></div>
</nav>
<div class="container-fluid" role="document" id="main_content_wrapper">
<div class="row">
<!-- Right sidebar first so it's at the beginning for mobile layouts -->
<aside class="right-sidebar col-lg-3 order-lg-4 p-0" role="complementary">
<div class="card" id="page-toc-wrapper">
<div class="card-header">
<h4>In this document</h4>
</div>
<ul class="card-body">
<li class="level-1"><a href="#basic-data-types">Basic Data Types</a></li>
<li class="level-2"><a href="#addresses">Addresses</a></li>
<li class="level-2"><a href="#hashes">Hashes</a></li>
<li class="level-3"><a href="#hash-prefixes">Hash Prefixes</a></li>
<li class="level-2"><a href="#account-sequence">Account Sequence</a></li>
<li class="level-2"><a href="#ledger-index">Ledger Index</a></li>
<li class="level-3"><a href="#specifying-ledgers">Specifying Ledgers</a></li>
<li class="level-2"><a href="#specifying-currency-amounts">Specifying Currency Amounts</a></li>
<li class="level-2"><a href="#specifying-time">Specifying Time</a></li>
</ul>
</div>
</aside>
<!-- main column -->
<main class="main col-md-7 col-lg-6 order-md-3 " role="main" id="main_content_body">
<nav class="breadcrumbs-wrap p-0 p-md-3" aria-label="breadcrumb">
<ul class="breadcrumb bg-white">
<li class="breadcrumb-item"><a href="index.html">Home</a></li>
<li class="active breadcrumb-item"><a href="docs.html">Docs</a></li>
<li class="active breadcrumb-item"><a href="references.html">References</a></li>
<li class="active breadcrumb-item"><a href="rippled-api.html">rippled API Reference</a></li>
<li class="active breadcrumb-item"><a href="api-conventions.html">API Conventions</a></li>
<li class="active breadcrumb-item">Basic Data Types</li>
</ul>
</nav><!--/.breadcrumbs-wrap--> <article class="pt-3 p-md-3">
<div class="content">
<h1 id="basic-data-types">Basic Data Types</h1>
<p>Different types of objects are uniquely identified in different ways:</p>
<p><a href="accounts.html">Accounts</a> are identified by their <a href="basic-data-types.html#addresses">Address</a>, for example <code>"r9cZA1mLK5R5Am25ArfXFmqgNwjZgnfk59"</code>. Addresses always start with "r". Many <code>rippled</code> methods also accept a hexadecimal representation.</p>
<p><a href="transaction-formats.html">Transactions</a> are identified by a <a href="basic-data-types.html#hashes">Hash</a> of the transaction's binary format. You can also identify a transaction by its sending account and <a href="basic-data-types.html#account-sequence">Sequence Number</a>.</p>
<p>Each closed <a href="ledger-data-formats.html">Ledger</a> has a <a href="basic-data-types.html#ledger-index">Ledger Index</a> and a <a href="basic-data-types.html#hashes">Hash</a> value. When <a href="basic-data-types.html#specifying-ledgers">Specifying Ledgers</a> you can use either one.</p>
<h2 id="addresses">Addresses</h2>
<p>Accounts in the XAG Ledger are identified by an address in the XAG Ledger's <a href="base58-encodings.html">base58</a> format. The address is derived from the account's master <a class="external-link" href="https://en.wikipedia.org/wiki/Public-key_cryptography" target="_blank">public key <i aria-hidden="true" class="fa fa-external-link"></i></a>, which is in turn derived from a secret key. An address is represented as a string in JSON and has the following characteristics:</p>
<ul>
<li>Between 25 and 35 characters in length</li>
<li>
<p>Starts with the character <code>r</code></p>
</li>
<li>
<p>Uses alphanumeric characters, excluding the number "<code>0</code>" capital letter "<code>O</code>", capital letter "<code>I</code>", and lowercase letter "<code>l</code>"</p>
</li>
<li>Case-sensitive</li>
<li>Includes a 4-byte checksum so that the probability of generating a valid address from random characters is approximately 1 in 2^32</li>
</ul>
<p>For more information, see <a href="accounts.html">Accounts</a> and <a href="base58-encodings.html">base58 Encodings</a>.</p>
<!-- -->
<h2 id="hashes">Hashes</h2>
<p>Many objects in the XAG Ledger, particularly transactions and ledgers, are uniquely identified by a 256-bit hash value. This value is typically calculated as a "SHA-512Half", which calculates a <a class="external-link" href="http://dx.doi.org/10.6028/NIST.FIPS.180-4" target="_blank">SHA-512 <i aria-hidden="true" class="fa fa-external-link"></i></a> hash from some contents, then takes the first half of the output. (That's 256 bits, which is 32 bytes, or 64 characters of the hexadecimal representation.) Since the hash of an object is derived from the contents in a way that is extremely unlikely to produce collisions, two objects with the same hash can be considered the same.</p>
<p>An XAG Ledger hash value has the following characteristics:</p>
<ul>
<li>Exactly 64 characters in length</li>
<li><a class="external-link" href="https://en.wikipedia.org/wiki/Hexadecimal" target="_blank">Hexadecimal <i aria-hidden="true" class="fa fa-external-link"></i></a> character set: 0-9 and A-F.</li>
<li>Typically written in upper case.</li>
</ul>
<p class="devportal-callout note"><strong>Note:</strong> SHA-512Half has similar security to the officially-defined <em>SHA-512/256</em> hash function. However, the XAG Ledger's usage predates SHA-512/256 and is also easier to implement on top of an existing SHA-512 function. (As of this writing, SHA-512 support in cryptographic libraries is much more common than for SHA-512/256.)
<!-- --></p>
<h3 id="hash-prefixes">Hash Prefixes</h3>
<p><a class="external-link" href="https://github.com/ripple/rippled/blob/master/src/ripple/protocol/HashPrefix.h" target="_blank" title="Source">[Source] <i aria-hidden="true" class="fa fa-external-link"></i></a></p>
<p>In many cases, the XAG Ledger prefixes an object's binary data with a 4-byte code before calculating its hash, so that objects of different types have different hashes even if their binary formats are the same. The existing 4-byte codes are structured as three alphabetic characters, encoded as ASCII, followed by a zero byte.</p>
<p>Some types of hash appear in API requests and responses. Others are only calculated as the first step of signing a certain type of data, or calculating a higher-level hash. The following table shows all 4-byte hash prefixes the XAG Ledger uses:</p>
<table>
<thead>
<tr>
<th align="left">Object Type</th>
<th align="left">API Fields</th>
<th align="left">Hash Prefix (Hex)</th>
<th align="left">Hash Prefix (Text)</th>
</tr>
</thead>
<tbody>
<tr>
<td align="left">Consensus proposal</td>
<td align="left">N/A</td>
<td align="left"><code>0x50525000</code></td>
<td align="left"><code>PRP\0</code></td>
</tr>
<tr>
<td align="left">Ledger Version</td>
<td align="left"><code>ledger_hash</code></td>
<td align="left"><code>0x4C575200</code></td>
<td align="left"><code>LWR\0</code></td>
</tr>
<tr>
<td align="left">Ledger state data</td>
<td align="left"><code>account_state</code> in <a href="ledger-header.html">ledger header</a></td>
<td align="left"><code>0x4D4C4E00</code></td>
<td align="left"><code>MLN\0</code></td>
</tr>
<tr>
<td align="left">Ledger data inner node</td>
<td align="left">N/A</td>
<td align="left"><code>0x4D494E00</code></td>
<td align="left"><code>MIN\0</code></td>
</tr>
<tr>
<td align="left">Ledger data inner node (<a href="known-amendments.html#shamapv2">SHAMapv2</a>)</td>
<td align="left">N/A</td>
<td align="left"><code>0x494E5200</code></td>
<td align="left"><code>INR\0</code></td>
</tr>
<tr>
<td align="left">Payment Channel Claim</td>
<td align="left">N/A</td>
<td align="left"><code>0x434C4D00</code></td>
<td align="left"><code>CLM\0</code></td>
</tr>
<tr>
<td align="left">Signed Transaction</td>
<td align="left"><code>hash</code> of transactions</td>
<td align="left"><code>0x54584E00</code></td>
<td align="left"><code>TXN\0</code></td>
</tr>
<tr>
<td align="left">Transaction with metadata</td>
<td align="left">N/A</td>
<td align="left"><code>0x534E4400</code></td>
<td align="left"><code>SND\0</code></td>
</tr>
<tr>
<td align="left">Unsigned Transaction (Single-signing)</td>
<td align="left">N/A</td>
<td align="left"><code>0x53545800</code></td>
<td align="left"><code>STX\0</code></td>
</tr>
<tr>
<td align="left">Unsigned Transaction (Multi-signing)</td>
<td align="left">N/A</td>
<td align="left"><code>0x534D5400</code></td>
<td align="left"><code>SMT\0</code></td>
</tr>
<tr>
<td align="left">Validation vote</td>
<td align="left">N/A</td>
<td align="left"><code>0x56414C00</code></td>
<td align="left"><code>VAL\0</code></td>
</tr>
<tr>
<td align="left">Validator subkey authorization ("validator manifest")</td>
<td align="left">N/A</td>
<td align="left"><code>0x4D414E00</code></td>
<td align="left"><code>MAN\0</code></td>
</tr>
</tbody>
</table>
<p><a href="ledger-object-ids.html">Ledger objects IDs</a> are calculated in a similar way, but they use a 2-byte prefix called a "space key" instead of a prefix in the form described here.</p>
<h2 id="account-sequence">Account Sequence</h2>
<p>A sequence number is a 32-bit unsigned integer that is used to make sure transactions from a given sender execute only once each, and in the correct order.</p>
<p>Every <a href="accounts.html">account in the XAG Ledger</a> has a sequence number in its <code>Sequence</code> field, which increases by 1 whenever that account sends a transaction and that transaction gets included in a <a href="ledgers.html">validated ledger</a>. Each <a href="transaction-basics.html">transaction</a> also has a sequence number in its <code>Sequence</code> field, which must match the account's current sequence number when the transaction executes. For each account, each sequence number can only be used once, in numerical order.</p>
<p>With the <a href="known-amendments.html#deletableaccounts">DeletableAccounts amendment</a>, the starting <code>Sequence</code> number for an account matches the <a href="basic-data-types.html#ledger-index">Ledger Index</a> of the ledger version where the account was created. Before DeletableAccounts, every account started with <code>Sequence</code> number 1.</p>
<p>Whenever a transaction is included in a ledger, it uses up a sequence number regardless of whether the transaction executed successfully or failed with a <a href="tec-codes.html"><code>tec</code>-class error code</a>. Other transaction failures don't get included in ledgers, so they don't change the sender's sequence number (or have any other effects).</p>
<p>It is possible for multiple unconfirmed transactions to have the same sender and sequence number. Such transactions are mutually exclusive, and at most one of them can be included in a validated ledger. (Any others ultimately have no effect.)
<!-- --></p>
<h2 id="ledger-index">Ledger Index</h2>
<p>A ledger index is a 32-bit unsigned integer used to identify a ledger. The ledger index is sometimes known as the ledger's <em>sequence number</em>. (This is different from an <a href="basic-data-types.html#account-sequence">account sequence</a>.) The very first ledger was ledger index 1, and each new ledger has a ledger index that is 1 higher than the ledger index of the ledger immediately before it.</p>
<p>The ledger index indicates the order of the ledgers; the <a href="basic-data-types.html#hashes">Hash</a> value identifies the exact contents of the ledger. Two ledgers with the same hash are always the same. For validated ledgers, hash values and ledger indexes are equally valid and correlate 1:1. However, this is not true for in-progress ledgers:</p>
<ul>
<li>Two different <code>rippled</code> servers may have different contents for a current ledger with the same ledger index, due to latency in propagating transactions throughout the network.</li>
<li>There may be multiple closed ledger versions competing to be validated by consensus. These ledger versions have the same ledger index but different contents (and different hashes). Only one of these closed ledgers can become validated.</li>
<li>The current open ledger's hash is not calculated. This is because a current ledger's contents change over time, which would cause its hash to change, even though its ledger index stays the same. The hash of a ledger is only calculated when the ledger is closed.
<!-- --></li>
</ul>
<h3 id="specifying-ledgers">Specifying Ledgers</h3>
<p>Many API methods require you to specify an instance of the ledger, with the data retrieved being considered up-to-date as of that particular version of the shared ledger. The commands that accept a ledger version all work the same way. There are three ways you can specify which ledger you want to use:</p>
<ol>
<li>Specify a ledger by its <a href="basic-data-types.html#ledger-index">Ledger Index</a> in the <code>ledger_index</code> parameter. Each closed ledger has a ledger index that is 1 higher than the previous ledger. (The very first ledger had ledger index 1.)</li>
<li>Specify a ledger by its <a href="basic-data-types.html#hashes">Hash</a> value in the <code>ledger_hash</code> parameter.</li>
<li>Specify a ledger by one of the following shortcuts, in the <code>ledger_index</code> parameter:<ul>
<li><code>validated</code> for the most recent ledger that has been validated by the whole network</li>
<li><code>closed</code> for the most recent ledger that has been closed for modifications and proposed for validation</li>
<li><code>current</code> for the server's current working version of the ledger.</li>
</ul>
</li>
</ol>
<p>There is also a deprecated <code>ledger</code> parameter which accepts any of the above three formats. <em>Do not</em> use this parameter; it may be removed without further notice.</p>
<p>If you do not specify a ledger, the <code>current</code> (in-progress) ledger is chosen by default. If you provide more than one field specifying ledgers, the deprecated <code>ledger</code> field is used first if it exists, falling back to <code>ledger_hash</code>. The <code>ledger_index</code> field is ignored unless neither of the other two are present.</p>
<p class="devportal-callout note"><strong>Note:</strong> Do not rely on this default behavior for specifying a ledger; it is subject to change. Always specify a ledger version in the request if you can.</p>
<h2 id="specifying-currency-amounts">Specifying Currency Amounts</h2>
<p>There are two kinds of currencies in the XAG Ledger: XAG, and issued currencies. These two types of currencies are specified in different formats, with different precision and rounding behavior.</p>
<p>Some fields, such as the destination <code>Amount</code> of a <a href="payment.html">Payment transaction</a>, can be either type. Some fields only accept XAG specifically, such as the <code>Fee</code> field (<a href="transaction-cost.html">transaction cost</a>).</p>
<p>XAG is specified as a string containing an integer number of "drops" of XAG, where 1 million drops equals 1 XAG. Issued currencies are instead specified as an object with fields for the decimal amount, currency code, and issuer. For example:</p>
<ul>
<li>
<p><strong>XAG</strong> - To specify an <code>Amount</code> field with a value of 13.1 XAG:</p>
<pre><code>"Amount": "13100000"
</code></pre>
</li>
<li>
<p><strong>Issued Currency</strong> - To specify an <code>Amount</code> field with a value of 13.1 FOO issued by or to rf1B...:</p>
<pre><code>"Amount": {
"value": "13.1",
"currency": "FOO",
"issuer": "rf1BiGeXwwQoi8Z2ueFYTEXSwuJYfV2Jpn"
}
</code></pre>
</li>
</ul>
<p>For more information, see <a href="currency-formats.html">Currency Formats</a>.</p>
<h2 id="specifying-time">Specifying Time</h2>
<p>The <code>rippled</code> server and its APIs represent time as an unsigned integer. This number measures the number of seconds since the "Ripple Epoch" of January 1, 2000 (00:00 UTC). This is like the way the <a class="external-link" href="http://en.wikipedia.org/wiki/Unix_time" target="_blank">Unix epoch <i aria-hidden="true" class="fa fa-external-link"></i></a> works, except the Ripple Epoch is 946684800 seconds after the Unix Epoch.</p>
<p>Don't convert Ripple Epoch times to UNIX Epoch times in 32-bit variables: this could lead to integer overflows.</p>
<!-- -->
<!-- -->
<!-- API object types -->
<!-- -->
<!-- -->
<!-- -->
<!-- rippled release notes links -->
</div>
</article>
</main>
<!-- Left sidebar last so it's at the end for mobile -->
<aside class="sidebar col-md-5 col-lg-3 p-0 order-md-1" role="complementary">
<div class="tree_nav">
<!---->
<div class="sidenav_parent">
<a href="rippled-api.html"> rippled API Reference</a>
</div>
<!---->
<!---->
<div id="sidenav" role="tablist" aria-multiselectable="true">
<div class="card active">
<div class="card-header" role="tab" id="sidenav_cat_head_14">
<a class="sidenav_cat_toggler" role="button" data-toggle="collapse" href="#sidenav_collapse_14" aria-expanded="true" aria-controls="sidenav_collapse_14"></a>
<h5 class="card-title">
<a class="sidenav_cat_title active-parent" href="api-conventions.html">API Conventions</a>
</h5>
</div><!-- /.card-header -->
<div id="sidenav_collapse_14" class="collapse show" role="tabpanel" aria-labelledby="sidenav_cat_head_14">
<div class="card-body">
<ul class="sidebar_pagelist">
<li><a class="active nosubcat-page" href="basic-data-types.html">Basic Data Types</a></li>
<li><a class="nosubcat-page" href="base58-encodings.html">base58 Encodings</a></li>
<li><a class="nosubcat-page" href="currency-formats.html">Currency Formats</a></li>
<li><a class="nosubcat-page" href="error-formatting.html">Error Formatting</a></li>
<li><a class="nosubcat-page" href="markers-and-pagination.html">Markers and Pagination</a></li>
<li><a class="nosubcat-page" href="modifying-the-ledger.html">Modifying the Ledger</a></li>
<li><a class="nosubcat-page" href="rate-limiting.html">Rate Limiting</a></li>
<li><a class="nosubcat-page" href="request-formatting.html">Request Formatting</a></li>
<li><a class="nosubcat-page" href="response-formatting.html">Response Formatting</a></li>
<li><a class="nosubcat-page" href="rippled-server-states.html">rippled Server States</a></li>
<li><a class="nosubcat-page" href="serialization.html">Serialization Format</a></li>
</ul>
</div><!-- /.card-body -->
</div><!-- /#sidenav_collapse14 -->
</div><!-- /.panel -->
<div class="card">
<div class="card-header" role="tab" id="sidenav_cat_head_15">
<a class="collapsed sidenav_cat_toggler" role="button" data-toggle="collapse" href="#sidenav_collapse_15" aria-expanded="true" aria-controls="sidenav_collapse_15"></a>
<h5 class="card-title">
<a class="sidenav_cat_title" href="public-rippled-methods.html">Public rippled Methods</a>
</h5>
</div><!-- /.card-header -->
<div id="sidenav_collapse_15" class="collapse" role="tabpanel" aria-labelledby="sidenav_cat_head_15">
<div class="card-body">
<ul class="sidebar_pagelist">
<li><a class="subcat-title" href="account-methods.html">Account Methods</a></li>
<li><a class="subpage" href="account_currencies.html">account_currencies</a></li>
<li><a class="subpage" href="account_info.html">account_info</a></li>
<li><a class="subpage" href="account_lines.html">account_lines</a></li>
<li><a class="subpage" href="account_objects.html">account_objects</a></li>
<li><a class="subpage" href="account_offers.html">account_offers</a></li>
<li><a class="subpage" href="account_tx.html">account_tx</a></li>
<li><a class="subpage" href="gateway_balances.html">gateway_balances</a></li>
<li><a class="subpage" href="noripple_check.html">noripple_check</a></li>
<li><a class="subcat-title" href="ledger-methods.html">Ledger Methods</a></li>
<li><a class="subpage" href="ledger.html">ledger</a></li>
<li><a class="subpage" href="ledger_closed.html">ledger_closed</a></li>
<li><a class="subpage" href="ledger_current.html">ledger_current</a></li>
<li><a class="subpage" href="ledger_data.html">ledger_data</a></li>
<li><a class="subpage" href="ledger_entry.html">ledger_entry</a></li>
<li><a class="subcat-title" href="transaction-methods.html">Transaction Methods</a></li>
<li><a class="subpage" href="sign.html">sign</a></li>
<li><a class="subpage" href="sign_for.html">sign_for</a></li>
<li><a class="subpage" href="submit.html">submit</a></li>
<li><a class="subpage" href="submit_multisigned.html">submit_multisigned</a></li>
<li><a class="subpage" href="transaction_entry.html">transaction_entry</a></li>
<li><a class="subpage" href="tx.html">tx</a></li>
<li><a class="subpage" href="tx_history.html">tx_history</a></li>
<li><a class="subcat-title" href="path-and-order-book-methods.html">Path and Order Book Methods</a></li>
<li><a class="subpage" href="book_offers.html">book_offers</a></li>
<li><a class="subpage" href="deposit_authorized.html">deposit_authorized</a></li>
<li><a class="subpage" href="path_find.html">path_find</a></li>
<li><a class="subpage" href="ripple_path_find.html">ripple_path_find</a></li>
<li><a class="subcat-title" href="subscription-methods.html">Subscription Methods</a></li>
<li><a class="subpage" href="subscribe.html">subscribe</a></li>
<li><a class="subpage" href="unsubscribe.html">unsubscribe</a></li>
</ul>
</div><!-- /.card-body -->
</div><!-- /#sidenav_collapse15 -->
</div><!-- /.panel -->
</div><!-- /.panel -->
</div><!-- /#sidenav -->
</div><!-- /.tree_nav --> </aside>
</div><!--/.row (main layout)-->
</div>
<footer class="xrpl-footer" role="contentinfo">
<section class="container-fluid p-5 pl-sm-0">
<nav role="navigation" class="d-flex mb-3 language-selector">
<img class="language_selector_icon" src="assets/img/icon-language-selector.svg" width="32" height="40" alt="language selection icon" />
<ul class="nav">
<li class="nav-item">
<a class="nav-link active" href="/basic-data-types.html"><i class="fa fa-check-circle"></i> English</a>
</li>
<li class="nav-item">
<a class="nav-link" href="/cn/basic-data-types.html">中文
</a>
</li>
</ul>
</nav>
<div class="absolute_bottom_footer">
<span>© XAG Ledger Project 2020</span>
<span><a href="">License</a></span>
</div><!-- /.absolute_bottom_footer -->
</section>
</footer>
<!-- Jump to top button -->
<a href="#main_content_wrapper" class="jump-to-top btn btn-primary btn-lg" role="button" title="Jump to top of page">Top</a>
<script type="text/javascript" src="assets/js/jump-to-top.js"></script>
<!-- Non-blocking resources -->
<!-- Bootstrap JS -->
<script src="assets/vendor/bootstrap.min.js"></script>
<!-- fontawesome icons -->
<link rel="stylesheet" href="assets/vendor/fontawesome/css/font-awesome.min.css" />
<!-- Algolia DocSearch -->
<script type="text/javascript" src="https://cdn.jsdelivr.net/npm/docsearch.js@2/dist/cdn/docsearch.min.js"></script>
<script type="text/javascript"> docsearch({
apiKey: '70de5b9b8ef95460f3c6e04054b325b2',
indexName: 'xrpl',
inputSelector: '#topsearchbar',
algoliaOptions: { 'facetFilters': ["lang:en"] },
debug: false
});
</script>
<script type="application/javascript">
gtag('set', {'content_group1': 'Content Docs'});
</script>
</body>
</html>