package
0.0.0-20201029031353-9742f5acb6e0
Repository: https://github.com/cachecashproject/go-cachecash.git
Documentation: pkg.go.dev

# Functions

No description provided by the author
No description provided by the author
No description provided by the author
No description provided by the author
No description provided by the author
No description provided by the author
No description provided by the author
No description provided by the author
No description provided by the author
No description provided by the author
No description provided by the author
No description provided by the author
No description provided by the author
No description provided by the author

# Constants

No special information from the client about the cache.
The client cannot use the cache, at this time we're not discriminating why but possible reasons include cannot establish TLS connections, routing failures, PMTUd black holes, or potentially some form of fraud detection (but thats hard!).

# Variables

No description provided by the author
No description provided by the author
No description provided by the author
No description provided by the author
No description provided by the author
No description provided by the author
No description provided by the author
No description provided by the author
No description provided by the author
No description provided by the author
No description provided by the author
No description provided by the author
No description provided by the author
No description provided by the author
No description provided by the author
No description provided by the author
No description provided by the author
No description provided by the author

# Structs

No description provided by the author
No description provided by the author
No description provided by the author
No description provided by the author
No description provided by the author
No description provided by the author
No description provided by the author
No description provided by the author
XXX: See similarities to ContentRequest.
No description provided by the author
Signed by escrow key; ensures that the key that produced the batch signature is authorized.
No description provided by the author
No description provided by the author
No description provided by the author
No description provided by the author
No description provided by the author
No description provided by the author
No description provided by the author
No description provided by the author
No description provided by the author
XXX: Remove me! This is not used over the wire; it's used only in the `cache` package.
No description provided by the author
No description provided by the author
No description provided by the author
No description provided by the author
No description provided by the author
No description provided by the author
No description provided by the author
No description provided by the author
Client-to-publisher.
No description provided by the author
Response to a ContentRequest.
No description provided by the author
No description provided by the author
No description provided by the author
XXX: return a response or error if we reject the escrow?.
GetBlocksRequest wraps up the requests for blocks.
No description provided by the author
No description provided by the author
XXX: Is this a good name if this message includes a port number?.
TODO: this struct is also used at the cache, but most of these fields are irrelevant for the cache and only relevant for the publisher.
No description provided by the author
No description provided by the author
No description provided by the author
No description provided by the author
No description provided by the author
No description provided by the author
No description provided by the author
XXX: This needs a better name.
Contains enough data to let a cache recompute/verify the ticket-bundle digest.
XXX: I suspect that the ticket number may be the only thing here's that's actually important, since it could be used in proofs of double-spending (on the CP's behalf).
By the time the L2 ticket is decrypted by the client, all of the caches must have provided data and outer encryption keys to the client; these are the inputs to the colocation puzzle, whose output is used to decrypt the L2 ticket.
No description provided by the author
This is what the client will present to the cache.

# Interfaces

CachePublisherClient is the client API for CachePublisher service.
CachePublisherServer is the server API for CachePublisher service.
ClientCacheClient is the client API for ClientCache service.
ClientCacheServer is the server API for ClientCache service.
ClientPublisherClient is the client API for ClientPublisher service.
ClientPublisherServer is the server API for ClientPublisher service.
FaucetClient is the client API for Faucet service.
FaucetServer is the server API for Faucet service.
LedgerClient is the client API for Ledger service.
LedgerServer is the server API for Ledger service.
NodeBootstrapdClient is the client API for NodeBootstrapd service.
NodeBootstrapdServer is the server API for NodeBootstrapd service.
PublisherCacheClient is the client API for PublisherCache service.
PublisherCacheServer is the server API for PublisherCache service.

# Type aliases

No description provided by the author