| 程序包 | 说明 |
|---|---|
| com.peersafe.base.core.binary | |
| com.peersafe.base.core.coretypes | |
| com.peersafe.base.core.coretypes.hash | |
| com.peersafe.base.core.types.known.sle.entries |
| 限定符和类型 | 方法和说明 |
|---|---|
Hash160 |
STReader.hash160()
Parse hash160.
|
| 限定符和类型 | 类和说明 |
|---|---|
class |
AccountID
Originally it was intended that AccountIDs would be variable length so that's
why they are variable length encoded as top level field objects.
|
class |
Currency
Funnily enough, yes, in rippled a currency is represented by a Hash160 type.
|
| 限定符和类型 | 方法和说明 |
|---|---|
Hash160 |
STObject.get(Hash160Field f) |
| 限定符和类型 | 方法和说明 |
|---|---|
static Issue |
Issue.from160s(Hash160 currency,
Hash160 issuer)
See
Field.TakerGetsCurrency
See Field.TakerGetsIssuer
TODO: better handling of Taker(Gets|Pays)(Issuer|Curency)
maybe special subclasses of AccountID / Currency
respectively? |
void |
STObject.put(Hash160Field f,
Hash160 o) |
| 限定符和类型 | 方法和说明 |
|---|---|
Hash160 |
Hash160.Translator.fromString(String value) |
Hash160 |
Hash160.Translator.newInstance(byte[] b) |
| 限定符和类型 | 方法和说明 |
|---|---|
Hash160 |
DirectoryNode.takerGetsCurrency() |
Hash160 |
DirectoryNode.takerGetsIssuer() |
Hash160 |
DirectoryNode.takerPaysCurrency() |
Hash160 |
DirectoryNode.takerPaysIssuer() |
| 限定符和类型 | 方法和说明 |
|---|---|
void |
DirectoryNode.takerGetsCurrency(Hash160 val) |
void |
DirectoryNode.takerGetsIssuer(Hash160 val) |
void |
DirectoryNode.takerPaysCurrency(Hash160 val) |
void |
DirectoryNode.takerPaysIssuer(Hash160 val) |
Copyright © 2021. All rights reserved.