Etherisc Documentation

Here you will find links to the most recent documentation:

1 Like

Dear Etherisc Community,

Regarding the tutorials and the setup described under A. on the current github from etherisc:

“5. npm run dev:services:run to run Docker Compose with RabbitMQ and PostreSQL”
This step does not run.

Beginning from this step, no steps work out of the box. We have tried this on multiple setups. We can however manage making most functionalities work by directly calling the scripts inside the package.json. We can run docker compose to run postgresql, rabbitmq, minio, ganache and ethereium_bridge. Also starting the microservices is not a problem. We can then migrate gif contracts manually (by using npm/truffle migrate inside the folder). We can also compile and deploy a custom insurance contract.
However, we fail using the gif-cli functionality as it is documented under the old tutorial mentioned above. Is this still working for the newest “sandbox” version? It is not mentioned in the newest readthedocs under Welcome to User Manual for the Generic Insurance Framework! — Etherisc GIF Manual latest documentation , but still a gif-cli folder is contained in the newest sandbox. Is this functionality deprecated?

Help would be appreciated. We are also happy contributing to the documentation/framework at a later point in time.

Hi 34Peter,

thanks for your interest in the platform! Let me give you a short update on the status of sandbox.
As you may have read in the tutorials, the GIF consists of on-chain and off-chain components. Some month ago, when the gas fees on ethereum mainnet started to become unreasonably high, we moved to xDai / Sokol. Based on our experience with the off-chain components, we also made a move away from a pure microservice based system to a much leaner system which can be run in a single docker container. If you are interested in a sneak preview, you can visit so you see where we are moving to.

The goal is to make the off-chain components as small as possible, the platform should not be dependent on off-chain components, and there should be no need for a centralized party to run any of the essential components.

Why then do we need off-chain components at all?

  1. We are dealing with real-world risks, so we need to store personal data - this is currently not (easily) possible on-chain.
  2. We need operational safety (the same reason why in most cases, you won’t directly interact with Uniswap but rather use their web interface which implements a lot of safety checks)
  3. We need a monitoring system which gives you always a quick and consistent view on what’s going on in the smart contracts. While this can be done - in principle - by the use of basic tools like Etherscan etc., we think we need a convenient access to on-chain data.

The off-chain components will offer these services:

  1. Monitoring all events of the core smart contracts
  2. Interact with the core smart contracts (via Metamask), e.g. approve new oracles and products, pause/unpause products.
  3. Trigger actions based on events which are emitted by the core smart contracts
  4. Sending notifications to defined recipients based on core contract events
  5. Offer a REST API to request core contract addresses and ABIs
  6. Manage core contract releases and versions.

Please share some information on your goals so we can see if we can help you to get a running system!

(Regarding your original question, the tutorials are currently being reworked and we plan to publish these in the next few days. But don’t hesitate to contact us directly, we can share pre-release versions with you).