indra
indra copied to clipboard
connext
[LEGACY] Monorepo containing everything related to the core Connext protocols and network.
**Is your feature request related to a problem? Please describe.** Follow-up of https://github.com/connext/indra/issues/27: we'd want the client to be able to pay for gas costs of collateralization. **Describe the solution...
All transfer types should have test where a sender sends multiple payments to the same recipient. An example of the test to emulate can be found [here](https://github.com/connext/indra/blob/2fbc6e581af250b8f4cb7563e62532bb497a2a32/modules/test-runner/src/flows/multichannelStore.test.ts#L109)
**Describe the bug** Many events and payloads are not strongly typed, leading to bugs from incorrect event payloads being emitted. **To Fix** In the [watcher](https://github.com/ConnextProject/indra/blob/ac3d84be53629fc3c0ee37b519bcaf0ae843b7ed/modules/types/src/watcher.ts#L91-L102) type defs, we define strongly...
**Describe the bug** [This](https://github.com/ConnextProject/indra/blob/1d3d50e4be3c16d94790cf6d7a06e2ca7db03487/modules/test-runner/src/restoreState/restoreState.test.ts#L60) test only passes because of a special case in the listener error handling, [here](https://github.com/ConnextProject/indra/blob/1d3d50e4be3c16d94790cf6d7a06e2ca7db03487/modules/client/src/listener.ts#L338-L340). The bug is likely a result of listeners not being properly cleaned...
Conditionally generate transfer data based on specific appInstance inserts into the DB. Not necessary immediately but will become a blocker when we implement rebalancing service algorithms.
We should store some metadata about the swaps we complete, including swap rates, etc. This is probably a lower priority since we have the data from the channel records anyways.
Deployment and CD/CI of collateral management service
Things needed for 3rd party collateral management services. - [ ] #788 Scaffolding including a django app that has the following API endpoints ``` 1. getTargets(hashOfXpub: string) => { collateralize:...
Token/simple bearer auth for service (also generate API Keys for clients)
Service should have its own database that it can query + update from node data. Should have views of type: ``` create view onchain_transactions ( "reason" enum nodeDeposit | nodeWithdrawal...