►
Description
Hyperledger Iroha: Enabling CBDC and FinTech Use Cases - Makoto Takemiya, Soramitsu
This is a technical talk discussing in detail the architecture of Hyperledger Iroha and how Iroha is designed to enable CBDC and FinTech use cases. First, notable use cases of Hyperledger Iroha in the Bakong CBDC in Cambodia, as well as numerous proofs-of-concept are used as examples of what Iroha is capable of. Next, the architecture of Hyperledger Iroha v2 is explained. Finally, a quick explanation of how to build apps that use Hyperledger Iroha v2 is presented, showcasing how Hyperledger Iroha can make it possible to create a wide variety of FinTech and payments use cases, from CBDCs to DeFi. This presentation will be aimed at beginners who know nothing about Hyperledger Iroha, but many details will be explained, down to the source code level, with the goal of imparting concrete and actionable knowledge about getting started with Hyperledger Iroha v2.
Sessions Details & Slides (if available): https://sched.co/14H75
Access All Sessions: https://events.linuxfoundation.org/hyperledger-global-forum/program/schedule/
----
Hyperledger – Open Source Blockchain Technologies
Hyperledger is an open source community focused on developing a suite of stable frameworks, tools and libraries for enterprise-grade blockchain deployments.
It serves as a neutral home for various distributed ledger frameworks including Hyperledger Besu, Fabric, Sawtooth, Indy, as well as tools like Hyperledger Avalon, Cactus and libraries like Hyperledger Aries, Ursa. Learn more about Hyperledger projects: https://www.hyperledger.org/use
Discord: https://discord.gg/rVCn4j7UFd
Case Studies: https://www.hyperledger.org/learn/case-studies
Training & Certification: https://www.hyperledger.org/learn/training
Tutorials: https://www.hyperledger.org/use/tutorials
Webinars: https://www.hyperledger.org/learn/webinars
Events: https://www.hyperledger.org/events
Vendor Directory: https://www.hyperledger.org/use/vendor-directory
Subscribe to the Hyperledger Newsletter: https://www.hyperledger.org/newsletter
Follow-us on Twitter @Hyperledger
Learn about Hyperledger Membership: https://www.hyperledger.org/about/join
#Hyperledger #Blockchain
License
Creative Commons Attribution license (reuse allowed)
A
Besides
edoha,
we
we
do
some
work,
also
with
Ursa
as
well
and
in
the
polka
dot
ecosystem.
We
do
quite
a
lot
and
we
do
quite
a
lot
of
different
things.
So
today,
I'm
going
to
talk
a
little
bit
about
idraha
and
use
cases,
especially
with
the
National
Bank
of
Cambodia,
but
we
also
have
other
projects
we're
working
on
we're
working
on
a
cross-border
CSD,
rtgs
linkage,
prototype
actually
Fujitsu
who's.
A
It
just
had
a
library,
predefined
commands
that
could
be
used
for
many
Financial
use
cases
so,
for
example,
cbdc
that
has
its
pros
and
cons.
Of
course,
by
not
having
smart
contracts
per
se,
irohawan
reduced
the
attack
space
that
you
could
do
so
there's
you
know
just
predefined
commands.
So
that's
all
you
you
can
manage.
So
if
you
test
that
you
can
prove
that
it's
safe,
but
it
it
is
kind
of
limiting.
A
So
in
Idaho
2,
we
expand
this
to
have
a
turing,
complete
smart
contract
functionality
using
wasm
or
webassembly,
and
you
know
how
to
is
written
in
Rust
rather
than
in
C
plus
plus,
and
it
has.
But
it
does
continue.
The
Eder
Hall
version,
one
kind
of
concept
or
philosophy
of
having
a
robust
internal
library
of
predefined
functions
that
can
be
used
for
simple
use
cases
like
minting
and
transferring
assets,
for
instance.
So
it's
great
for
a
payments
use
case.
A
Also
Edo
Hot
2
is
really
exciting,
features
like
event
driven
triggers
that
can
execute
certain
code
on
an
event.
So
I'm
going
to
talk
a
little
bit
about
this
today,
but
first
I'm
going
to
talk
about
a
few
of
the
case.
A
few
of
the
use
cases
that
we
worked
on
with
either
hot
version
one.
So
the
first
one
I'll
talk
about
is
the
digital
identity,
use
case
and
I'm
not
going
to
go
into
the
details,
but
this
was
actually
published
in
a
paper.
A
An
IEEE
called
sora
identity,
and
this
was
I.
Think
in
2017
we
published
this,
but
for
digital
identity.
It's
a
we
experimented
with
use
cases
using
a
decentralized
identifiers
working
with
a
Bank
Central
Asia
in
Indonesia
to
build
a
prototype
identity
solution,
and
this
was
done
several
years
ago.
But
the
the
key
point
is
that
we
use
a
blockchain
platform
that
is
running
eroha,
that
each
of
the
group
companies
would
run
a
node
in
the
Prototype
and
then
the
verified
book
validated.
A
The
verifiable
claims
about
a
decentralized
identifier
were
written
into
the
blockchain
and
then
all
the
the
nodes
could
get
access
to
this
information
in
a
in
a
way
that
stored
the
provenance
of
how
the
data
was
introduced
into
the
system.
So
the
goal
of
this
was
to
create
kind
of
a
standardized
group
identity
because,
like
many
large
Financial
groups,
there's
no
standard
identity
for
all
all
clients
across
the
group,
and
we
built
this
prototype
and
I.
Don't
have
a
a
link
to
the
paper
on
the
slides,
but
we
wrote
a
paper
called
sora
identity.
A
A
Another
use
case
that
we
explored
in
either
hot
version.
One
was
weather
derivatives
for
insurance
contracts,
so
the
use
case
is
like
if
you
have
a
big
concert
outside
and
if
it
rains
it
gets
canceled,
and
so
you
have
a
big
Financial
loss.
So
what
you
can
do
is
you
can
hedge
against
this
loss
by
buying
from
Sao
Paulo
Japan?
A
You
can
buy
this
weather
derivative
contract
where,
if
it
rains,
you
get
your
you
know
some
amount
of
money
and
if
it
doesn't
rain,
you
don't
get
anything,
and
so
we
programmed
this
in
the
blockchain
in
in
a
way
similar
to
either
hot
version.
2
triggers,
but
either
version
one
you
know,
doesn't
have
this
functionality,
but
we
added
it
for
this
proof
of
concept
and
really
what
it
has
is
we
wrote.
A
We
used
an
oracle
to
write
weather
data
about
a
given
location
into
the
blockchain
at
some
fixed
time
interval,
and
then,
if
there
was
the
rain,
then
some
code
would
be
executed
automatically
on
chain
that
transferred
money
from
an
account
to
the
the
customer.
So
it's
an
automatic
payout,
so
this
was
just
a
a
way
to
simplify
or
optimize
the
workflow
for
an
insurance
contract
like
this.
A
A
Another
cool
example
we
did
in
2016
was
a
moike
is
a
event
digital
currency
that
we
did
in
Japan
in
a
in
ISO
wakamatsu,
which
is
in
Fukushima
prefecture
and
what
it
was.
It
was
a
currency
like
a
cryptocurrency,
but
it
was
only
for
a
closed
event
and
it
only
lasted
one
day,
and
if
you
would,
if
you
meet
somebody,
you
can
shake
your
phone
and
they
shake
their
phone
and
then
there's
you
know
some
app
that
that
well,
you
get
a
QR
code
that
then
you
scan.
A
A
So
people
did
these
things
to
get
this
token.
So
it
was
a
lot
of
fun,
and
this
was
a
great
use
case
for
either
hot
version.
One
showing
that
how
simple
it
was
to
just
create
a
currency
and
then
exchange
it.
It
would
transferred
to
other
users-
and
this
was
expanded
from
this
event,
to
be
used
in
in
the
campus
of
ice
University
of
Izu
in
isobakamatsu.
A
So
this
is
the
bjorko
app
and
it
launched
in
production
in
2020,
and
it's
been
running
ever
since
in
the
cafeteria
and
the
campus
store.
So
it's
a
prepaid
type
of
system,
so
users
would
go
to
the
campus
store
and
pay
some
money,
and
then
they
get.
You
know
these
tokens
that
then
they
can
use
at
the
campus
store
and
the
the
the
cafeteria
to
buy
food
and
the
motivation
for
doing
this
is,
if
you
pay
with
the
system,
you
get
a
slight
discount
on
food
that
you
buy.
A
A
But
here
they
just
have
it
on
their
phone,
and
it's
really
simple
and
fast,
and
this
has
been
running
since
2020,
with
with
Eder
Hall
version
one,
and
so
that's
in
like
the
local
context,
but
then
another
great
use
case
I'm
going
to
go
into
more
detail
with
is
bakong,
which
is
a
central
bank
digital
currency.
So
the
cbdc,
of
course,
is
I
mean
it's.
A
A
Here
I
can
be
cool
like
Steve
Jobs,
so
this
is
this
is
the
wallet
and
there's
two
currencies
in
the
wallet:
there's
a
US
dollar
and
Kumari
real,
because
cambodia's
heavily
dollarized
country,
so
many
transactions,
actually
vast
majority
of
transactions
are
in
US
dollar
and
as
a
customer,
even
though
I'm
transacting
and
I'll
talk
about
the
architecture
later.
But
the
central
bank
is
running
the
blockchain
system,
even
though
I'm
transacting
on
the
central
banks,
Ledger
I'm
intermediated
by
a
commercial
bank,
so
you
can
see
FTB
logo
up
there.
A
That's
foreign
trade
Bank
of
Cambodia,
so
it's
really
a
simple
app
there's,
just
four
features
send
receive
a
scanning
QR
code
and
deposit.
So
to
send
money,
I
can
choose
one
of
the
users
and
I
can
send
some
small
amount
of
money
like
one
command
deal.
It's
one
four
thousandth
of
a
dollar
and
let's
hit
confirm
and
then
yeah,
it's
sent
so
yeah.
It's
already
done
too.
A
So,
that's
it
so
that
actually
got
a
transaction
finality
on
either
version
one
and
it
gets
sent
it
from
my
account
to
this
user's
account
at
another
bank.
So
I'll
talk
about
the
architecture
in
just
a
moment,
but
it's
you
know
it's
pretty
fast.
You
can
use
it
to
actually
buy
things
in
stores
which
is
really
cool
and
recently
they
they
upgrade
the
system
to
Interlink
all
the
other
Payment
Systems
in
Cambodia
through
khqr.
A
A
So
I
just
showed
a
demo
of
the
app,
so
you
know
how
it
works.
There's
also
some
desktop
apps.
So
one
of
the
key
points
of
idahos,
we
put
a
lot
of
emphasis
on
actually
building
a
self-custodial
library.
So
what
that
means
is
that
if
you
have
like
a
web
app
or
a
mobile
app,
you
want
to
generate
the
key
into
all
the
transactions
signing
on
the
client
side.
You
don't
want
to
send
any
private
keys
to
servers
like
that's.
You
know
that
would
be
bad
for
many
reasons.
A
So
on
the
app
I
just
showed
the
transactions
signed
on
my
device
and
then
just
the
signed
transaction
is
sent
to
the
the
course
system
and
we
have
the
same
type
of
thing
for
desktop
apps.
So
there
are
JavaScript
libraries,
libraries
for
Android
libraries
for
iOS
and
then
eat
raw
version.
2
has
libraries
for
rust
that
are
able
to
sign,
generate
keys
and
sign
transactions
locally.
A
So
let's
talk
a
little
bit
about
the
architecture
of
bakong,
because
I
do
think
it's
potentially
interesting.
So
back
home
is
a
two-tier
architecture.
So
what
that
means
is
that,
even
though
all
the
user
accounts
are
on
a
shared
Ledger,
the
end
users
intermediated
by
the
commercial
Banks-
and
this
is
done
for
many
reasons-
one
is
privacy
because
the
central
bank
doesn't
want
to
know
the
personally
identifiable
information
of
a
user,
and
another
is
really
just
you
know
from
operational
aspects,
because
the
central
bank
is
not
providing
customer
support.
A
So
so
they
need
to
have
someone
like,
like
a
commercial
Banker
payment
service
provider
that
provides
the
support,
here's
an
another
view
of
the
same
architecture,
so
you
have
at
the
core.
You
have
hyperledger
Ed
Roja
that
is
running
as
the
kind
of
the
ground
truth
of
the
world
state.
So
who
has
what
balance
at
you
know
at
a
given
time
and
every
Bank
sets
up
a
payment
Gateway
that
then
users
like
me,
my
device
connects
to
the
payment
Gateway
and
not
to
the
the
course
system
directly.
A
So
if
I
send
a
transaction,
it
goes
to
the
Gateway.
The
gateway
then
transmits
it
to
either
hawk
to
one
of
the
peers
and
then
I
think
it's
finality,
and
then
that
comes
back
to
my
device
and
the
Commercial
Bank
also
is
part
of
the
payment
giveaway
stores.
My
personal
information
like
for
you
know,
kyc
reasons.
A
A
Popcorn
is
different
from
an
e-money
system,
because
you
know
most
in
many
systems,
at
least
in
the
in
Asia
most
of
the
time
they
work
like
this,
so
you
you'd
have
like
a.
If
you
had
like
a
prepaid
system
like
in
Japan,
we
have
a
suica
right,
I
think
in
London
they
have
oyster
here
in
Ireland.
They
have
another
analog
of
the
same
type
of
system,
but
you
pre-paid
pre-charge
it
with
some
cash.
A
Usually
and
then
you
get
some
balance
from
the
pavement
processor
on
your
card,
but
then,
when
you
actually
go
to
the
store
and
spend
the
money
you're
not
actually
making
the
payments
you're
just
sending
a
payment
instruction
that
then,
maybe
two
to
four
weeks
later,
the
store
actually
gets.
The
money
in
their
bank
account.
A
So
there's
like
a
time
lag
and
that's
not
always
convenient
for
stores,
because
they
have
to
manage
cash
flow
and
Treasury,
but
with
a
cbdc
system
like
bakong,
if
you
You're,
basically
digitizing
the
cache,
so
you
can
go
to
a
bank
charge
up
your
background
balance
and
you
get
the
background
money
and
then
you
make
a
payment
to
a
store.
They
get
the
money
instantly
and
they
can
reuse
it
or
cash
it
out
or
do
anything
they
want
with
it
with
just
a
few
seconds
right.
A
So
that's
that's
really
exciting
and
I
do
think.
This
is
the
future
and
it's
a
it's
a
way
to
easily
make
you
know
to
facilitate
payments
and
make
a
payment
infrastructure
more
convenient
in
many
countries,
some
contextual
reasons
for
those
who
are
interested
as
to
why
backlog
was
created.
So
Cambodia
is
a
large
unbanked
population.
It's
only
around
22
percent
of
cambodians.
A
So
it's
it's
a
payment
within
the
same
country,
but
traditionally
you
know
there's
no
easy
way
to
make
this
payment,
so
they
would
go
to
one
of
the
payment
operators
and
then
they
would
hand
them
some
cash.
And
then
you
know
get
like
a
code
that
then
you
message
to
your
friend.
The
friend
takes
the
code
and
it
goes
pick
up.
It
picks
up
the
cash
at
one
of
the
stores.
So
it's
it's.
A
We
used
either
hot.
For
this
mainly
I
would
say
because
it
creates
a
trust,
minimized
system.
So
it's
very
highly
robust
and
from
an
operational
standpoint,
it's
it's
kind
of
nice
to
use
a
blockchain,
because
if
one
of
the
core
Ledger
nodes
goes
down
like
on
a
weekend,
let's
say
you
don't
really
have
to
go
and
set
it
up
again
instantly,
because
you
have
enough
redundancy
built
into
the
system
that
it
just
keeps
running
and
you
can
go
and
set
it
up.
A
You
know
the
next
working
day
and
this
makes
operation
much
easier
and
from
a
central
bank
standpoint,
you
really
appreciate
the
the
robustness
of
the
decentralized
consensus,
because
you
have
many
different
nodes
that
have
to
sign
off
on
the
data.
It
makes
it
very
hard
to
hack
a
system
like
this
because
all
the
transactions
are
digitally
signed.
So
you
can't
fake,
you
know
any
kind
of
transaction,
it's
just
not
possible,
so
it
does
make
the
system
quite
quite
robust.
A
That
being
said,
you
know
this.
It
is
a
central
bank
system.
So,
at
the
end
of
the
day,
if
there
was
like
a
legal
sanction
against
somebody,
they
they
do
have
the
ability
to
you
know
to
take
action
via
the
court
system
in
the
country.
So
that's
that's
more
of
done
on
the
payment
Gateway
side
than
on
the
court.
Ledger,
though,
and
I
mean
I'm
a
Libertarian
myself,
so
I
kind
of
wish
that
everyone
would
just
use
public
blockchains,
but
unfortunately,
the
world
we
live
in.
A
You
know
there
are
certain
rules
that
that
have
to
be
implemented,
and
so
we
try
to
work
with
Central
Bank
to
design
this
in
a
way
that
doesn't
violate
anyone's
privacy
or
property
rights,
because
you
do
have
this
clear
separation
of
the
responsibilities
of
the
of
the
banks
which
manage
their
customers
and
the
central
bank,
which
is
managing
just
a
balance.
Updating
infrastructure
so
yeah
the
system's,
been
in
many
articles,
like
I,
said
pilot
launched
in
2019
and
officially
launched
in
2020,
and
it's
been
yeah
just
running
for
several
years
now.
A
A
This
is
a
data
from
last
last,
two
years
so
from
the
launch
and
then
also
in
2021
and
in
2021.
There
were
two
almost
three
billion
dollars
in
transaction
volume
and
eight
million
transactions
that
were
processed
in
2021,
and
this
year
is
much
much
higher.
So
maybe
10
times
the
schedule
of
the
exact
number
so,
but
in
between
2020
and
2021.
These
bars
are
not
to
scale
but
yeah
transaction
volume
in
khar
went
up
62
times
and
USD
went
up
95
times.
A
So
it's
really
quite
quite
exciting,
and
this
is
getting
even
background
is
getting
even
more
use
because
of
the
integration
to
the
standardized
QR
system
that
launched
in
July
called
khqr,
and
this
allows
any
of
the
banking
apps
to
scan
the
standard
QR
code
and
behind
the
scenes
it
will
do.
The
routing
and
a
lot
of
the
interbank
payments
are
going
through
bakong,
because
bekong
doesn't
have
any.
You
know
the
fees
are
cheaper
compared
to
other
systems.
A
For
a
system
like
this,
there
are
no
negative
effects
on
monetary
policy.
I
would
say
so
what
we've
observed
over
the
past
two
years
is
that
so
I'll
just
step
back
and
say
that
a
lot
of
especially
European
central
banks
are
very
scared
about
competition
between
cbdc
and
and
Banks
commercial
Banks,
and
that's
because
there's
a
lot
of
talk
about
opening
up
direct
accounts
on
the
central
bank's
Ledger.
A
So
so
really
because
these
are
non-interest
bearing
accounts.
It
doesn't
really
give
me
a
big
motivation
to
store
a
lot
of
money
in
this
account.
So
it's
really
more
of
like
just
a
replacement
for
pocket
change
that
you
would
use
physical
cash
for
anyway.
So
it's
for
daily
payments.
It's
not
really
for
savings.
I
would
say
people
have
lots
of
money.
They
use
Traditional
Bank
account,
especially
in
Cambodia,
where
you
can
get
five
percent
interest
paid
on
your
savings.
So
people
people
don't
really
store
large
amounts
of
money.
A
In
background
is
what
we've
observed
over
the
past
two
years
and
it's
more,
for
you,
know
small
transactions
and
also
as
a
payment
rails
for
wholesale
payments
between
things,
so
I
would
say:
there's
no
negative
effects
and
there's
lots
of
positive
effects
too,
because
it
acts
like
the
glue
to
integrate
all
these
different.
You
know
payment
apps
across
all
the
different
banks
and
that's
really
exciting,
because
users
shouldn't
have
to
think
about.
A
You
know
what
app
is
the
store
using
you
know,
just
signing
an
app
is
makes
it
very
easy
and
what's
really
exciting,
is
that
there's
integration
work
being
done
with
a
prompt
pay
in
Thailand,
so
people
will
be
able
to
then
go
to
Thailand
with
back
home
app
and
make
a
payment,
and
then
it
will
convert
behind
the
scenes
to
Thai
bot
and
send
it
across
the
prompt
paid
Network.
So
that
and
because
prompt
space
also
used
in
Laos
you,
you
can
kind
of
use
the
same
app
in
three
countries,
which
is
really
cool.
A
There's.
Also,
some
cool
use
cases
for
cross-border
use,
so
back
home
is,
is
used
for
cross-border
payments
from
Malaysia
to
Cambodia
via
Maybank.
So
Maybank
has
Branch
offices
in
both
countries,
so
in
Kuala
Lumpur
you
can
go
to
Maybank
office
and
you
can
convert
dollar
or
convert
digest,
ring
it
to
Dollars
in
a
back
home
system.
Then
you
can
send
it
to
somebody
in
Cambodia.
So
this
is
a
really
great
because
you
don't
just
send
it
to
somebody's.
A
You
know
bank
account,
but
you
can
also
make
payments
directly
to
any
background
user
and
in
theory,
because
khqr
is
standardized
now
you
can
make
a
payment
to
any
anyone
in
the
payments
Network
in
Cambodia
from
Malaysia
like
directly.
So
this
has
use
cases
for
empowering,
especially
women
who
go
out
of
Cambodia
and
go
to
work
in
Malaysia
like
in
a
Hospitality
use.
A
Really
you
have
the
concept
of
a
domain,
an
account
and
an
asset,
and,
as
you
can
see
in
this
in
this
diagram
here,
a
domain
acts
like
a
box
that
you
can
put
accounts
in,
you
can
put
Assets
in
and
the
the
assets
can
be
owned
by
counts.
So
it's
it's
a
very
simple
object
model,
but
these
are
basic
Primitives
that
that
are
important
to
think
about,
because
this
helps
to
standardize
the
Assets
in
a
ledger.
A
So
if
you
don't
have
this,
then
you
end
up
with
something
like
ethereum,
where,
for
instance,
even
if
you
have
an
erc20
token,
the
specific
implementation
of
the
contract
can
be
different.
So,
like
some
erc20
contracts
referred
to
failed
transactions,
some
emit
events
or
some
return
false
and
don't
emit
events.
So
you
have
to
handle
all
these
special
cases
in
ethereum
because
there's
no
asset
standardization,
even
though
there's
like
a
kind
of
a
loose
standard
but
idroja
actually
standardizes
how
you
represent
it
like
an
an
asset.
A
A
So
I
can't
actually
zoom
in
more
than
400.
That's
too
bad,
okay.
So
in
a
domain,
for
instance,
a
domain
has
accounts,
it
has
asset
definitions
and
also
has
this
metadata
field,
so
you
can
add
other
types
of
metadata
associated
with
the
domain.
This
could
be,
you
know,
really
anything
so
some
kind
of,
like
you
know,
key
value
model.
You
can
add
to
represent
any
kind
of
annotation
about
what
a
domain
is.
We
also
have
this
logo
field
too.
A
That's
to
help
like
data
viewers
to
be
able
to
in
a
decentralized
way,
show
information
about
the
the
data
on
chains.
So
sometimes
you
would
want
like
logo
data.
This
is
optional.
Of
course,
domain
has
accounts.
So
what
that
means
is
that
all
accounts
on
the
Chain
are
associated
with
some
domain
and
they
can
inherit
some
properties
from
the
domain
too,
like
permissions
and
accounts
have
assets
and
they
have
signatories.
A
There's
lots
of
options
that
you
can
play
with
it's
made.
It's
made
to
be
really
robust
out
of
the
box,
so
you
don't
have
to
write
all
this
logic
yourself.
If
you're
trying
to
do
common
asset
use
cases,
one
thing
that
may
also
make
it
easy
to
kind
of
see
how
the
data
model
works
is
taking
a
look
at
an
example
Genesis
box.
So
in
the
Genesis
Book
you
can
have
this
optionally.
A
You
can
have
a
definition
of
some
assets
and
users
right
in
the
the
first
block
and
I
was
hoping
actually
to
zoom
in
more
than
400
percent,
but
anyway,
it
is
what
it
is.
So
I'll
just
read
it
through
in
case
you
can't
read
this.
So
what
you
have
in
the
Genesis
block
is
a
very
simple
definition
in
Json,
where
you
have
a
list
of
transactions
that
are
executed
in
order,
and
you
have
Isis
which
I'll
talk
about
in
the
next
slide
actually,
and
so
in
either
Hot
2.
A
We
have
a
list
of
predefined
kind
of
commands
like
a
library,
and
these
are
called
Isis
or
your
house
special
instructions.
The
idea
is
it's
similar
to
how
CPU
has
a
instruction
set.
That
is
predefined
and
these
are
just
high
level.
Instructions
like
a
register
like
like
a
mint
like
I,
think
there's
a
a
dementor
burn
type
of
instruction
too.
So
here's
an
example
of
registering
a
new
domain
called
Wonderland.
A
So
there's
a
lot
of
wrapping
and
stuff
that,
hopefully,
will
be
simplified
in
the
future.
But
what
you
have
is
the
register
isi
that
says
register
and
then
you
create
an
object
and
it's
an
identifiable
answer
domain
and
it
has
the
name
Wonderland
and
at
the
beginning,
when
you
first
registered,
it
has
no
accounts
or
assets,
but
once
you
register
the
domain
in
this
transaction,
you
can
Define
the
next
transaction,
which
is
registering
a
new
account
called
Alice
in
the
domain.
Wonderland
and
Albus
has
the
signatory
just
one
signatory
here.
A
This
is
a
public
key,
so
it
it
uses
the
Twisted
Edwards
curve
Ed
and
then
then
has
the
public
key
bytes
here.
So
you
could
have
actually
multiple
signatories
here.
If
you
wanted
to
have
a
multi-signature
account,
so
it's
really
easy
way
to
make
multi-sync
accounts
and
then
you
can
also
register
an
asset
definition.
So
here's
an
asset
definition
so
register
object,
as
the
definition
name
is
rows
and
it's
in
the
domain
Wonderland
and
you
can
just
create
the
asset
definition.
A
Then
you
can
mint
some
roses,
so
you
call
them
mint
instruction
and
it's
for
the
asset
definition
rows
in
domain
Wonderland
and
you
give
it
to
an
account
ID
Alice
in
the
domain
of
Wonderland
and
you
mint
13
of
these
roses.
So
it's
a
little
bit
verbose,
but
this
is
you
know
the
predefined
Genesis
block,
that
kind
of
starts
up
the
system
and
in
the
future,
I
think
it'll
be
a
little
bit
simplified
using
something
like
the
python.
A
Library
also
makes
it
easier
to
write
this,
but
this
is
showing
an
example
of
of
how
the
Isis
work
so
the
pre,
this
pre-built
library,
is
really
robust.
So
you
can
create
many
different
types
of
accounts
and
assets
right
out
of
the
box
without
having
to
do
anything
complex
and
because
it's
written
right
into
the
core,
the
data
flow
is
really
optimized
for
these.
So
it's
it
can
be
made
very
fast.
A
Here's
some
more
examples
of
the
eye
size,
so
this
is
using
the
Rest
Library,
so
I
mean
I
kind
of
simplified
it
a
little
bit,
but
you
can
create
this
domain,
Looking,
Glass
and
then
inside
of
Looking
Glass.
So
once
you
create
the
domain,
you
you
can
build
the
transaction
use.
The
library
then
submit
the
transactions.
A
So
it's
really
easy
to
just
you
know,
write
some
code
as
a
client
and
submit
it
directly
to
one
of
the
peers
on
your
network
and-
and
it
just
takes
a
few
seconds
and
once
you
have
this
domain
Looking
Glass,
you
can
register
a
new
account
White
Rabbit
at
Looking
Glass.
So
this
is
kind
of
like
an
optional,
well,
I'm,
not
sure
if
it's
optional,
yet
it
will
be
in
the
future.
At
least
this.
This
type
of
named
account
structure.
A
It's
like
an
email
address
type
of
structure,
but
you
can
also
send
directly
to
other
types
of
identifiers
in
the
future
or
maybe
even
now,
I'm
not
sure
if
it's
finished
yet
actually
so,
I
should
check.
So
Isis
are
nice,
but
there's
also,
you
know
whole
universe
of
possibilities
out
there.
So
you
want
to
also
be
able
to
execute
arbitrary
code,
and
that's
really
robotism
helps
so
awesome
is
webassembly.
We
use
it
wasn't
VM
to
safely
run
executable
code
and
we
have
some
interfaces.
So
we
can.
A
You
can
call
the
object
model
inside
of
your
wasm
contracts.
So
here's
an
example
of
a
use
case
where
you,
you
query:
you
find
all
the
domains
in
the
system,
so
you
just
say
give
me
all
the
domains
and
you
get
this
vector
and
then
for
each
domain.
You
add
a
you
add
a
new
account
called
mad
header,
so
you
basically
Loop
through
all
the
domains.
You
add
a
new
account
to
all
the
domains,
and
then
you
register
this.
That's
what
the
register
instruction
down
here
does.
A
So
you
can
call
the
Isis
inside
of
your
awesome
contracts,
and
this
is
how
you
update
the
world
state.
So
this
is
a
silly
example,
but
it
kind
of
shows
you
how
it's
really
easy
to
do
these
types
of
things
with
the
isi
framework
and
because
you
can
write
this
code
in
any
language
that
compiles
to
wasm
like
it
wasn't
blob.
A
I
mean
you
do
have
to
have
the
libraries
built
for
it,
of
course,
and
then
finally,
I
want
to
talk
a
little
bit
about
exciting
feature
called
triggers,
so
triggers
are
quite
complex
and
I
can't
go
into
all
the
details
now,
but
it
allows
you
to
execute
some
some
code
or
an
action
on
an
event
that's
submitted.
So
when
you
execute
certain
types
of
events
in
iraha,
you
get
an
event
that's
emitted,
and
you
can
listen
to
these
events.
A
So
here's
a
silly
example,
but
it
allows
you
to
create
a
trigger,
so
you
register
hey
a
trigger
called
refresh
T
and
this
trigger
when
it's
executed.
The
executable
here
creates
a
t
asset
and
of
quantity,
one
and
transfers
it
to
Alice
from
the
Mad
Hatter.
So
what
this
does
is
when
the
when
Alice
reduces
the
well
I'll
I'll
talk
about
the
events
here
in
a
moment,
but
what
it's
supposed
to
do
is
when
the
asset
drinks
some
tea,
she
gets
more
tea
from
the
Mad
Hatter.
A
So
when
the
acid,
in
her
account
reduces
she
gets
more
sent
to
her.
So
the
way
it
works
is
there's
it's
easier
to
look
on
my
screen
here.
So
when
the
so
you
have
this
trigger
that
repeats
indefinitely.
That
is
looking
for
some
event,
that
is,
asset
event,
filter
removed.
It
says
by
remove
so
when
the
asset
you're
looking
for
is
removed
from
an
account.