install all the dependencies for ethereum smart contract on mac

#INSTALL ALL THE DEPENDENCIES FOR ETHEREUM SMART CONTRACT ON MAC UPDATE#
#INSTALL ALL THE DEPENDENCIES FOR ETHEREUM SMART CONTRACT ON MAC FULL#
#INSTALL ALL THE DEPENDENCIES FOR ETHEREUM SMART CONTRACT ON MAC REGISTRATION#

The contract is compatible with official ENS standards so, eventually, it will be possible to register your real domain and point to this resolver.

#INSTALL ALL THE DEPENDENCIES FOR ETHEREUM SMART CONTRACT ON MAC FULL#

You can find the open source code, full documentation, and examples here. These helpers can be imported in your JS code as well. We also prepared a script that you can load in a geth console and use convenient functions that allow you to configure the names pointing to addresses. We also came up with the possibility of tagging addresses, such as v1, v2, test, latest, default, production, etc. We decided to prepare a slim version of the resolver contract and a set of helpers that simplify managing addresses to the bare minimum, without having to rely on ENS. In the rapid development phase, we would like to bypass this process and have some kind of tagging and versioning. Also, your domain doesn’t point to your address directly it points to the resolver contract that you have to deploy (for managing all subdomains on your own).

#INSTALL ALL THE DEPENDENCIES FOR ETHEREUM SMART CONTRACT ON MAC REGISTRATION#

However, domain registration in ENS takes some time and you need to lock your Ether in order to own it, or register a. Moreover, you can change the address at any time, so we don’t have to do it in the many configs of our applications, but only in the ENS. Everything is stored on the same blockchain where our smart contracts live. Analogically to DNS, this service points unique domain names to the complex, long and difficult to remember addresses. The first solution that came to our minds was to use a public ENS (Ethereum Name Service), which is a “DNS” for smart contracts. We decided to spend some time addressing the issue.

This turned out to be very annoying and time-consuming in the long term.

#INSTALL ALL THE DEPENDENCIES FOR ETHEREUM SMART CONTRACT ON MAC UPDATE#

Each deployment of a new version of any contract required us to set the new address in both FE clients and AWS Lambda functions, as well as requiring us to inform all developers that they should update versions on local machines, too. The problem occurred once we wanted to keep addresses in all environments (development, test, staging, production) in sync. Since it’s written in JavaScript, we decided to implement AWS Lambda functions in Node.js and invoke them via our backend. We also took advantage of web3, the most established library that allows for connecting to the Ethereum node. To achieve this, we decided to build the backend in Ruby and use two decentralized front-end clients (dApps) in React.

In case a client decides to pay by credit card, we have to use our wallet and pay on his behalf. Our goal was to support both payments by Ethereum wallets and by credit cards, for less tech-savvy clients. During the development phase, we came across some inconveniences, though. The decentralized nature of this network allows us to provide a service for manufacturers that want to certificate their valuable products. Libellum is our home-grown product, designed to take advantage of smart contracts on an Ethereum blockchain.

Install all the dependencies for ethereum smart contract on mac