►
From YouTube: NEAR Certified Demo | Episode 5.4 -- NEAR Merge Data
Description
This demonstration was presented by the author(s) after just 1 week of working with the NEAR platform as part of the NEAR Certified Developer program.
You can find the source code to this demo here:
https://github.com/Learn-NEAR/NCD-05--near-merge-data
---
Follow the latest from NEAR Protocol on:
Website: https://near.org/
Discord: https://near.chat/
Blog: https://near.org/blog/
Twitter: https://twitter.com/NEARProtocol
GitHub: https://github.com/near https://github.com/nearprotocol
#Blockchain #FutureIsNEAR #NEAR #nearprotocol
A
Oh
okay,
so
ilya
you're
up
next
with
near-merged
data
whenever
you're
ready.
B
B
Two
and
more
and
and
merch
eat
two
one
release.
B
And
transfer
sender
one
yokto,
one
array:
it
a
simple
implementation.
B
B
B
B
B
B
Ci
local,
it.
B
B
B
Oh
okay,
make
yarn.
It
may
build,
make
your
it
like.
B
And
integrate
integration
for
all
command,
jfk
and
blinker
best
anyway.
Okay,
the
demo
run
contract.
B
B
C
Oh
I'm
saying
there
might
be
other
contracts
that
are
looking
for
similar
functionality
and
it
seems,
like
you,
kind
of
ironed
it
out
pretty
well,
like
let's
say
if
I
want
to
use
this
function,
your
merge
function
like
as
a
utility
library,
so
import
importing
your
lib
rs.
A
Or
just
or
just
use
his
deployed
contract
as
a
service,
if
you
wanted
to,
but
his
I
I
think
his
his
statement
earlier
was
that
this
was
intended
as
an
exercise,
so
it
seems
like
he
spent
most
of
his
attention,
not
on
the
functionality
of
the
contract,
but
on
the
kind
of
state
of
the
machinery
around
it.
The
unit
test
integration,
test,
local
automation,
documentation,
so
all
of
that
is
sort
of
at
a
very
high
level,
and
then
the
contract
is
solving
a
problem.
You
know
some
some
reasonably
scope
problem.
I
think
yeah.
B
B
B
I
I
start
last
no
one
one
day.
B
D
Yeah,
which
is
pretty
usual
right,
the
very
first
one
takes
you
like
quite
a
bit
of
time
and
when
you
get
get
aware
about
what
you
actually
want.