Wij want to add spil many exchanges, pools and services spil wij can to Openclerk (the underlying open source project). The requirements for supporting a fresh service are:
- The service needs to be stable, and accept free public registrations.
- The service needs to have a public API to obtain balances vanaf currency.
- This public API vereiste be read-only, it vereiste not be possible for someone with a read-only API key to perform an exchange or trade.
- Kont (wallet API wasgoed eliminated)
- Bitcoin China
- Bitcurex (API is not safe &ndash, #297)
- Bitfinex (API is not safe &ndash, #283)
- BitGo (#288)
- Blockchain.informatie Wallet (API is not safe &ndash, #195)
- BTER (#237)
- CampBX (read-only API “coming ter September”)
- CoinJar (requested)
- Coinotron (on development list)
- CoinEX (API is not safe &ndash, #37)
- coinmine.pw (PayAPI is not safe &ndash, #106)
- Coinsortium (#318)
- Flexcoin (no API yet)
- itBit (API is not safe &ndash, #249)
- Intersango (registration is closed)
- mcxNOW (API is not safe &ndash, #91)
- MintPal (#214)
- NetcodePool (all currencies)
- VirtEx (wallet balances API coming)
Example: Existing mining pool software
Mining pools that are run on existing mining pool software, such spil MPOS and mmcFE, often automatically provide users with read-only API keys for balances and hashrates. Thesis pools can lightly be added to Openclerk.
There are many supported pools that go after this treatment. For example, Pool-x.eu and HashFaster both provide a read-only API key for each account (illustrated).
Example: A read-only balance API key
This treatment is an effortless way to add read-only API keys to a service that either has no API, or already supports a utter trade API. Te this treatment, a different API key is generated for each account, and this API key is explicitly read-only.
This means the service does not need to support revoking keys, managing numerous keys, managing key permissions etc. However, this does mean that once an API key is collective, it cannot be revoked.
For example, Litecoin Global provided a read-only API key for each account (illustrated).
Example: Permissions-based API keys
This treatment involves much more work but is the most powerful treatment. Te this treatment, a service supports numerous API keys, with each API key given different permissions – including a read-only “Get Balance” permission. API keys can also be revoked at any time, making this the most secure treatment spil well.
For example, Havelock Investments permits numerous API keys to be created, each with different permissions (illustrated).
Requesting a fresh service
If you would like Openclerk to support a fresh mining pool, exchange or service, please let us know through one of the following methods: