Ripple Ledger Gets New Smart Contract Feature: “Hooks”

[ad_2][ad_1]
  • Ripple Ledger has finally received its new Hooks feature, which will allow the execution of smart contracts.

  • This was one of the most anticipated additions to the XRP ledger in 2020.

  • The new feature will allow XRP to get some new use cases and attract more users.

Ripple, a Californian cryptocurrency startup, has managed to make impressive progress when it comes to partnering with banks and financial institutions and convincing them to use its currency for international transactions. However, when it comes to the coin, XRP itself actually seems to be missing when it comes to useful applications.

This is something Ripple hopes to change by bringing smart contracts into the XRP ledger.

Are you looking for quick news, important tips and market analysis? Sign up for the Invezz newsletter today.

The hooks finally become available for use

Ripple has long been partnering with Flare Networks to enable Ethereum smart contract execution on XRP Ledger for a long time. The new interface will open up a number of new features for XRP. However, the most notable recent development is the introduction of smart contracts with “Hooks”.

Hooks was originally introduced in the alpha version of XRP Ledger in October and looks like one of the most anticipated additions to the Ledger in a while.

Hooks introduced the first proprietary smart contract functionality the XRP exosystem has ever experienced. It was announced on Twitter two days ago, on November 18th, by lead developer, Wietse Wind, who noted that the code is now available to everyone.

There is still a lot of work to be done

In addition to announcing it, Wind also shared a number of different commands for the app running this software: Docker. The released code and commands are required to use smart contracts on XRP Ledger.

Furthermore, it has also provided a Github link which comes with all the instructions.

Simply put, there are two steps that developers need to follow. The first is that one node must be used to view the logs, while the other is that another node must implement the smart contract execution commands. Of course there is still some work to be done, so further adjustments and updates are expected.

[ad_2]Source link