Thread by @juanjo_arlandis

_OVERLEDGER PROGRAMMING_

Let's dive in some programming content about Quant´s interoperability tech.

#OVERLEDGER #QUANT #GITHUB

Firstly, I want to make this clear, I'm not a professional programmer, just a Telecommunications Student that has been interacting and playing with the programming material Quant has given us.

LET’S BEGIN 👇🏻

- QUANT SDK -

Not many people know that Quant has a GitHub profile, where they show publicly some programming stuff they have designed for us to interact with.

github.com/quantnetwork

They have some public showcases, some code that by the time they deployed, worked, but now it doesn't.

But the interesting part is in two specific repositories:

- Overledger SDKs
- Blockchain-developer-exercises-foundations

In these two repositories, I have found some cool and interesting stuff that allows us to interact with the CORE of Overledger itself.

_Blockchain-developer-exercises-foundations_

This repository was created for a special purpose, to teach us some examples of how Overledger works and what kind of stuff can be done. All are explained in the Kings College Overledger Introduction Course.

👇🏻👇🏻👇🏻

1. We have 7 different exercises that allow us to set-up what we need to interact with Overledger.

These exercises show us how to create our Quant account, set-up our MDAPP and link our client and secret password to interact with it.

2.
These exercises also show us how to run the code needed to search a block, search an account, send a tx in 3 pre-made DLT testnets...

-Bitcoin
-Ethereum
-XRP

But this is just an apéritif of what we can do with OVL.

The code is already made by LukeRiley, we just have to set our data and run it to see some “action”.

As I said, this repository is simply an introduction to show how works some things we can do with Overledger.

In my case, I took the given code and modify it to use it in more DLTs that Quant has added and notified through the product releases in their webpage.

Some sexy EVM-based TESTNET DLTs first.
#Goerli #Polygon #Avalanche #XDC

Of course, how I could just say these things without showing you some proofs?

That´s why I created some new accounts and funded them with their respective faucets (Except Goerli, that moth*** ****r is always dry😅😅).

So let´s see some OVERLEDGER ACTION 👇🏻👇🏻👇🏻

In these examples, I'm going to show you I have just made a transaction from my funded account to another one on each DLT through Oveledger´s API Gateway.

_POLYGON MUMBAI TESTNET_

There is a little easter-egg in the message field of the following tx 😉.

Here is the tx --> mumbai.polygonscan.com/tx/0xe7306b1ff…

And here is the answer given by Overledger in my PC terminal:

1 . First, it uses my login info to obtain the green light from OVL to use its system:

2. Prepares the transaction to send it to OVL, I was the one that gave this info to the programm.

3. Overledger gives me a response to my previous tx petition, look carefully to that gatewayFee field and remember I'm in the sandbox 😎😎😎

4. Now Overledger uses my private-key to firm the transaction 🔑

5. The transaction is broadcasted to the DLT and the following response is given, take your time to read al the fields.

_AVALANCHE FUJI TESTNET_

Here is the tx --> testnet.snowtrace.io/tx/0xb5f3262f9…

_XDC APOTHEM TESTNET_

Here is the tx --> "The Explorer is SHIT and doesn't show the info"

So, to conclude, let's come to some conclusions.
All the previous tx I have shown you, have been made from a single API, making some calls with some parametrized values.

Secondly, if you try to spot any type of OVL trace in the tx explorers you wont find anything.

Just my message, that I purposely added to give proof.

I hope you liked this thread, which I would complete in the future.

Actually, I'm interacting with smart-contracts, making more complex things than simple txs, all with the same API.

Special thanks to the Quant Developer group lads that have helped me these days 😁😁😁