-
Notifications
You must be signed in to change notification settings - Fork 8
/
Copy pathfungible-token.json
53 lines (53 loc) · 3.9 KB
/
fungible-token.json
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
{
"$schema": "https://cashtokens.org/bcmr-v2.schema.json",
"version": { "major": 1, "minor": 1, "patch": 0 },
"latestRevision": "2023-04-14T00:00:17.720Z",
"registryIdentity": {
"name": "Example.com Token Registry",
"description": "An example registry demonstrating how the issuer of a single kind of fungible token might publish information about the token.",
"uris": {
"icon": "https://example.com/registry-icon.svg",
"web": "https://example.com/",
"registry": "https://example.com/.well-known/bitcoin-cash-metadata-registry.json"
}
},
"identities": {
"89cad9e3e34280eb1e8bc420542c00a7fcc01002b663dbf7f38bceddf80e680c": {
"2023-01-13T00:00:00.000Z": {
"name": "Example Asset",
"description": "This is a short description of Example Asset. In most interfaces, it will be hidden beyond 140 characters or the first newline character.\n\nThis sentence should be hidden in user interfaces with limited space.\n\nNote that this snapshot was introduced on 2023-1-13, but the 'migrated' property indicates that the migration took place over the following month. During that month, most clients should have warned users about the upcoming change, referring users to the 'migrate' URI for information about the change. (Some clients may also offer clients the option to dismiss the migration period and immediately show the new metadata.) At 0 UTC on 2023-2-13, all clients should have switched their default display for this token to use the new metadata, i.e. ticker symbol XAMPL, with 6 decimal places. After the migrated timestamp, old metadata should only be displayed when providing historical context.",
"token": {
"category": "89cad9e3e34280eb1e8bc420542c00a7fcc01002b663dbf7f38bceddf80e680c",
"decimals": 6,
"symbol": "XAMPL"
},
"migrated": "2023-02-13T00:00:00.000Z",
"uris": {
"icon": "https://example.com/xampl-icon.svg",
"web": "https://example.com/about-xampl",
"migrate": "https://blog.example.com/example-asset-is-now-XAMPL",
"blog": "https://blog.example.com/",
"chat": "https://chat.example.com/",
"forum": "https://forum.example.com/",
"registry": "https://example.com/.well-known/bitcoin-cash-metadata-registry.json",
"support": "https://support.example.com/",
"custom-uri-identifier": "protocol://connection-info-for-some-protocol"
}
},
"2023-01-03T00:00:00.000Z": {
"name": "Example Asset",
"description": "This is a record of an older entry for the token identity. The token was rebranded (from EXAMPLE to XAMPL) and redenominated (from 8 to 6 decimals), but the existing token category was not modified: users were not required to trade their original EXAMPLE tokens for the redenominated XAMPL tokens, their wallets simply updated the way tokens are displayed using the new metadata. Note, this entry has likely been updated by the issuer to provide useful historical information rather than attempting to preserve the precise contents of the old snapshot; the 'web' URI links to a blog post about XAMPL's re-denomination/re-brand, and outdated URI information is excluded. There may have been metadata updates published between this snapshot and the latest snapshot, but they've been excluded because registries should strive to present a useful history of only meaningful changes to identities. This information can be used in user interfaces to improve continuity following metadata updates or to offer historical context.",
"token": {
"category": "89cad9e3e34280eb1e8bc420542c00a7fcc01002b663dbf7f38bceddf80e680c",
"decimals": 8,
"symbol": "EXAMPLE"
},
"uris": {
"icon": "https://example.com/old-example-asset-icon.png",
"web": "https://blog.example.com/example-asset-is-now-XAMPL"
}
}
}
},
"license": "CC0-1.0"
}