|
@@ -2,7 +2,7 @@
|
|
|
|
|
|
|
|
## DarkFi Fullnode Daemon
|
|
## DarkFi Fullnode Daemon
|
|
|
|
|
|
|
|
-`drkd` the darkfi fullnode. It manages the blockchain, validates transactions
|
|
|
|
|
|
|
+`darkfid` is the darkfi fullnode. It manages the blockchain, validates transactions
|
|
|
and remains connected to the p2p network.
|
|
and remains connected to the p2p network.
|
|
|
|
|
|
|
|
Clients can connect over localhost RPC or secure socket and perform these functions:
|
|
Clients can connect over localhost RPC or secure socket and perform these functions:
|
|
@@ -12,12 +12,12 @@ Clients can connect over localhost RPC or secure socket and perform these functi
|
|
|
* Broadcast txs to the p2p network.
|
|
* Broadcast txs to the p2p network.
|
|
|
* Get tx status, query the mempool and interact with components.
|
|
* Get tx status, query the mempool and interact with components.
|
|
|
|
|
|
|
|
-`drkd` does not have any concept of keys or wallet functionality. It does not
|
|
|
|
|
|
|
+`darkfid` does not have any concept of keys or wallet functionality. It does not
|
|
|
manage keys.
|
|
manage keys.
|
|
|
|
|
|
|
|
## Low Level Client
|
|
## Low Level Client
|
|
|
|
|
|
|
|
-Clients manage keys and objects. They make queries to `drkd`, and receive notes
|
|
|
|
|
|
|
+Clients manage keys and objects. They make queries to `darkfid`, and receive notes
|
|
|
encrypted to their public keys.
|
|
encrypted to their public keys.
|
|
|
|
|
|
|
|
Their design is usually specific to their application but modular.
|
|
Their design is usually specific to their application but modular.
|
lunar-mining