►
Description
An exploration of Developer Experience (DevX).
We know there are many challenges around User Experience (UX) for end-users who are trying to use decentralized applications but what about the developers who build those applications? Their experience is often under-appreciated.
In this meetup, we dug deeper into what developer experience (DevX) really means, the state of it on today's platforms and how we can improve it in the future. We surveyed the landscape and tore down a couple of existing platforms.
Following the talk by Erik Trautman, our Head of Operations, we moved to a panel discussion with developers of apps on multiple different platforms about the pros and cons of development on each platform.
About the Speaker and Host:
Erik Trautman leads operations at NEAR Protocol, which is a scalable mobile-first blockchain. He has a long history in technical education: he started in market analysis on Wall Street in 2007, created the popular Odin Project in 2012 and ran Viking Education as its CEO until its acquisition in 2017.
Panelists:
1) Viktor Radchenko, Founder of Trust Wallet (Acquired by Binance).
2) Amhed Herrera is a Software Engineer from the Dominican Republic, where he founded two startups before moving to the US. He's been working as a full-stack software engineer since 2010, and on smart contracts and dApps since 2018. Recently joined the Harbor.com team where they're working on tokenizing securities on the blockchain.
3) Jehan Tremback is CEO of Althea (althea.org), working on a system that makes it easy for communities to set up networks which are faster and cheaper than the existing ISP monopolies, by enabling routers to pay each other for bandwidth, using cryptocurrency. He has years of experience in the Ethereum ecosystem and will be speaking about the ins and outs of building Dapps such as payment channels, voting systems, and DAOs.
4) Chris Li is the founder of Forge Labs, a decentralized blockchain accelerator headquartered in San Francisco. He recently led the team to build a game Dapp on EOS and became No.8 in daily DAU. Before, he was director of engineering at Bodhi Prediction Market, in charge of smart contract and backend development. Before blockchain, he was a serial entrepreneur and senior engineer at Microsoft, where he worked on Exchange, a complex distributed system for 4 years.
**About the Blockchain Onramp Series**
Blockchain Onramp is a series of events covering the full spectrum of knowledge necessary to operate effectively within the blockchain ecosystem as a designer, developer or product person. After participating in these events, you should be able to take your functional expertise in any of these areas and apply them to blockchain projects.
We are doing this to provide a key -- and currently missing -- plain-English onramp for people of all functional experience who are interested in building real businesses on this new technology.
The format of each event may differ slightly, but they will be a combination of expert talks and discussions with industry practitioners.
The rough Blockchain Onramp Series roadmap is:
+ Product Series: Ecosystem, DApps, and Strategy
+ Design Series: Onboarding UX, Best Practices
+ Development Series: Developer stack, Building on TestNets, Security, Best Practices
+ Startup Series: Marketing, Business Models, and Fundraising
Follow the latest from NEAR Protocol on,
Medium: https://medium.com/nearprotocol
Twitter: https://twitter.com/nearprotocol
GitHub: https://github.com/nearprotocol
LinkedIn: https://www.linkedin.com/company/near-protocol/
Telegram: https://t.me/cryptonear
Discord: https://discord.gg/gBtUFKR
#FutureIsNEAR
A
A
So,
as
far
as
as
far
as
tonight's
format,
basically
I'm
just
gonna
kind
of
kick
things
off
and
basically
frame
the
discussion
that
we're
gonna
have
afterwards
so
sort
of
provide
that,
but
that
slow
on
ramp
up
into
that
talk
a
little
bit
about.
Well,
you
know
I'll
go
into
it,
but
talk
a
little
bit
more
from
the
ground
up
about
user
experience
and
what
that
means
in
the
developer,
experience
ecosystem
and
how
that
extra
release
of
some
case
studies
that
we
did
with
solidity
and
sorry
with
with
aetherium
in
the
OS.
A
But
then
with
the
panel
afterwards.
You
guys
got
a
chance
to
take
another
step
up,
and
these
are
people
who
have
obviously
been
developing
for
a
lot
more
on
these
platforms,
and
so
I
think
you
can.
You
know,
begin
to
kind
of
go
beyond
sort
of
the
the
entry-level
side
and
much
more
into
the
actual
experience
developers
developing
actual
difficult
things
on
top
of
these
platforms.
A
So
that's
that's
kind
of
framing
for
the
night
and
I
think
we're
good
to
go
so
I'll
dive
right
in
so
basically,
the
goal
for
tonight
is
to
just
talk
about
developer
experience,
so
we
spend
a
lot
of
time
talking
about
user
experience
tonight.
Hopefully
we'll
expand
that
a
little
bit
so
just
to
get
everyone
on
the
same
page
user
experiences
about
the
overall
experience
and
to
end
of
somebody
who's
using
a
project
or
using
a
platform
or
using
the
website,
or
something
like
that.
A
It's
oft,
confused
and
and
and
used
interchangeably
with
user
interfaces.
One
of
the
classic
examples
of
the
difference
between
the
two
is:
is
that
I
don't
know
if
you're
familiar
with
the
ketchup
bottles,
but
many
many
many
many
many
years
the
ketchup
bottle.
The
Heinz
ketchup
bottle
was
that
iconic
shape
is
the
glass
bottle
and
nobody
could
get
the
ketchup
out.
You
bang
it.
A
You
shake
it
as
much
as
you
want,
and
and
and
until
we
had
Google,
and
we
could
find
out
that
you
actually
had
to
tap
it
exactly
in
the
right
place
on
on
the
label.
I,
don't
know
if
you
guys
knew
that
trick,
you
tap
it
on
the
label
and
that
actually
gets
the
ketchup
out.
It's
a
beautiful
bottle.
It's
incredible!
It's
well
branded,
it's
crafted
and
its
iconic,
but
it
doesn't
actually
really
give
you
I
mean
you
can't
use
it
on
the
other
side.
A
You
have
you
have
these
new
squirt
bottles
that
just
sort
of
sit
on
the
table.
They're
not
they're,
not
they're
kind
of
frumpy
looking,
but
they
really
get
the
job
done.
They
do
exactly.
What
you
want.
Another
thing
is
is
usability
is
is
something
that
that
overlaps
really
well
with
user
experience,
but
it's
not
exactly
the
same
thing
you
could
you
could
you
could
go
to
the
ends
of
Google
and
find
all
sorts
of
interesting
ways
of
delineating
between
the
two
but
I
kind
of
like
the
the
science
versus
art
usability
is
very
targeted.
A
It's
you
have
a
goal
in
mind
and
you
want
to
accomplish
that
goal
with
the
most
effectiveness.
The
most
efficiency
and
the
most
satisfaction
for
the
users.
Ux
is
much
more
about
everything
around
it
as
well.
So
it's
designing
and
specifically
a
lot
of
the
question
that
we
ask
ourselves.
A
lot
is:
is
this
delightful?
Is
this
something
that
the
user
is
really
just?
A
It's
kind
of
is
happy
is,
is
having
a
good
experience
operating
within
within
the
ecosystem
or
through
the
product
that
we're
actually
trying
to
get
them
in
and
again,
I
just
want
to
emphasize
that
that
where
usability
is
very
goal,
focused
UX
is
really
about
the
full
journey
and
there's
actually
kind
of
a
fun
reference
which
is
a
highway.
A
highway
is
usable,
but
not
all
highways
have
good
user
experience
right.
You
have
a
highway,
we'll
get
you
there
very
quickly,
but
not
all
of
them.
A
So
the
way
these
we're
talking
about
the
blockchain
ecosystem,
which
means
we're
talking
about
platforms-
and
you
know
we're
talking
about
kind
of
base
level
stuff
and
we're
trying
to
create
the
platforms
that
developers
are
going
to
be
able
to
build
apps
on
top
of
or
decentralized
apps
on
top
of
so
this
really
requires
a
two-step
product
market
fit
or
a
two-step
path
to
market.
Whatever
I
mean
there's
a
lot
of
ways,
you
could
phrase
it,
you
could
call
it.
You
know
B
to
B
to
D
to
C.
A
You
know
business
to
developer
to
consumer,
but
basically
what
it
means
is
that
is
that
we
have
to
kind
of
go
through
developers
to
get
to
our
consumers.
We
have
to
think
about
the
consumer,
the
end
users
who
are
going
to
be
using
these
apps,
but
obviously
you
know,
but
the
first
step
is
making
sure
that
the
developers
actually
want
to
use
the
platform
that
they
can
use.
The
platform
I
mean
I,
think
I
think
you
know.
We've
everybody
wants
to
design
for
end
users.
It's
it's
fun!
It's
sexy!
It's!
A
A
It's
you're
you're
living
in
text,
you're
living
on
the
command
line,
and
it's
just
it
doesn't
have
the
same
appeal,
but
but
in
the
world
that
we're
in
it's
I,
don't
I,
don't
necessarily
want
to
categorize
that
it's
more
important
but
I
think
relative
to
the
building
it
gets.
It
is
significantly
more
important,
and
so
specifically
the
intention
of
designating
this
as
developer
experience
and
really
trying
to
try
to
fork
out
a
difference
between
what
we're
thinking
about
when
we're
thinking
about
user
experience,
which
I
mean
it
may
not
be
semantically
correct,
you
know
it's.
A
It
is
technically
a
sub
subset
of
user
experience,
but
really
the
intention
behind
this
language
is
to
say
that
there's
actually
a
lot
of
difference
in
what
we're
trying
to
talk
about
when
we're
addressing
developer
tools,
as
opposed
to
what
we're
talking
about
when
we're
talking
about
end-users,
who
are
gonna,
be
using
the
apps
that
the
developers
are
creating.
So
you
also
see
this
somewhere
on
the
web.
If
you're
googling
around
you
can
find
it
under
under
DX,
but
I
think
I
think
it's
a
little
less
descriptive
than
something
like
def
X.
A
A
So
just
a
quick
bit,
I
didn't
introduce
myself,
so
my
name
is
Eric
and
I
lead
operations
at
NIR,
so
we
actually
have
the
office
upstairs
and
we
are
we're
also
a
blockchain
and
we're
a
blockchain
that
is
scalable.
It's
charted
and
it's
our
contract
platform
I.
My
background
is
in
both
markets
on
the
Wall
Street
side
and
education,
I
used
to
run
a
business
that
was
doing
online
software
engineering,
education,
so
I
care
really
deeply
about
helping
people
into
the
ecosystem
and
creating
ecosystems,
and
things
like
that.
A
So
that's
why
I'm
here
so
as
far
as
tonight,
the
first
thing
we're
gonna
kick
off
with
is
again
just
looking
into
the
components
of
developer
experience.
Good
place
to
start
is:
who
is
our
who's?
Our
user
I
mean
this
is
going
to
be
a
little
bit
general.
You
know
by
definition,
but
I
think
we
have
to
just
kind
of
start
somewhere
and
so
we'll
say
that
you
know
we're
talking
about
a
developer,
who
has
some
experience,
who's
comfortable
in
the
command
line,
who's
comfortable
with
probably
web
languages
or
something
along
those
lines.
A
You
know
a
lot
of
people
get
their
entry
on
that
level
and
you
know
they're
comfortable
with
version
control
like
it
and
you
know,
they've
worked
with
deployment,
they
may
not
be
a
DevOps
engineer,
but
you
know
they've
sort
of
deployed
their
own
stuff.
So
someone
someone
who
I
guess
you
could
call
kind
of
a
maybe
an
early
to
mid
minimum
hurdle
of
full
stack
developer
or
something
like
that
and
of
course
you
spend
a
lot
of
time
in
documentation.
A
So
so,
specifically,
what
are
some
of
the
differences?
What
are
some
of
the
things
that
are
actually
really
worth
highlighting
in
the
difference
between
user
experience
and
developer
experience
and
I
think
there
are
a
whole
number
of
them.
One
of
them
in
particular,
is
that
you
don't
actually
control
the
whole
user
users
experience
when
you're
talking
about
developer
tools
because
developers
operate
em,
it's
the
whole
constellation
of
different
tools.
A
So
you
know
you,
you
might
you
might
even
control
the
IDE
that
they
operate
within,
but
they're
still
gonna
go
out
and
they're
gonna
look
for
debugging
information
away
from
you,
they're
they're
gonna
be
using
some
sort
of
build
process
behind
the
scenes.
They're
gonna
be
using
a
whole
bunch
of
things
that
you
don't
control,
so
there's
literally
there's
no
way
for
you
to
control
the
entire
experience
and
end
of
a
developer,
like
you
do
with
a
user
on
your
website.
Another
one
is
that
it's
about
creation,
and
so
it's
not
about
you
know.
A
You
know
finite
goal
accomplishment.
You
know
there
are
user
facing.
You
know,
let's
say
consumer
facing
apps
that
are
about
creation,
but
for
the
vast
majority
of
them
we're
really
trying
to
get
the
user
to
accomplish
a
very
specific
goal.
Code
is
creative
and
and-
and
so
this
is
it's
a
little
bit
different-
we're
not
trying
to
get
them
done
with
the
specific
thing
as
fast
as
possible,
we're
trying
to
nurture
them
through
the
creative
process
and
a
couple
couple
more
things.
One
is,
of
course
the
developers
are
operating
within
their
own
environments
as
well.
A
So
it's
sort
of
in
the
same
idea
that
you
can't
control
the
entire
experience
developers.
You
know
one
developer
is
going
to
be
operating,
you
know,
he's
gonna,
prefer
vim
and
he's
gonna
be
operating.
You
know
deep
in
text
and
another
might
might
actually
prefer
she
might
like
to
work
in
in
the
web
interface.
A
Who
knows
right
and
and
has
an
online
ID,
some
something
that's
hosted
on
the
web
and
and
those
are
both
entirely
valid
approaches
to
accomplishing
the
exact
same
thing,
because
what
matters
is
what's
the
code
that
they
created
and
they
might
be
collaborating
on
literally
the
same
codebase
and,
of
course,
the
common
language.
They'll
speak
is
text,
you
know
so
code
is
text
and
that
bad
it
actually
becomes
one
of
the
most
significant
factors
when
we're
thinking
about
how
do
we
design
for
these
experiences
as
well?
A
A
The
whole
point
is
that
there
are
a
lot
of
different
a
lot
of
different
areas
to
the
deployment
of
these
apps.
That
add
a
little
bit
of
extra
complexity,
specifically
everything
dealing
with
the
cryptography
side,
and
you
know
the
the
the
wallets
and
the
tokens
and
the
keys
and
things
like
that.
That's
that's
new
relative
to
somebody
who
say
has
web
experience
and
is
used
to
just
throwing
it
up
on
a
server
and
then
it's
it's
good
to
go.
A
So
as
far
as
as
far
as
where
does
the
developer
experience
actually
touch
things
so
I
mean
there
are
a
lot
of
places
right
a
so.
If
you're
designing,
you
have
to
think
about
okay.
So,
what's
the
design
of
the
API,
you
know
what
are
water?
How
do
we?
How
do
we
use
naming
conventions?
How
do
we
organize
it?
How
do
we
call
it?
It
goes
into
the
documentation
itself.
A
You
know
whether
that
that's
the
API
reference,
it's
the
tutorials,
that's
back
up
the
the
the
reference
and
then
we
get
into
the
details
of
the
tooling
itself.
You
know,
obviously,
the
programming
language
that
that's
supported
is
obviously
super
important,
but
you
know
you
have
everything
from
the
CLI
to
the
text
editor
to
the
to
the
build
tools
and
the
logging
and
everything
along
that
whole
whole
constellation
and
then,
finally,
of
course,
you
have
more
on
the
support
side.
A
Libraries,
I,
guess
you
could
call
them
tooling
or
support
you
have
you
know
VM
scaffolding,
you
have
all
the
forums
that
people
are
going
for
help
and
you
have
live
chat
and-
and
you
know
so,
you
have
to
everything
from
Stack
Overflow,
all
the
way
to
jumping
in
a
discord
or
slack
channel
or
an
IRC
channel
and
asking
for
help.
So
my
point
in
talking
about
that
is,
is
again
just
to
emphasize
how
broad
a
developer's
experience
actually
is
relative
to
what
you
might
get
as
thinking
about
an
end
user.
A
So
and
again
this
is
just
a
visual
representation
where
you
know
sort
of
the
heart
of
everything.
The
beating
heart
in
the
middle
is
the
command-line
interface,
but
you've
got
the
text
editor.
Coming
in
to
that,
you
have
a
whole
bunch
of
tools
that
are
off
of
the
command
line.
Interface.
You've
got
a
jump.
A
You've
got
to
kick
the
code
up
to
version
control,
you've
got
to
work
on
testing
frameworks,
and
then
you
have
multiple
environments
that
you're,
probably
deploying
to
you,
might
have
a
local
developer
net,
which
you
know,
maybe
you
call
it
local
host.
You
have
the
test
net,
which
is
you
know,
probably
commonly,
in
other
other
words
the
staging
environment,
and
you
know
you
have
a
production
environment
which
is
main
menu.
You
have
a
whole
set
of
other
tooling
around
just
kind
of
the
instrumentation,
like
the
exploring
your
block
Explorer
and
things
like
that.
A
So
I,
just
a
quick
note,
also
a
lot.
A
lot
of
a
lot
of
these
tools
are
optimized
for
developers,
because
they're
built
by
developers
and
the
developers
who
built
the
tools
are
by
nature
experienced,
and
you
know
they
there's
always
the
dogfooding,
which
is
great.
You
know
that
that's
why
so
many
awesome
developer
tools
get
created,
but
where
it
tends
to
fall
short,
is
that
you
have
experienced
developers
creating
tools
for
experienced
developers
or
who
are
assuming
that
they're
power
users
or
you
know
who
are
who
are
creating
it
for
other
power
users.
A
So
you
often
don't
get
there's
often
a
discontinuity
in
the
learning
curve
around
these
curt
around
these
tools
as
well,
which
is
of
course,
part
of
the
the
experience
of
somebody
who's
coming
into
this
ecosystem
and
onboarding
as
hopefully.
Hopefully
we
all
know,
onboarding
is
actually
one
of
the
most
important
pieces
of
experience
altogether.
I
mean
if
you
have
a
poor,
onboarding
experience,
they're,
never
even
gonna,
get
into
your
app
sufficiently
to
the
degree
that
they
actually
get
stuck
in
and
they
stick
around.
A
So
a
typical
flow.
What
happens
when
a
developer
jumps
into
a
project?
It's
like
cool
I,
just
heard
of
a
really
cool
blockchain
and
and
what
do
I
do
usually
it
starts
with
Google
and-
and
you
know
first,
you
want
to
gather
information-
you,
google,
a
bunch
of
stuff.
Then
you
have
to
download
a
whole
bunch
of
tools.
You
have
to
verify
that
those
tools
are
actually
connected.
A
It's
hooked
up,
you
gotta
fight
with
a
bunch
of
error
messages
along
the
way
you
have
to
you
know,
then
you
have
to
actually
get
in
your
text
editor
and
write
the
code
that
you
know
maybe
you're
following
a
tutorial.
You
have
to
actually
obviously
put
that
into
text.
Editor
save
that
down.
You
have
to
I
mean
there's
a
lot
of
steps
in-between,
obviously
interfacing
with
saving
that
up
into
version
control.
A
You
know,
you're
gonna
want
to
deploy
it
and
you
know
eventually,
once
you
get
through
kind
of
a
test
app
and
you
and
you've
tasted
it.
You
know
you've
basically
done
the
hello
world
up.
Then
you
want
to
you,
go
in
and
figure
out.
How
do
you
production
Eliza's?
How
do
you
actually
make
this?
Something
that
could
work.
You
know,
how
do
you
put
a
user
interface
on
top?
How
do
you,
how
do
you
make
it
secure
and
begin
to
move
into
the
into
the
best
practices
side
of
things
along
the
way?
A
There's
all
these
interrupts,
which
are
which
are
errors,
errors
up
and
down
googling
sec
overflowing
chatting
banging
your
head
against
the
wall
cheering
and
in
success.
It's
it's
all
part
of
the
process,
and
you
know
it
again.
It's
it's
all
about
this.
This
disparate
ecosystem
of
touch
points
that
you
go
through
when
you're,
when
you're
fighting
to
debug
these
kinds
of
issues,
so
I
want
to
dive
into
a
case
study
with
aetherium
that
we
did
Jane
to
do.
Did
you
want
to
chat
about
that?
So
so?
B
Hi,
my
name
is
Jane
and
I
I
work
in
here
and
I
joined
last
Monday.
So
my
background
is
pretty
interesting.
I
didn't
know
anything
about
blockchain
before
the
Thursday
before
last
Monday
and
I
actually
worked
in
a
RvR
space
Atlantic,
which
is
also
known
as
the
company
who
made
Pokemon
go
but
anyways
so
now,
I'm
kind
of
interested.
In
this.
From
the
perspective
of
answer
that
person
who
didn't
know
anything
about
blockchain,
how
is
it,
how
hard
is
it
going
to
be
to
actually
get
started
on
a
blockchain
project?
B
B
The
first
ten
hits
kind
of
look
like
they're
already
getting
to
the
point
where
it's
like
individual
people
who
are
in
the
space
are
writing
this,
which
may
or
may
not
be
reputable
I'm.
Having
a
question
of
well
like
this
deaq
university,
do
I
trust
this
time?
Does
he
know
what
he's
doing?
What's
the
search
term
at
the
search
term
is
built
a
Tyrian
package,
yep
I
mean
mm-hmm.
C
C
B
B
B
What
I'm
a
little
bit
surprised
here
is
just
how
much
no
aetherium
stuff
I
have
to
install,
and
once
again
one
of
the
question
that's
going
on
through
my
head
and
filter
is
well
like
who's
maintaining
this
package.
If
I
actually
build
a
project
on
this-
and
this
is
a
real
project
that
I
will
have
to
maintain-
is
this
kind
of
work
five
years
down
the
road
so
basically
feels
slightly
sketchy.
B
Now
this
is
fine
I'm,
like
generally
okay,
installing
a
Chrome
extension,
but
as
a
developer,
who
wants
to
get
to
a
hello
world
and
just
run
something.
This
language
is
very
scary,
like
it's
now
telling
me
that
somebody
can
steal
my
stuff
and
like
I'm
thinking
real
money.
I'm
like
whoa,
now
definitely
not
giving
these
people.
My
credit
card
number
and,
of
course
like
this
is
another
friction
point
where
I'm
like
this
is.
This
does
not
feel
like
this
is
getting
me
closer
to
hello
world.
B
B
This
was
a
really
nice
part
of
the
tutorial
that
it
actually
got
two
instructions:
how
to
download
some
code.
I
think
that
does
a
developer.
We
like
to
see
code
so
if
you
can
get
people
to
that
point
where
you
open
something
in
your
development
environment
and
like
that's
a
success
so
here,
I'm
happy
I'm,
generally
happy.
B
The
only
thing
is
that
the
language
I'm,
starting
to
experience,
problems
with
the
language
so
like.
Why
do
we
every
time
we
invent
a
new
computing
pirate
parrot
I'm?
Why
do
we
introduce
the
language?
So
what's
this
migrating
thing,
I
I'm
used
to
deploying
I'm
always
deploying
to
like
my
cloud
services
or
to
like
physical
hardware.
So
it's
better
to
not
introduce
new
words
unless
we
really
have
to
another
thing
that
I
am
experiencing
is
that
the
tutorial
was
published
on
December
10th,
it's
actually
pretty
new
I
would
have.
B
I
would
be
expecting
this
to
just
work
like
great.
This
was
published
five
days
ago.
The
guy
must
have
gotten
latest
in
everything,
but
hey
actually
stuff
did
not
work
so
like
I
was
getting
compilers
from
running
the
code
that
was
in
the
sample.
Application
and
I
was
like.
Oh
wow
I
have
to
read
this
output
and
actually
figure
out.
What's
breaking
and
I've
never
works
with
this
language
of
language
before
not
cool,
probably.
C
B
Yes,
I'm
talking
about
this
I'll
go
on
a
rant
about
the
particular
error
rate
here,
because
it's
telling
me
that
the
syntax
for
constructor
is
deprecated
how
many
apps
use
a
constructor,
all
of
them
so
like
if
I
broke.
My
app
before
this
happened,
and
now
this
happened.
I
would
have
to
change
all
of
this
code
to
use
the
new
syntax.
Don't
do
that
to
your
developers?
That's
not
cool
yeah,
okay
and
rent.
B
B
B
Okay,
nobody
knows
yeah
so
that
that's
that
was
the
boat
I
was
in
I'm
like
well,
if
I'm
trying
this
new
thing
and
I'm
kind
of
not
sure,
what's
going
on,
I
would
like
to
know
if
stuff
succeeded
at
every
step,
where
it's
possible
to
tell
you
that
it
succeeded
here.
I
wasn't
always
insure
so
I'm
kind
of
that
kind
of
person
that
let's
just
try
the
next
step
and
see
what
happens.
Fortunately,
it
did
work,
so
that
was
a
success.
What
we
saw
in
this
previous
page.
B
Thing
said
this
was
the
best
tutorial
available
and
the
number
one
hit
on
Google,
just
saying:
okay,
what
are
we
here?
Oh
now,
we
got
into
some
actually
writing
writing
business
logic
for
for
the
app
the
app
was
imposing
system,
so
we
basically
had
like
a
map
of
candidates,
a
mapping
of
candidates
to
numbers
which
represented
like
how
many
people
voted
voted
for
this
candidate
and
immediately
like
this
should
be
really
simple
right,
but
in
this
language
we
have
a
mapping
construct
that
does
not
keep
track
of
its
own
size.
C
B
C
sharp,
or
maybe
the
JavaScript
I'm
like
why
do
I
have
to
keep
track
of
the
size
of
my
dictionary
or
whatever
table.
That's
crazy.
I
am
as
a
developer.
I'm
not
excited
about
this
I
know.
I
will
forget
to
do
this,
because
this
is
boring,
and
this
is
going
to
cause
bugs
that
I'll
have
to
troubleshoot
and
potentially
like.
Maybe
this
I
will
not
catch
this
book,
and
some
voting
will
happen
in
the
wrong
way,
because
the
system
thought
number
of
candidates
was
not
the
same
as
it
actually
was.
B
I'm
like
it's
good
to
have
usable
language
constructs
what
anyways
after
going
through
that
little
rant
I
did
get
to
the
point
where
I
could
run
stuff,
and
so
this
is
why
we're
getting
into
ganache,
which
is
a
way
to
test
this
locally.
So
basically
we're
running
a
simple
block
chain,
just
in
a
local
machine.
It's
going
to
connect
to
it
from
the
app
and
things
are
happy
in
general.
This
was
actually
a
pretty
smooth
experience,
except
for
the
fact
that
the
tutorial
didn't
really
go
into
details
about
what
all
these
things
mean.
B
So
when
you're
a
first
time
developer,
just
kind
of
like
I
want
to
run
stuff,
there's
a
lot
of
clutter
on
this
page
and
things
look
kind
of
scary.
You
don't
really
understand.
What's
this
TX
account,
do
I
need
to
worry
about
this,
so
hiding
this
would
be
nice
just
kind
of
like
get
me
to
my
hello
world.
B
Cool,
so
the
next
step
in
the
tutorial
was
talking
about
writing
tests,
which
was
actually
super.
Awesome
I
was
happy
to
see
that
a
lot
of
deaf
frameworks
forget
about
testing
and
kind
of,
like
oh
people
don't
write
automated
tests.
Who
does
that?
Well,
that's
not
true.
Automated
tests
are
very
important
for
a
real
project
that
you're
going
to
be
maintaining
for
five
years
and
making
changes
to
so
having
testability
is
great.
Now,
in
this
case,
I
was
kind
of
worried
with
this
text.
B
B
There
were
like
a
couple
of
Stack
Overflow
pages
with
six
outputs,
not
getting
any
confidence
that
this
is
going
to
work
five
years
down
the
road.
So
at
this
point
I
kinda
bad,
that's
the
whole
testing
scenario
like
maybe
it
will
work
out.
Let's
just
get
the
whole
world.
Oh
yeah!
This
was
good.
The
tutorial
got
you
don't
download
a
petshop
app
for
the
blank
sample
code
that
we
changed
to
into
election
app.
B
B
Cool
okay,
so
I
got
through
the
part
of
copy
pasting,
some
sample
HTML
code
for
the
UI
which
built
this
made
me
happy
so
now
we're
trying
to
deploy
and
actually
run
the
UI
and
test
everything
and
see
everything
working.
This
is
going
pretty
well,
except
for
we
have
to
go
back
to
meta
mask
and
this
part
of
the
experience
felt
really
really
janky,
because
meta
mask
is
something
that
I
kind
of
downloaded
and
this
was
associated
with
etherium.
It
had
like
the
Ethier
iam
stamp
on
it.
I
was
expecting
the
user
experience.
B
But
it
was
actually
pretty
bad
so
like,
for
example,
if
you
selected
the
wrong
option
in
the
drop
in
the
drop
down
it
went
to
the
spinner
and
then
clicking
nowhere
on
the
screen
would
get
rid
of
the
spinner
it
just
kept.
Spinning
restarting
the
browser
also
didn't
get
rid
of
the
spinner.
You
would
come
back,
reopen
meta
mask
and
it
was
still
spinning.
I'm
like
oh,
do
I
have
to
like
reinstall
everything
they
have
to
reinstall
my
OS
to
get
back
well,
no,
like
I,
did
more
clicking
and
render
places
on
the
screen.
B
C
B
B
Eventually,
I
managed
to
add
a
past
account
so
that
it
showed
up
on
in
that
screen
and
it
was
kind
of
still
some
of
that
sketchy
experience.
At
some
point,
I
actually
saw
my
testing
account,
which
was
from
the
like
ganache
tool
on
like
running
locally,
and
my
real
account
wish.
I
could
have
like
my
real
ether
in
it.
They
were
in
the
same
drop-down.
One
was
cool
to
camp
one
and
the
other
one
was.
E
B
Yeah
summary
the
pros
it
did
work
so
yeah.
This
is
what
the
developers
want
to
see.
I
think
look
like
if
you
don't
have
number
one
you're,
basically
done.
People
are
not
even
gonna
bother
with
it
testing
frameworks,
great
and
just
the
fact
that
you
have
like
this
thing,
but
you
can
run
on
your
localhost,
but
now
it's
anything
more
complicated
help
someone,
but
there
are
a
lot
more
cons
that
I
definitely
was
throughout.
This
whole
experience
feeling
like
well
I'm
getting
into
some
sketchy
places.
Maybe
the
tutorial
is
not
good.
B
I
would
have
liked
to
see
like
more
officially
branded
tutorial,
to
be
sure
that
the
path
I'm
following
is
the
right
path,
and
it
will
lead
me
to
good
places
for
the
code
because
of
the
kind
of
thing
I
VAP
I
felt
undercooked.
So
a
lot
of
boilerplate
code
right,
the
API
versioning
problems
with
a
constructor
that
did
not
feel
make
me
feel
very
confident
in
the
ability
to
write,
maintainable,
apps
metamath
collects
was
pretty
janky
and
scary.
B
Run
into
that
one,
that's
one's
mine
and
yeah
lots
of
language
that
I
was
not
familiar
with,
and
you
know
like
I
had
ten
ten
years
of
in
software
engineering
experience
so
I'm
like
whoa.
Is
this
like
actually
the
inventing
new
language
for
the
sake
cooking
language?
Why?
Why
is
this
different?
Oh
yeah,
do
you
want
to
talk
about
number
five.
A
No
I
don't
think
we
need
to
go
too
deep
and
do
it
I
think
the
one
that
was
actually
most
interesting
to
me
was
was
that
you
have
so
much
exposure
to
the
meta
mask
CX
justjust,
because
again
it's
sort
of
that
idea
that
you
just
can't
control
it
all
and
and
if
you're
off
off
shooting
something
to
a
third
party.
She
has
this
long
ordeal.
That's
that's
totally
off
your
radar.
Potentially
that
has
nothing
to
do
with
you,
but
that
affects
her
entire
experience.
You
know
thinking
about
the
ecosystem.
A
Thank
you
so
so
I'll
move
quickly
through
through
us.
So,
basically
for
me,
I
ran
through
EOS.
My
experiences
is
on
the
web
stack
and
just
just
did
a
helloworld
tutorial
as
well
ended
up
building
an
ICO
or
ended
up
building
a
token
sort
of
it
had
no
idea
what
it
was.
It
was
a
little
hard
to
figure
out,
but
you
know
again.
My
search
process
is
where
is
the
official
tutorial
I
think
I
found
it?
No
I
didn't
find
it.
A
It's
somebody
who
had
really
good
SEO
and
and
figured
out
how
to
pretend
that
they're,
the
official
tutorial
you
have
all
these
block
producers
who
are
out
there
putting
out
their
content,
pretending
that
they're,
the
official
but
they're
not
or
maybe
they
are
it
was.
It
was
kind
of
confusing
and
I.
Think
I
just
ended
up
going
to
the
to
the
website
and
going
to
the
developer
portal
and
looking
for
something
authoritative,
again,
lots
of
lots
of
infusing
lots
of
downloading
things
them
in
particular,
again.
A
I
know
that
they're
much
newer
than
aetherium,
but
but
they
really
require
you
to
download
a
whole
lot
of
very
specific
individual
things
that
run
very
specific
snippets
of
code
and
your
in
your
command
line,
which
is
something
that
there
was
a
little
I
mean.
I
was
able
to
do
it
there.
Documentation
is
actually
fairly
good.
You
know
the
interface
of
the
documentation
is
pretty
good.
They
have
a
lot
of
code
snippets
and
things
like
that.
But
but
I
mean
it
was
still
it
was.
A
A
Iii
don't
know
C++,
it
was,
it
was
actually
the
first
course
I
ever
took
was
C++,
and
that
was
long
gone.
So
I
have
no
idea
what's
going
on
there,
but
it
seems
reasonable
and
the
problem
is
I
mean
it
wasn't.
Actually
that
exciting
either
his
it
was
I
mean
I,
guess
HelloWorld
is
never
really
supposed
to
be
that
exciting,
but
you
know
sometimes
it's
nice
to
feel
like.
Maybe
someone
tried
a
little
harder
errors,
I,
don't
know,
I,
don't
know
what
was
going
on.
A
A
I,
know,
intellectually
what
they
are,
but
I've,
no
idea
what
role
they're
playing
right
now
in
this
code
so
again
and
and
I
also
the
Stack
Overflow
was
far
less
helpful
for
for
this
than
it
was
for
aetherium,
and
then
the
second
part
of
the
tutorial
was
just
about
putting
together
a
token
I
actually
had
no
idea
what
then
ever
actually
introduced
what
it
was
we're
trying
to
accomplish
I
just
kind
of
figured
out.
Oh
wait:
we're
building,
essentially
a
TRC
20
token
on
on
us.
Okay,
that's
fine,
and
we
ended
up
it
was.
A
It
was
actually
pretty
straightforward
to
deploy
it
and
it
was
pretty
straightforward
to
set
it
up,
but
there
was
never
any
deploy
either
and
I.
Don't
know
it
seemed
ignore
it
ignore
the
snarkiness
did
just
the
quick
overview
of
my
experience
was
I
actually
thought
the
docks
were
actually
pretty
good.
I
think
it's
pretty
clear
that
they
put
in
the
time
to
make
the
documentation
clean,
well-written
it
needed
more
context.
A
It
needed
more
educational
support
behind
it
because,
as
somebody
who's
coming
in
you
know,
you
I
have
a
healthy
dose
of
blockchain
experience,
but
there
are
still
things
that
they
were
talking
about.
That
I
didn't
know
you
know.
Maybe
it
was
their
language,
the
way
they
were
describing
it.
Maybe
it
was
a
new
concept,
it's
hard
to
tell
if
you
don't
have
some
sort
of
link
back
to
some
sort
of
education.
That
kind
of
helps
me
expand,
expand
on
my
knowledge.
You
know
that
kind
of
stuff
is
really
useful
right.
A
Studies
back
obviously
have
a
chance
to
talk
to
the
panelists
a
little
bit
deeper
about
you
know,
moving
beyond
the
beginner
stage,
I
just
thought
it
would
be
useful
to
illustrate
the
kind
of
that
experience
and
sort
of
sort
of
live
live-tweet.
The
experience
a
little
bit
just
so
you
kind
of
get
a
sense
of
what's
going
on
inside
of
our
heads
on
the
the
developer
experience
side.
There
are
some
things
that
are
that
are
pretty
clear
that
are
quite
useful
on
the
high
level.
Obviously
it's
still
it's
still
user
experience.
A
The
way
that
you
want
to,
and
they
might
only
take
a
piece
of
it
and
then
other
people
might
come
in
and
fill
in
the
gaps,
and
then
you
have
this
totally
fractured
experience
and
you've.
You
know
built
something:
that's
not
quite
quite
ideal
on
kind
of
a
micro
side.
Obviously
it's
text,
you
know
so
there's
a
lot
of
stuff.
That
could
be
really
helpful
error
messages.
Please,
please
go
beyond
just
just
the
stack
trace
and
and
tell
me
what
I
should
do
to
like
give
me
something
to
try.
A
You
know:
I
come
from
a
Ruby
on
Rails
world,
where,
where
you
can,
you
can
often
click
through
a
link
on
the
message,
and
it
brings
you
to
a
website
that,
at
least
like
gives
you
some
more
more
stuff
you
could
play
with
in
a
deeper.
You
can
look
into
it
and
you
know
it's
kind
of
hard
to
hard
to
fall
back
and
again,
obviously
we're
we're
early
in
this
ecosystem.
A
But
these
are
the
things
that
I
know
are
out
there
and
I
really
wish
existed
and,
of
course,
the
the
microcopy
and
and
and
really
focusing
on
like
how
can
we
help
people
not
have
to
leave
our
environment
I?
Think
it's
one
of
the
key
objectives
from
from
the
experience
side
is
if,
if
I
have
to
leave
and
go
and
Google
something,
that's
already
a
lost
opportunity,
or
it's
already
gonna
be
a
fracture
in
the
experience.
A
So
I
talk
to.
We
talk
a
lot
about
like
some
of
some
of
the
experience,
the
journey
of
somebody
coming
into
these
platforms,
but
but
it
is
worth
taking
a
step
back
and
acknowledging
that
the
developer
experience
of
blockchain
is
actually
more
than
just
learning
to
use
the
platform
we're
using
the
platform,
because
it's
also
the
experience
kind
of
kind
of
from
a
high
level
that
you
know
there
are
definitely
pros.
You
know
we
spend
a
lot
of
time
talking
about
some
of
the
things
that
we're
challenging
about
it.
A
But
you
know
there
are
also
things
that
blockchain
gives
us,
which
are
some
of
the
reasons
why
we're
developing
on
blockchain
in
the
first
place,
so
I
just
did
want
to
take
a
moment
and
just
highlight
that
you
know
some
of
the
reasons
for
developing
on
blockchain
which
which
come
at
a
cost.
Obviously
you
know
it,
but
it
does
give
us
new
primitives,
like
all
the
identity,
primitives
and-
and
you
know
that
there
are
spam
protections
that
you
know
in
logins
and
identity
that
that
we
can
travel
with
there.
A
You
know
we
can
work
with
micro
transactions.
We
have
instant
finality
on
transaction.
Those
transactions
can
be
peer-to-peer.
You
know
on
the
cryptography
side,
there's
cryptography
all
over
the
place
and
yeah
you
have
to
deal
with
a
bunch
of
keys
and
stuff,
but
from
from
from
the
experience
of
somebody
who
who
might
be
trying
to
build
a
similar
type
of
app
in
the
web
world
and
trying
to
decide,
do
I,
build
it
in
the
web
or
do
I
build
it
on
blockchain.
These
are
the
kinds
of
things
that
actually
make
blockchain.
A
A
Aside
from
that,
you
know
we're
obviously
not
used
to
a
world
where
we
have
to
pay
for
individual
transactions
or-
and
you
know
where,
where
those
transactions
are
gonna,
be
a
thousand
times
higher
than
AWS
so
cool.
Just
a
quick
look
ahead.
I
mean
you
know,
I,
think
it's
pretty
clear
from
the
way
that
we've
been
describing
things
that
yeah
there's
a
lot
to
work
on.
You
know,
I
and
I.
Think
some
of
these
are
coming
down
the
pipes.
You
know
that
there
are
people
who
are
working
on
IDs
that
are
they're
crossing
over
I.
A
Think
God,
you
know,
we've
had
it.
We
had
someone
the
other
week
who
is
doing
that?
You
know
error
messages
is
something
that
I'm
not
I,
don't
know
how
what
my
confidence
level
is.
That
will
improve
this,
because
I
think
there
are
a
lot
of
existing
developer
platforms
that
have
not
improved
it
in
10
years,
but
and
I
think
one
thing
that
it's
really
necessary
to
back.
All
this
up
is
more
education
and-
and
you
know
much
more
conceptual
support
for
people
who
are
coming
into
this
because
everybody's
coming
into
this
new.
A
This,
isn't
this
isn't
like
switching
laterally
across
languages.
This
is
this
is
jumping
into
a
new
paradigm.
So
so
a
real
understanding
of
how
do
we?
How
do
we
put
these
conceptual
models
out?
There
is
something
that
we
have
to
do
and
I
think
we're
beginning
to
do
it,
but
we're
definitely
not
there
yet.
So
thanks
a
lot.
Alright,
everyone,
let's,
let's
get
started
with
the
panel.
A
F
We'll
start
with
my
name's
Victor
and
I'm
working
on
trust,
wood,
so
I,
founded
trust
about
like
14
months
ago,
and
the
problem
for
myself
was
I,
wanted
to
participate
in
the
ICO
and
don't
think
you
have
on
the
market
is
like
way
that
wallet.
So
that's
like
on
the
side
of
user
experiences
like
a
really
complicated
tool
to
use
it's
not
available
in
mobile
and
then
just
like
you're,
not
really
confident
in
the
tools
you
use.
So
at
that
point
they
realized
I,
wanted
to
build
the
wallet
and
I.
F
C
E
B
E
I
joined
Harvard
comm
around
five
months
ago
and
we're
trying
to
tokenized
securities
when,
when
I
got
excited
about
everything
that
was
happening
on
the
blockchain
I
thought.
What's
the
next
real-world
application,
that's
a
no-brainer,
that's
an
actual
application
and
not
speculative
investment.
So
I
started
looking
at
securities
at
tokenizing
houses,
assets,
real.
G
Johan
Trebek
I
work
on
a
project
called
Althea
and
what
that
does
is
it
allows
people
to
set
up
last
mile
internet
access
networks,
sort
of
like
decentralized
ISPs
in
their
communities,
and
so
it
does
that
by
allowing
you
know,
people
who
property
owners
and
other
people
to
set
up
long-range
radio
notes
on
their
property
and
network
them
together
and
then
notes,
basically,
it
paid
per
byte
before
the
amount
of
bandwidth
they
forward
to
other
nodes
in
the
network.
So
as
far
as
the
blocking
space
I've
been
I
was
I
was
a
little
bit.
G
It's
a
blockchain
before
he
theorem,
then
when
Darren
came
out,
I
was
really
interested
in
that
and
so
I've
kind
of
watched
it
like
the
whole
time
and
the
first
time
I
really
tried
using.
It
was
probably
like
you
know.
It's
a
really
embarked
on
this,
like
project
was
maybe
two
or
two-and-a-half
years
ago
and
was
like
you
had
to
take
your
code
and
like
copy
and
paste
it
into
a
website
pilot.
D
Chris
Lee
developer
and
entrepreneur
I
founded
the
4G
labs,
which
works
with
great
engineers
to
build
blockchain
project
and
recently,
since
we
ran
out
of
great
engineers
to
work
with,
we
served
a
few
games,
not
use
ice
I
started
to
work
on
porch
and
since
2017,
so
road,
smart
contract
on
a
severe
metal
quantum
last
year,
and
this
year
went
to
yields
may
be
near.
Protocol
is
the
next.
D
A
Actually,
actually,
but
that's
a
good
place
to
go
forward
with,
because
I
think
kind
of
the
operative
question
here
is:
what
is
your
experience
been
and
you're
someone
who's
developed
on
multiple
platforms
and
so
I'm
quite
curious,
then?
So
what
was
your
experience
with
the
first
platform
and-
and
why
did
you
switch
to
the
second
and
was
that
a
good
switch
Oh.
D
So
this
well,
the
first
of
the
theorem
just
tests,
a
workup,
a
test
of
water
to
learn,
solid
programming
and
then
went
to
quantum.
So
I
was
hired
by
a
project
called
bode
prediction
market
which
builds
a
prediction
market
on
quantum
chain
at
the
time
they
didn't
the
in
infrastructure
builder.
So
we
end
up
building
a
web
three
four
quantum
which
is
called
web
three.
We
call
it
factory
and.
G
D
View
the
our
first
day,
like
Quantum's,
first
step
on
top,
then
now
is
you
as
a
CEOs
I
think
it's
everything
is
like
the
whole
plot
in
industry
is
evolving
use.
You
know
it's
much
faster,
although
is
there's
no
gas
based
it's
much
faster.
The
accomplice
in
the
global
ID
system,
used
by
every
adapts
identities,
is
one
step
of
West,
but
further
to
the
broad
chain.
Usability
are.
A
D
D
A
G
G
Etherium
I
mean
it's
I
think
it
has
like
a
critical
mass.
So
for
us
it's
very
that's
it's
very
much
reality,
because
our
system
actually
uses
Aragon,
which
is
a
kind
organizational
platform
on
aetherium
and
so
for
us.
If
a
platform
doesn't
support
EVM,
it's
gonna
be
hard
for
us
to
use
it.
There
are
a
lot
of
issues,
of
course,
with
it
we
want
to
use.
We
want
to
use
cosmos,
but
cosmos
doesn't
support
EVM.
Yet
so
we're
still
that's
interesting.
D
E
Terrifying,
not
not
only
you're
worried
that
the
code
you're
putting
out
there
is
final,
even
though
there
are
ways
to
upgrade
contracts.
You're
you're,
not
not
only
you're,
worried
that
if
there's
a
bug,
your
users
might
actually
lose
money,
but
then
the
whole
build
stack
is
very
disjointed.
It
works.
You
can
make
it
work,
but
this
lovely
young
lady
was
saying
the
output
you
get
from
the
debugger
is
really
bad.
E
C
E
Of
gas,
yes,
I
want
to
know
why
it's
harder
to
get
through
that
the
debugger
support
is
in,
isn't
there
there
was.
There
was
one
project
that
came
out
like
four
or
five
months
ago.
That
was
really
good
and
then
a
blotching
project
hired
that
guy
and
he
stopped
updating
it
on
github
and
there's
like
a
warning
sign
that
says.
D
E
D
F
So
I'm,
basically
the
bridge
between
the
users
and
Austin
developers.
So
the
way
we
do
work
with
wall
into
that
we
have
the
connection
to
the
blockchain
straight,
so
we
have
ability
to
connect
electron
or
a
theorem,
and
so
our
goal
as
a
wallet
provider
to
provide
as
much
information
possible
today
and
user
like
how
much
did
to
have
an
imbalance.
What
kind
of
transaction
did
was
the
state
of
a
transaction
and
the
more
that
you
can
show
the
user.
F
F
People
just
mentioned
it's
like
there's
no
error
codes,
and
so
that's
what
we're
getting
from
the
users
they're
trying
to
like
send
a
token
or
do
something
breach
and
they're
like
complain
to
us.
Oh,
this
has
failed
like
why,
and
so
we
need
to
explain.
Oh
here's,
why?
Like
because
you're
the
smart
contract
is
freezed
and
we
tell
them
like
you
need
to
talk
to
them
as
more
contra
owner.
C
C
F
Of
issues
that
have
come
up
I
think
there
was
more
often
when
there
was
like
I
chose,
because
the
smart
contracts
were
creased
in
the
first
month
until
Daisuke
is
over,
so
transactions
were
like
failing
and
user,
wouldn't
know
like
why,
so
it
was
really
good
if
we
can
actually
show
it
to
them
like.
Oh
here's.
The
reason
why,
and
so
one
of
the
things
we
currently
facing
went
like
a
deer,
for
example,
because.
F
They
just
want
to
see
hold
the
tokens
they
own
in
order
to
know
like
which
tokens
user
actually
owned.
We
need
to
go
through
the
whole
blockchain
and
see
what
transfers
happened
to
this
specific
address,
and
this
is
like
really
complex
operations,
so
you
need
to
have
indexers
on
top
of
each
block
chain
here
or
to
actually
see
so
they,
like
they
noted
here,
wouldn't
support
that
and
there's
many
like
small
things
that
would
be
really
cool
to
have
on
the
bottom
right.
F
F
F
So
how
open
source
tool?
It's
called
trust
rate
that
allows
you
to
set
up
your
own
instance
and
then
it
will
basically
go
through
every
block
with
record
all
the
transaction
that
happen
for
like
specific
user
right.
So
if
you
send
here
C
20
token,
it
will
try
to
fetch
the
information
about
the
tokens
story
on
the
in
database.
F
So
we
use
like
one
go
to
pieces
to
store
and
then
we'll
also
have
a
mapping
called
all
the
tokens
that
each
user
own
and
so
I
think
it's
really
complicated,
and
you
know
in
order
to
sing
that
note.
It
will
take
me
like
two
weeks
to
do
it,
so
you
need
to
like
go
through
every
block
and
just
like
5
million
blocks
already.
So
you
know.
F
C
F
E
For
us
query
is
also
a
problem,
and-
and
there
are
many
tools
there
out
there-
that
do
things
like
reading
about
blockchain
and
then
putting
it
on
graph
QL
or
putting
it
on
manage
regular,
our
DVR
at
DBS.
So
it
was
it
was.
It
was
hard
for
us
to
choose
how
to
do
that
and,
and
at
the
same
time
run
a
note
that
that
we
can
always
have
running
so
that
that's
hard.
E
Key
management
is
also
hard
when
you
have
contracts
that
so
our
our
company
just
created
our
first
offering
it's
still
open,
it
hasn't
closed
and
after
it
closes,
then
we
mint
and
that's
when
arts
more
conscious
lives
are
going
to
be
used
for
the
first
time
so
going
going
through
the
process
of
defining
how
to
manage
our
keys.
We
have
specific
wallets
that
control
that
have
godlike
powers
in
certain
contracts.
So
so
that's
really
scary.
E
G
We've
got
to
build
our
own
transaction
library,
for
it,
for
rust
and
specifically
for
for
routers,
usually
have
like
armed
32-bit
or
MIPS
CPUs,
and
so
we
wanted
to
use
parody
for
who
use
rust.
So
we
thought
parodies
rust,
you
know,
and
so
we
we
tried
it
out
and
it
doesn't
support
anything
besides
like
64-bit
x86,
and
so
we
I
thought.
We
first
tried
to
like
correct
this
stuff
in
parody,
but
it
was
too
big
the
job,
so
we
built
our
own
can.
G
Sorry
three
levels:
so:
okay,
so
basically,
if
your
transaction
needs
to
have
a
signature
on
it,
so
the
block
she
knows
is
valid
and
the
existing
the
existing
libraries
that
will
that
there
are
really
no
existing
libraries
that
will
work
on
routers,
and
so
our
software
works
on
routers
is
for
the
Internet.
Routers
have
slower
CPUs
because
they
always
want
to
save
money
on
the
CPU
and
put
that
money
into
the
radios
and
network
cards
itself.
G
D
I
think
two
things:
first,
the
the
web
who
WebSocket
like
Victor,
mentioned
the
push
notifications.
So
as
a
game
developer
like
we
are
on
the
top
publisher
of
the
on
the
stack
a
while
I,
don't
think
we
should
go
to
I,
hosted
a
non
producing
nodes
and
build
up
the
wrapper
around
it
and
put
your
notification.
Somebody
should
have
done
that
for
us
yeah.
Ideally,
some
companies
are
working
them
on
that
I
haven't
tried,
their
API
is
actually
I
haven't
tried
about
a
due
to
the
network.
D
Latency,
it's
not
ideal
for
us,
so
our
gaming
is
kind
of
a
fall
behind.
Like
me,
in
terms
of
speed
on
that,
that's
one
problem:
I
need
to
solve
the
other
problem
for
games.
Is
the
feed
channel
like
we,
we
incubated
the
project
is
this
in
game
company
game
platform?
They
want
to
build
like
a
put
their
game,
some
blockchain.
Those
are
really
great
games
like
with
good
animations
game
mechanics,
but
their
problem
is
that
they
have
16
million
registered
users.
There
are
no
one
knows
how
to
use
blockchain
like
cryptocurrency.
D
A
So,
in
theory,
we're
decentralized,
but
in
practice,
what
what's
centralizing
shortcuts
have
you
had
to
take
because
decentralization
didn't
didn't
quite
work.
The
way
it
needed
to
I
guess
one
example
that
I'm
thinking
of
is
using
a
trusted
node,
for
instance,
as
an
access
point
into
the
blockchain,
which
is
which
is
reasonably
common.
These
days,
you.
F
Know
I
think
is
pretty
common,
especially
for
the
wallets
right,
so
that
you
have
basically
two
options.
You
either
implement
the
lightning
or
light
node
which
usually
pretty
for
the
end-user,
so
I
think
good
example
with
the
red
wallet
they
have
light
notes
for
both
like
Bitcoin
than
the
con
cash.
So
in
order
to
sync
up,
it
will
take
you
around.
You
know
maybe
like
an
hour
or
two
at
least
so.
F
You
need
to
have
your
phone
open
for
like
two
hours
and
we're
going
to
sync
that
up
right,
so
I
think
that's
the
benefit
and
we
like
to
get
the
security,
because
it's
SPD
client.
At
the
same
time,
you
lose
the
flexibility
of
like
syncing,
so
you
can
send
foreign
transaction
right,
so
we
currently
using
you,
know
the
trusted
notes
or
we
just
connect
to
them.
It's
simplifies
for
the
end-user
because
they
are
you
able
to
see
their
balances,
make
the
transaction
straight
away,
but
at
the
same.
C
F
You
know
like
we,
basically
the
gate
which
will
kind
of
keep
that,
but
at
the
same
time
we
want
to
like
provides
ability
for
anyone
to
use
any
notable
set
up.
Obviously
no
one
will
do
it
because,
like
a
few
users
will
complain,
but
the
same
time
I
think
it's
okay
for
now,
as
a
first
step,
but
the
same
time
we'll
build
more
technology
in
the
future
which
allows
you
to
be
like
fully
decentralized.
So
as
long
as
you
have
the
internet
connection,
you
can
just
sync
up
easily
at
the
moment.
C
F
So
on
the
peer
network
will
have
like
in
Europe
and
so
I
think
this
is
the
centralized
point
at
the
moment,
because
there's
no
other
notes
to
use
it.
The
other
problems
that
like
thinks
that
computer
build
it's
not
open
source,
so
you're
not
even
able
to
run
their
own
notes.
If
you
try
to
run
your
own
note,
you
will
die
just
like
really
quickly,
because
it's
not
optimized
for
requests.
F
So,
like
a
trust
wallet,
we
have
around
like
don't
request
a
second
just
for
the
note
itself,
so
doesn't
means
that
if
you
run
regularly
like
go
note,
it
will
just
die
because
it
won't
be
able
to
process
it.
So
you
need
to
build
the
caching
layer
in
front
to
be
able
to
like
surf
requests
and
that
stuff
and
there's
not
a
really
good
solutions
out
there.
We're
currently
working
like
with
a
few
companies
to
build
it.
C
C
C
E
G
Well,
for
us
we
haven't,
we
haven't
hit
the
kind
of
scale
where
our
full
noes
have
died,
like
you
was
saying
so
are
we
have
two
networks
right
now
and
they're,
pretty
small
like
less
than
40
people,
so
we
actually
in
our
system.
We
have
something:
that's
called
an
exit
node,
which
is
kind
of
like
a
VPN
server,
so
that
since
you're
you
may
be
buying
banned
from
your
neighbors
and
stuff.
G
G
D
C
D
My
problem,
my
problem,
was
that
I
I
wrong
nose
in
Hong
Kong,
that's
serving
that
like
serving
the
Chinese
users
and
it's
really
slow.
It
become
really
useful.
He
use
every
master,
knows
clothes
there
of
endpoint
and
there's
a
there's
one
company
ability
it's
like
proxy
Messer
that
that's
just
one
endpoint
you
talk
to
it
automatically
select
the
faster
note
that
you
can
connect
to
which
is
really
great.
So
it
saves
me
a
lot
of
time
and
energy
yeah
just
point
to
just
one
endpoint.
D
A
On
ask
one
more
question,
but
and
I'm
gonna
see
you
guys
to
ask
questions
as
well,
so
I
hope
you
can
think
of
some
good
ones,
so
you
have
had
a
chance
to
ramp
up
to
or
you
you've
had
a
chance
to
hire,
developers
and
and
and
I
know,
I'm
sure
you
guys
have
as
well
either
hired
or
work
with
developers
who
are
new.
So
so
what
are
the?
What
are
the
most
challenging
parts
of
ramping
up
new
developers
in
your
teams
and
getting
them
up
to
speed
I.
D
F
I
think
person
looks
away,
yeah
I
like
higher.
Usually
people
is
that
I
look
for
interest
in
the
blockchain
itself.
I've
read
sure
no
one
has
experienced
would
like
not
working
with
the
blockchain
itself,
because
you
know
it's
really
new
everyone
just
coming
from
different
backgrounds,
and
you
know
it's.
F
And
interest
in
a
blotchiness
all
right,
because
you
want
people
who
will
come
to
the
market
who
will
understand,
you
know
the
importance
of
the
blockchain.
You
know.
Do
centralization,
however,
works,
and
they
should
be
also
involved
into
perk
tips,
or
they
should
own
it
right
if
they're,
not
only,
then
they
wouldn't
have
any
incentive
to
build
like
things
on
top
right.
So
this
is
all
the
point
of
the
community
said
that
we
have
tokens
to
people
gonna.
F
Have
that
token
and
they're
like
part
of
any
community,
and
so
are
always
looking
people
for
interest,
so
they
have
something
that
kind
of
connects
them
with
the
product
because
of
this
down
market.
Many
people
just
leave
the
market
just
because
you
know
like
what's
the
point
like
I
lost
over
money,
it's.
A
F
I
think
there's
always
challenges
around
like
explaining.
You
know
how
the
block
chains
are
working
right,
like
even
concept
like
what
the
block
is
with
the
consensus
is
I
think
they
basically
give
like
full
overview
on
how
the
mechanism
works
with
a
bob
chain
the
importance
and
how
everything
is
connected.
Since
we're
mostly
focused
on
a
mobile
site,
we
only
intern
with
nodes
itself.
We
don't
do
the
smart
contracts,
part,
so
I
think
you
live
at
different
prices.
I.
E
C
E
Simple
contract,
we
want
you,
we
don't
want
this
to
be
completed
and
it's
entirely.
We
just
want
you
to.
We
just
want
to
see
how
you
react
to
touching
this
technology
for
the
first
time
and
then
coming
coming
here
for
an
interview
and
talking
about
what
decisions
you
make
so
half
of
the
folks
that
that
come
to
us
and
say
hey
I,
want
to
work
on
blockchain.
Don't
even
finish
that
assignment
and
just
disappeared,
I
mean.
E
F
E
A
E
Before
thinking
of
your
contract
of
your
app
as
app,
it
actually
needs
to
work
first
and
all
of
the
stuff
we
do
are
related
with
complying
with
securities
law,
so
our
contracts
have
to
be
ironclad.
We
we
shoot
for
a
hundred
percent
test
coverage,
so
everything
we
do
every
time
we
touch
a
smart
contract
to
people
they're
on
it
and
we
test
drive
it.
E
G
F
F
C
D
F
A
sting
chain
for
example,
example:
boy:
did
you
water,
it
smart
contract
and
they
have
like
fifty
thousand
dollars
on
the
contract
that
were
stolen
in
order
to
article
smart
contract
that
they
wrote,
it
would
cost
him
$50,000.
So
it's
interesting
like
how
would
you
find
that
balance
if
it's,
neither
or
not
yeah.
D
Yeah
but
I
wanted
sugar-coated
like
once
you
get
it
good
at
it.
I
guess
smart
country
to
the
program
is
it's
not
complicated
because
there's
no
like
a
you
know,
largest
updater,
did
are
related
to
smart
contract
program.
You
can
deceive
I.
Can
large
data
there's
not
much
data
processing
that
can
you
won't
mean
that
so,
but
basically,
as
I
said,
like
you
just
do
the
common
team
comment
all
the
rest
of
the
code
and
it's
uncommon,
the
more
line
by
line
to
figure
it
out.
F
G
F
G
C
A
E
A
D
G
G
The
code
you're
like
Cody
writing
and
in
most
systems
there's
like
pretty
well-defined
places
where
the
public
is
interacting
with
it,
and
if
you
guard
it
where
the
public
is
interacting
with
it,
then
you
might
be
okay,
but
with
a
smart
contract,
every
part
of
the
contract
public
is
interacting
and
so
I
think
that's
part
of
it
plus
the
centralized
system.
Something
goes
wrong.
A
lot
of
things
that
go
wrong.
G
C
A
D
I'll
do
the
security
exchange
next
year
so
never
well.
We
have
buta
an
exchange
before
it's
like
the
OTC,
so
have
that
experience
so
I'm
gonna
work
with
a
agrea
founder
to
build
out
a
security
exchange.
Well,
tech
part.
There
are
a
lot
of
challenges
in
tech
part.
It's
is
enterprise,
change,
it's
not
public.
It's
the
transaction,
our
own
chain,
but
identities
are
detached
from
the
transactions
and
the
exchange
is
essentially
so
the
publisher,
the
transactional
down
to
the
enterprise
chain
so
yeah.
This
is
interesting.
E
E
Developers
on
Stack
Overflow
answering
answering
question:
there's
tons
of
meetups
there's
lots
of
hackathons
core
developers
are
very
accessible.
If
you
find
something
really
weird
and
you
need
to
talk
about,
you
can
go
to
every
develop
well,
most
developer
calls
if
you
want
it's
about
getting
support
from
the
developer
community,
because
there's
no
single
entity
that
is
keeping
the
network
running.
There's
multiple
teams
working
sometimes
on
solving
the
same
problem
to
see
who
gets
there
first
or
better
so
I
will.
G
Yeah
I
think
that
having
a
large
develop
developer
community
can
sort
of
paper
over
a
lot
of
flaws,
because
you
know
mostly
you're
trying
to
solve
a
blog
you're
trying
to
go
on
Stack
Overflow.
Look
it
up
so
having
those
answers
that
helps
a
lot.
I
would
look
at
besides.
That
I
would
also
look
at
just
the
ease
of
use
for
the
end
user
because
that's
been
something
that
we've
run
into
because
our
end
users,
and
not
people
who
are
savvy
with
cryptocurrencies.
G
It
hasn't
been
too
big
of
an
issue
with
aetherium
for
parts
parts
of
our
stuff,
like
what
madam
asked
is.
Definitely
not
a
very
friendly
experience
for
people
so
like
she
was
saying,
and
then
another
thing
was
just
just
another.
Random
example
is
the
the
gasps
Andy
theorem
is
is
hard
to
understand
if
you're
using
another
token,
so
we're
using
die.
G
If
you
got
to
tell
somebody,
you
know,
here's
how
you
use
here's
they
use
die,
that's
simple
I
mean
that's
like
PayPal
has
dollars
in
it
like
it's
just
dollars
right,
but
then
there's
a
second
thing.
It's
called
ether
I'm
like
you
need
this
to
turn.
It
into
gas,
which
is
like
major,
you
know
in
way,
okay,
you
know,
and
then,
if
you
I'm
gonna,
give
you
I'm
going
to
send
you
this,
you
can
try
it
out,
but
I'm
gonna
also
send
used
ether
and
then,
if
you.
G
You
have
some
some
ether
to
otherwise
they're,
not
gonna,
be
able
Sunday
like
it's
pretty
bad,
so
we're
we're,
probably
gonna,
add
some
when
we
do
switch
to
die
in
production.
We're
gonna,
add
some
stuff
to
our
contracts
that
let
them
do
gasless
transactions,
but
it
would
be
really
nice
if
those
like
built-in
understand.
F
It
yo
says
some
it's
kind
of
funny
before
you
get
the
died
in
the
ether
you
need
to
like
take
a
selfie
and
register
for
the
exchange
and
all
that
there's
so
many
other
steps.
Well.
I
personally
would
like
focus
on
a
few
things.
I
guys,
like
I,
think
the
communities
like
the
most
important
thing
right
now,
but
the
other
problem
is
that,
like
even
if
you
build
it
like
the
question
is:
is
there
any
users
to
use
it
right?
So
there's.
C
F
Us
has
more
users
or
like
Ron,
for
example,
right
if
you
compare
to
like
you,
do
them,
but
the
same
time
theorem
has
this
drawn
this
community
I
think
it's
all
about
like
solving
some
problems
the
same
time,
so
you
can
even
will
build
good
POS
system.
Then
it
means
that
it
will
have
more
volume
for
transactions
and
it
will
allow
you
to
do
like
Dax
is
right
or
some
other
examples
that
will
work
for
the
end
user,
because
if
you
want
to
use
tax
at
the
moment,
you
know
it's
really
slow
transaction.
F
E
Try
to
hold
the
hands
of
the
user
as
as
much
as
we
can
when
they
are
onboarding.
When
you
come
to
our
platform,
we
talk
about
the
offering
and
like
we,
we
present
you
everything
that
you
need
to
know
in
order
to
determine
or
whether
or
not
you
can
invest
in
that
offering
and
we
guide
them
through
the
process
of
getting
accredited
and
there's
that's
something
that
they
do
on
our
platform
and
they
don't
touch
anything
related
to
the
block.
E
E
E
And
that's
something
we
never
stored
that
they
store
it
themselves,
but
we
we
guide
them
through
baby
steps
so
that
they
get
acquainted
with
the
technology.
It's
not
hey.
You
need
made
a
mask,
hey,
you
can
eat
this.
Other
thing,
hey
is
hey.
This
is
what
we're
doing?
Can
you
invest?
Do
you
want
to
the
best?
Yes,
okay,
can
you
invest
and
you
go
through
accreditation
and
then,
a
few
days
later,
let's
set
up
your
wallet
X
months
later.
Here
are
you
tokens?
Oh
I
want
to
go
to
at
least
on
July
6th
age.
E
D
E
C
F
So,
for
us,
for
example,
would
actually
start
training
them
before
they
join
the
team.
So
all
the
homework
would
give
its
all
related
to
the
current
production
code.
So
one
of
the
homework
I
give
them
is
about.
You
know
integrating
the
new
chain
also
a
little
like
here's
the
chain.
You
can
pick
any
chain
from
this
list
and
I
tell
them
like
it'll
take
around
like
five
hours
or
so,
and
then
it
usually
takes
around
like
25
hours.
F
Think
it
depends
on
which
stage
choose
your
company
is
ready
to
you're,
really
small.
You
only
find
people
sure
I
mean
you
can
take
a
January
developer,
but
then
the
questions
like
who's
going
to
be
spending
time
working
with
him.
So
I
think.
If
you
use
skill
big
enough,
you
have
enough
resources
to
do
it.
Definitely
you
will
do
it,
but
for
small
teams,
I,
don't
think
that's
going
to
work
well,
especially.
G
Yeah,
you
need
to
have
at
least
somebody
on
your.
We
have
like
four
developers,
and
so
you
need
someone
on
your
team.
Who's
like
immersed
in
the
blockchain
ecosystem,
so
have
like
three
three
people
work
on
on
blockchain
stuff,
but
one
of
them
is
like
a
frying
guy
who
touches
the
blockchain
stuff,
another
one's
the
guy
working
on
the
rust
libraries
types
of
blocking
stuff.
We
also
have
a
guy
who's,
just
really
into
blockchain,
that's
necessary
to
have
that
sort
of
to
have
someone
who's
like
really
into
it
intrinsically
just
so.
G
E
F
I
think
it's
important
to
pick
a
problem.
You
know
personal
when
I
joined
blockchain,
you
know,
I
was
like
doing
token
sales
and
like
participating
in
you,
know
just
buying
crypto
right,
but
when
I
started
coding,
I
thought
that
I
wanted
to
build
a
wall.
For
me
personally,
the
good
start
is
to
have
that
idea.
What
I
wanted
confident
with
watching
and
then
it
just
kind
of
follows
right
because,
like
how
do
you
build
a
wallet?
And
then
you
start
finding
tools,
you
know
plugins
or
like
open
source
code,
and
you
can
start
using.
F
E
Started
looking
to
engage
with
companies
and
every
company
that
I
went
to
and
knocked
on
his
door,
hey
hi
I'm,
a
man
I'm,
a
software
engineer,
I'm
learning
solidity:
these
are
the
things
I've
done.
Can
I
spend
some
time
in
your
office
and
help
you
with
with
with
anything
you
need,
and
most
most
people
will
say:
yeah
comfort
they
in
hack
with
us
and
I
hadn't,
seen
that
before
and
in
my
professional
career,
so
look
look,
look
for
a
problem
like.
C
F
F
F
A
We
think,
thank
you
guys.
I
have
one
final
thing:
we've
talked
a
lot
about
challenges
in
the
ecosystem
and
like
what's
scary,
and
things
like
that,
but
I
I'm
also
curious
about
gratitude.
You
know
so
so
what
are?
What
are
the
things?
The
tools
is
there
something
that
you,
you
are
most
grateful
for
in
in
the
ecosystem.
Right
now
that
you're
a
part
of
well.
D
There
are
some
designers
sitting
out
there,
so
I
will
say:
I
appreciate,
I,
appreciate,
good
designs,
so
I
remember
the
ether
than
were
in
the
beginning
of
the
year.
That's
the
way,
I'm
mad
at
Victor.
Rita
really
asked
me
to
do
a
user
testing.
Iii
spent
I
seen
there
15
minutes
couldn't
find
where
to
open
the
water.
It's
really
really
like
the
famous
washing
project,
because
they
they
hide
in
the
sidebar,
there's
a
like
there's
a
bottom,
but
it
doesn't
look
like
a
bad
thing.
You
need
to
click
off
to
expand.
G
Would
say
like
I
think,
just
in
general
likes
like
ëthere
him
and
and
and
solidity
when
it
came
out,
I
mean
people
were
thinking
about
programming,
block
chains
in
a
whole
different
way,
which
was
much
less
flexible
and
and
harder
to
use,
and
it's
really
open-ended
and,
and
that
brings
with
a
lot
of
a
lot
of
danger
and
vulnerabilities
and
stuff,
but
also
just
when
it
came
out
of
just
you
know.
Having
like
this
is
a
program
you
can
write
and
it's
going
to
run
on
the
blockchain.
G
E
Pretty
grateful
about
what
I
mentioned
earlier,
that
the
community
is
very
open
to
allow
new
people
to
come
in
and
help
them
with
the
project
and
like
I,
had
access
to
people
that
are
working
on
the
wasum,
EVM
and
and
that
guy
just
been
an
afternoon
talking
to
people
who
were
just
getting
started
on
it.
So
I
see
that
every
single
time
I
go
to
a
hackathon
I,
see
that
every
single
time
I
I
go
to
a
company.
C
F
Things
safe
for
me:
I
think
that
people
are
really
open.
So
then
you
can
pretty
much
find
anyone
in
developer,
community
buzzing
telegram,
and
you
can
just
message
him
any
time.
Ask
questions
and
he'll
have
me
out
and
then
but
I
appreciate
people
who
come
to
crypto
for
just
an
investment.
I
think
this
is
the
worst
people
you
would
probably
see
in
the
market.
They
complain
so
much
developers.