►
From YouTube: Developer Spotlight: Tal Muskal - LiquidApps CTO
Description
LiquidApps CTO Tal Muskal joins Zack Gall to discuss his background as a developer and entrepreneur. They discuss Dan Larimer, distributed systems, mesh networks, multi-layered services, man-machine collaboration, immortal applications, and Tal's vision for LiquidApps and the DAPP Network.
https://www.liquidapps.io
https://t.me/LiquidAppsOfficial
https://twitter.com/LiquidAppsIO
https://twitter.com/tmuskal
Everything EOS is the longest running EOS podcast. Zack Gall and Rob Finch go in-depth on EOS dapp news, EOS VC announcements, dapp funding announcements, EOSIO upgrades, EOS mainnet news, EOS side chain news, and so much more.
***
Series Sponsor:
Cypherglass - https://www.cypherglass.com
https://www.eosnameservice.io
For more information on sponsorship opportunities or content partnerships, please contact zack@everythingeos.io
https://www.EverythingEOS.io
https://youtube.com/c/Everything_EOS
http://t.me/Everything_EOS
https://anchor.fm/everythingeos
https://itunes.apple.com/us/podcast/everything-eos/id1434560651?mt=2
A
A
B
A
Ages
ago
it
was,
it
was
right
after
the
DAP
network
launched
a
little
over
six
months
ago,
back
in
March
and
little
did.
We
know
where
we
would
be
six
months
later,
myself
and
Peter
K
are
now
with
liquid
apps.
The
services
built
on
top
of
the
network
has
grown,
but
I
don't
really
we'll
get
into
that
network
stuff
and
liquid
app
stuff.
But
what
I
really
wanted
to
talk
about
today
is
Thomas
cow,
because
this
is
actually
honestly
it's
it's
a
treat
for
me.
A
If
the
legends
are
true,
ii-I've
heard
things,
I
saw
Saeed,
Jaffrey
'he's,
calling
you
out
as
being
a
genius
in
in
telegram
it's
it's.
Definitely
something
I
believe
and
I
think
after
this
conversation,
I
think
other
people
might
might
get
a
better
idea
of
the
legend
that
is
thomas
cow.
So
who
is
thomas
cow.
B
A
A
B
I
think
that's
a
Tillamook,
a
pretty
accurate
way
to
describe
and
a
hacker,
not
in
a
you
know,
malicious
kind
of
way,
but
the
hyper-intense
that
I
love
taking
system
and
reuse
them
for
for
other.
You
know
other
things
they
weren't
exactly
designed
for
or
I
think.
That's
that
that's
kind
of
the
way
I
I
think.
B
First
yeah
so
I
think
it
kind
of
maybe
grow
out
of
proportion.
A
little
bit.
Some
people
were
saying
that
I
I
built
it
but
I.
Actually,
our
chief
scientist
in
insane
Monty
net
was
was
the
a
guy
who
built
it
and
he
came
to
me
and
use
my
help
to
scale
it
basically
from
chroma
single-threaded
application
to
distributed
system,
because
that
that's
that's,
the
kind
of
things
with
them
are
familiar
with.
A
A
You've
done
some
impressive
things.
You
mentioned
it
a
little
bit
ago.
A
company
called
semantic
net.
Is
that
how
I
say
it
submitted
not
yeah?
You
sent
me
some
information
about
what
you're
building
there
and
it
I
almost
got
the
idea
that
you
were
on
the
right
path,
but
you
were
too
early
on
this.
Like
could
you
kind
of
describe
at
a
high
level
what
you
built
like
what
this
is
over
ten
years
ago,
this
company
called
semantic
net,
which
is
one
of
your
previous
projects.
Years
ago,
yeah.
B
A
Particular
piece
right:
there
you
sent
me
some
documents
and
it
almost
looked
like
you're
doing
like
things
that
Siri
does
today
like
you're
prettier,
like
AI,
like
personal
assistant,
that's
kind
of
what
you
were
building,
but
back
in
like
2006
2008
like
in
that
timeframe.
You
started
building
this
and
it
was
like
what
a
Firefox
extension
I
think
is
what
I
read
yeah.
B
But
we
were
back,
then
it
wasn't
that
popular
to
be
a
platform.
Basically
it's
a
business
strategies,
so
everybody
told
us
you
need
to
build
to
build
a
killer
application,
something
that
will
will
showcase
the
power
of
the
of
this
platform
and
basically
we
we
we
failed
with
with
that
product.
It
didn't
really
it
couldn't
really
grasp
the
potential
of
such
a
platform
and
I.
Think
one
that's
one
of
the
reason.
The
entire
vision
of
the
Semantic
Web
failed
up
until
this
day.
It's
not
it
didn't
fulfill
itself,
because
there
was
a
lack
of
incentives.
B
There
was
a
lack
of
killer
application
because
the
entire
power
from
from
that
comes
from
from
the
long
tail,
the
long
tail
of
connectivity
that
you
can
do
with
with
with
all
those
thousands
of
data
sources,
on
the
other
hand,
for
every
killer
application,
someone,
someone
just
filled
something
that's
tailored
there,
and
then
you
don't
need
that
kind
of
flexibility.
So
we
reflect
that
that
kind
of
incentives
to
be
able
to
build
a
horizontal
killer
application
I
think
maybe
it
will
be
back
some
someday.
B
So
what
what
I
did
was
like
a
little
application
that
you
would
you
the
hum
a
song
that
you
couldn't
get
out
of
your
head
and
it
would
recognize
the
sound
basically
back,
then
they
weren't
even
mp3s,
or
any
way
to
monetize
anything
on
the
Internet.
Nobody
even
really
used
the
internet
yet
like
if
they
come
on
audience,
and
it
taught
me
a
really
great
lesson
about
less
than
about
coming
coming
too
early.
A
That
what
you
just
described,
that
there
there
is
an
app
that
was
popular
I,
did
that
with
like
a
song
on
the
radio.
It
would
tell
you
what
the
song
was
called
but
you're
saying
in
1996.
You
had
something
that
didn't
have
to
hear
the
actual
song,
just
like
the
tune
of
it,
the
humming
it
yes,
yeah
sane.
B
You
know
from
things
that
you
that
they
needed
myself,
we
love
music
and
you
know
I
wanted
it
and
I
Willie
and
then
people
I
had
had
some
mentors.
That
told
me:
listen
if
you
want
to
be
in
the
business
out
of
it,
you'd
need
to
think
of
a
way
to
monetize
it
and
then
I
got
my
and
then
I
had
to
join
the
army.
Basically
I
had
to
shut
it
down.
A
B
B
B
Basically,
I
joined
a
company
that
did
embedded
real-time
development
or
Wi-Fi
mesh
network.
So
that
was
my
first
time
that
I
did
I
basically
got
to
work
on
on
the
distributed
system
and
got
to
think
you
know
in
a
distributed
perspective.
I
did
use,
you
know,
peer-to-peer
file-sharing
services,
but
back
in
the
day
in
Israel
it
was
very
common,
and
so
it
was
familiar
with
the
technology
and
I
did
some
emule
patches,
but
back
in
the
day,
but
but
that
was
the
first
time
I
really
got
to
work.
B
You
know
from
the
bits
and
bytes
and
trying
to
to
make
a
distributed
system
much
much
better,
and
it
taught
me
certainly
quite
a
lot
both
on
the
aspects
of
operating
system
development,
because
back
then
strenghten
companies
worth
using
open
source
software
to
run
embedded
systems.
They
were
using
other
commercial
operating
systems.
B
It
was
a
they
weren't,
using
Linux
and
or
embedded
Linux
back.
Then,
which
I'm
canvases
to
2004
yeah,
so
we
we
kind
of
I,
I
kind
of
somehow
I
convinced
the
team,
even
though
I
was
very
young,
I
convinced
it
even
in
that
space
I
convinced
the
team
they
would
to
consider.
Taking
this
amazing
change,
that's
open
and
trying
to
build
a
product
with
with
it
like
a
real
hard
wall
product,
that's
working
and
shift
to
consumers,
so
we
were
kind
of
pioneering
in
that
space
without
without
really
knowing.
B
A
So
you're,
basically
like
in
the
weeds
from
the
transition
of
everything,
was
closed
source
so
once
like
open
source
started
becoming
more
and
more
acceptable
and
then
do
you
feel
like
blockchain
and
like
these
incentivized
like
economies
and
systems,
is
like
the
next
step
of
open
source.
Definitely.
B
The
next
iteration
yeah,
it's
exactly
that
I
think
that's
that's
one
of
the
things,
one
of
the
amazing
things:
models
in
general
licensing
models
and
incentive
models
around
the
open
source.
That
was
always
interesting
to
me.
If
is
the
kind
of
system
that
allows
people
to
collaborate
in
the
first
place
and
why
to
release
open
source
other
than
kind
of
like
a
gift
economy.
Kind
of
thing
were
it's
never
as
good
as
the
competitor
that
held
you
know
they
have
a
lot
of
resources
and
always
be
project.
B
Basically,
it's
a
software
license
that
back
then
it
it.
It
was
very
efficient
in
enforcing
people
to
bring
back
to
contribute
back
fixes
and
changes
and
enhancements.
They
didn't
in
an
open-source
project
and
that
led
big
companies
to
actually
invest
in
open
source
projects,
and
you
know
good
people,
then
developers
and
pay
their
salaries
to
work
on
something
that
is
open
and
I.
Think
that
that
was
a
really
interesting
thing.
B
You
know,
like
everything,
I
think,
like
everything
that
that
I
get
into
I.
It
feels
like
it
was
a
slow
process,
but
in
retrospect
I
I
was
really
an
early
adopter
yeah
same
as
happened
to
me
in
cloud
services.
I
felt
I
like
I
was
feeling
I.
I
missed
the
train,
but
I
was
just
you
know
was
exist,
I,
don't
know
two
years
before
before
I
joined
and
back
then
it
was
nothing
and
I
just
became
an
expert
just
by,
but
you
know,
being
there
early.
B
B
That
was
one
big
aspect
that
that
I
think
that
imported
for
for
for
this
all
vision
to
to
fulfill
itself.
The
other
aspect
that
that
we
felt
is
kind
of
lacking
is
the
the
ability
to
connect
different
options.
Basically,
the
block
chains
were
islands
like
silos
of
value
and
and
and
functionality,
and
there
there
should
be.
There
must
be
a
way
to
to
have
the
network
effects
and
connectivity
and
basically
build
a
mesh
network
of
over
all
the
okay.
A
B
Exactly
yes,
I
think
it's
the
next
logical
step
and
you
see
it
in
every
kind
of
system
in
every
kind
of
distributed
systems
where
the
RT
builds
up
and
basically
and
basically
you
get
specialized
silos
and
the
fact
they
are
connected,
as
everyone
can
specialize
in
in
its
own
thing
and
I'm
instead
of
compete
on
the
same
thing.
Another
point
that
that
we
that
we
felt
is
is
kind
of
lacking
is
the
is
the
ability
to
to
connect
to
the
outside
world
from
a
contract.
B
Basically,
contracts
are
very
useful,
and
even
if
we
do
mesh
network
of
all
the
chains,
it's
still
an
island
by
itself,
it's
not
connected
to
the
day-to-day
everything
else.
We
know
into
the
value
that's
outside,
and
that
brings
me
to
the
fourth
point,
which
is
the
value
that
is
outside
fear.
Basically,
what
we
call
see
Otto
onboarding.
So
that's
that's.
Another
challenge,
work
where
the
majority
of
the
value
and
the
systems
exist
outside
of
this
this
ecosystem.
B
So
there
should
be
a
bridge,
very
good
bridge
from
value
to
tools
go
in
and
out
from
those
system
a
bit
to
the
outside
world,
not
just
data,
and
that's
that's
another
challenge
that
I
think
it
still.
It's
still
a
challenge
these
days
it
so
I
I
was
thinking
of
what
what's
the
best
best
way,
not
just
to
solve
those
problems.
But
what
was
the
the
best
way
to
to
to
architect
the
technology?
B
Or
maybe
we
architected
the
technology
in
order
for
those
problems
to
to
to
be
solved,
you
know
independently
and
not
be
you
know
in
a
monolithic
kind
of
technology
and
and
they
brought
me
back
to
to
the
layers
vision
to
the
ability
to
encapsulate
things
in
layers
of
abstractions
and
and
how
a
blockchain
should
probably
be
layered.
You
know
multi-layered
instead
of
having
one
kind
of
monolith.
B
Basically,
blue
be
in
charge
of
everything
whether
it's
communication,
peer-to-peer
consensus,
execution,
language,
basic
function,
I
think
that
set
model
can
be
improved.
Basically,
so
it's
started
building
kind
of
a
process
I
for
four
layered
blockchain,
which
is
kind
of
a
grass-based
chain.
You
could
say
it's
similar
to
Yoda
in
some
ways,
but
where
every
branch
is
of
the
graph
is
kind
of
how
can
have
a
different
content
mechanism
so
I
call
this
block
space.
B
B
Management
is
an
entirely
different
layer.
Permissions
is
if
a
layer
on
its
own
communication
and
all
those
things
basically
were,
were
kind
of
layered,
and
then
I
saw
that
yosi's
is
doing
those
basic.
Let's
say
the
the
basic
layers
pretty
well
with
wisdom
and
everything
that
Mindlin
my
implementation
was
with
basically
containers
as
the
execution
layer.
B
B
A
B
B
Now
now
I
understand
better,
but
but
still
I
think
it's
a
it.
I
think
that
the
in
in
April
I
really
got
in
April
2018,
I,
really
dived
into
the
rabbit
hole.
It
was
an
interesting
experiment,
I
think
bootstrapping,
a
blockchain
is
much
more
than
the
technology.
You
know
it's
it's
it's
a
it's
a
lot
more.
It
bootstrapping
a
community
and
it
I
was
the
technology
was
interesting,
but
I
learned
a
lot
from
years
and
and
being
a
part
of
launching
the
the
meyneth
and
being
one
of
the
top
block
producers.
B
A
project
that
was
written
by
one
company
and
then
launched
by
without
the
help
of
the
of
that
company,
like
completely
independent
of
that
company
for
the
first
time
in
production
and
it
went,
went
amazingly
well
like
I-
was
a
bit
skeptical
at
first,
but
as
soon
as
I
met
the
people
before
before.
The
launch
and
I
got
more
and
more
country
than
that.
The
this
that
crazy
approach
is
actually
going
to
work.
Mmm-Hmm.
A
B
It's
definitely
a
genius,
definitely
I,
think
and
here
the
his
visions.
You
know
for
for
quite
a
long
time
as
well.
In
there
and
and
like
me,
he
if
his
own
dog
food
and
planning
to
you
to
you,
know
to
utilize
that
the
platform
to
really
build
the
things
that
he'd
build
the
platform.
For
you
know
I
haven't
I.
B
They
say
that
you,
you
can
really
know
how
good
someone
is
if
you
set
a
road
code
with
them
like
like
yeah
in
the
army,
it's
like,
if
you
really
you
know,
I
slept
near
him
in
a
tent
and
there
oh
its
encoding
its.
If
you,
if
you
did
a
whole
night
of
coding
with
it
with
someone,
then
then
you
know
how
good
is
so.
B
I
haven't
got
a
chance
to
do
it
with
with
them,
but
the
I
imagine
is
quite
quite
quite
a
legend
as
they
fade
here,
but
I
watch
a
lot
of
his
code
on
github.
You
know
you
can
you
can
measure
in
the
beginning
of
the
project,
how
much
person
that
Zoey's
also
have
a
lot
of
capacity
in
it
in
his
fingers?
That's.
A
Funny
that
when,
when
we
were
in
Washington
DC
for
b1
June
people
at
least
three
people
off
the
top
of
my
head
said
that
about
you.
Looking
at
your
code,
well,
I,
don't
know
what
it
was
about.
It
I,
just
remembered
three
different
people
said
he's
got
really
good
code
and
I'm
like
geez.
You
can
just
tell
so.
B
That's
one
of
the
fun
things
about
about
an
open-source
project
which
has
an
engaged
community
around.
It
is
that
that
people,
people
actually
notice
and
appreciate
the
the
thinking
that
you
put
into
things
and
and
even
even
provide
the
feedback
that
they'll
they're
like
for
the
first
time
in
my
life,
people,
people
write
me
I,
I
love
that
line
of
code
because
I
learned
something
from
it,
and
and
that's
that's
amazing,
because
because
because
people
appreciated
the
time
that
you
put
into
the
you
know
the
details,
we.
A
Just
recently
celebrated
six
months
since
the
DAP
network
launched-
and
we
celebrated
it
with
a
teaser
for
a
hackathon,
and
we
I
do
want
to
share
another
towel
story
about
ears
hackathons,
because
we've
told
the
story
on
here
a
bunch
of
times
of
how
I
met
Tao
for
the
first
time
at
the
San
Francisco
hackathon,
the
eoseo,
global
hackathon
and
Tao
is
a
mentor
there.
And
everyone
was
like.
B
I
wouldn't
say:
fourth,
but
but
but
yeah
yeah
I.
First,
the
first
time
that
I
heard
the
hackathon
and
I
was
lived
nearby
and
I
think
they
were
talking
about
the
fact
that
BP
are
not
allowed
to
participate.
So
he
was
thinking
to
participate.
You
know
independently
and
I
didn't
have
a
team
and
I
wanted
to
just
compete
myself
as
a
one-person
and
I
really
planned
to
win
this.
The
hackathon
actually.
A
B
A
B
B
A
You
think
we
even
gave
I
don't
know
where
we're
gonna
be
on
the
edited
version
of
this,
but
we're
probably
at
least
30
minutes
through
in
the
edited
version,
and
we
never
got
to
what
is
liquid
apps
and
what
is
that
Network
at
a
very
high
level
enjoy
spot
by
the
the
man
who
architected
it.
So
what
is
that
network
and
all
right
what
you
envision
it
becoming
so.
A
I
try
to
describe
that
network
and
the
problems
it's
solving
to
someone
who
knows
nothing
about
it.
I
try
to
explain
it
like
we
have
all
of
these
silos
of
daps
and
their
own
development
teams.
They're
all
kind
of
trying
to
say
solve
the
same
problems
over
and
over
again,
like
free
accounts,
is
something
everyone's
needed
and
and
we've
seen,
projects
like
es
Bette
and
others
build
their
own
virtual
account
system.
But
then
it's
not
interoperable
and
no
one
else
could
really
gain
from
that.
A
So,
like
we
have
liquid
accounts,
which,
which
is
solving
that
problem,
making
it
very
easy
for
adapt
to
add
this
functionality
without
investing
a
bunch
of
their
own
resources
to
build
it
from
scratch,
like
companies
previously
may
have
had
to
have
done
same
thing
with
Oracle's.
Instead
of
having
to
develop
your
own
Oracle,
we
have
this
Oracle
service
that
that
you
have
an
entire
network
of
DSPs.
You
could
choose
from
so
it's
just
kind
of
removing
all
of
the
different
bottlenecks
that
occur
whenever
you're
just
trying
to
develop
a
general
use
case
application.
A
There
are
certain
things
that
that
you're
need
to
build
in
your
own
little
silo
and
I.
Think
that
the
the
best
thing
to
compare
it
to
is
we
leading
up
to
the
US
may
net
and
the
the
narrative
around
us
and
block
one
and
Dan
was
that
Dan
built
a
previous
blockchain.
So
we
ran
into
limitations
and
by
building
the
second
and
the
third
one
he
realized
all
of
these
things.
You
have
to
do
every
time
you
want
to
build
a
new
blockchain,
so
he
just
built
a
general
use
case
like
walking.
A
That
everyone
could
build
on
top
of
and
do
whatever
they
wanted
to
do
so
that
they
didn't
have
to
build
a
blockchain
from
scratch
and
that
that's
that's
where
we're
at
with
just
the
eoeo
base
layer,
but
then
I
think
the
dab
layer,
it
kind
of
gives
them
every
everything
else.
Beyond
that,
and
it's
very
similar,
your
experience
is
very
similar
in
that
way
where
Dan
built
previous
block
chains-
and
then
he
is
third-generation
blockchain
is
like
the
grand
vision.
Where
is
with
you.
You've
been
building
this
other
thing.
A
It
wasn't
in
a
blockchain
industry
because
it
didn't
even
exist
at
the
time,
but
but
you've
iterated
over
these
ideas
and
now
we're
here.
We
have
this
base
layer
that
you're
building
on
top
of
now,
you
don't
want
to
add
these
service
layers
so
that
I
develop
a
developer,
could
build
a
distributed,
decentralized,
autonomous
project
and
they
don't
have
to
they're
basically
able
to
hit
the
ground
running
because
they
could
they
could
skip
all
of
these
building
block
steps
that
every
developer
before
that
network
has
had
had
to
do.
B
Usually
with
when
I
build
platforms,
the
first
users
of
the
platform,
you
know
with
ease
me
I
wanted
to
use,
I
want
to
use
it
myself
and-
and
it
feels
like
I'm,
really
we
really
starting
to
get
to
the
point
to
the
tipping
point
where
it's
really,
you
have
enough
of
the
tool
sets
and
enough
of
things
that
you
don't
need
to
worry
about
in
order
to
accomplish
things
fast
and
that's
basically
the
end
goal
in
in
conventional
software.
We
we
had,
you
know
the
concept
of
we
using.
B
You
know
things
that
other
people
built,
but
when,
when
you,
when
you
talk
about
blockchain
technologies,
it's
not
enough
that
things
that
are
open
source,
you
also
need
distributed
entities
to
actually
run
the
code,
even
if
you're
a
developer,
and
you
want
to
create
your
own
solution
for
something.
Unless
you
get
a
layer
of
participants
that
are
that,
have
the
right
incentives,
you
basically
have
a
weak
link
of
decentralization
because
you're
running
your
own
service.
B
So
that's
that's
another
interesting
aspect
that
it's
it's
not
even
a
technological
aspects,
it's
a
complication
from
from
from
the
nature
of
blockchain
itself
and
and
game
theory
around
this
think
that
it.
It
brings
me
back
to
you
the
question
of
what's:
what's
the
the
end
goal
like
what's
the
end
goal
of
decentralization
and
and
those
kind
of
technologies
in
the
first
place
and
what's
the
what's:
what's
even
the
goal
of
making
an
immortal
application?
B
You
know
to
freedom
to
participate
in
the
systems
that
that
control
our
lives
and
the
system
that
we
that
we're
a
part
of
and
and
many
times
is
called
you
know
most
times,
collaboration
between
people
has
at
all
of
centralization
and
and
generalization
leads
to
two
abuse
of
power
and
corruption
and
inefficient
things.
So
it's
basically
there's
the
freedom
to
do
it
more
efficiently
to
collaborate
more
efficiently
the
freedom
to
to
participate
in
indexing,
the
systems
that
you're
that
you're
the
could
control
you.
B
That's
that's
a
very
powerful
thing
in
in
in
the
ability
for
people
to
collaborate
around
anything
without
having
other
groups
of
power,
interfere
and
and
an
immortal
application
is
basically
it's
an
application.
That
is,
that
is
not
not
in
not
in
control
of
anyone,
so
end-to-end
that
once
it's
out
there,
nobody
can
can
change
how
it
behaves
and
nobody
can
manipulate
it
and
nobody
can
abuse
the
the
logic
in
it
and
basically
something
that's
going
to
stay
there
forever.
So,
within.
A
B
A
Something
like
like
it
Dow
could
could
manage
anymore
to
out
yep
yeah
exactly
we
did
spend
a
lot
of
time
on
your
background
and
stuff
I.
Think,
like
the
original
plan
was
to
get
people
to
know
you
and
not
so
much
focus
on
liquid,
apps
and
I
think
we
did
a
good
bit
of
that.
Oh
I
didn't
that
flavor
at
all,
okay,
so
the
labor
part
is
we.
B
B
Basically
I've
been
thinking
a
lot
of
how
to
take
management
and
management
processes
and
making
them
in
software,
whether
it's
taking
a
project
and
breaking
it
down
to
pieces
and
contracting
it
every
little
piece
to
a
different
contractor
on
a
crowdsourcing
platform
like
Fiverr
or
or
whatever,
and
and
and
whether
it's
trying
to
create
liquidity
for
for
for
work.
Basically,
if
you
think
about
it,
work
an
hour
of
work
or
skill,
work
doesn't
have
liquidity.
Today.
B
If
you
want
someone
to
work
on
something,
you
probably
have
the
right
context
to
participate
in
your
collaboration
and
your
organization.
You
need
a
lot
of
context.
You'll
need
to
hire
him,
probably
or
or
have
a
long
term
relationship
and
then
trust,
and
then
it's
not
like
that.
You
can
get
that
thing:
a
logo
designer
okay,
it's
not
like
you
can
like,
have
a
specs
for
a
logo
and
have
an
exchange
of
hours,
logo,
design,
hours
standard.
B
B
B
In
that
vision,
or
in
that
direction,
I
would
say,
and
I
can
go
over
them.
One
was
basically
something
that
you
could
a
marketplace
where
you
could
write
tests
and
someone
else
could
write
code
to
pass
your
tests
and
basically
only
she
wrote
code
that
tests
your
tests.
You'd
get
your
bounty.
Basically,
it's
like
a
verified
bounty
system
for
pieces
of
code
and
and
tests
that
it
want
to
verify
that
that's
a
kind
of
an
effort
to
create
liquidity
around
around
problem
programming.
Basically
around
function,
functions.
A
B
Right
right
and
back
when
I
was
building
that
project
people
told
me:
I
wanted
to
basically
create
a
coin.
/
kind
of
skill
task
and
people
told
me
listen.
You
should
really
look
into
aetherium
and
blockchain,
because
that
synchronization
is
exactly
what's
happening
there
right
now,
but
but
I
only
came
to
that
later.
B
A
It's
funny
the
way
you
describe
some
of
some
of
these
ideas
of
yours,
because
there
there's
projects
that
are
currently
being
built,
that
in
a
way
try
to
solve
some
of
these
problems
or
build
or
approach
these
problems
so
like
for
the
the
passing
the
tests
in
the
code
like
looking
at
something
like
nougat
and
what
they're
trying
to
accomplish
it.
I
could
see
some
similarities
there,
then,
when
you're
talking
about
liquidity
on
a
labour
market,
I
think
effect,
AI
and
I'm
excited
for
that
project.
A
So
I
think
it's
public
they've
said
that
they're
going
to
be
launching
a
DSP
and
using
certain
services,
possibly
even
offering
their
own
services
that
are
unique
to
what
they're
doing
I
remember
whenever
I
had
Chris
from
effect
III
on
everything
he
owes.
I
came
to
you
for
advice,
because
I
knew
a
I
and
human
collaboration
was
one
of
your
personal
interests,
and
you
told
me
some
different
things
about
crowd,
wisdom
and
things
like
that.
What
are
your
thoughts
on
the
effect,
a
I
project
and
what.
B
A
Of
things
are
possible
with
these,
like
crowd,
Mandy's,
man-machine
collaborative
work
forces
that
you're
describing
whether
through
something
like
effect,
III
or
something
that
hasn't
even
been
built.
Yet
what
what
does
this
man-machine
collaboration?
Look
like
like?
What's
your
vision
for
this
so.
A
B
A
My
mind
I
could
wrap
my
head
around
this,
like
crowd,
wisdom
and
crowd
sourcing,
the
work
for
like
a
micro
task-
that's
very
simple,
like
if
you
have
to
identify
something
on
an
image,
but
it's
like
hard
for
me
to
even
wrap
my
head
around.
How
would
work
when
you're
talking
about
more
complex,
complicated
tasks
that
you
think
of
as
jobs
that
require
like
dedicated
human
involvement
here,
like.
B
Much
more
adaptive
adaptive
to
those
those
techniques,
it's
not
necessarily
the
same
process,
it's
a
different
process,
but
but
potentially
it
can
be
much
more
efficient
and
in
software,
for
example,
you
have
modular
thinking.
So
you
you
build
you
software
that
it's
built
well,
it's
built
that
small
teams
can
work
on
different
components
of
it.
I
think
the
same
kind
of
thinking
can
be
applied
to
many
other
kind
of
work,
processes
and
project.
A
So
this
is
fun
I,
don't
think
I
didn't
expect
to
go
so
long
without
talking
about
liquid
apps
adapt
network
too
much.
That
was
kind
of
the
goal
here,
this
new
concept,
so
everyone
watching,
let
us
know
in
the
comments
what
you
think
about
getting
to
know
the
leaders
in
this
industry
yo
sandboxing
as
a
whole.
You
have
such
an
interesting
background.
A
Ty
I'm,
really
glad
I
got
to
have
you
be
kind
of
the
champion
of
this
new
concept
here,
III
think
we
will
have
to
have
you
back
on
again
to
talk
in
more
detail
about
liquid
apps
and
app
network,
but
it's
it's
been
really
fun.
Getting
to
hear
some
of
these
stories.
About
your
background
and
some
of
I'd
say
you
validated
some
of
the
legend
III
I
think
the
legend
is
still
legitimate
and
the
legend
is
still
real
is.