This file has been truncated. show original
# Safecoin Revised
- Status: implemented
- Type: new feature
- Related components: SAFE Vault, Routing, SAFE Client Libs
- Start Date: 01-05-2019
- Discussion: https://safenetforum.org/t/rfc-57-safecoin-revised/28660
- [RFC 0005: Balance Network Resources][rfc05]
- [RFC 0012: Safecoin Implementation][rfc12]
- [RFC 0051: Safecoin Alternative Implementation][rfc51]
- Superseded by: N.A.
This RFC combines the three previous RFCs as indicated above. It describes the link between resource constrained sections and the desire to add new nodes. As safecoin is the "oil" of the network it may appear to couple certain aspects of the network and in many ways does, but this is a critical aspect of the network that combines many aspects into a cohesive system. It should be noted that a client's identity on the network is represented by a `BLS::PublicKey` which allows multisig capabilities and which is probably essential for any currency to be secured and usable. Such a public key requires an amount of safecoin to be associated with it to be of any use. This relationship is represented by a `CoinBalance`.
In addition we recognise that writes to the network will be slowed down as `CoinBalance`s are checked for payment, but this is both acceptable and also important for the network to not be spammed without payment. Writes are slow, but reads will be as fast as possible as caching and no request for payment is involved. There will also be replay attack prevention for transfer of coins.