monorepo
monorepo copied to clipboard
counterfactual
Home for all packages related to the Counterfactual project
The return type is encoded in `GetAppInstancesResults`, an array of elements of type `AppInstanceInfo`, whose `timeout` field is of type `BigNumber`; however manual examination of the return type at https://github.com/counterfactual/monorepo/blob/master/packages/node/test/integration/get-app-instances.spec.ts#L108...
Could be confused with `appInstanceId`. Can be renamed to `appDefinitionAddr` for consistency.
Presently it is left as a job for the user of the state channel application to challenge their counterparty if they are ever unresponsive. This issue is to add a...
Presently when running any of the protocols and a counterparty is not responsive the Node will throw an error inside of the `IO_SEND_AND_WAIT` function implementation after 60 seconds. This error...
Logging in the Node package is currently not that readable as there has been no effort to discern spammy logs from critical information via any kind of logging level system...
It seems like EIP 165 is being worked on to support one of our use cases; to verify that a particular interface is supported. For us, we'd want to verify...
- We need a queue that writes to browser persistent storage - Need a mechanism to flush the queue
There is a bug in the `setState` function which checks that the app is `ON`. See https://github.com/counterfactual/monorepo/blob/99fc5556d212843dd1c0c4f6c90b4043256e4607/packages/contracts/contracts/mixins/MixinSetState.sol#L45 It should instead check if the app is either ON or DISPUTE (but...
It should be possible to create `contract X is CounterfactualApp {}` and have that exist as a real app inside the framework.
Metadata
Owner
Metadata
Home for all packages related to the Counterfactual project