You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are looking for help (from an experienced JavaScript dev) with a standalone JS library/SDK that wraps the Kchannels API. We have working JS code that already contains a lot of the requested functionality to help you with this effort.
The API is mostly JSON-RPC-based, although some parts of it are REST-style. There are also 2 WebSocket endpoints.
IMPORTANT: The library must perform all the client-side validation (checking hashes, detecting channel inconsistencies) to protect the client whenever required (e.g. when data is returned in a response).
The library should
use modern, idiomatic JavaScript
be of high quality and use good coding practices (in the spirit of Code Complete -- good variable names, documentation, etc.)
contain unit tests (using mocking where appropriate) with good coverage
be structured in a way that lets it be uploaded to NPM
use a permissive, open-source license
come with a README that explains how to get started quickly
be publicly available on GitHub
Additional pointers:
The library should support all the ways that keypairs are commonly represented in the Ethereum ecosystem (as files, strings, etc).
The library should cleanly, idiomatically present the WebSocket information to the client.
We are open to discussing whether you continue to maintain the library or hand it off to us.
The text was updated successfully, but these errors were encountered:
We are looking for help (from an experienced JavaScript dev) with a standalone JS library/SDK that wraps the Kchannels API. We have working JS code that already contains a lot of the requested functionality to help you with this effort.
The API is located at https://docs.kchannels.io/docs/api (all of the subsections of the API docs should be part of the library).
The API is mostly JSON-RPC-based, although some parts of it are REST-style. There are also 2 WebSocket endpoints.
IMPORTANT: The library must perform all the client-side validation (checking hashes, detecting channel inconsistencies) to protect the client whenever required (e.g. when data is returned in a response).
The library should
Additional pointers:
We are open to discussing whether you continue to maintain the library or hand it off to us.
The text was updated successfully, but these errors were encountered: