Skip to content

Commit

Permalink
English changes for exchange doc (neo-project#427)
Browse files Browse the repository at this point in the history
  • Loading branch information
Celia18305 authored and PeterLinX committed Feb 28, 2018
1 parent 05385f0 commit 36cfb0d
Show file tree
Hide file tree
Showing 4 changed files with 837 additions and 2 deletions.
8 changes: 8 additions & 0 deletions en-us/exchange/general.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,8 @@
# Document for Exchange Developers

This document is intended to guide exchange developers to set up NEO nodes on the exchange server and complete related program development for NEO assets transactions. Before reading, maker sure you have read [NEO White Paper](index.html) and understand the NEO background knowledge and technologies.

> [!Note]
>
> Different versions of NEO-CLI are different in ways of interfacing with exchanges. Please note the version behavior differences before upgrading your client version.
11 changes: 10 additions & 1 deletion en-us/exchange.md → en-us/exchange/v2.6.0.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,8 @@
# Document for Exchange Developers

This document is intended to guide exchange developers to set up NEO nodes on the exchange server and complete related program development for NEO assets transactions. Before reading, maker sure you have read [NEO White Paper](index.html) and understand the NEO background knowledge and technologies.
> [!Note]
>
> This document provides information based on [Neo CLI v2.6.0](https://github.com/neo-project/neo-cli/releases/tag/v2.6.0).
In general, an exchange needs to do the following:

Expand Down Expand Up @@ -232,6 +234,13 @@ In this file, there is an array of notifications with only one object, which mea

[event, from account, to account, amount]

```json
{
"type": "ByteArray",
"value": "7472616e73666572"
}
```

- The first object with the type "bytearray" and the value "7472616e73666572", as shown in the example, can be converted to the string "transfer". "transfer" is a method in NEP5 that represents an asset transfer.
- The second object in the array is the account address where the asset is transferred from. Its type "bytearray" and the value "d336d7eb9975a29b2404fdb28185e277a4b299bc“ can be converted to "Ab2fvZdmnM4HwDgVbdBrbTLz1wK5TcEyhU". Note that for the hexadecimal string with "0x" prefix, it is processed as big endian; otherwise, it is processed as small endian.
- The third object in the array is the account address where the asset is transferred to. If the address is an exchange account address, it is a deposit transaction.
Expand Down
Loading

0 comments on commit 36cfb0d

Please sign in to comment.