Near Line Connect

Introduction

#

A little bit of back story, we are 3 front-ends developer who enjoy learning new technology and exploring new domain of knowledge.

We come together on the same interest. It is blockchain technology. We have been exploring as engineers eager to learn new technology and applying them to our project.

The Goals of this talk

#

Demonstrate our progress of approaching and applying blockchain

#

Inspire developer to explore new technology

#

Traditional world and Blockchain world

#

When we dived into blockchain space. We found out that there are 2 separated flow of information, or data, scrattered in 2 worlds. I call it Traditional world and Blockchain world.

I will give some of my own interpretation to identify the two:

Traditional world

#

• User’s profile and identify that are kept with consensus and in centralized organization.

• User normally would like to build his/her profile online to connect to other people such as friends or business contracts.

• Data storage and processing are generally cheap, easy to access and exchange between server, using API and databases.

• Examples for this are services like Line, Facebook, Twitter etc.

Blockchain world

#

• User has a "Wallet" to identify his/herself this comes in form of key-pair secret and a hexadcimal public address such as "0x71C7656EC7ab88b098defB751B7401B5f6d8976F".

• User send and verify a transaction that effect the blockchain. Common action such as sending fund, purchase token (either fungible token ie. coins or Non-fungible token ie. certificates).

• Data is recorded in form of Smart Contract and Transactions. These can be viewed publicly using Blockchain Explorers.

• All transations on the blockchains is charged with a fee (usually called gas fee) to maintain the network in decentralized fashion. Fee are paid toward the maintainer who keeps the blockchain ledger up and running.

• There are many blockchains that provide public services and process millions of transactions every day such as Ethereum, Binance Smart Chain, Solana, Near Protocol, etc.

Connect the 2 worlds

#

Expanding the traditional world to blockchain world to quickly verify and identify has becoming a need for any business.

It will allow user to explore the crypto currency market and services with a sense of ownership in parallel of their connection with the traditional world. Where they can build their own social network and wealth just as normal.

What we want to do

#

Imagine where you can purchase a extreamly rare Brown NFT and share it to your feed. And anyone can use Blockchain Smart Contract to verify your authenticity of the purchase and connect it with your Line Account or Facebook account.

What we want to do is a system that can verify the authenticity of a NFT right on-chain. Preserve the correctness of the authorization that published the NFT and proven ownership of the owner.

Message Signing

#

Given the above goal we need to perform 2 steps:

• User verify him/herself with the Traditional Authentication system. In this case we will use LIFF - LINE Front-end Framework for example.

• User request a certificate that is signed by Traditional Authentication and will be accepted by the Blockchain Smartcontract

Signing a message

#

Why we need to sign a message

#

• To prevent data modification in the middle of data transfer

• Make sure the message come from the right source

How it works

#

1. Signing the Message

• Server calculate a hash from the messageM (the message you want to encrypt)

• Server encrypt the hash by using public and private key pair (This is signing the message)

• Message now can be sent together with the Signature to the Smart Contract to perform registration action

• Open the Signed message

• Smart Contract calculated the hash of the Message by using public key.

• Smart Contract decrypt the Signature using the public key.

• Compare if two hash is the same, the Message is valid and not modified by third party in the middle of transfer.

Quick word for the solution we choose - Ed25519.

#

As mention above Near Protocol compile the smart contract into wasm to execute them efficiently and correctly.

The SDK to write smart contract is provided in AssemblyScript and Rust. And we choose Rust to implement this part of the application for its correctness and safe memory management system during development.

(Which comes with a steep learning curve of a new language and system)

We need to compile the code, targeting wasm32-unknown-unknown in order to deploy our Smart Contract.

Which comes to some of problem of compatibility problems. We need to aware that the library we use must be able to compiled into wasm. We have learned it the hard way when implement the first version using a library that depends on openssl written in C and at the moment cannot compiled into wasm. We had to rewritten that part again.

Ed25519 also provide a robust and fast execution compare to equivalent scheme.

Compare standards

#

Benchmarks

#

Below are benchmarks from a Core-i5 6400 @ 2.7 GHz.

Source: https://www.cryptopp.com/wiki/Ed25519#Benchmarks

The Concept Application

#

With the solution of Message Signing we develop a scheme to allow user login to LINE and request us to sign the Registration Message.

User then can use that Registration message to register his/her LINE Profile with the Near Protocol wallet by sending it to designated Smart Contract.

As you already expected, after the registration user will has the items and services on Near Protocol identified and connected with LINE Profile. And enjoy the extended features.

Features

#

Near & Line Connect

#

(The main research of this presentation)

Fungible Token - LINE coin

#

Non-fungible Token - Line NFT Shop

#

Q&A

#