►
Description
Join us as Aaron Cox from Greymass unpacks the innovations behind WharfKit. Dive into how WharfKit is transforming blockchain development, bridging web applications with diverse blockchain networks seamlessly. With WharfKit's intuitive tools, mastering decentralized app creation has never been easier.
00:00 - Intro
01:01 - How Aaron became a block producer and started working on EOS
04:15 - Origins of Greymass and where the idea came from
13:08 - What is an SDK? Why does it matter?
14:43 - Upcoming features: Session Kit, Contracts Kit, and Account Kit
18:01 - The types of developers who will be able to use these tools
24:13 - How Aaron envisions developers creating and extending those toolsets, and how they can get involved now
28:34 - Wharf's vision for building on EOS and other Antelope chains
33:05 - Release timelines and collaborations within the community
37:05 - Advice for newcomers to the ecosystem
39:32 - Possibilities with new tools
41:30 - How people can learn more about Greymass and support their work in the ecosystem
48:30 - Dogfooding some Wharf kits
52:55 - Upcoming Webinar
The EOS Network Foundation coordinates financial and non-financial support to encourage the growth and development of the EOS Network. We’re harnessing the power of decentralization to chart a coordinated future for the EOS Network as a force for positive global change.
// EOS Network Foundation //
https://www.eosnetwork.com
https://twitter.com/EosNFoundation
https://www.linkedin.com/company/eos-network-foundation
https://t.me/EOSNetworkFoundation
https://discord.gg/eos-network
info@eosnetwork.com
#EOS #Web3
A
We're
here
today
with
Aaron
Cox
I'm,
your
host
Brandon
Lovejoy,
with
the
es
Network
Foundation
and
Aaron
you're,
a
difficult
person
to
introduce
I
mean
for
me,
you're
kind
of
quintessential
figure
in
the
space
and
I
suspect
for
a
lot
of
people.
You
are
you're
history
with
EOS
and
indeed
with
EOS
iio.
Now
Antelope
goes
back
to
the
very
beginning,
but
let's
go
even
further
back
before
before,
even
that,
you
were
very
much
involved
in
the
steam
blockchain.
That's
where,
where
we
first
met
I
believe
if
I'm
not
mistaken,
yeah.
A
A
long
time,
yeah
I
think
you're
about
right.
20,
2014,
I
feel
like
in
April
of
2014
I
was
out
in
blackt
getting
to
know
what
was
going
on
with
the
bitshares
team
and
then
somewhere.
No,
that
was
2015
I,
it's
all
blur,
but
so
so
you
got
into
were
you
involved
in
bit
sharers
at
all?
I
can't
remember
if
you
I.
A
B
I
was
working
at
a
startup
at
the
time.
Doing
kind
of
my
history
before
blockchain
was
all
in
kind
of
social
systems
and
like
connecting
people
on
the
web,
and
one
of
the
things
I
was
working
on
at
the
time
was
kind
of
a
review.
Engine
and
Trust
was
a
big
issue
like
being
able
to
understand
and
have
verifiability
in
people
reviewing
things
and
when
I
stumbled
into
steam,
because
I
was
just
like
passively
interested
in
crypto.
B
At
that
point,
it
was
seeing
user
generated
content
on
the
blockchain
that
Drew
me
in
to
actually
start
like
investigating
in
the
technology.
So
that's
I,
guess
what
pulled
me
in
and
steam
being.
This,
like?
Oh
people
can
actually
like
write
and
participate
on
chain
with
more
than
just
Financial
activity
is
when
I
decided
to
jump
in
and
start
learning
and
building,
and
that's
the
origin
of
kind
of
how
I
got
to
where
we
are
today.
A
Yeah,
so
you
you
kept
at
it
with
steam
and,
of
course,
steam
forked
to
Hive
I
know,
there's
some
really
interesting
stories
and
lessons
from
all
that
we
probably
don't
need
to
get
into
right,
but
just
just
for
context
for
any
listeners
out
there
and
you
were
a
block
producer
or
back,
then
it
was
called
something
else,
a
witness
on
that
Network
and
then
so,
when
EOS
launched.
What
was
your
you
know?
What
was
your
segue
there?
How
did
you?
How
did
you
make
the
the
leap?
No
P.
B
Well,
I'd
always
like
steam
was
very
much
designed
to
be
this
like
social
media
platform
and
I
wanted
it
to
be
able
to
do
other
things.
So
when
you
know
EOS
was
announced
and
the
eosio
stack,
it
was
what
I
wanted
steam
to
do
originally
to
to
Branch
off
into
more
generic
purposes
and
allow
multiple
applications
to
exist
like
coexist
with
different
purposes
in
the
same
space
with
steam.
B
It
was
all
very
much
structured
like
here's,
a
post,
here's
this
reward
system
around
these
posts,
and
you
can
like
things
but
when
it
opened
like
EOS,
offered
the
potential
to
do
that
and
then
anything
else,
alongside
of
it
with
just
its
generic
smart
contract
language.
So
for
me
it
was
kind
of
just
the
Natural
Evolution
of
going
from
this
very
bespoke
blockchain.
B
That
did
one
thing
to
having
a
similar
blockchain
with
the
account
structure,
some
sort
of
resource
system
and
all
of
the
like,
and
with
the
block
production
mechanisms
into
a
generic
use
case
that
anybody
could
build
on
like
that
was
just.
It
was
such
a
powerful
step
forward.
It
was
no
longer,
you
know
you
needed
the
witnesses
and
steam
to
approve
the
system.
Contract
updates
to
make
the
system
behave,
different
L
it
was.
A
With
EOS
emerge
the
one
of
the
first
Prime
examples
of
a
real
general
purpose:
smart
contract
platform,
giant
permissionless,
Ledger
that
anyone
can
plug
into
and
when,
when
Yos
first
launched.
Interestingly,
to
continue
a
bit
with
your
running
bio.
Here,
we
didn't
have
any
way
to
vote.
So
in
June
of
2018
when
EOS
first
went
live,
I
mean,
apart
from
cleos
the
command
line.
I,
don't
know
that
there
was
another
way
to
vote
and
along
Along,
Comes
Aaron
and
had
had
grey
Mass
was
grey.
B
Well,
I:
it's
because
it's
what
I
knew
at
that
time
in
my
efforts
to
build
other
applications
on
Steam
I
had
already
for
I
think
maybe
two
years
been
working
on
kind
of
wallet
software
in
the
steam
ecosystem.
So
it
was
when
Scott
and
I
Scott
is
the
other
co-founder
of
Grey
Mass
we
teamed
up.
I
was
like
hey,
let's,
let's,
this
will
be
our
public
offering.
B
This
will
be
what
we
know
that
we
can
bring
to
the
ecosystem
and
we
can
leverage
kind
of
some
of
the
tech
that
we've
already
built,
because
Steam
and
EOS
were
somewhat
similar.
So
we
decided
that
was
the
first
project
we
would
take
on
alongside
launching
apis
to
power
it
because
both
Scott
and
I
were
very
big
API
providers
in
the
steam
ecosystem.
So
we
were
like.
B
Let's
do
a
wallet,
let's
do
apis
and
let's
just
connect
people
to
the
chain
and
even
before,
like
when
working
on
wallets
in
the
steam
ecosystem,
we
had
seen
the
difficulties
of
like
connecting
external
app.
So
we
were
like
okay,
we're
going
to
going
to
take
what
we
know
and
we're
going
to
start
building
and
start
doing
this
like
integration
layer.
So
that
way
we
could
build
the
apps
that
we
wanted
to
build
on
the
blockchain
and
we
still
haven't
quite
gotten
back
to
that.
Yet
still
building
the
tools
to
build
the
house
right.
A
A
Oh,
the
analogies
are
going
to
start
cting
here.
I
can
feel
it
so
so
yeah
Yos
spotter
came
online.
Eventually
that
was
rebranded
to
ankor.
Ankor
became
a
pretty
like
a
Cornerstone
wallet
in
the
in
the
ecosystem.
Let's
say
and
Y
all
continued
working
on
that
welcome
to
your
architects
of
consensus
ATV
by
the
way,
help
was
fine
that
we've
just
like
I,
see
you
as
one
of
the
core
Architects
and
it's
interesting.
A
We
focused
in
the
past
on
on
more
of
the
like
the
deeper
consensus
level
protocol
Engineers,
but
in
reality
and
like
you're
one
of
the
people,
that's
working
to
bring
that
sort
of
like
deep,
dark
Machinery
that
no
one
can
really
touch
or
access,
and
you
know,
or
very
few
people
have
the
the
skills
to
do
it.
You're
making
it
accessible
and-
and
so
perhaps
that's
our
segue
into
into
Warf,
so
yeah
I
think
your
bonafides
are
very
established
now.
If
anyone
didn't
know
Aon
Cox
before
tuning
in
now,
you
have
a
pretty
good
idea.
A
This
gentleman's
been
at
it
for
quite
a
while
and
I
do
want
to
ask
before
we
get
into
war
fully.
What
so,
okay,
so
you
kind
of
said
you
came
to
EOS-
is
kind
of
like
this
natural
migration
from
Steam,
and
you
continue
to
build
on
on
EOS
to
this
day
and
now
you're,
even
building
tools
to
help
people
build
on
EOS
with
with
Warf
and
know
before
we
go
too
deep
into
the
details
here,
like
what
keeps
you
what
keeps
you
building
in
this
space?
What
gets
you
up
in
the
morning.
B
I
I
think
it
really
does
boil
back
down
to
that.
I
eventually
have
dreams
of
building
an
app
and
I
know
what
tools
I
need
to
build
that
app
and
they
just
they
haven't
existed.
We
we
spent
a
lot
of
years
like
the
early
years
of
EOS
building
the
tools
we
needed
around
anchor
exclusively
like
when
fuel
came
out.
B
A
B
We
had
control
over
this
one
app
and
the
sdks
for
our
app,
but
we
couldn't
get
outside
of
that,
because
there
were
just
these
other
tools
that
were
being
built
that
wasn't
taking
into
account
all
of
these
things
that
we
needed.
So
Worf
really
gave
us
the
chance
to
be
like
okay,
we're
not
we're,
not
building
tools
for
our
products,
we're
building
tools
for
all
product
and
we're
going
to
take
everything.
We
learned
that
we
built
into
anchor
and
we're
going
to
bring
that
out.
So
that
way
anybody
can
use
it
with
any
application.
B
Right
I
mean
there's
some
Origins
even
further
back.
We,
it
depends
on
how
deep
down
you
want
to
go
into
the
SDK
layer,
like
our
initial
try
at
all
of
this
with
ankor
was
using
the
sdks
that
block
one
created.
Basically,
when
the
network
launched
and
then
those
sdks
didn't
really
evolve
at
all,
but
the
network
kept
evolving,
so
I
think
it
was
maybe
2019
or
2020.
We
set
out
to
build
sdks
that
replaced
what
block
one
had
built
and
then
we
started.
B
There
we
go
another
analogy,
but
there
was
no
opportunity
to
break
out
of
that.
Like
you
couldn't
go
your
own
way
with
that
software,
so
we
had
a
point
where
it
was
just
we
needed
to
go
other
directions
to
improve
the
user
experience
fuel
being
a
really
good
example
of
that
and
the
software
just
didn't
allow
us
to,
and
there
was
so
little
collaboration
happening
from
the
external
Community
us
being
in
the
external,
with
the
developers
who
maintained
the
software
block,
one
that
we
were
like.
B
Okay,
we
just
need
to
abandon
this
and
go
our
own
path.
We
migrated
all
of
our
software
to
that
and
started
like
that
is
the
framework
in
which
all
of
Warf
is
now
built
on.
Is
this
more
flexible
furbos
thing
that
anybody
can
use
to
build
their
own
path
and
we're
now
using
Warf
to
create
what
we
think
some
of
the
best
paths
are?
But
if
you
don't
like
that
path,
now,
there's
an
option
to
break
out
of
it
and
like
go
your
own
way.
B
B
A
Much
more
granular
history,
I
guess,
I,
wasn't
totally
aware
of
a
lot
of
the
earlier
conversations,
which
is
great
I'm
learning
as
we
go
here,
and
also
just
to
keep
this
conversation
as
accessible
as
possible
to
anyone.
That's
just
tuning
in
and
doesn't
know
a
lot
of
these
terms
like.
Can
you
just
give
us
a
like
a
the
cliff
noes
version
of
what
is
an
SDK?
Why
does
it
matter?
Software
development
kit
is
what
it
stands
for.
B
B
You'd
have
to
make
your
own
tools,
whereas,
like
in
this
hypothetical
analogy,
it's
like
okay,
we
dropped
you
off
in
the
middle
of
nowhere
and
now
here's
a
tool
box
that
it's
got
a
hammer
and
some
nails
and
a
screwdriver,
that's
what
the
SDK
is
for
developers.
It
gives
them
that
basic
set
of
tools
for
the
thing
that
they
need
to
do
so
it's
just
this.
It's
super
valuable
when
you're
walking
into
an
ecosystem,
there
were
no
sdks
in
the
steam
world
you
jumped
in,
and
you
had
to
build
your
house
from
scratch.
A
Doesn't
sound
ideal,
okay,
cool
and
I
had
some
other
stuff,
but
we'll
just
shove
that
for
now
and
just
get
into
the
the
heart
of
the
matter,
because
they
I
think
we've
been
teasing,
people
L
it
up
so
at
least
I
have
them
thanks
for
playing
a
lot.
I
I
think
it's
valuable
history
to
to
help
us
understand.
You
know
how
we
got
here
and
why
we're
in
this
space
a
lot
of
people
I
think
don't
have
all
this
history
kind
of
baked
in
their
brain.
So
it's
good!
A
So
you
you
said
that
the
the
warf
Warf
kit,
originally
the
wallet
plus
blue
paper
that
was
funded
by
to
the
enf
and
then
and
then
eventually
it
got
funded
through
the
anop
Coalition
itself.
The
actual
coding
of
it
right
is
that
how
that
all
yep
so
now
that
you've,
we've
gotten
to
the
point
you
just
released
the
first
session
kit
V1,
is
that
right
with
a
couple
others
on
the
way
yep
yep
there
yeah
go
ahead,
drop
us
into
what's
on
offering.
B
Sure,
a
couple
weeks
ago,
we
released
the
the
version,
one
kind
of
the
production
ready
version
of
the
session
kit,
which,
to
kind
of
step
back
from
that
a
little
bit
Warf
as
a
project,
is
a
suite
of
tools
like
it
is
it's
like
a
name
brand
of
tools.
The
session
kit
itself
is
one
of
these
products
in
this
product
Suite,
it's
it's
the
one
that
I
think
everybody's,
probably
most
familiar
with,
because
it
replaces
all
of
the
tools
we've
had
up
until
now.
B
The
the
analou
library
is
like
kind
of
the
foundation
of
all
of
this,
and
it's
also
part
of
the
warf
product
Suite.
That
is,
we
basic,
basically
rebranded,
eosio
core
the
piece
we
were
talking
about
a
little
earlier
and
now
we're
just
calling
it
analou,
because
it's
kind
of
the
core
library
for
it.
So
these
are
the
two
major
components
that
are
out
in
the
wild
at
this
point,
they're
being
used
in
production
by
a
handful
of
applications.
B
Already
some
of
the
early
adopters
have
been
just
running
with
it
and
building
it
into
their
applications,
and
then
there
are
other
components
that
exist
in
this
product.
Suite
we're
going
to
probably
talk
about
the
session
kit,
mostly
today,
which
is
the
one
that
was
released
recently
and
then
there's
also
going
to
be
the
contract
kit,
which
is
this
new
tool
that
has
never
existed
before
in
our
space
that
serves
a
completely
different
function,
functions
that
all
developers
in
the
space
are
creating
themselves.
B
This
will,
you
know,
give
them
a
toolbox
for
that
area
of
development,
that
they're
doing
right
now,
and
then
we're
going
to
have
a
number
of
other
packages
that
are
coming
out
in
this
product
Suite,
like
the
account
kit,
which
that
one
is
coming
after
after
the
contract
kit,
and
then
there
are
going
to
be
some
starter
kits
whether
they
are
for
specific
Frameworks.
So
that
way
you
know
you're,
like
I'm
a
view
developer
or
something
and
I.
B
You
could
have
a
view,
starter
kit,
that
bundles
everything
up
for
you
in
this
nice
way
to
get
started
on
a
new
project,
and
there
will
also
be
some
other
products
that
are
focused
on
specific
contracts
or
specific
protocols
like
there
will
be
an
atomic
asset
bundle
per
se
that
will
live
under
this
umbrella.
Of
the
warf
project,
so
WARF
in
itself
is
just
this
big
umbrella
that
encompasses
all
of
this
new
tooling.
That
developers
will
be
able
to
leverage
when
they're
building
applications
in
this
kind
of
modular
plug-in
approach
based
way.
A
Nice
that's
a
good
overview,
so
you've
got
the
session
kit,
the
contract
kits
coming
next
and
then
an
account
kit
and
then
some
other
other
items
that
we
don't
need
to
get
into
some
much,
but
a
session
kit
well,
first
just
rolling
back
a
little
bit.
What
sort
of
developers
are
going
to
be
able
to
use
these
tools
like?
Who
are
you
providing
these
these
tools?
For
now,
like
describe
your
target
audience,
I
guess
like
who
do
you
want
to
get
in
and
start
picking
up
these
tools.
B
It's
the
audience
is
basically
anybody
that
is
using
a
variant
of
JavaScript.
You
know
they're
building
web
applications
or
web-
based
applications
for
any
analog
blockchain.
You
know
it
could
be
EOS
or
wax
or
Telos
or
ux
any
of
these
chains.
This
will
be
compatible
with
development
around
plugins
and
then
it's
also
extensible.
So
that
way,
if
there's
other
some
other
analou
chain
in
the
future,
that
might
be
doing
something
somewhat
differently.
A
Isn't
familiar
with
blockchain,
but
they
they
have
an
inkling
that
they
want
to
use
blockchain.
Where
would
you
put
this
on
like
the
scale
of
difficulty
in
their
in
the
Journey
of
like
a
like
a
journeyman
application
developer
that
wants
to
use
blockchain?
Are
you
anticipating
that
you'll
have
some
beginners
coming
in
and
and
using
these
tools
and
trying
to
figure
out
how
to
web
apps
using
the
antelope.
B
I
think
so
I
mean
you
need
a
grasp
on
the
language
itself
in
order
to
be
able
to
use
it,
but
I
believe
that
even
some
more
Junior
developers
are
going
to
be
able
to
pick
this
up
and
make
use
of
it
and
the
way
that
a
lot
of
this
is
designed,
especially
the
session
kit,
is
to
more
align
the
blockchain
conventions
to
traditional
web
development
conventions.
That's
that's
why
it's
called
the
session
kit
is
that
sessions
are
a
common
principle
in
web
development.
B
Like
typically
it's
your
web
browser
establishing
a
session
with
some
sort
of
backend
application.
It's
just
in
this
instance.
The
black
the
back
end
is
a
blockchain
or
a
wallet,
so
we're
we're
trying
to
make
those
connections.
So
that
way,
the
developers
who
are
coming
in
you
know
if
they're
learning,
web
development
or
they're
very
versed
in
web
development.
A
B
A
A
B
A
We
are
gonna,
do
this
AMA
on
the
31st,
where
it's
basically
gonna
be
a
master
class
on
on
Warf
kit,
with
Aaron,
so
you're
going
to
want
to
keep
an
eye
out
for
that
I.
Don't
believe,
we've
posted
about
it
yet,
but
August
3
first
so
keep
an
eye
out,
and
then
we
have
a
chance
to
get
pretty
deep
into
all
these
different
territories
and
take
questions
Also.
A
B
B
So
there's
no
like
application.
A
did
a
really
good
job
at
solving
one
of
those
aspects.
Application
B
just
can't
pick
that
up
and
use
it.
The
session
kit
is
meant
to
be
that,
like
Nexus,
that
connect
and
allows
people
to
share
that
kind
of
code.
You
know
if
you
are
using
the
session
kit
and
you
build
a
plugin
that
really
helps
solve
one
of
these
problems.
B
Persp
perspective,
it's
going
to
be
a
lift
to
swap
over
and
be
able
to
move
into
this
sharable
environment
as
with
any
shift
in
technology,
but
moving
forward
as
more
and
more
people
start
using
this
and
more
and
more
people
start
sharing
their
work.
That
just
means
that
more
applications
can
leverage
that
it'll
help
establish
best
practices.
It'll
help
people
learn
how
to
do
these
things
more
effectively,
because
now
we're
isolating
those
those
things
into
packages
that
we
can
share
with
each
other.
For.
A
Sure
so
you
alluded
to
the
fact
that
developers
can
can
get
in
and
create
their
own.
They
can
add
to
session
kit.
So
session
kit
is
or
I
mean.
Sorry
Warf
kit
is,
is
free
and
open
source
software
correct
yep.
What
are
some
of
the?
Maybe
you
could
talk
a
little
bit
about
that
for
a
second
like
what
are
some
of
the
ways
you
envision
developers,
kind
of
creating
or
building
extending
this
tool
set
that
you
are
working
on
and
what
are
Maybe
some
of
the
ways
that
they
could
get
involved
now.
B
Currently,
we
can
add
more
if
we
need
them
moving
over
time,
but
currently
the
four
areas
are
wallets,
which
is
a
pretty
big
one.
That's
how
your
application
is
going
to
connect
with
an
external
wallet,
whether
that's
ankor
or
the
wax
Cloud
wallet
or
whatever
it
may
be.
Anybody
can
build
a
plugin
like
this
that
connects
to
any
wallet
essentially
so
long
as
it's
capable
of
taking
in
the
data
and
then
returning
the
data
it
needs
like
there's
a
some
architecture
there.
B
The
other
three
are
there's
one
called
the
transact
plugin
which
modifies
how
how
a
transaction
is
performed-
and
this
is
what
is
used
for
things
like
providing
resources
to
users
or
correcting
problems
with
transactions
or
ensuring
that,
like,
if
x,
happens,
y
happens.
It's
it's.
This
plug-in
approach
that
allows
flexible
abilities
to
perform
transactions,
there's
another
one
for
logging
in
which
just
basically
adds
the
capability
for
you
to
model
different
login
behaviors.
B
Maybe
when
in
your
application,
when
a
user
logs
in
maybe
you
also
need
to
connect
to
a
backin
service
like
a
a
Web
2.0,
more
centralized
service,
you
could
build
a
plugin
for
that
that
then,
during
the
login
process,
that's
built
into
the
session
kit.
It
could
then
perform
that
additional
logic
and
log
you
into
something
else
completely
unrelated
to
Warf,
and
then
the
last
one
is
actually
the
user
interface
itself
is
a
plugin.
We
published
a
user
interface
plug-in
by
default.
A
Gotcha,
so
lots
of
opportunities
for
people
to
get
in
and
play
around
with
these
plugins
and
figure
out
different
ways
to
extend
the
functionality,
which
is
cool
nice
to
have
a
little
community
that
can
kind
of
grow
around
this
set
of
tools.
So
you
don't
to
be
building
tools
by
yourself,
which
you
know,
unfortunately,
we've
been
doing
for
a
long
time,
everybody
in
there
a
little
Buble.
So
now
we
have
a
common
framework.
We
can
all
gather
around
gather
at
the
warf
look
out
over
the
water,
your
unic!
How
do
you
get
in
this?
B
B
A
A
A
B
I
really
hope
to
see
a
lot
of
development
around
plugins
and
then,
as
that
development
occurs,
that
there
are
people
identifying
areas
that
we
may
have
missed
and
maybe
contributing
back
up
to
the
core
code
base
and
being
like
hey.
We
need
this
opportunity
to
do
this
thing
and
it's
something
that,
like
during
our
work
over
the
last
couple
years,
we've
never
thought
of
so
and
then
being
able
to
come
together
and
like
figure
out
okay.
How
do
we
solve
this
for
everybody?
So
that
way
we
can
move
forward
with
that.
So
I
really
hope.
B
This
is
an
opportunity
for
the
development
Community
to
come
together
around
the
warf,
but
I
really
hope
that
we
see
a
lot
of
applications
that
adopt
this
and
then
don't
need
to
write
so
much
code
and
they're
going
to
be
able
to
faster
on
what
their
actual
vision
for
their
application
is.
That
is
why
we
started
down
this
path
going
all
the
way
back
to
steam
was
like.
B
Think
that's
going
to
determine
what
what
kind
of
looks
what
things
look
like
next
and
obviously
we
hope
other
people
are
going
to
do
that
and
collaborate,
so
I
I
think
in
telegram.
Somebody
asked
like
some
of
the
future
features
could
be
for
Warf
that
are
implemented,
and
none
of
these
are
in
scope
of
the
project
as
it
exists
now,
but
I
want
to
see
like
automatic
signing
type
procedures
which
we've
been
calling
request
for
permission.
So
that
way
you
can
authoriz
applications
to
perform
actions
on
your
behalf
or
I.
B
Guess
you
can
authorize
other
devices
so,
like
let's
say
you
are
a
ledger
user
and
you
find
this
really
cool
game
you
like
and
it
uses
Warf
the
game
using
Warf
would
be
able
to
say:
hey,
hey
external
wallet,
which,
right
now
it
happens
to
be
a
ledger.
My
game
calls
these
actions.
It
lets
people
move
their
pieces
on
the
board
or
what
you
know
whatever
the
action
is.
B
So
that
way,
you
could
do
like
inapp
Creation,
with
just
a
click
and
like
the
key,
is
generated
in
the
app
and
you
can
sign
transactions
there
and
then
maybe
you
could
walk
through
processes
to
further
secure
your
account
in
the
future.
If
it
ever
became.
You
know
like
something
worth
protecting,
so
there's
there's
a
lot
of
angles
we
could
hit
and
like
future
ways,
we
could
build
on
top
of
Warf
to
add
just
some
really
cool
functionality.
A
Yeah,
that
was
you.
You
anticipated
my
next
question
question
and
just
kept
rolling
right
into
it.
That
was
a
great
question
from
Stonehenge
in
the
Theos
Network
Foundation
chat
about
this
very
thing
that
you're
just
talking
about
being
able
to
sign
or
like
authorize
the
signing
of
transactions,
which
seems
like
a
pretty
crucial
feature
to
have
for
kind
of
having
that
web
to
experience.
There
aren't
many
people
I
know
that
want
to
use
an
application
and
approve
every
single,
a
separate
individual
transaction.
A
B
B
Yeah
I
mean
there's
going
to
need
to
be
some
collaboration
like
if
anybody
else
did
it
today,
which
I
actually
think
the
ux
team
experimented
with
a
plug-in
that
does
something
similar
to
the
but
like,
if
you
do
it
now
and
you're,
an
anchor
user
Anchor's
going
to
pop
up
with
a
big
ugly
warning.
That's
like
hey!
This
is
dangerous.
What
are
you
doing?
Yeah
so
like
doing
kind
of
a
a
community
collaborative
project
to
deliver
something
like
that?
B
I
think
is
the
right
way
to
do
it
so
that
way,
it's
something
that
works
with
all
wallets
and
all
wallets
know
how
to
not
scare
their
ferves
and
all
applications
could
use
it.
So
it's
certainly
something
that
anybody
could
build,
but
it
will
require
some
collaboration
between
lots
of
parties
to
be
able
to
pull
something
like
that
off,
so
maybe
that
it
needs
to
be
a
proposal
at
some
point.
B
A
At
the
end
of
the
day,
yeah
Warf
is
the
place
we
can
all
gather
around
and
you
any
different
chain
using
anal
based
software
and
kind
of
agree
on
the
way
that
we
go
about
about
doing
these
things
for
the
different
wallets,
then
that'll
be
killer
because
we'll
yeah
we'll
have
very
fresh
and
free
experiences
and
lots
of
lots
of
people
able
to
like
pitch
in
to
the
work
at
the
same
time.
I
think
yeah,
that's
one
of
the
Hidden
benefits
of
the
a
coalition.
A
You
know,
especially
as
we
get
out
further
into
like
the
application
layer.
You
know
because
I
know
a
lot
of
the
the
deeper
heavier
lifting
at
the
consensus
level
has
been.
You
know
only
really
possible
for
a
very
rare
class
of
human
but
I
think
with
the
sdks.
It
seems
like
this
is
a
more
access
accessible
terrain
for
a
lot
more
developers
to
to
lend
a
hand
yeah.
B
The
audience
is
much
wider
than
like
the
platform
itself
like
when
we're
talking
the
recent
developments
in
like
IBC
or
changing
consensus
like
we're
talking
about
in
leap
5.0
like
those
are
those
are
very
inaccessible
like
even
to
me
a
lot
of
that
inaccessible,
whereas
on
the
warf
side,
it's
just
this
broad
community
and
it's
more
focused
on
the
application.
Ler,
it's
it's
the
middle
ground.
It's
the
last
mile
of
delivery
of
this
so
I
know.
B
I
got
asked
recently
about
like
what
I'd
like
to
see
next
in
kind
of
the
platform
side
of
things,
and
that
was
my
answer
was
focusing
on
the
last
mile
of
the
platform
and
how
we
deliver
and
improve
user
experience
from
the
platform
itself,
in
conjunction
with
something
like
Warf,
whether
that
means
we're
making
the
permission
system
better
or
we're
making
the
apis.
That
leap
provides
better
and
just
finding
ways
to
increase
the
interoperability
between
those
two
things.
A
Yeah
seems
like
yeah
War
opens
up
a
lot
of
collaboration
between
the
layers
or
potential
for
opportunity,
for
you
know
adjusting
the
different
layers.
Gosh
I
had
another
question:
I
guess:
I'll
I'll
I'll
come
back
to
that
when
it
returns
to
my
brain.
What
what
advice
would
you
give
to
new
Builders
just
getting
started
in
the
ecosystem
like
where
it's
at
Now
versus,
where
we
see
it
being
what's
a
good
place
to
for
people
to
start
I.
B
One
of
them,
in
my
opinion,
is
and
I'm
obviously
biased,
but
it's
more
a
matter
of
like
one
of
them
is
we're
actively
pushing
forward
on
and
when
you're
evaluating
that
stuff.
Are
you
going
to
look
at
the
sdks
that
haven't
been
touched
in
four
years
or
whatever
it's
been
or
do
you
want
something?
That's
actively
being
developed
right
now
that
you'll
be
able
to
leverage
and
use
it
like
moving
forward
and
joining
this
community
of
people
that
working
on
it.
I
can
say
that
from
our
team's
perspective
like
this
is
the
direction
we're
going.
A
B
A
B
A
These
new
tools
that
are
available
and
with
Warf
kit
and
I
know
that
Nathan
James
and
crew
from
the
developer
relations
team
at
the
enf
recently
well
released
the
web
IDE,
and
that's
so
going
to
enable
folks
to
kind
of
not
have
to
set
up
their
whole
development
environment
to
like
start
playing
around
with
smart
contracts,
ostensively
other
Antelope
chains,
I
guess
I,
haven't
thought
about
it,
much
how
generic
it
is
in
that
case.
But
how
do
you
foresee
the
web
IDE
and
kind
of
synergizing
with
each
other
or
what's
what's
the
potential
there.
B
I
think
if
the
like
right
now,
I
I
am
not
one
that
does
much
if
any
smart
contract
development,
so
I
haven't
used
the
ID
the
web
ID
too
much,
but
I
do
think
that
there's
a
potential
for
the
web
ID
de
to
also
offer
the
other
side
of
development
really
as
a
application
developer.
You
have
two
sides
in
traditional
web
development.
You
have
front-end
development
and
backend
development
in
analou,
World
and
Other
blockchain
development.
You
have
front-end
development
and
then
smart
contract
development,
maybe
there's
a
better
term
for
it.
B
But
the
smart
contract
is
your
backend
and
right
now
the
IDE
is
only
for
that
backend
development,
but
it
could
be
expanded
into
also
doing
front-end
development
and
be
this
like
cohesive
environment,
which
you
could
build.
Both
your
smart
contract
and
the
like
the
user
interface
to
interact
with
it
and
I
think
that
there's
some
really
powerful
opportunities
for
the
contract
kit,
specifically
to
integrate
into
the
the
IDE
environment,
to
really
help
set
you
up
and
get
you
moving
cool.
A
That's
something
to
look
forward
to
I
think
that's
a
really
interesting
area
of
collaboration
and
it
bring
those
two
two
hemispheres
into
vment
together,
yeah.
So,
let's
see
here,
how
can
can
folks
learn
more
about?
Let's
not
save
this
to
the
very
last
like
how
can
folks
learn
more
about
greymass
and
support
your
work
in
the
ecosystem?
That's
an
excellent
question.
B
I
mean
our
website:
grey
mass.com
is
our
primary
facing
area
like
it
kind
of
it's
a
really
broad
overview
of
what
we
do.
If
you're
more
technically
oriented
you
can
check
out
GitHub,
that's
where
all
the
action
happens.
We've
got
I
mean
over
the
past
five
years
or
so
now
we're
between
both
the
gr
Mass
organization
and
GitHub
and
the
wor
kit
organization,
there's
hundreds
of
GitHub
repositories
between
those
two,
both
with
examples
and
usable
software
and
a
number
of
other
things.
B
It's
obviously
kind
of
like
a
kitchen,
a
catchall
kitchen
drawer,
with
all
everything
in
it,
but
in
terms
of
support
we
have
GitHub
sponsors
set
up.
Obviously
you
can
vote
for
Block
producers
or
it's
just
just
a
matter
of
like
I,
think
the
most
valuable
thing
right
now
is
and
using
these
tools
and
communicating
to
help
us
make
a
better
product.
B
There
may
be
additional
opportunities
in
the
future
to
support
us,
but
as
it
stands
right
now
like
we
are
100%
on
Warf,
at
least
for
the
next
two
months
or
so,
and
financially,
that's
being
sponsored
by
the
Coalition.
So
anything
on
top
of
that
is
obviously
welcome,
but
right
now
it's
it's
the
feedback
back.
It's
like
use,
use
these
things
and
be
critical
like
let
us
know
what
needs
to
be
changed:
cool.
A
I,
don't
think
I'll
be
able
to
to
help
out
with
that
maybe
I,
maybe
I'll,
try
someday
just
to
humble
myself
to
sit
on
the
warf
and
stare
off
at
the
vastness
of
the
the
ocean.
I'm
curious
like
in
the
past.
We
talked
about
this.
This
thing
called
code
golf
you
still
doing
code
Golf
and
is
that
still
happening
like
in
the
what's
your
code
golf
score
like
these
days.
B
We
we
did
that
really
early
on
and
B,
we
had
a
whole
GitHub
repository
for
it.
There
wasn't
too
much
engagement,
so
I,
don't
know
that
we
engaged
publicly
too
much
on
it.
So
it's
been
stagnant
for
a
couple
months,
but
that
was
really
methods
to
experiment
with
how
how
to
write
code
really
like
how
best
to
write
code.
We
still
do
that.
It
just
happens.
B
A
lot
in
poll
requests
now
on
GitHub,
so
I
mean
if,
if
you
want
to
participate
and
provide
feedback
in
that
regard,
guard
it
rather
technical,
but
you
can
kind
of
watch
the
poll
requests
as
they
come
through
and
follow
them
and
provide
feedback.
That's
essentially
what
the
code
golf
was,
it's
just.
We
were
doing
it
in
this
golf
format,
because
we
didn't
have
GitHub
repositories
to
begin
with,
like
there
was
no
code
base
to
play
with
it
was.
It
was
like
our
sandbox
before
the
code
existed,
so
that
process
still
happens.
A
B
Nice,
where
it's
like
here's
something
you
need
to
make,
you
need
to
make
something
that
does
this
and
there
will
be
like
an
objective
and
the
goal
is
in
traditional
code.
Golf
is
to
accomplish
that
goal
in
the
least
amount
of
characters
possible.
So
that's
where
the
term
golf
comes
from,
is
you
know
you're
trying
to
hit
it
at
the
hole
in
the
least
swings
possible
and
code
golf,
it's
the
least,
characters
possible,
so
yeah,
and
just
this
programmer
thing.
B
A
That's
great,
though
I
mean
I,
don't
know
like
as
a
non-developer
I
I
find
that
sort
of
thing
totally
fascinating,
like
I,
would
I
would
love
just
watching
the
process.
I
think
even
if
I
could
barely
understand
what
the
heck
was
happening.
It's
like
I,
don't
know
there
there's
some
analogy
there
that
I
can't
quite
pull
out
of
my
brain,
but.
B
A
B
Yeah,
it
definitely
and
I
guess,
jumping
back
one
point:
when
we
were
talking
about
supporting
and
using
the
product
like,
we
were
trying
to
make
the
warf
kit.com
website
a
hub
of
information
like
on
how
you
would
do
that.
There's
a
couple
guides
there
right
now
we're
still
working
on
more
there.
The
documentation
just
got
updated
a
couple
days
ago,
like
the
session
kit
documentation
like
a
rough
version
of
it,
got
published
that
dives
into
how
to
use
all
the
different
components.
B
What
the
plugins
do,
what
methods
you
can
perform
on
it,
that's
all
hosted
it's
all
open
source
on
GitHub.
The
documentation
is
it's
kind
of
like
a
Wiki,
so
either
like
you're,
welcome
to
contribute
through
pull
requests
or,
if
you
read
something
and
you're
like
I,
don't
understand
how
this
works
still,
even
though
you've
written
a
page
documentation
like
that's
valuable
feedback
to
us.
So
that
way
we
can
help
or
inform
people
as
they're
learning
how
to
use
all
this
stuff.
B
So
not
only
trying
the
code
but
like
feedback
on
the
documentation
would
definitely
be
welcome
as
well
well
and
that
Warf
kit.com
website
is
really
where
we're
focusing
to
like.
If
somebody
you
know,
or
you
want
to
get
started
doing
this
JavaScript
type
development
that
should
be
the
de
facto
like
landing
page
for
it.
There's
no
I
say
this:
there's
no
incentive
for
us
to
to
like
do
that.
It's
not
like
we're
collecting
information
or
selling
or
doing
anything
there.
A
Well,
I
think
you,
you
all
have
done
a
really
great
job
with
with
branding
you're
you're
way
ahead
of
the
curve
in
at
least
our
neck
of
the
woods
in
this
industry.
So
Warf
kit.com
is
a
very
a
welcome
addition
to
the
to
the
landscape
here
so
I'm,
just
going
to
say,
Warf
kid.com
a
few
more
times,
people.
B
A
Go
to
Warf
kid.com
if
they're
interested
in
learning
more
about
Warf
kit.com,
because
it's
the
place
the
place.
That
is
the
place
to
start
your
journey
and
it's
free
and
open
source
software.
So
that's
pretty
rad.
Anyone
can
take
it
and
play
with
it
and
build
it.
There's
there.
The
only
limit
is
your
your
courage
and
your
imagination.
B
Yeah
it's,
it
is
really
something
that
you
have
to
bring
your
own
idea
to.
You
know
which
I
think
is
a
it's.
The
reason
a
lot
of
us
are
here
is
we
all
have
our
own
ideas
about
what
we
want
to
see
exist
and
that's
what
this
is
for.
This
tool
isn't
going
to
build
your
app
for
you,
but
it
will
certainly
help
you
build
your
app.
You
know
gets
out
of
the
way
and
lets
you
do
your
thing
and
that's
warp.
A
Kid.Com
right,
yes,
it
is
hey.
Speaking
of
cool
ideas.
You
mentioned
you
wanted
the
dog
food,
some
warp
kit
yourself.
When
the
time
comes,
what
do
you
give
us
any
hints
like?
What
are
you?
What
are
you
kind
of
intrigued
by
I
heard?
You
mention
one
possible
thing
that
used
to
Fascinate
you
the
other
day
but
curious.
What
you'll
say
today
considering.
B
So
that
way
we
move
Unico
from
being
just
anchor
exclusive
to
being
any
wallet,
and
we
still
have
like
desires
and
dreams
for
building
that
platform
out
a
little
bit
just
to
kind
of
act
as
the
hub
for
analou
networks
like
if
you
need
to
do
something
generic
on
the
network,
that's
where
you
can
go
to
do
it
and
then
using
that
as
like
a
springboard
to
push
people
into
other
apps
that
do
more
specific
things
so
I
mean
I,
know,
that's
one!
That's
there!
B
Our
team
is
very
much
talking
right
now
about
what
we
want
to
build
with
it.
It
ranges
from
games
to
social
app
to
productivity
things
to
marketplaces
to
it's
kind
of
all
over
the
place
in
terms
of
ideas
right
now.
It's
because
we're
just
brainstorming,
so
yeah
I,
don't
I
me
personally,
I,
I,
love,
video
games
and
I
would
love
to
build
a
video
game
with
it.
But
I
don't
know
if
that's
the
direction,
we're
going
and
there's
still
so
much
more
tooling
to
build
by
maybe
it's
time
to
time
to
build
an
app.
A
B
A
Man,
Victory
is
going
to
be
very
sweet
for
you,
Aaron
I,
hope
so
I
I
I
believe
so
yeah
games
I'm
prone
to
thinking
about
games
a
lot
and,
like
you
know
in
my
non,
my
non
Dev
way:
I'm
free
to
imagine
all
sorts
of
preposterous
things
without
having
to
think
about
the
consequences
of
my
my
my
dreaming,
which
is
you
know
in
some
ways
like
a
super
power,
because
a
lot
of
developers
would
go.
Oh
my
God!
No,
you
know
this
I
don't
want
to
even
go
near
that
idea,
but
I'm
wondering
like.
A
Is
there
like
a
super
simple
I
mean
what
is
the
simplest
possible
game
like
iteration?
You
can
imagine
for
like
I
guess
like
what
are
the
components
like
say
like
somebody
comes
along
and
they're
like
game
developer
and
they're
like
all
right,
I
need.
You
know
all
the
pieces
of
the
puzzle.
I
just
want
like
to
move
a
ball
around
a
screen.
You
know
I
need
the
the
web
app
the
smart
contract
like.
Is
there
like
a
way
to
create
like
a
game
kind
of
toolkit
in
and
of
itself?
B
Potentially,
though
it
would
I,
don't
know
how
opinionated
it
would
I
don't
know
when
you
were
just
talking
about
your
superpower.
I
was
like
my
superpower
is
pooking
holes
and
I,
like
figuring
out,
why
they
wouldn't
work
so
immediately.
I'm,
just
like
I,
don't
know
about
this
and
that
so
yeah
I
don't
know
how
that
would
work.
But
it's
certainly.
A
Possible
their
games
are
just
super
hard.
I
was
teing
a
g
idea
to
somebody
the
day
they're
like
yeah.
That's
like
that's,
that's
a
fun
idea,
but
that's
a
lot.
That's
more
than
you
know.
You
want
to
get
into
I.
Think
people
don't
appreciate.
Yeah,
myself
included,
don't
appreciate
just
how
much
work
goes
into
building
stuff
like
that.
So.
A
B
A
Yeah,
so
speaking
of
getting
super
deep
once
again,
the
upcoming
scheduled
for
August
31st
we're
going
to
go
a
lot
deeper
into
the
the
code
side
of
things.
If
you're
a
developer
and
you
want
to
get
your
hands
dirty,
you
can
come
scope
out.
The
webinar
keep
your
eyes
peeled
on
enf
social
channels,
I
presume
on
Grey,
mass
and
other
places.
You'll
find
mention
of
this
upcoming
webinar.
So
sign
up
for
that.
A
When
you
see
it
and
Aon
will
be
there
to
answer
all
your
difficult
questions,
you
might
have
to
bring
some
some
backup
with
you,
so
you
don't
just
get
parched
right
exactly
and
yeah
keep
an
that
on
EF
socials
for
this
and
other
future
spaces.
You
can
always
talk
to
Aron
that
heos
fireside
chat
you're,
usually
there
every
week
pretty
much
without
fail.
I
must
say,
and.
B
A
Work:
cool
yeah:
it's
a
good
good
time
to
do
that
sort
of
thing.
Well,
thanks
everybody
for
tuning
in
and
thanks
for
Aon,
for
giving
us
an
hour
plus
of
your
time
to
tease
us
about
how
awesome
Warf
kit
is
going
to
make
our
ecosystem.
How
easy
it
is
to
build
or
how
easy
it
will
be
to
build
and
yeah
what
was
that
address
again:
Warf
kit.com,
absolutely
okay,
cool
Warf
kit.com,
then,
is
the
place
check
out.
A
If
you
want
more
information,
we'll
see
you
next
time,
we'll
see
you
on
the
webinar
and
between
now
and
then
I'm,
probably
in
multiple
other
places,
so
thanks
for
being
here,
absolutely
feel
free
to
reach
out
I'm,
pretty
easy
to
get
a
hold
of.
You
are,
and
thank
you
for
that
this
community
is,
is
rich
in
that
way,
it's
we've
got
a
lot.
I
think
you
made
a
comment
to
that
effect.
The
other
day
like
we're.