►
Description
Aaron Cox of Greymass joins hosts Zack Gall and Brandon Lovejoy of the ENF to unpack the details and significance of Wharf, Antelope’s New Web Client SDK Project. The conversation ranges from the history of the Wallet+ Blue Paper to the future of application development on Antelope and the impact on user experience.
Note: This podcast was recorded before the name-brand "Wharf", Antelope’s New Web Client SDK Project was revealed.
Introducing Wharf, Antelope’s New Web Client SDK Project
https://greymass.medium.com/a98fb12ff51f
Get in touch with Greymass:
https://twitter.com/greymass
hello@greymass.com
Greymass Support
https://support.greymass.com/support/home
Timestamps:
00:00:00 Intro
00:02:10 Greymass projects and priorities
00:05:20 Web Client SDKs: what are they, why do they matter?
00:08:53 History of Wallet+ Blue Paper, Antelope Coaliton, SDK funding through milestone based grants, reflections on the grant process.
00:14:21 Venturing into the unknown with SDKs
00:16:47 Escaping from abstract data types with an open, modular toolkit
00:20:10 Other value-adds from the Web SDKs
00:22:37 IBC, good UX, multi-chain login, Anchor wallet
00:29:33 Fuel, PowerUp, Abstracting away resource costs + resource cost on IBC
00:37:50 User experience
00:41:15 Branding SDKs
00:46:17 Near term development and availability of Wharf
00:49:30 Code Golf with Greymass
00:53:37 Ledger update
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 #EOSIO #Web3
A
No
longer
are
you,
like,
oh
gotta,
create
a
new
tab
and
leave
my
game
and
I
gotta
go
to
blocks
or
I
gotta,
go
to
whatever
application
and
then
figure
out
how
much
to
power
up
and
do
that
transaction.
Then
close
the
tab
and
come
back
to
my
game
like
that,
is
a
huge
distraction
in
the
user
experience
that
the
sdks
are
going
to
help
solve.
B
This
is
the
everything
EOS
podcast
I'm
Zach
go
and
I'm
joined
today
by
my
co-host
Brandon
Lovejoy,
and
we
are
here
with
our
esteemed
guest
of
the
hour.
Aaron
Cox
Aaron
is
the
founder
of
gray
Mass,
a
top
21
EOS
block
producer,
as
well
as
a
block
producer
on
many
other
Antelope
networks.
He
is
the
builder
of
the
anchor
wallet
in
EOS
Foundation
board
member,
the
very
first
Eden
head,
Chief
delegate,
co-host
of
the
coffee
with
gray
Mass
podcast,
author
of
the
wallet
plus
blue
paper
product
lead
for
today's
topic.
B
A
B
List
continues
to
grow
so
Brandon
and
I
had
a
conversation
with
you
a
couple
of
months
ago
about
a
very
similar
topic
actually
and
I
had
the
show
notes,
I
copy
and
pasted
of
like
your
resume,
essentially
of
things,
you've
done
within
the
EOS
and
antonovico
systems
and
honestly,
since
the
last
time,
it's
continued
to
grow
and
it
will
continue
to
grow
moving
forward.
I
think
but
really
appreciate
your
time.
C
C
That'd
be
appropriate,
I
think
so.
Yeah
I
mean
let's
talk
a
little
bit
about
what
you're
up
to
these
days,
I
mean
outside
of
sdks,
which
we
know
we're
gonna
dive
into
pretty
deeply
here.
What
are
you
up
to?
What
are
the
different
projects
and
priorities
that
you
and
gray
Mass
are
currently
working
on.
A
I
mean
at
a
really
high
level,
aside
from
sdks
those
take
up,
I'd,
say
about
50
of
our
time
right
now,
maybe
a
little
bit
more
various
person
to
person
there's
a
lot
of
focus
on
anchors
like
a
product
around
it,
whether
that's
website
and
support
and
like
I,
how
we
encapsulated
into
just
a
better
experience
for
users.
That's
not
always
about
improving
the
app
itself.
Sometimes
it's
about
building
all
the
stuff
around
it.
So
there's
a
lot
of
work
going
into
that
side
and
brainstorming
on
how
we
make
all
that
better.
A
We
are
doing
a
lot
of
cross
training
internally
right
now
like
right
before
this
call.
I
was
on
one
where
we
were
doing
cross-training
on
infrastructure,
and
we
were
talking
about
how
to
set
up
history
apis
and
how
to
maintain
them
and
how
like
they're,
configured
and
whatnot
and
aside
from
like
those
are
the
big
ones.
Unicove
I
guess
has
been
still
a
fairly
big
part
of
what
we're
doing
the
development
on
that.
We've
got
some
stuff
going
on.
A
C
A
No
I
mean
it's
just
like
with
the
sdks
that
we
started
years
ago
to
work
in
the
website
of
antelope
blockchains.
We
really
kind
of
take
our
time
at
the
beginning
of
a
project
and
do
the
building
blocks,
which
are
really
not
noticeable
from
like
a
user
perspective,
but
it
sets
us
up
so
that
way
we
can
really
just
start
running
once
we
hit
a
certain
point
where
the
foundation
is
stable,
so
we're
kind
of
doing
that
with
Unicode
right
now.
C
B
A
A
Year
I
think
four
we
had
some
like:
we've
lost
some
and
gained
some,
but
I
think
there
are
four
new
people
as
of
this
year
that
are
still
here
so
very
nice
yeah,
so
almost
doubling
over
the
course
of
this
year
and
we're
still
kind
of
recruiting
at
this
point,
we've
got
outstanding
spots
for
some
project
management
type
stuff,
we're
looking
for
very
specific
kinds
of
developers
to
come
in.
Our
medium
blog
I
believe
has
some
of
the
posts
that
talk
about
this
and
that's
at
graymass.medium.com.
C
A
Think
web
sdks
is
probably
the
best
way
to
to
describe
them.
These
are
eventually
going
to
have
a
name
like
leap
is
an
example.
We
have
leap
which
is
the
C
plus
implementation
of
kind
of
the
protocol.
The
sdks
are
going
to
have
their
own
name
as
well,
but
right
now
they
are
just
the
web
client
sdks,
because
that
is
I
think
the
most
concise
accurate
description
of
what
they
are.
A
They
are
a
series
of
tools
that
let
web
developers
build
things
that
interact
with
analog-based
blockchains,
whether
it's
kind
of
a
server-side
thing
that
runs
in
the
background
like
a
bot
or
a
script
or
whatever.
If
it's
using
webtech
it'll
be
able
to
use
these
sdks
and
then
anything
in
the
web.
Browser
will
also
be
able
to
leverage
these
sdks
to
build
user
experiences.
A
B
A
I
think
in
the
wallet
plus
paper,
when
we
first
started
talking
about
this
idea,
we
cited
a
couple
other
examples,
something
like
hard
hat,
which
is
an
ethereum,
SDK
and
I
believe
that
one
specifically
for
building
contracts,
but
it
is
it's
in
a
similar
vein
in
terms
of
being
named
like
that,
there's
one
called
Morales,
which
is
also
an
ethereum.
It's
a
bigger
Suite
that
lets
you
build
applications
with
it
within
these
ecosystems.
A
They
have
kind
of
these
named
things
that
a
lot
of
people
will
associate
with
being
able
to
build
a
specific
kind
of
thing,
even
I.
Think
probably
the
best
analogy
is
stepping
outside
of
crypto
and
just
thinking
about
the
web
and
web
development.
People
know
what
react
is
if
you
have
any
familiarity
with
like
web
development.
React
is
a
branded
SDK
for
web
development.
This
is
something
that
developers
will
put
on
their
resumes
things
that
employers
will
cite
as
a
technology
that
they
want
people
to
be
able
to
use.
A
These
are
all
just
sdks
that
really
help
accelerate
the
development
of
applications
on
the
web.
So
that's
kind
of
the
goal
with
these
web
client
sdks
is
to
give
them
that
name
recognition
so
that
way
within
the
space
you
know
like
if
I'm
looking
for
a
web
developer-
I
can
say
you
know-
have
experience
with
this
SDK,
because
if
you
have
experience
with
that,
SDK
you're
going
to
be
a
lot
more
familiar
with
the
tech
stack
than
me.
A
Just
saying
know
these
programming
languages,
like
the
sdks
kind
of
introduce
the
concepts
to
you
without
you
having
to
write
all
the
code
for
that.
It's
your
Lego
box,
with
all
your
cool
toys
that
you
know
your
employer
can
say,
build
me
a
castle
out
of
this
box
of
Legos
and
you'd
be
able
to.
If
they
just
said,
build
me
a
castle
and
didn't
give
you
any
Legos,
then
you'd
be
like
well.
What
do
I
use
so
kind
of
a
bad
analogy
on
the
spot,
but
that
that's
what
we're
really
going
for
with
this
project?
B
So
you
described
what
we
needed
and
put
out
a
rough
proposal
at
the
time
in
the
wallet
plus
blue
paper,
and
then
right,
as
the
wallet
plus
blue
paper
was
being
published,
is
right
around
the
same
time
that
the
antelope
Coalition
kind
of
came
together
and
started
becoming
a
formidable
thing.
So
at
that
time,
I
believe,
like
a
lot
of
these
bigger
initiatives
that
are
kind
of
cross
chain
functional
as
far
as
being
something
useful
to
all
of
the
different
envelope
chains.
B
One
other
step
was
that
last
April
April
8th
I
believe
was
whenever
the
antelope
Coalition
announced
eight
million
dollars
of
funding
commitment
for
the
next
year
and
at
that
time
all
of
the
chains
made
a
two
million
dollar
commitment
in
U.S
tether
EOS
was
like
73
of
it,
then
the
other
three
chains
kind
of
made
up
the
rest
and
that
account
mostly
sat
untouched
for
a
very
long
time.
The
tether
sitting
in
that
account,
because
we've
had
other
proposals
that
were
funded
so
instant,
finality
and
interblock
chain
Communications.
B
Those
were
very
large
proposals
over
three
million
dollars,
a
milestone-based
grant
funding
for
those,
but
they
were
all
paid
in
EOS,
wax
Talos
and
ux
tokens,
because
they're
going
to
bootstrap
some
liquidity
for
something
else
with
that.
So
this
tether
just
sat
there
for
a
very
long
time
and
it
was
very
nice
to
see
it
finally
started
moving
around
recently
because
I
said
at
the
beginning
of
this
call:
1.3
million
dollar
grant
for
gray,
mass
and
I.
Think
it's
important
to
kind
of
make.
B
A
The
time
the
blue
paper
is
finished
in
like
March
or
April,
whenever
those
were
finished
and
published
up
until
maybe
August
or
September,
there
was
the
Coalition
forming
and
there
was
a
lot
of
back
and
forth.
We
were
kind
of
one
of
the
guinea
pigs
for
how
does
this
process
work
to
be
able
to
do
rfps
and
assign
grants,
and
whatever
so
from?
A
Think
two
weeks,
maybe
three
weeks,
total
I
would
have
to
look
to
know
the
exact
number,
but
the
title
of
it
was
just
architecture,
and
the
goal
of
that
was
for
our
team
to
sit
down,
collect
everything.
We
had
been
doing
basically
over
the
past
year
of
talking
about
this
idea
and
presenting
and
everything
like
that
and
come
up
with
an
architecture
document
of
how
we
plan
on
kind
of
attacking
this
project
and
what
the
end
result
of
this
project
will
look
like
to
that
end.
A
We
decided
that
this
is
going
to
be
a
living
document,
so
that
kind
of
messed
with
the
Milestones
a
little
bit.
But
what
we
came
to
an
agreement
with
the
Coalition
was
that
revision.
One
of
this
living
document
would
be
the
completion
of
this
first
milestone.
So
we
submitted
this
document.
We
had
some
calls
about
this
document.
A
We
talked
with
a
number
of
application
developers
in
the
Antelope
community
and
validated
that,
like
this
architecture
that
we're
going
to
follow,
there's
like
no
objections
to
it,
there's
no
major
problems
with
it
and
that
this
is
a
solid
path
forward.
So
we
finished
that
and
we
had
a
meeting
it
was
approved
and
then
that
first
Milestone
was
marked
as
complete
and
that's
what
earlier
this
week
actually
released
the
first
Milestone
payment,
which
was
paid
to
our
account
tether.
So
now
we
have
I.
A
Don't
know
three
percent
of
the
total
budget
paid
out
for
this
overall
project,
so
we're
kind
of
working
towards
each
Milestone
reporting
and
then
once
external
parties
say
yes,
this
is
an
acceptable
completion
of
this
Milestone.
Then
we
get
retroactively
paid
for
that
work,
so
that's
kind
of
how
the
system
works.
C
So
yeah
you're
kind
of
in
Uncharted
Territory
here
with
the
sdks
and
seemingly
this
is
not
really
been
attempted
on
EOS.
Yet,
what's
that
like?
Why
is
that
and
like?
How
do
you
see
the
the
path
forward?
Through
all
this
I
mean
I
know
we
have
Milestones
to
kind
of
guide
you
along
the
way,
but
it
wasn't
easy
to
get
there
even
and
yeah
yeah.
It's.
A
I
I
think
it
wasn't
easy
to
get
here,
but
it's
probably
been
worth
it,
because
we've
kind
of
set
a
path
forward
for
other,
potentially
larger
projects
to
follow
this.
It
hasn't
I,
don't
think
been
done
before
in
our
space
I'm,
not
sure
how
comparable
it
would
be
to
other
projects
and
other
ecosystems
that
are
crypto,
related,
I'm
sure
there's
some
similarities,
but
I
can't
give
a
great
example
of
something
that's
kind
of
unique
to
this
network
story.
A
A
That
was
like
something
that
hadn't
been
done
before
and
while
what
we
had
built
was
super
crude,
it
like
just
kind
of
venturing
into
the
unknown
and
trying
it
gave
us
a
lot
of
knowledge
about
okay,
what
worked
and
what
didn't
and
really
we're
kind
of
leaning
on
all
of
that
experience
to
help
us
wander
into
this.
This
kind
of
Blue,
Sky
project
I,
think,
is
what
I
have
been
calling
it.
A
It's
just
you've
got
emptiness
in
front
of
you
and
you
could
go
whichever
direction
you
wanted
with
it,
but
which
way
is
the
best
and
that
prior
knowledge
will
hopefully
help
keep
us
on
track,
along
with
the
Milestones
that
we've
laid
out
that
were
largely
created
on
that
past
experience,
but
yeah
I'm
sure
we're
going
to
run
into
some
sort
of
snag
along
the
way
and
have
to
Pivot
and
probably
Panic
a
little
bit,
but
we'll
figure
it
out.
I.
C
Just
wanted
to
say
real,
quick
I,
don't
know
quick
it'll
be
your
answer,
but
you
know
for
for
people
that,
like
myself,
also
that
don't
really
appreciate
so
far,
we've
been
that
the
conversation
has
been
very
abstract
about
sdks,
and
that
is
part
of
the
problem
that
they
address.
Is
that
the
way
that
developers
now
interact
with
the
blockchain
is
very
abstract,
and
what
sdks,
if
I
understand
this
correctly
are
attempting
to
do,
is
to
give
them
some
sort
of
concrete
things
to
hang
on
to
in
this
abyss
of
like
potential
right
now.
C
A
So
the
that
library
is
something
that
we
started.
It's
called
the
Osio
core
still
right
now
we
think
we're
just
going
to
rename
it
to
Antelope
or
something
it
just
hasn't
happened
yet
when
it
gets
merged
into
this
new
SDK
project
in
some
form,
that's
like
a
perfect
opportunity
to
rename
it
so
when
that
event
happens,
we're
going
to
rename
it
but
yeah.
We
started
that
a
long
time
ago,
because
what
we
had
for
sdks
in
the
ecosystem
was
It
was
kind
of
top
down
it.
A
It
would
give
you
a
machine
effectively
that
you'd,
like
you,
would
input
a
piece
of
paper
in
and
then
Inside
the
Box.
It
would
do
a
bunch
of
things
and
then
give
you
something
back
out
like
maybe
it
gave
you
a
dis
like
it
copied
the
paper
or
something,
but
you
really
had
no
idea
what
was
going
inside
the
machine
and
you
couldn't
open
the
machine
so
like
that's
how
the
sdks
that
we
have
had
have
worked.
The
insides
were
just
kind
of
unknown
jumbled
mess
and
you
couldn't
access
it.
A
So
what
we
did
when
we
started
eosio
core
was
to
take
and
build
every
individual
piece
that
goes
inside
the
machine
and
just
not
assemble
the
machine.
It
was
kind
of
an
ikea-like
thing
where,
when
you
install
eosio
core
into
your
program,
we
gave
you
like
this
toolbox
that
just
had
a
bunch
of
parts
in
it,
and
it
was
like
here
figure
out
how
to
assemble
it.
That's
the
core
component,
it's
those
abstract
data
types
I
could
ramble
through
some
but
they're
kind
of
irrelevant.
A
This
next
part
of
the
SDK
project,
we're
doing
is,
is
we're.
We're
like
giving
you
pre-made
machines
based
on
all
of
those
parts,
so
you'll
be
able
to
use
that
machine
immediately.
But
you
can
also
like
look
at
the
machine
and
see
how
all
the
parts
are
hooked
together,
and
then
you
also
have
that
toolbox
with
all
the
parts
where
you
could
like
build
it
yourself.
A
That
is
kind
of
a
design
philosophy
that
we
have
followed
since
the
beginning
is,
and
it's
really
made
us
kind
of
slow
to
be
honest,
is
to
build
all
the
parts
and
to
build
like
from
the
bottom
up.
So
that
way,
it's
not
just
us
that
gives
you
a
black
box.
In
the
end,
that's
like
here,
you
go.
Here's
run
this
thing.
We
always
give
you
all
of
the
parts
to
build
the
things.
So
that
way,
when
you
want
to
build
something
different,
you
can.
B
Another
value
add
to
the
sdks,
is
there's
a
lot
of
different
ways
to
solve
a
variety
of
different
problems
and
every
dap
up
until
now
has
been
doing
it
on
their
own
in
their
own
way.
The
way
that
they
believe
is
best,
but
there
hasn't
been
any
standards
across
the
entire
ecosystem
so
that,
if
I'm
building
an
nft
Marketplace
like
I,
should
just
focus
on
what
an
nft
Marketplace
is
and
whatever
my
business
model
is
around,
that
I
shouldn't
need
to
worry
about
resources
or
how
to
integrate
different
wallets.
B
A
Those
are
good
examples.
Ibc
transactions
are
going
to
be
a
new
one
that
nobody's
having
to
do
yet
unless
you're
playing
with
IBC
on
the
test,
Nets
that
it
exists
on
right
now,
but
once
developers
start
wanting
to
do
that,
we're
going
to
enter
the
same
situation
where
everybody
will
be
Reinventing
the
wheel
in
their
own
application.
The
sdks
once
released,
will
be
able
to
give
you
one
of
those
kind
of
pre-formed
machines.
A
That
is
the
IBC
machine
and
you'll
just
be
able
to
use
that
in
your
application
to
then
perform
like
I'm
doing
a
token
transfer
on
EOS
and
I
want
to
prove
it
on
wax.
You
know,
that'll
just
be
a
thing
that
applications
can
do
without
having
to
invent
that
wheel.
Like
you
mentioned,
wallets,
there's
the
account
creation
part
of
it.
A
C
B
You
brought
up
IBC
and
it
wasn't
a
topic.
I
had
planned
to
talk
about
it,
brought
up
a
discussion.
I
remember
when
the
RFP
for
IBC
was
getting
finalized
by
geom
and
the
origin
team,
and
you
took
your
I
guess
one
of
your
first
Peaks
at
how
this
thing
was
going
to
work,
and
you
saw
the
complications
with
signing
on
two
different
chains
and
it
was.
It
was
like
a
light
bulb
moment
for
me
of
like
wow.
B
This
is
how
things
should
be
done,
because
previously
and
probably
in
other
ecosystems
as
well,
people
are
working
in
these
isolated
sandboxes
and
they
don't
make
all
of
the
different
considerations,
but
because
of
this
collaborative
nature
of
the
antelope
ecosystem
and
even
EOS
itself,
you
kind
of
looked
at
this
IBC
and
you
saw
a
pain
point
right
away
like
whoa
whoa
whoa.
This
is
going
to
be
super
super
complicated
for
the
user.
Experience
and
origin
wasn't
really
thinking
about
that
they're.
B
Just
thinking
of
how
to
get
these
like
Miracle
proofs,
they
all
make
sense
and
some
some
really
hardcore
Tech
underneath,
but
you
were
looking
at
it
from
the
user
experience
perspective.
Can
you
kind
of
share
that
story
from
your
perspective,
because
it
was
quite
interesting
to
me
watching
it
play
out.
A
What
is
this
step
doing
and
what
is
this
doing
and
trying
to
figure
out
how
we
could
reduce
that
from
the
end
user's
perspective
instead
of
two
logins?
Maybe
there's
a
protocol
that
allows
you
to
log
into
multiple
blockchains
at
the
same
time
like
that
could
be
a
thing.
That's
not
part
of
the
SD
case
right
now,
but
if
it
becomes
a
standard
it
could
be
adopted
by
the
sdks.
A
The
sdks
will
be
flexible
enough
to
handle
it.
It
was
also
interesting
because
we've
got
into
the
two
transactions,
and
the
first
transaction
is
just
it's
you
doing
something
on
the
origin
chain,
and
the
second
transaction
is
the
proof
that
you
did
something
on
the
other
chain
to
the
like
second
blockchain,
and
what
we
discussed
in
that
conversation
is
is
that
the
user
might
not
actually
have
to
be
the
one
that
has
to
sign
that
transaction
like
anybody
could
prove
that
this
action
on
chain
a
happened
on
chain
B.
A
So
then,
not
only
are
we
like
okay,
we
can
do
that
in
the
sdks,
but
we
could
do
that
in
like
Fuel
and
have
so
the
user
doesn't
even
see
the
second
transaction
like
fuel
in
the
background,
might
just
create
that
transaction
sign
it
and
do
it
either
for
free
or
for
a
fee
and
like,
let's
just
completely
make
the
user
experience.
You
know
that
much
better,
so
that's
that's
our
lens
into
a
lot
of
this
stuff
right
now.
Is
this
like?
How
many
times
is
the
user
clicking?
How
much
do
they
have
to
read?
A
B
I
mean
the
IBC
is
more
nuanced
than
the
most
common
bridging
between
chains.
So
when
you're
doing
interoperability
between
two
evm
compatible
chains,
you
have
your
same
public
key,
sometimes
being
used
on
both
chains.
So
you
don't
really
need
to
validate
across
chains,
because
if
you
have
the
private
key
on
one
chain,
you
have
the
private
key
on
another
chain.
It's
just
the
RPC
node
might
be
different,
whereas
between
Antelope
chains,
the
the
account
structure
is
different.
B
My
account
on
EOS
might
be
already
squatted
on
Talos,
so
I
can't
just
create
the
same
account
and
I
might
not
have
the
same
public
and
private
keys.
So
it's
a
whole
different
animal.
You
really
need
to
create
this
mapping
process
that
Maps
the
accounts
together.
So
my
account
is
this:
on
EOS
my
account
is
out
on
Telos.
A
I
I
think
on
our
side.
It's
more,
it
would
be
off
chain,
it
would
be
kind
of
it's.
The
wallet
talking
to
the
app
to
begin
with
what
you're
trying
to
solve
for
is
the
like
the
interface
that
you're
doing
the
swap
on
to
know
who
you
are
on
chain
a
and
who
you
are
on
chain
B
and
potentially
proving
that.
So
that
way,
you
know,
there's
a
layer
of
protection
that
something
didn't
get
sent
wrong.
A
B
From
standpoint
of
anchor
like,
if
you
have
your
your
keys
and
accounts
stored
for
the
multiple
chains,
all
within
anchor
anchor
knows,
you
hold
these
keys
for
all
of
these
different
chains.
So
it
really
is
on
the
client
side.
Then
it
can
happen
off
chain,
it's
still
just
as
secure,
because
if
you
trust
the
wallet
itself
to
store
your
keys,
you
obviously
trust
it
and
you
don't
got
to
worry
about
things.
Getting
lost.
I,
don't
have
an
Unchained
strategy.
This
is
also
new.
I.
A
Yeah
and
that's
what
the
login
processes
that
we
have
submit
signatures
you're.
Actually,
when
you
log
into
an
application
with
the
protocols,
bind
anchor,
it
proves
that
you
have
access
to
the
private
key
to
that
account.
So
never
will
you
log
in
with
an
account
that
you
can't
actually
like
then
withdraw
tokens
or
perform
actions
on
so
that's
kind
of
a
safety
mechanism
there
during
the
login
flow.
We
can
just
leverage
that
to
make
it
so
you
log
into
multiple
things
at
once
and
it'll
work
great
for
IBC.
C
B
Going
to
bring
it
back
to
the
IBC,
because
I
want
to
extend
on
this
question
is
we.
We
just
talked
about
the
the
accounts
on
the
different
chains
and
how
you
need
to
kind
of
map
them
together,
but
then
there's
also
like
the
resource
components,
you're
spending,
one
resource,
token
or
power
up
or
rex,
or
staking
whatever
one
Chain's
doing
then
there's
might
be
a
whole
other
resource
model
on
the
other
chain.
So
I
guess
stick
to
Brandon's
question
and
tie
all
that
into
so.
A
No
I
I
mean
I
think
if
you've
used
anchor
and
you've
seen
the
transaction
fee
model
that
we
have
built
into
our
sdks
for
anchors.
Specifically,
that
sort
of
approach
is
going
to
be
possible
and
it's
not
just
going
to
be
because
that
leverages
fuel
on
our
side
with
anchor,
but
that
sort
of
approach
to
building
interfaces
into
applications
is
going
to
be
repeatable
for
other
processes.
A
It's
going
to
like
prompt
you
in
advance
to
say
we
need
you
to
take
an
action
alongside
of
what
you
were
trying
to
do
to
make
sure
that
you
could
do
it
and
maybe
there's
a
way
to
make
it
so
that
just
automatically
happens
like
that'll,
be
up
to
the
architect
of
the
plugin
and
maybe
there's
like
a
remember
options
that
way
just
automatically
puts
it
into
the
transaction,
for
you,
it'll
be
like
some
user
preference
on
how
you
interact
with
resources.
But
the
win
here
is:
is
that
no
longer
are
you
like?
A
Oh
gotta,
create
a
new
tab
and
leave
my
game
and
I
gotta
go
to
blocks
or
I
gotta,
go
to
whatever
application
and
then
figure
out
how
much
to
power
up
and
do
that
transaction.
Then
close
the
tab
and
come
back
to
my
game
like
that,
is
a
huge
distraction
in
the
user
experience
that
the
sdks
are
going
to
help
solve.
B
I'm
in
advanced
EOS
user
and
if
I'm
not
using
anchor
because
I
do
use
token
pocket
mobile
for
a
lot
of
things
when
I'm
in
that
Mobile
Wallet
I
can't
tell
you
how
many
times
I
try
to
do
something,
get
the
error
message
I'm
like
and
you
can't
do
multiple
tabs.
There's
one
browser.
Yeah
within
the
wallet
gotta
go
back,
go
it
was
power
up
gotta
power
up.
My
account
then
go
back
to
what
I
was
trying
to
do
in
the
first
place
and
I'm
just
like
man.
A
B
C
A
The
wallet
blue
paper
went
into
this.
This
was
like
the
one
of
the
big
pitches
of
the
wallet
paper.
Was
that
the
reason
that
we
all
have
to
do
that
right
now
is
to
speak
in
large
part
due
to
the
sdks
that
we've
had
like
applications
didn't
have
an
option
to
build
a
better
way
to
do
it
like
the
sdks
we
have
had
for
years
are
hey.
A
You
want
to
do
something
just
tell
me
what
you
want
to
do
and
then
I
will
try
to
do
it
and
when
it
fails
I'm
going
to
give
you
an
error,
so
there
was
never
any.
There
was
no
way
in
those
sdks
to
say:
hey.
Is
this
going
to
work
like?
Is
this
transaction
going
to
succeed?
Should
we
do
anything
else
to
help
this
transaction
succeed?
A
That
was
just
like
a
foreign
concept
to
those
sdks
and
the
only
reason
that
we
get
around
that
using
the
anchor
sdks
is
because
we
stopped
using
those
those
old
sdks
like
we
completely
ditched
them,
and
we
then
had
the
flexibility
to
do
things
like
offer
transaction
fees
and
catch
that
in
advance
and
be
like.
Oh,
this
transaction
is
going
to
fail
unless
you
buy
100
bytes
of
ram,
so
we're
just
going
to
add
the
100
bytes
of
ram
to
your
transaction.
B
B
And
all
of
what
you
mentioned
was
the
reason
why,
when
fuel
was
first
released
and
anchor
really
started
growing
in
popularity,
a
lot
of
Legacy
sites
that
maybe
weren't
being
greatly
maintained,
they
still
had
the
scatter
login,
which
works
for
token
Puck
and
everything
else.
But
then
you
wouldn't
have
the
anchor
log
in
and
that's
because
you
used
a
completely
different
method.
Or
would
you
call
it
an
SDK.
B
B
And
it
took
quite
some
time
there
it
was.
It
seemed
like
it
was
slow
to
see
adoption
of
that
anchor
login
for
some
applications.
I
think
at
this
point,
I
think
all
of
the
applications
that
I
use
regularly
do
allow
the
anchor
login
and
have
for
for
quite
some
time
the
reason
I
still
use
token
pocket
mobile
is
literally
the
the
browser
and
certain
things
that
I
do
yeah.
A
It
took
a
long
time
for
adoption
and
I
think
we
were
also
in
a
little
bit
of
a.
We
were
in
a
little
bit
of
a
lull
and
there
was
lots
of
crazy
stuff
going
on
in
the
world,
and
it
just
felt
like
it
wasn't
that
the
apps
didn't
want
to
adopt
it.
It
was
just
that
it
wasn't
their
priority
at
that
moment
in
time,
so
over
time,
I
think
users
have
nagged
enough
of
the
popular
applications
that
they
did
do
that
and
now
hopefully
it
won't
even
be
a
second
thought
for
new
applications.
A
B
The
acronym
SDK
software
development
kit,
so
you
got
software
and
developer
development
right
in
that
word.
So
when
we
talk
about
sdks,
we're
usually
talking
about
the
developer
side
is
it's.
It
makes
development
easier.
So
therefore,
you
will
hopefully
get
more
applications
and
better
applications
being
built
in
Antelope
chains.
Let's
talk
about
the
user
experience,
though,
because
this
whole
conversation
has
been
going
back
and
forth
like
the
sdks,
you
think
of
it
like
a
developer
tool
like
toolkit,
which
it
is
but
really
the
end
users
or
the
main
beneficiaries.
Could
you
kind
of
yeah.
A
They're
really
intertwined
I
mean
I.
Think
a
good
analogy
is
probably
the
just
the
web
over
the
past
10
years
without
crypto
in
it.
We've
seen
that
now
that
there's
kind
of
shared
sdks
in
the
web
space
the
reacts
of
the
world,
the
bootstrap
csses
of
the
world,
the
the
wordpresses
like
WordPress-
isn't
an
SDK,
but
maybe
a
bad
example.
A
So
that's
kind
of
I
think
how
the
ux
ties
into
these
sdks
is
we're
also
doing
that
on
the
SDK
side,
there's
going
to
be
some
interfaces
that
when
you
click
log
in
regardless
of
what
application
it
is
it's
going
to
be
this
familiar
like
box.
That's
like
pick
your
wallet
or
pick
which
network
or
you
know,
prompting
you
for
information
and
we've
seen
that,
like
just
spread
across
Web
2.0
and
really
help
improve
the
the
experience
and
that's
gonna.
That
has
to
be
something
we
consider
in
3.0
as
well.
A
A
B
A
And
there
are
some
ux
standards
that
were
applied
over
the
evolution
of
those
things
so
and
now
those
things
have
also
evolved
into
sdks,
the
Tailwinds,
the
bootstraps.
The
reacts,
the
views
like
all
these
things
that
web
developers
are
going
to
know
that
most
people
won't
but,
like
those
words,
are
building
blocks
for
people
to
build
applications
that
have
kind
of
homogenized
the
internet
in
some
way
and
made
it
so
that
you
can
just
jump
on
a
new
web
page
and
you're
like
oh.
C
So
yeah,
that's
something
I'm
kind
of
curious
about
is
I
learned
through
reading
the
Milestones
that
there's
a
there's
a
brand
development
aspect
to
this,
and
you
say
that
this
these
sdks
will
be
branded.
They'll
have
an
identity
and
a
website,
and
how
did
that
all
fit
in?
Why
is
that
a
thing?
It's.
A
Something
that
I
think
we
know
is
important
and
we're
starting
to
push
on
for
more
than
just
the
sdks,
but
these
other,
like
I,
threw
kind
of
buzzword
type
things
out
for
these
other
sdks
in
the
Web
2.0
world.
When
I'm
talking
about
the
reacts,
the
views
that
sort
of
thing
those
all
have
Brands
and
they
have
identities
that
developers
within
those
spaces
like
associate
to
solving
problems.
A
They're
like
educational
leap,
like
jumping
off
points
into
further
things,
you
can
learn
the
sdks
like
the
internals
or
you
can
just
use
them
like
machines,
but
you
need,
like
the
machine,
needs
a
name.
So
when
we
were
looking
at
other
ecosystems
like
going
back
to
when
I
was
talking
about
hard
hat
and
Morales,
and
some
of
these
other
branded
sdks
we've
seen
how
how
that
causes
kind
of
I.
A
Don't
like
it's
weird,
applying
that
to
sdks,
because
it's
such
a
weird
subset,
but
like
developers,
develop
this
sort
of
brand
loyalty
towards
sdks,
because
it
is
how
they
learn
to
build
a
better
machine
and
I
think
within
the
crypto
space.
We've
seen
a
few
examples
of
that
again,
the
hard
hats
moralysis
these
sorts
of
things,
and
we
need
to
do
that
within
our
space
as
well.
The
renaming
of
the
C
plus
implementation
to
LEAP
I
think
was
a
great
move
in
that
direction.
A
You
know
you
now
have
leap
which
people
just
kind
of
understand
is.
This
is
the
server
side
component
to
the
Antelope
protocol
and
when
we're
looking
at
other
layers
of
the
stack,
because
leap
is
just
one
layer
of
the
stack
there's
web
development
game
development,
mobile,
app
developments,
there's
like
server-side
stuff,
there's
multiple
like
avenues
that
are
completely
different
to
completely
different
people
of
interest
to
different
people.
I
should
say
we
need
those
to
kind
of
all
have
their
own
unique
names.
We
need
them
to
all,
have
their
own
unique
entry
points.
A
So
that
way,
people
who
are
interested
in
that
side
of
this
ecosystem
have
kind
of
this
one
thing
they
can
glom
onto
learn
about
and
then
spread
out
to
the
others.
So,
just
like
we've
always
named
all
of
our
other
products,
except
for
Eos
voter,
something
unique
like
there's
anchor,
there's
fuel,
there's
Unicode
gray
Mass
was
not
EOS
anything.
We
need
names
to
be
unique,
so
that
way
they
stand
out
to
the
people
that
make
use
of
them
in
the
ecosystem.
A
So
we're
continuing
that
with
this
theme
of
sdks
and
I,
think
it's
the
right
direction
to
both
onboard
developers
and
to
create
some
sort
of
brand
loyalty.
That
is
like
oh
I'm,
this
kind
of
developer
I'm
good.
At
this
thing,
you
can't
really
say
I'm
good
at
web
client
sdks,
but
you
could
be
like
I'm
good
at
something
with
this
name
is.
A
A
That
one's
a
lot
more
catchy-
and
we
did
joke
about
that
a
little
bit,
but
we
want
to
be
able
to
present
the
name.
Along
with,
like
an
icon,
a
color
scheme,
an
identity,
we
did
a
whole
branding
Workshop
around
the
name
to
make
sure
that
developers
would
get
what
they
wanted
out
of
the
brand
I'm,
not
a
brand
person.
So
this
is
all
kind
of
theoretical
to
me,
but
like
it's,
my
understanding
that
Brands
resonate
with
groups
of
people
and
like
subconsciously
it
even
helps
to
some
degree.
A
It's
we
went
through
those
exercises
and
came
up
with
a
list
of
good
names,
a
list
of
good
identities
and
we've
kind
of
narrowed
it
down
and
we're
we're
assembling
a
presentation
now
to
bring
to
the
stakeholders.
I,
don't
know
if
there's
an
approval
required,
but
we
definitely
want
to
present
it
and
make
sure
that
nobody
just
says
that's
terrible,
let's
change
direction,
so
that
should
be
soon.
B
So
soon
is
a
very
ambiguous
term
that
we've
heard
for
a
very
long
time
without
any
certainty
of
when
soon
actually
is
weeks.
The
last
milestone
for
this
particular
piece
of
body
of
work
is
September
2023.
That's
when
everything
that's
when
the
last
Milestone
will
be
achieved
before
some
kind
of
maintenance
mode
in
the
more
short
term.
So
you
mentioned
a
couple
of
weeks.
A
Think
by
Year's
End
or
maybe
January,
we
are
going
to
have
something
usable,
something
that
maybe
the
more
advanced
developers
or
the
more
I
shouldn't
say.
Advanced.
The
people
that
have
some
level
of
experience
with
Antelope
should
be
able
to
start
using
pieces
of
it
and,
like
it'll,
be
a
good
chunk
of
the
work
that's
actually
done,
but
I
made
this
analogy
somewhere
the
other
day.
A
It's
been
a
lot
of
conversations
about
sdks,
but
the
way
that
we
originally
rolled
out
anchor
was
we
finished
like
the
protocol
and
anchor
and
then
we
released
it
and
there
were
like
no
applications
that
had
integrated
anchor,
and
so
there
wasn't
much
of
a
purpose
for
it.
So
what
we
did
was,
then
we
really
started
working
with
the
developer
community
and
we
helped
people
implement
this
new
thing
into
their
applications.
Just
like
me
personally,
some
other
people
on
the
teams.
A
Personally,
we
were
like
Hands-On
helping
with
the
integration
of
that
stuff
and
I
think
that
is
what
got
people
to
understand
how
to
do
it.
It
helped
us
learn
what
the
problems
were
and
like,
where
the
pain
points
and
using
it
were,
and
so
then
that
really
helped
evolve
anchor
over
like
the
next
couple
months.
A
The
sdks
are
probably
going
to
be
a
very
similar
flow
to
that
as
to
where,
within
the
next
two
to
three
months,
we'll
have
like
a
usable
thing
and
then
we're
going
to
make
a
big
hubbub
about
it.
We're
going
to
be
like
hey,
we
need
developers
to
work
with
this
new
thing
and
then
we're
going
to
interact
with
them
as
much
as
they
are
willing
in
seeing
how
they're
using
it
where
it
excels
at
doing
things
for
them
and
then,
where
it
just
absolutely
doesn't
solve
their
problem.
A
And
then
we
can
take
that
kind
of
feedback,
loop
and
iterate
on
the
sdks
over
time
to
slowly
improve
them.
So
I
think
that
well,
the
project
in
total
is
a
year
long,
there's
going
to
be
a
really
usable
Chunk
in
the
first
quarter
of
the
project
and
then
a
lot
of
iterations
on
that
afterwards
and
you'll
notice
that
a
lot
of
the
later
Milestones,
if
you
do,
go
through
them,
one
by
one,
they
are
documentation.
They
are
education.
They
are
like
they're
things
around
the
project.
A
It's
like
building
the
website
and
you
know
creating
a
good
onboarding
flow
for
new
developers
to
learn
about
the
ecosystem.
It's
the
front
load
of
the
project
is
really
development,
heavy
and
the
second,
or
that
latter
half
of
the
project
is
really
educationally
heavy,
so
you
definitely
will
get
if
you're
a
developer
interested
in
this
you'll
get
something
a
lot
earlier
than
next
September
it'll
be
it'll,
be
like
in
an
alpha
state
or
early
release
date.
Much
sooner
than
that
and
I
would
absolutely
encourage
people
to
come.
Try
it
out.
C
A
Code
golf
is
a
thing
that
I
was
exposed
to
years
and
years
and
years
ago,
in
a
different
form
code.
Golf
in
the
sense
that
I
was
first
introduced
to
it
was
you
need
to
do
something
like.
Let's
say
you
need
to
compute
some
value
to
some
number
of
length,
or
you
know
some
sort
of
operation.
The
goal
is
to
do
it
in
as
few
characters
as
possible.
Just
like
golf
is
to
get
the
ball
in
the
hole
in
a
few
swings
as
possible,
so
code
golf
is
just
using
as
few
characters
as
possible.
A
A
It
just
has
to
be.
It
has
to
be
like
pseudo
code.
It
doesn't
have
to
run
it
just
has
to
be
like.
Oh,
this
is
the
best
way
to
do
this
thing
in
sudo
code.
So
we
have
multiple
rounds
of
that
running
for
different
topics.
We
keep
adding
more
and
more
with
the
development
of
the
sdks,
we're
building
from
the
bottom
up,
we're
doing
those
building
blocks
and
we're
building
the
Legos,
and
it
takes
a
while
to
get
to
a
usable
state
with
golf.
What
we're
doing
is
we're
attacking
it
from
the
top
down.
A
We
are
like
okay,
what
does
the
end
result?
Look
like
what
is
the
opening
sentence
to
the
book
or
something
and
then
we're
right,
we're
going
to
meet
in
the
middle
somewhere
where
the
foundational
Pieces
come
together
with
the
code
golf
rounds
and
hopefully
the
way
you
actually
use
the
code
is
the
way
that
we
all
dreamed
up
collectively
in
these
code
golf
rounds.
That
is
unrestrained.
What
is
the
nicest
way
and
the
easiest
way
to
do
an
IBC
transaction?
A
You
know
we
don't
have
a
round
for
that
yet,
but
we
probably
should
and
then
what
we're
going
to
do.
We
haven't
done
this
yet,
but
it's
on
our
upcoming
activities
is
we're
going
to
start
talking
about
this
publicly
and
try
to
get
other
developers
in
the
Antelope
space
who
know
like
how
did
do
things
currently
today
for
them
to
help
dream
up?
What
the
ideal
way
to
do.
Those
things
is
so
how
to
get
how
to
get
the
ball
in
the
hole
and
the
least
amount
of
swings
do.
A
I
mean
it's
right
now
in
terms
of
both
Golf
and
sdks.
It's
primarily
our
team.
We
do
want
to
really
open
that
up,
but
it's
it's
just
kind
of
the
guys
that
have
been
working
on
this
with
me
for
quite
some
time
now
to
build
a
lot
of
this
stuff,
plus
we're
training
up
some
new
people
to
be
able
to
participate
so.
C
B
A
I
guess
we
haven't
started
seeking
it
heavily
and
that's
why
I
don't
have
anybody
to
like
shout
out
right
now,
I've
talked
with
a
number
of
people
that
are
like.
Let
me
know
the
minute
I
can
start
playing
with
this
like
and
it's
just
we
haven't
like
leave
the
flag
and
said:
go
yet
so
I
do
have
a
number
of
people
that
have
shown
interest
but
nobody's
participating
yet
and
that's
by
Design,
because
we're
still
creating
the
experience
around
that
ledger.
B
So
you
you
provided
an
update
to
the
Coalition
members
recently
that
were
asking
about
the
status
of
ledger,
so
you
actually
had
an
interaction
with
Ledger
the
hardware
wallet
company.
Can
you
kind
of
debrief
the
EOS
Community?
What
that
conversation
was
and
what
some
of
the
current
limitations
are?
Yeah.
A
So
earlier
this
year
there
was
an
issue
where,
if
your
account
was
Associated
to
a
ledger,
it
was
not
able
to
be
unassociated
to
The
Ledger.
So
you
were
stuck
on
The
Ledger,
there's
a
action
you
can
perform
to
change
permissions
and
that
didn't
work.
So
it
you
were
just
locked
into
a
ledger
effectively
and
you
couldn't
get
off.
So
we
reached
out
to
The
Ledger
team.
A
We
started
a
dialogue
with
them
both
about
the
wallet
paper,
just
to
kind
of
collect
some
ideas
on
what
was
possible
for
proposals
within
the
wallet
paper,
and
then
we
were
like
and
hey.
We've
got
this
issue.
Our
users
are
stuck.
We
can't
fix
this.
We
need
help
the
guy
that
built
the
app
isn't
around
anymore,
and
so
the
Ledger
team
stepped
up
and
fixed
the
issue
for
us
I
think
their
users
were
also
reaching
out
and
saying
hey.
A
This
is
not
working,
so
they
were
getting
hit
kind
of
from
both
sides,
so
The
Ledger
team
fixed
that
issue
and
got
it
deployed
and
then
that
dialogue
between
gray,
mass
and
The
Ledger
team
kind
of
continued
on
and
The
Ledger
team
wanted
to
establish
kind
of
a
more
formal
relationship
on
how
this
is
going
to
be
maintained,
moving
forward.
So
that
way
they
don't
have
to
drop
what
they're
doing
to
fix
our
apps
problem.
So
connections
were
made
with
the
Coalition
and
the
enf
that
is
all
within
the
past
couple
weeks
has
happened.
A
I
think
the
Coalition
call
this
week
talked
about
a
ledger
meeting
between
the
enf
and
The
Ledger
team.
To
start
that
conversation
I
wasn't
on
that.
So
I
don't
know
exactly
what
happened
in
there,
but
now
it's
more
than
just
gray
Mass
talking
to
The
Ledger
team.
It's
now
the
enf
and
more
formally
the
Coalition,
and
hopefully
we
will
be
getting
some
of
the
other
more
minor
issues
resolved
with
the
app
and
then
have
a
path
forward
to
maintain
that
so
that
way,
EOS
users
and
all
Antelope
users
have
access
to
this
great
Little.
B
When
that
ledger
app
was
created,
it
was
I
believe,
2018
or
19..
It
was
funded
through
a
fifty
thousand
dollar
Bounty
from
Cipher
glass
at
the
time,
and
it
shows
one
of
the
weak
points
of
bounties
with
because
there's
no
like
service
contract
involved,
so
things
get
deprecated
teams
shift
priorities
over
time
and
there
was
never
really
a
good
public
goods
like
funding
mechanism
or
way
to
to
to
achieve
these
public
goods
because
nobody's
making
money
off
of
this
Ledger
live
application.
B
So
it's
nice
to
hear
that
there's
movement
on
it
I'm
glad
getting
this
out
in
the
open,
because
we
probably
won't
share
a
formal
announcement
until
there's
announcement
to
share.
But
there
is
dialogue
happening
and
that's
kind
of
like
step,
one
to
figuring
out
what
the
ultimate
solution
will
be,
but
I'm
really
looking
forward
to
that,
because
I
just
follow
monitoring
the
chats
over
the
years,
I
mean
there's
every
couple
days,
there's
usually
a
ledger
question
going
on
or
things.
A
I
I
mean
I,
don't
have
any
like
deep
thoughts
or
anything
I
if
interacted
with
Bart
over
the
years.
I'm
pretty
sure
I
met
him
at
a
couple.
Events
I,
don't
remember
exactly
what
the
topics
were,
but
I've
been
on
calls
with
him
over
the
past
four
years,
for
probably
something
wallet
related
and
I've
always
had
a
good
experience
like
throughout
all
of
that
stuff,
so
I
mean
I'm
excited
to
see
where
it
goes.
I
think
he
certainly
has
a
lot
of
knowledge.
A
B
B
A
Way
out,
yeah
I,
there's
gonna
be
a
lot
of
that
kind
of
messaging
coming
out
here
soon,
a
lot
of
it
involving
the
sdks
and
like
wanting
engagement
and
wanting
to
really
make
this
kind
of
a
community.
You
know
like
it,
takes
a
village
to
raise
a
child
sort
of
situation.
We
want
to
kind
of
get
everything
ready
and
then
ask
the
village
to
come
like
make
sure
that
the
child's
not
crawling
into
Wells
or
something
but.
A
Yeah,
so
we're
we're
gonna
come
up
with
a
name
for
the
kid
or
announce
the
name,
but
I'm
gonna
stop
with
this
analogy
now.
The
whole
point
of
it
is
that
I
think
I
will
have
a
lot
of
those
kind
of
shout
outs
or
mentions
or
like
trying
to
call
out
specific
people
once
we
do
that.
But
if
I
do
any
of
that
now,
if
there's
no
action
to
it,
it's
like
hey
someone
hold.
A
A
A
telegram
Channel
anymore,
because
there's
a
whole
drama
about
wallet,
support
and
scammers
and
that
kind
of
stuff,
but
yeah
I,
would
say.
Twitter
or
email
are
probably
the
best
way,
and
if
you
need
support,
you
can
go
to
support.greymass.com,
which
is
the
support
portal
that
we've
been
working
on.
So
that
way
we
can
try
to
split
the
like
hey
my
anchors,
broken
from
the
people
who,
like
hey
I,
want
to
help
you
build
something.
So
if
we
can
separate
those
two
types
of
communication,
it'll
make
it
a
lot
more
effective.