BotC Overview issueshttps://git.fairkom.net/faircoop/BankOfTheCommons/BotC_Overview/-/issues2024-03-04T11:41:53Zhttps://git.fairkom.net/faircoop/BankOfTheCommons/BotC_Overview/-/issues/39Solve the Api protection, for avoid bots in faircoin exchanges2024-03-04T11:41:53ZDuran EnricSolve the Api protection, for avoid bots in faircoin exchangesThe concept is that fair to eur or fair to btc or fair to eth, should work only from inside the wallet
and not with the api, for default users.
Could be needed to activate some specific cases for doing the exchange from the api, but the ...The concept is that fair to eur or fair to btc or fair to eth, should work only from inside the wallet
and not with the api, for default users.
Could be needed to activate some specific cases for doing the exchange from the api, but the default option should protect from the use of bots for taking adventage in faircoin exchanges.Release 2020https://git.fairkom.net/faircoop/BankOfTheCommons/BotC_Overview/-/issues/38To add Mx pesos. transfer in option in the multicurrency wallet2024-03-04T11:41:54ZDuran EnricTo add Mx pesos. transfer in option in the multicurrency walletJust is a feature activated in chip chap wallet, and pending in Botc, with assembly aprovalJust is a feature activated in chip chap wallet, and pending in Botc, with assembly aprovalRelease 2020https://git.fairkom.net/faircoop/BankOfTheCommons/BotC_Overview/-/issues/94Upgrade Ethereum node2024-03-04T11:40:51ZRamaxxUpgrade Ethereum nodeBotC core tech team discovered a general issue which may affect some outgoing ETH transactions.
It's still not clear the reason why some cashouts fail.
After some investigation, we've realised the version of Ethereum node we are runnin...BotC core tech team discovered a general issue which may affect some outgoing ETH transactions.
It's still not clear the reason why some cashouts fail.
After some investigation, we've realised the version of Ethereum node we are running is quite old, so it's necessary to upgrade it in order to do debugging on a current latest stable version.
Upgrading Ethereum node may require changes on the wallet code, so we should evaulate if the process could be tracked publicly or on our internal tools.
**Update:** we've decided to migrate to `Geth` since it's a very mature and well developed software, and after our tests we've discovered it's a drop-in replacement for `Parity` and no changes to our code are needed.
Migration checklist:
- [x] Ensure that API code does not use Parity-specific namespace methods
- [x] Ensure that Wallet code does not use Parity-specific namespace methods
- [x] Ensure that API code does not use Parity-specific response fields
- [x] Ensure that Wallet code does not use Parity-specific response fields
- [x] Ensure that API code does not rely on Parity-specific API responses for bad requests
- [x] Ensure that Wallet code does not rely on Parity-specific API responses for bad requests
- [x] Ensure that API code does not rely on Parity-specific error codes
- [x] Ensure that Wallet code does not rely on Parity-specific error codes
- [x] Set up Geth infrastructure
- [x] Set up Geth software to run on a different port, in parallel with the Parity node
- [x] Notify users about maintenance window
- [x] On maintenance window, point the BotC API to the Geth port (change API config) and verify
- [x] On maintenance window, import private keys from Parity
- [x] On successful traffic, switch over all traffic to Geth and monitor for a period (weeks)
- [x] After successful switch, shut down Parity nodeRelease 2020Gampe SebastianGampe Sebastian2020-12-22