Peer Protocol
Peer Protocol for Channel Management
To exemplify the protocols as we define them, we will assume there exists a multisignature wallet shared between two parties, Alice and Bob. This is the only required re-usable on-chain component (with the exception of supporting libraries) to execute each of the protocols below.
Type Definitions and Global Variables
Primitive Types
Type | Description | Sample |
| Ethereum address |
|
| HD wallet extended public key |
|
| 8 bit unsigned integer | |
| 256 bit unsigned integer | |
| 32 bytes |
Global Variables
Variable Name | Type | Description |
|
| The deployed on-chain address of the |
|
| The deployed on-chain address of the |
JSON
This type specifies a modification of JSON that disallows the following primitive types: true
, false
, null
. Note that when represented in javascript, large numbers which fint into uint256
must be represented as either BigNumber
s or as serialized BigNumber
s (e.g., { _hex: '0x01'}
).
Type: Terms
Field | Type | Description |
|
| A value in the enum of |
|
| The exact total budget that an application can spend |
|
| If |
Type: CfAppInterface
Field | Type | Description |
|
| The on-chain address of the |
|
| If |
|
| The ABIEncoderV2 representation of the application's state encoding (e.g., |
TODO: The name
getTurnTaker
needs to be standardized
Last updated