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
Copy file name to clipboardExpand all lines: content/appendix/address.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: "Address"
3
3
weight: 2
4
4
dashboardWeight: 0.2
5
-
dashboardState: wip
5
+
dashboardState: reliable
6
6
dashboardAudit: n/a
7
7
---
8
8
@@ -18,7 +18,7 @@ Accounts have a public key-based address (e.g. to receive funds), and non-single
18
18
19
19
An account actor's crypto-address (for signature verification) is found by looking up its actor state, keyed by the canonical ID-address. There is no map from ID-address to pubkey address.
20
20
21
-
The reference implementation is https://github.com/filecoin-project/go-address
21
+
The reference implementation of the Filecoin Address can be found in the [`go-address` Github repository](https://github.com/filecoin-project/go-address).
22
22
23
23
## Design criteria
24
24
@@ -64,13 +64,13 @@ When encoded to a string a filecoin address contains the following:
64
64
65
65
### Network Prefix
66
66
67
-
The **network prefix** is prepended to an address when encoding to a string. The network prefix indicates which network an address belongs in. The network prefix may either be `f` for filecoin mainnet or `t` for filecoin testnet. It is worth noting that a network prefix will never appear on chain and is only used when encoding an address to a human readable format.
67
+
The **network prefix** is prepended to an address when encoding to a string. The network prefix indicates which network an address belongs to. The network prefix may either be `f` for filecoin mainnet or `t` for filecoin testnet. It is worth noting that a network prefix will never appear on chain and is only used when encoding an address to a human readable format.
68
68
69
69
### Protocol Indicator
70
70
71
71
The **protocol indicator** byte describes how a method should interpret the information in the payload field of an address. Any deviation for the algorithms and data types specified by the protocol must be assigned a new protocol number. In this way, protocols also act as versions.
72
72
73
-
-`0` : ID
73
+
-`0` : ID
74
74
-`1` : SECP256K1 Public Key
75
75
-`2` : Actor
76
76
-`3` : BLS Public Key
@@ -91,7 +91,7 @@ const (
91
91
92
92
#### Protocol 0: IDs
93
93
94
-
**Protocol 0** addresses are simple IDs. All actors have a numeric ID even if they don't have public keys. The payload of an ID address is base10 encoded. IDs are not hashed and do not have a checksum.
94
+
**Protocol 0** addresses are simple IDs. All actors have a numeric ID even if they don't have public keys. The payload of an ID address is base10 encoded. IDs are not hashed and do not have a checksum.
95
95
96
96
**Bytes**
97
97
@@ -206,7 +206,7 @@ type Address interface {
206
206
```
207
207
#### New()
208
208
209
-
New returns an Address for the specified protocol encapsulating corresponding payload. New fails for unknown protocols.
209
+
`New()` returns an Address for the specified protocol encapsulating corresponding payload. New fails for unknown protocols.
0 commit comments