History

Oskar Thoren f292346293 18: Bump update		2021-03-30 13:14:38 +08:00
..
README.md	18: Bump update	2021-03-30 13:14:38 +08:00

README.md

slug	title	name	status	editor
17	17/WAKU2-SWAP	Waku SWAP Accounting	raw	Oskar Thorén <oskar@status.im>

This specification outlines how we do accounting and settlement based on the provision and usage of resources, most immediately bandwidth usage and/or storing and retrieving of Waku message. This enables nodes to cooperate and efficiently share resources, and in the case of unequal nodes to settle the difference through a relaxed payment mechanism in the form of sending cheques.

Protocol identifier*: /vac/waku/swap/2.0.0-alpha2

Motivation

The Waku network makes up a service network, and some nodes provide a useful service to other nodes. We want to account for that, and when imbalances arise, settle this. The core of this approach has some theoretical backing in game theory, and variants of it have practically been proven to work in systems such as Bittorrent. The specific model use was developed by the Swarm project (previously part of Ethereum), and we re-use contracts that were written for this purpose.

By using a delayed payment mechanism in the form of cheques, a barter-like mechanism can arise, and nodes can decide on their own policy as opposed to be strictly tied to a specific payment scheme. Additionally, this delayed settlement eases requirements on the underlying network in terms of transaction speed or costs.

Theoretically, nodes providing and using resources over a long, indefinite, period of time can be seen as an iterated form of Prisoner's Dilemma (PD). Specifically, and more intuitively, since we have a cost and benefit profile for each provision/usage (of Waku Message's, e.g.), and the pricing can be set such that mutual cooperation is incentivized, this can be analyzed as a form of donations game.

Game Theory - Iterated prisoner's dilemma / donation game

What follows is a sketch of what the game looks like between two nodes. We can look at it as a special case of iterated prisoner's dilemma called a Donation game where each node can cooperate with some benefit b at a personal cost c, where b>c.

From A's point of view:

A/B	Cooperate	Defect
Cooperate	b-c	-c
Defect	b	0

What this means is that if A and B cooperates, A gets some benefit b minus a cost c. If A cooperates and B defects she only gets the cost, and if she defects and B cooperates A only gets the benefit. If both defect they get neither benefit nor cost.

The generalized form of PD is:

A/B	Cooperate	Defect
Cooperate	R	S
Defect	T	P

With R=reward, S=Sucker's payoff, T=temptation, P=punishment

And the following holds:

T>R>P>S
2R>T+S

In our case, this means b>b-c>0>-c and 2(b-c)> b-c which is trivially true.

As this is an iterated game with no clear finishing point in most circumstances, a tit-for-tat strategy is simple, elegant and functional. To be more theoretically precise, this also requires reasonable assumptions on error rate and discount parameter. This captures notions such as "does the perceived action reflect the intended action" and "how much do you value future (uncertain) actions compared to previous actions". See Axelrod - Evolution of Cooperation (book) for more details. In specific circumstances, nodes can choose slightly different policies if there's a strong need for it. A policy is simply how a node chooses to act given a set of circumstances.

A tit-for-tat strategy basically means:

cooperate first (perform service/beneficial action to other node)
defect when node stops cooperating (disconnect and similar actions), i.e. when it stops performing according to set parameters re settlement
resume cooperation if other node does so

This can be complemented with node selection mechanisms.

SWAP Accounting

See Book of Swarm section 3.2. on Peer-to-peer accounting etc., for more context and details.

This approach is based on communicating payment thresholds and sending cheques as indications of later payments. The first part is done with a handshake, the second done once payment threshold is hit.

TODO: Illustrate payment and disconnection thresholds

TODO: Elaborate on how accounting works with amount in the context of e.g. store

TODO: Illustrate flow

A cheque is best thought of as a promise to pay at a later date.

TODO Specify chequebook

Accounting

Nodes perform their own accounting for each relevant peer based on some "volume"/bandwidth metric. For now we take this to mean the number of WakuMessages exchanged.

Additionally, a price is attached to each unit. For now, this is is simple a "karma counter" and equal to 1 per message.

NOTE: This may later be complemented with other metrics, either as part of SWAP or more likely outside of it. For example, online time can be communicated and attested to as a form of enhanced quality of service to inform peer selection.

Flow

Assuming we have two store nodes, one operating mostly as a client (A) and another as server (B).

Node A performs a handshake with B node. B node responds and both nodes communicate their payment threshold.
Node A and B creates an accounting entry for the other peer, keep track of peer and current balance.
Node A issues a HistoryRequest, and B responds with a HistoryResponse. Based on the number of WakuMessages in the response, both nodes update their accounting records.
When payment threshold is reached, Node A sends over a cheque to reach a neutral balance. Settlement of this is currently out of scope, but would occur through a SWAP contract (to be specified).
If disconnect threshold is reached, Node B disconnects Node A.

Policy

If a node reaches a disconnect threshold, which MUST be outside the payment threshold, it SHOULD disconnect the other peer. For the PoC, this behavior can be mocked.
If a node is within payment balance, the other node SHOULD stay connected to it.
If a node receives a valid Cheque it SHOULD update its internal accounting records.
If any node behaves badly, the other node is free to disconnect and pick another node. Peer rating is out of scope of this specification.

Protobuf

// TODO What information to include here? For now "payment" threshold
message Handshake {
    bytes payment_threshold = 1;
}

// TODO Signature?
// Should probably be over the whole Cheque type
message Cheque {
    bytes beneficiary = 1;
    // TODO epoch time or block time?
    uint32 date = 2;
    // TODO ERC20 extension?
    // For now karma counter
    uint32 amount = 3;
}

Enhancements

Settlements. At a later stage, these cheques can be redeemed. For now they are better thought of as a form of Karma.
More information to make a decision. E.g. incorporate QoS metrics such as online time to inform peer selection (slightly orthogonal to this).

References

Changelog

TBD.