Azure Blockchain Tokens Part 2: Managing Accounts


[MUSIC].
>>Hello, everyone. Welcome to
another episode of Block Talk,
and today we have a special
guest with us Greg Cignavitch,
who is a Senior Software
Engineer on the team.
Greg what are you going to
talk to us about today?
>>Today we’d like to talk about
Azure Blockchain Tokens
Account Management.
>>Awesome. So account management
seems like a pretty complex topic,
what exactly does that entail
for Azure Blockchain tokens?
>>So for Azure Blockchain tokens,
different users have
different levels of access
to perform different operations
within tokenized scenario.
One of the first flows
fundamental questions
that may took Blockchain scenario
is what accounts will
adjust in the ledger,
and how to manage the access of
those accounts between participants,
and how this all fits together as
a well-controlled and
well understood scenario.
>>So sounds like there’s some
complex concepts in there,
like how the account ties
to the different
networks that you’re on,
and sounds like you have
to assign different users,
access to different groups as wall.
Do you mind going over some of
those complex concepts with us?
>>Absolutely. So let’s take
the high-level concepts from Azure
Blockchain tokens one by one.
The first one is Blockchain Networks.
In Azure Blockchain tokens,
the service is built to enable
cross ledger interoperability,
it can also work as a single ledger,
it’s really your choice.
So depending on whichever
set of networks you want,
you can onboard the music
connection string and then start
creating accounts and this shrink
transactions against those networks.
>>Okay.
>>The second part is
the accounts themselves.
So once I’ve identified that the
network or networks
that I want to use,
I can create the
accounts that typically
a public-private key
pair on the Blockchain.
This allows Azure
Blockchain tokens to
create transactions for you to
sign them and route them to
the appropriate network,
which you chose to the API.
So that makes it really
easy to actually handle
the transactions and map
the identities as well,
because the identities on
the Blockchain are typically
just a public key string,
and how would you know
what this represents,
this is a way that lets
you easily track through
the account you created
throughout the Blockchain tokens.
What’s the account
address on the chain?
In which Blockchain
does it belong to?
>>Okay.
>>Finally, groups allow you to
solve the problem of how to manage
a large number of accountants across
Blockchains or across your scenario.
They also allow you to
easily track and audit
which applications and users in
the Directory have the ability
to use the Azure Blockchain
tokens API to fire off
the transactions and transform the
state of the world as it were.
So this feature for example
could be used to model
many different different lines of
business or different participants
in a Blockchain scenario.
>>Interesting. So let me see if
I’m grasping the idea correctly.
So in terms of groups and accounts,
let’s say in a loyalty
points scenario,
if I am shopping at a store and
the store issues logy points,
and I’m coming in as a
customer of this store,
I might be in a group that’s
like a customer group,
and all we can do is
receive tokens or use
our tokens and we’re
all in one group that has
a certain level access.
>>Right.
>>Maybe there’s another
group that’s owned
by the actual store
that’s selling us stuff,
and they will be in a separate
group that has higher privileges,
like maybe they can mint additional
loyalty points are certainly.
>>Yeah.
>>Great. So how would I model
this with Azure
Blockchain tokens side?
>>So let’s take it step by step.
So at the very beginning,
we’ll create a new instance of
Azure Blockchain tokens which will
organize all these concepts
together and allow us to use
a single API to drive the scenario.
We’ll then choose which
Blockchain we want to use,
and right now we can connect with
any Ethereum premium Blockchain,
and one great way to get started
this Azure Blockchain
service to create
a node and create a network
which will have the tokens.
>>Okay.
>>Next, we’ll create groups for
the three different
scenarios you mentioned.
Maybe you will create one
group for the token holders,
a group that represents
the token holders,
and one that represents the preps the
accounting department of the
store or the loyalty system.
>>Right.
>>Which is able to issue new tokens
and bring you tokens
in the ecosystem.
Then maybe a third group
which is some service or
process that actually
cancel those tokens
out once they’ve been used and
removes them from the supply.
>>Got it.
>>So we have the granularity
to control who can-
>>Do perform which actions.
>>Precisely.
>>Yeah. Nice.
>>Then, we’ll go ahead and create
the actual Blockchain accounts,
because Blockchain
protocols are great
about mapping these
public-private key pairs,
but sometimes the deployment
of those accounts can
be quite complicated.
So what we’ll do throughout your
Blockchain tokens is simply say,
let’s create an account for
you, an account for me,
an account for 50 other customers
and that consumer group,
and then let’s say that there’s
two or three accounts
that have access,
let’s say in this
particular business that
have access to create new
tokens are appointed tokens.
Finally, we’ll establish what level
of Active Directory Access is
needed for these different groups.
So the application that is involved
with receiving the
transactions of the usage
of the points and the redeemer of
the points can be connected
to the consumers group.
Then the counting application
could be connected to the others.
Over time these scenarios can change,
you can reorganize the
permissions on the Blockchain,
and you can reorganize
the API or the front of
permissions that give
access to different
service principles
or accounts to use
these functionalities.
>>Just one quick question before
asking some more questions.
When I’m creating
groups and accounts,
seems like those are tightly
coupled with Blockchain networks.
Can you explain a bit about how
those all relate to one another?
>>Sure. So groups exist
across Blockchain networks.
Groups represents an
abstract concept and
it’s a flexible container that
you can adapt to your scenario.
>>I see.
>>Including any number of accounts.
Each account will be tied to
one Blockchain or deployed
for one Blockchain.
>>So if I am a store
and maybe I have
customers on one network or
maybe I’ve customers on
three different networks.
>>Sure.
>>I can have maybe loyalty points
holding accounts across
all three networks,
but I can group all
of those different accounts
in one group where I
am creating and issuing
these loyalty points into
the holding accounts.
>>Yes. Even though there’s
three Blockchains in place,
you can have one single Active
Directory service principle
that gives access to users accounts
and the controllers accounts.
>>Okay. Great. Thank
you for explaining.
>>So just to recap through
Azure Blockchain tokens,
you can easily create
and deploy new tokens
using any account which you want in
any flexible account model which
your application requires.
You’re able to add
accounts to tokens and
roles quickly and easily,
dynamically on the fly.
It doesn’t need to be just something
you do at deployment time.
It could be something that can evolve
through the integration
with your application.
Finally, these groups and
accesses can change over time,
depending on the business scenario,
systems come and go,
micro-services are added,
and you are quite
flexible in managing
both the API access to
perform these operations and
access to the accounts underneath.
Then, also what on the ledger
controls access to those account?
How on the ledger we allow or deny?
Definitively who can
perform those actions?
>>Nice. Yeah, this sounds
like it’s pretty flexible
and really adopted for
different scenarios.
So that’s really nice to hear.
I guess if I wanted to learn
more is there somewhere
I can go to read a little more,
or technical documentation,
and things like that?
>>Yes, absolutely. Please
visit aka.ms/ABTDocs,
and start looking at
our product documentation
and learn how you can
integrate Azure Blockchain
tokens into your system,
and use Azure Blockchain tokens
to create your scenario today.
>>Awesome. Thank you for joining us.
I’m curious sharing about
account management,
and for everyone
watching thank you for
joining us today on Block Talk,
and we will have more
coming up for you.
If you haven’t watched
our other videos yet,
go ahead and take a look.
There’s three parts for
this initial series of
Azure Blockchain tokens,
so go ahead and check that out.
Thank you so much for joining
and we will see you next time.
>>Thanks. Bye.
>>Thank you.
[MUSIC]

Add a Comment

Your email address will not be published. Required fields are marked *