AppCoins News Update, or ANU for short, is a regular bi-weekly update by the AppCoins team. As usual we are going to cover dev updates, market reports, team members and upcoming events. This week’s focus is on PoC of the In-App Purchases (IAP) flow using µRaiden, the discloser of a new web page for the consolidation of the different use cases of the AppCoins Protocol, AppCoins featured member, and Upcoming News. You may expect the next ANU on the 20th June.

Quicklinks

Dev Update

APPC Markets Report

Featured Team Member

Upcoming Events

This week’s Dev Update will essentially build on the last point of the last ANU, as we’re putting a lot of effort in the Scalability Proof of Concept (SPoC) for the Knuth release.

We’ll also cover the development of a new web page that will serve as the entry point for everyone that wants to know more about the AppCoins Protocol and its use cases, as well as products (Wallet and SDK).

Scalability Proof of Concept (SPoC)

As we’ve said in ANU #10, we’re working hard to build a PoC of the In-App Purchases (IAP) flow using µRaiden. µRaiden consists of unidirectional payment channel technology, enabling instant transactions with zero fees. It will enable AppCoins users to perform latency-less transactions with cryptocurrencies and all the advantages of Blockchain without having to pay for transactions fees.

The µRaiden flow pattern is the following:

An Ethereum account opens a payment channel with another Ethereum account. The payment channel is unidirectional , which means only the account that opened the channel (i.e., the sender) can send tokens to the other address (i.e., the receiver).

, which means (i.e., the sender) (i.e., the receiver). The sender tops up the payment channel with a number of tokens of his choosing. The sender can then perform fee-less transactions until the chosen number of tokens is exhausted .

. When the sender wants to perform a transaction, he produces a balance proof . This proof is sent to the receiver, which confirms its validity. If the balance proof is valid , this means the transaction was successful . Then, the tokens involved in the transaction are allocated to the receiver .

. This proof is sent to the receiver, which confirms its validity. , this means . Then, the . Both the sender and the receiver can close an open channel at any time, provided they possess the valid balance proofs. When a channel is closed, the receiver gets the tokens allocated to him and the sender gets back the tokens he didn’t spend.

The above pattern applied to the IAP flow of the AppCoins Protocol will be:

The user is using an app with the AppCoins SDK integrated. Once the user wants to buy an in-app item and clicks on it, the AppCoins Wallet is triggered and shows the payment dialog .

and clicks on it, . The payment dialog will state if there’s an open µRaiden payment channel or not. If there’s already an open channel, the user can confirm the payment, and it will be done using the APPC in the channel. The transaction will be instantaneous and fee-less.

or not. If there’s already an open channel, the user can confirm the payment, and it will be done using the APPC in the channel. If there isn’t already an open channel, the user will be able to open one and top it up with a certain amount of APPC . Then, the payment is done already using the payment channel.

and . Then, the If the user has an open µRaiden payment channel, it can be closed in the AppCoins Wallet at any time, and the unused APPC are sent back to the user’s account.

Below are some of the layouts that will be included in the AppCoins Wallet, which supports the SPoC.

IAP dialog of AppCoins Wallet with µRaiden integration

“Read More” web page

We’ve developed a new web page that consolidates the development status of the several use cases of the AppCoins Protocol, as well as of the products supporting them.

Developers, users, app stores and any interested party can see how to use the AppCoins Protocol, how the Wallet works, how to test and experiment with the two use cases we’re tackling at the moment: In-App Purchases (IAP) and Mobile Advertising.

From there, visitors are directed to other web pages that are specific to each use case and go more in-depth about what’s done and how. Feel free to explore and give us your feedback.