Skip to content

Commit 1ed3c2e

Browse files
s/token/tokenization/
1 parent eb84ed1 commit 1ed3c2e

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

README.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# rain.vats
22

3-
VATS = Verifiable Asset Token System.
3+
VATS = Verifiable Asset Tokenization System.
44

55
## High Level (VATS)
66

@@ -52,7 +52,7 @@ this makes them all similar to each other, which justifies their "sameness", an
5252
important feature of any fungible token. In another sense we have simply shifted
5353
our liquidity problem offchain. What if there is a bank run on the token and a
5454
significant percentage of these 100 houses all need to be sold in a short period
55-
of time in order to maintain the backing. Selling 1 house in a good area is
55+
of time in order to maintain the backing? Selling 1 house in a good area is
5656
relatively simple, although still might take months, selling 100 houses in the
5757
same area could take many years to do in a way that doesn't crash the sale price
5858
due to sudden oversupply.
@@ -89,8 +89,8 @@ are created and destroyed in lockstep to maintain supply integrity.
8989
V: Verifiable => "Anyone" can compare the onchain ERC1155 NFT IDs/data/supply
9090
against the offchain assets to check the integrity of the system.
9191
A: Asset => The system is designed to work referencing/backed by real assets.
92-
T: Token => The system is fundamentally a tokenization approach to building
93-
liquidity for the referenced assets.
92+
T: Tokenization => The system is fundamentally a tokenization approach to
93+
building liquidity for the referenced assets.
9494
S: System => This is a system of tokens, both an ERC20 and ERC1155, and cannot
9595
provide all promised features/guarantees without multiple tokens bound together
9696
logically somehow (e.g. at mint/burn time)

0 commit comments

Comments
 (0)