You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You can choose the most reliable provider for you and your region.
7
+
Choose the provider most reliable for your needs and region.
8
8
9
9
[Open the TXMS Status page](https://txms.info)
10
10
11
-
## How does it work?
11
+
## How Does It Work?
12
12
13
-
This tool using for conversion encoding UTF-16 Big Endian (UTF-16BE).
13
+
This tool is used for converting HEX encoding to UTF-16 Big Endian (UTF-16BE).
14
14
15
-
### What is UTF-16 and (Big, Little) Endian?
15
+
### What Are UTF-16 and (Big, Little) Endian?
16
16
17
-
UTF-16 is a character encoding capable of encoding all 1,112,064 valid code points of Unicode.
17
+
UTF-16 is a character encoding that can encode all 1,112,064 valid Unicode code points.
18
18
19
-
Big-endian is an order in which the "big end" (most significant value in the sequence) is stored first, at the lowest storage address.
19
+
Big-endian is an order in which the "big end" (most significant value in the sequence) is stored first at the lowest storage address.
20
20
21
-
Little-endian is an order, in which the "little end" (least significant value in the sequence) is stored first.
21
+
In contrast, little-endian is an order where the "little end" (least significant value in the sequence) is stored first.
22
22
23
23
Byte Index | 0 | 1
24
24
--- | --- | ---
25
25
Big-Endian | 12 | 34
26
26
Little-Endian | 34 | 12
27
27
28
-
## Practical use
28
+
## Practical Use
29
29
30
-
### Negative №1
30
+
### Disadvantage 1
31
31
32
-
SMS can encode 160 7-bit characters into 140 bytes, but even that not all characters represent 1 character. Certain characters in GSM 03.38 require an escape character, such as: `|, ^, {, }, €, [, ~, ]` and `\`.
32
+
An SMS can encode 160 7-bit characters into 140 bytes. However, not all characters represent 1 character. Certain characters in GSM 03.38 require an escape character, such as: `|, ^, {, }, €, [, ~, ]` and `\`.
33
33
34
-
In Unicode SMS we are limited to 70 characters (or 67 in multipart SMS).
34
+
For Unicode SMS, we are limited to 70 characters (or 67 in multipart SMS).
35
35
36
-
### Negative №2
36
+
### Disadvantage 2
37
37
38
-
Most providers are not accepting`invisible control characters and unused code points`; or `any kind of invisible separator` and they are replacing them with the character `�``U+FFFD`.
38
+
Most providers do not accept`invisible control characters and unused code points` or `any type of invisible separator`. They replace these with the character `�``U+FFFD`, which makes the transaction invalid.
39
39
40
-
This will make the transaction invalid.
40
+
### Advantage 1
41
41
42
-
### Positive №1
42
+
Modern providers and phones support UCS-2 (a now-defunct character encoding), which has been replaced with UTF-16 Big Endian (UTF-16BE).
43
43
44
-
Modern providers and phones are supporting UCS-2 (a now-defunct character encoding), which is replaced with UTF-16 Big Endian (UTF-16BE).
44
+
### Advantage 2
45
45
46
-
### Positive №2
46
+
To prevent the rejection of certain characters, we prefix them with a tilde `~` character ([007E](https://codepoints.net/U+007E)), followed by the 2+2 hex digits converted to Unicode characters.
47
47
48
-
To avoid non-acceptance of certain characters, we are prefixing them with a tilde `~` character ([007E](https://codepoints.net/U+007E)) following the 2+2 hex digits converted to Unicode characters.
49
-
50
-
Both 2 hex digits will get the `01` prefix.
48
+
Both 2 hex digits receive the `01` prefix.
51
49
52
50
For example:
53
-
1. We are getting hex `09CA`, which is not a valid Unicode character in [Bengali](https://codepoints.net/bengali).
54
-
1. We are splitting it into two parts 2+2.
55
-
1.First half we are prefixing with `01` and we are getting `0109`, which will be converted to [ĉ](https://codepoints.net/U+0109).
56
-
1.Second part we are prefixing with `01` and we are getting `01CA`, which will be converted to [NJ](https://codepoints.net/U+01CA).
57
-
1.Converted characters we are prefixing with `~` tilde.
58
-
1.As a result we are getting the `~ĉNJ` string.
51
+
1. We receive hex `09CA`, which is not a valid Unicode character in [Bengali](https://codepoints.net/bengali).
52
+
1. We split it into two 2+2 parts.
53
+
1.We prefix the first half with `01`, resulting in `0109`, which is converted to [ĉ](https://codepoints.net/U+0109).
54
+
1.We prefix the second part with `01`, resulting in `01CA`, which is converted to [NJ](https://codepoints.net/U+01CA).
55
+
1.The converted characters are prefixed with a`~` tilde.
56
+
1.The result is the `~ĉNJ` string.
59
57
60
-
### Splitting Tx
58
+
### Transaction Splitting
61
59
62
-
For dividing the transactions in the data feed you must use [Line feed](https://codepoints.net/U+000A) character. In script normally referred to as `\n` or `\r` depending on the OS.
60
+
To divide transactions in the data feed, use the [Line feed](https://codepoints.net/U+000A) character. In scripts, this is usually referred to as `\n` or `\r`, depending on the OS.
63
61
64
-
### Result
62
+
### Outcome
65
63
66
-
Based on these findings you should be able to send CORE transactions (or any other) encoded by UTF-16BE in modern networks and phones with SMS.
64
+
Based on these findings, you should be capable of sending CORE transactions (or any others) encoded by UTF-16BE on modern networks and phones through SMS.
67
65
68
66
Notes:
69
-
- In some cases, you need to swap the buffer from Little Endian to Big endian.
70
-
- Base62 is one of the best tools to convert UTF-16 characters into ASCII.
71
-
- We are excluding characters from UTF-16 Basic Multilingual Plane:
67
+
- In some instances, you may need to swap the buffer from Little Endian to Big Endian.
68
+
- Base62 is a great tool for converting UTF-16 characters into ASCII.
69
+
- We exclude characters from the UTF-16 Basic Multilingual Plane:
72
70
- tilde `~` character ([007E](https://codepoints.net/U+007E))
73
71
- replacement `` character ([FFFD](https://codepoints.net/U+FFFD))
74
72
- Control, Format, Unassigned, Private use, Surrogate characters
@@ -80,11 +78,11 @@ Core Blockchain transactions should be packed into 2-3 SMS messages.
80
78
81
79
#### Sending TXMS vs HEX
82
80
83
-
TXMS is shorter but dependent on UTF-16, which makes it with plain HEX comparison slightly better in the SMS use case.
81
+
TXMS, while dependent on UTF-16, is shorter, making it slightly more efficient than plain HEX in the context of SMS.
84
82
85
-
But there is a big difference in the length of the message.
83
+
However, there is a significant difference in the length of the messages.
86
84
87
-
In native systems, which are supporting UTF-16 you will get always the best or most competitive results.
85
+
In native systems that support UTF-16, you will always achieve the best or most competitive results.
88
86
89
87
## Installation
90
88
@@ -100,7 +98,7 @@ npm i txms.js
100
98
yarn add txms.js
101
99
```
102
100
103
-
## Use
101
+
## Usage
104
102
105
103
### Importing
106
104
@@ -126,7 +124,7 @@ var decoded = txms.decode(string);
126
124
127
125
### Parameters
128
126
129
-
-`hex` = hexadecimal representation of transaction without 0x prefix. (Even prefix is inserted, it is cutting it.)
127
+
-`hex` = hexadecimal representation of transaction without 0x prefix. (If a prefix is present, it is removed.)
130
128
-`data` = UTF-16BE data
131
129
-`network` (default: 1) = ID of Core Blockchain network or its name (such as: mainnet, devin).
132
130
-`countriesList` (default: all) = ISO 3166 Alpha-2 country/ies code/s.
This is not encrypting tool, but a conversion. All people can read your signed transaction, but don't worry they can do it in any case on Blockchain.
187
+
This tool doesn't encrypt, it converts. Therefore, anyone can read your signed transaction, but don't worry as they could do this on the Blockchain anyway.
190
188
191
-
You should be safe. Don't stream your private key or any sensitive data that you want to protect.
189
+
Stay safe. Do not broadcast your private key or any sensitive data you wish to safeguard.
-Send us some Øres / ₡ores: [cb7147879011ea207df5b35a24ca6f0859dcfb145999](https://blockindex.net/address/cb7147879011ea207df5b35a24ca6f0859dcfb145999)
-Sending us some Øres / ₡ores: [cb7147879011ea207df5b35a24ca6f0859dcfb145999](https://blockindex.net/address/cb7147879011ea207df5b35a24ca6f0859dcfb145999)
0 commit comments