►
From YouTube: URL/URI standard working group meeting 2
Description
Working document - https://hackmd.io/@poojaranjan/URLWorkingGroup
A
A
So
that's
for
background
meeting.
We
have
two
action
items
proposed
by
matt.
I'm
not
sure.
If
we
have
any
update
on
that
but
yeah.
I
would
like
to
open
the
flow
for
sharing
progress
and
continue:
brainstorming
wallet,
plus
theft,
and
maybe
it
is
something
that
we
can
be
reaching
out.
But
I
know
there
are
this
wallet
dev
discord,
channel.
A
B
Right
I
mean
I
didn't
feel
like
the
the
qr
code.
You
are
uri
for
adding
the
networks
was
really
moving
in
the
direction
that
we
want
to
be
moving
in,
but
that
doesn't
preclude
the
author
from
continuing
to
push
it
forward.
I
just
think
that
it's
best
to
you
know
come
from
it
approach
it
from
a
different
direction.
A
Sorry
I
was
looking
for
a
mute
button.
Yeah,
that's
right!
That
is
available
in
the
draft
right
now
and
if
author
wants
to
continue
moving
in
that
direction,
that
is
they
are
free
to
do
that
key.
You
shared
the
proposal
4804
in
the
last
meeting.
I
see
that
is
still
in
the
draft
status.
Is
there
anything
that
you
would
like
to
add
or
share,
or
maybe
the
progress
or
anything
new
on
that
proposal?.
D
Yeah,
so
this
is
the
basic
form.
Discussion
of
eip
4804,
so
basically
for
e04
is,
can
be
truly
a
kind
of
like
a
http
web
3
version
of
http.
So
the
format
is
quite
straightforward.
If
I
using
a
very
simple
picture,
something
like
that,
basically
it's
going
to
replace
the
schema
http
with
fdrf3
and
then
user
is
going
to
put
what
the
contract
is
that
the
user
wants
to
locate.
D
Basically
in
http
protocol,
it's
going
to
locate
our
website
two
resources
together
with
dns
and
ibhs
in
the
western
world,
which
we
will
project
that
we
should
have
some
decentralized
way
to
locate
the
resources.
While
we
can
inherit
some
good
properties
of
http
spectrum
equipment,
readable
and
also
other
features
like
relative
parts
that
widely
use
in
http
url.
D
D
Oh
so
yes,
the
user
info
is
basically
when,
when
we
translate
to
a
user
message,
it
will
tell
us
what
is
the
sender
after
a
message.
So
this
is
the
user
input
that
we
just
directly
borrow
from
http
standard.
You
know
http
yeah
so
and
definitely
it
can
also
be
moved
to
the
query
path
but
feel
like
this
is
kind
of
more
like
if
we
treat
a
schema
here.
This
is
basically
what
we
just
put
the
rap3d
part
into
the.
D
D
Basically,
we
are
able
to
using
a
simple
link
instead
of
query
adjection
with
some
parameter,
then
we
are
able
to,
for
example,
check
some
balance
or
call
basically
pro
arbitrary
method
of
a
contract
and
return
its
value
back.
This
is
kind
of
like
a
complimentary
options.
Rpc
another
one
that
I
feel
like
is
more
excited
about
is
able
to
basically
return
kind
of
a
web
content
that
is
generated
by
the
by
the
contract
itself.
D
So
recently
we
see
a
lot
of
some
some
application,
like
using
on-chain
contract
that
is
able
to
generate
a
web
content
such
as
svg
one
example
that
we
found
in
the
market
is
called.
They
called
cyber
brokers,
so
they
basically
upload
all
the
svg
data
to
the
blockchain
and
then
and
then
this
is
the
one
one.
Actually
we
create
a
subcontract
because
they
don't
have
a
way
to
be
able
to
display
this
their
svg
that
is
composed
on
top
of
the
exterior
directory,
so
using
our
protocol.
D
So
basically,
this
is
gateway,
so
in
investment.
This
will
be
like
something
like
that.
So
we
look
look
at
this
contract
and
call
the
random
broker
method.
Together
with
the
id
of
the
mft
token,
then
it
just
call
their
contract
and
then
we'll
compose
the
svg
content,
basically
kind
of
like
xml
content
and
put
it
together
and
return
to
browser.
But
in
this
way
we
don't
really
rely
to
any.
D
Okay,
cool,
so
so
that
that's
the
kind
of
application
that
we
are
now
able
to
use
in
smart
contract
to
build
like
a
caller
common
gateway
interface
programs
that
can
random
html
svg,
which
stable
brokers
is,
is
already
done.
Maybe
more
complications
like
png
that
we
may
observe
in
other
blockchain
that
might
have
cheaper
upload
costs,
like
example,
polygon
or
bsc,
so
some
something
that
we
feel
like
this.
D
In
this
way,
we
are
able
to
build
the
counterpart
of
rev3
versus
the
http
web
2
way
and
be
able
to
access,
locate
this
resources
in
a
decentralized
way,
and
then
we
are
able
to,
for
example,
to
to
to
query
them
and
then
be
able
to
display
them
in
decentralized
ways.
So
one
one
interesting
thing
is
like,
for
example,
we
have
other
ens
domains
to
the
rinkeby,
so
this
system,
four,
which
is
rankingb
but
yeah,
it's
the
message
standard
in
call
yeah
and
then
so
all
the
ens
program.
D
We
just
upload
it
to
the
to
the
rinkeby
testnet,
and
so
you
can
now
just
just
directly
access
using
the
ens
plus
the
with
the
chain
id
I'll.
Take
it
with
right.
Now.
It's
using
the
gateway
method,
but
definitely
in
the
future
we
feel
like
once
the
standard
is
being
mature.
Then
we
can
build
kind
of
like
a
extension
in
brave
firefox
that
we
are
able
to
directly
access
the
reserve
resources
and
display,
on
top
of
the
browser,
without
using
any
example,
dns
or
centralized
servers.
D
D
D
Or
two
filled
by
the
wallet
yeah,
it's
the
wallet
is
that
is
the
part
of
logistic
core
that
will
autofill
by
the
wallet
when
we,
for
example,
connect
wallet,
but
at
the
same
time
this
is
another
way
that
is
directly
accessing
the
web
resources
wire,
the
this
link
so
without
using
the
json
design
pc.
So
this
allows
another
way,
basically
complementary
way
to
access
the
blockchain
resources
using
just
link
only
so
it
can
be
done
by
both,
but
we
also
provide
an
optional
for
the
users
to
so.
D
So
so,
for
example,
if
you
treat
an
email
message,
when
we
call
inside
a
if
you're
in
gas,
basically
it
will
check
pass,
have
a
field
call,
that's
actually
there's
a
phone
sorry.
This
is
there's
a
form
field
with
a
message
standard,
so
in
json.
Obviously,
basically
people
used
to
call
the
json,
rpc
and
supply
this
field
to
say,
hey
what
which
water
is
calling
the
contract
or
estimated
gas.
D
What's
the
corresponding
return,
some
value
and
then
so
here
we
provide
another
way
to
basically
to
tell
what
is
who
is
going
to
call
this
contract
and
but
actually
most
of
time
probably
doesn't
need
to
be
used,
because
if
user
just
created
some
somebody
was
the
owner
of
nft.
What
is
the
balance
of
somebody?
D
C
D
Yeah
so
so
one
is
schema,
and
then
there
are
also
a
couple
questions
regarding
what
if
we
want
to
return
a
type
types
like
like
example,
when
the
smart
contract
returns
a
binary,
how
they
are
able
to
pass
this
binary
treaty,
like
as
a
web
content
by
default
or
just
treated
couple
of
type
value,
and
there
are
also
couple
of
different
formats
that
we
also
provide
and
so
but
yeah.
This
is
basically
a
couple
of
questions
that
we
are.
D
B
D
B
Like
one
thing
to
consider
that
I,
like
don't
really
know
how
to
trade
off,
is
that
the
in
the
picture
there's
not
enough
information,
I
think
to
actually
send
the
call,
because
you
need
the
exact
type
parameter
of
the
methods,
and
I
don't
think
that
that
this
gives
that
to
you.
Is
that
wrong,
or
is
that
right.
D
Prefix,
yes,
yeah,
that's
great
questions,
so
here
like
so
first
first
path,
complement
is
master,
id
is
just
should
be
a
string
and
the
rest
of
the
arguments
is
just
rest
of
parts.
That's
just
a
list
of
arguments,
and
so
here
there's
a
rule
that
will
be
automatically
detect
those
types,
even
if,
if
it's
some
format,
for
example,
if
it's
pure
integer,
then
it
will
be
just
automatically
su
into
256
unless
there's
a
specific,
explicit,
explicit
type
conversion
before
yeah.
D
Yeah,
so
you
can
put
that
and
then
exclaimer
mark
and
then
your
chords
are
eth.
You
use
the
address
type
for
this
one
yeah,
okay
and
yeah.
I
think
this
is
a
good
question,
really
good
question,
because
here
I
feel
like
it.
Probably
we
should
convert
it
to
explicit
address
for
all
the
domain,
because
dot
eth
may
be
treated
as
a
zuck.eth
file,
because
a
file
it
can
be
ends
with
different
suffix
may
collide,
with
existing
name
service.
D
Oh
yeah,
so
this
is
a
good
question.
Sam
mentioned,
so
suppose
we
have
do
something
with
given
string,
address
or
integer
how
it
looks
like
so
basically
the
pro
so
when
I
type
something
web3
and
a
contract,
and
then
I
put
a
method
master,
it's
called
do
something,
and
then
suppose
this
is
pure
integer.
D
Then
it
will
call
you
in
256,
because
the
master
id
when
when
we
translate
it
to
the
master
id
the
mass
id,
contains
the
integer
itself
so
that
it
will
become
us
like
will
be,
there's
no
ambiguity
of
the
master
iv.
If
we
just
put
it,
it
can
successfully
detect
the
type
and
suppose
it's
addressed,
then
it
will
be
something
that
is
20
bytes
hex.
Then
it
will
also
be
detected
as
edges,
and
so
the
address
will
be
also
in
the
master
id
and
so
that
it
will
be.
D
C
C
B
D
Obviously
you
could
go
down,
but
so
right
now
we
have
limited
ports
that
are
limited
types
that
will
automatically
detect
it
as
yeah,
as
you
mentioned,
because
right
now,
autos
type
in
general,
their
parameter
space
is
non-overlap,
so
their
order
doesn't
make
too
much
difference
because
we
also
want
to
make
this
rule
to
be
too
complicated,
so
the
user
can
kind
of
understand.
So
right
now
you
just
automatically
detect,
detect
you
into
another
v6
and
for
other
non-supported
type.
It
must
be
parameterized.
D
String
support,
natively
string
couldn't
work
because
url
could
fill
the
most
string
yeah.
I
think
this
character
will
kind
of
handle
this,
and
so
I
think
in
our
test,
so,
for
example,
first,
first
string,
let
me
see
all
bytes
that
so
actually
there's
another
case
that
we
can
adjust
the
basically
the
the
the
skate
issue,
for
example,
for
the
streams
of
bytes.
Basically,
users
can
also
use
the
hex
way
to
to
improve
it.
It
is
less
human
readable,
but
it
can
adjust.
Also
this
ambiguity
and
force
really
string.
D
D
D
D
D
D
D
This
is
the
website
we
register.
Basically
right
now,
it
has
a
text
record
tells
what
is
the
basically
three
link
and
address,
and
this
is
basically
gives
a
change
specific
address,
which
is
points
to
our
test
net,
and
then
this
is
shot
name
of
the
test
net
and
also
the
contract
address.
So
in
that
way,
we
are
able
to
register
the
domain
on
ens
by
able
to
point
to
any
address
on
ebn,
compatible
chains.
D
D
D
A
D
D
D
D
E
E
The
first
bullet
point
is
the
ethereum
name
service
and
the
second
one
is
the
w3q
name
service
and
then
in
the
section
below
it,
you
are
numbered
list.
This
time
number
one
is
fetching
the
w3q
record
from
ens
and
number
two
is
okay,
fair
all
right,
so
that,
essentially,
is
how
to
load
the
data
from
ens.
D
D
But
for
this
one
yeah,
this
is
the
version
that
we
just
created
on
testnet
to
to
double
check
the
cost.
Basically,
the
the
name
service-
that
is
it's
the
same
as
ens,
but
just
running
on
top
of
us
on
top
of
the
basic
right
now
sidechain,
but
right
now
we
have.
The
target
is
to
fully
integrate
with
uns
with
this
chain
specific
address
that
uns
is
now
able
to
support.
D
D
D
So
we
have
to
rely
on
different
lane
service
on
different
blockchains
so
that
it
can
be
located
on
different
blockchains,
smart
conscious,
but
now
using
the
ip36770
now
they're,
just
using
ens
and
then
put
the
chain
specific
shot
names
and
then
now
they're
able
to
reference
these
addresses.
So
this
is
basically
the
change
of
when
we
say
hey
now.
We
need
extraneous
service
from
different
change
resources.
Now,
with
this
we're
just
using
an
ens
and
can
do
other
things.
E
Because
you're
already
claiming
the
or
at
least
you're,
creating
an
eip
at
the
moment
to
essentially
reserve
the
entire,
not
just
the
the
web
3
schema
itself,
which
you
know
is
very
broad
web
3
is
very
broad.
It's
not
just
evm
calls
right
and
you're,
reserving
an
entire
schema
for
that,
so
putting
hypothetically
renaming
the
schema
to
to
the
test
is
something.
E
Furthermore,
the
w3
name
service,
I
suppose,
with
any
name
service
you
should
just
to
to
quote
resolve
using
the
name
service
of
your
choice
right.
So
if
that
is
an
unstoppable
domain,
then
the
browser
or
extension
or
whatever
is
resolving,
should
just
figure
out
how
to
do
it
themselves.
If
it
ends
with
w3q,
then
they
should
just
figure
out
how
to
do
it
themselves.
That
should
not
be
something
specifically
described
in
the
specification
right
like
that
can
be
abstracted
away
as.
E
E
Sure,
right
and
as
much
as
I
understand,
you'd
like
to
have
the
web
3
key
right
yeah.
I
think
you
might
the
text
record
right.
You
might
want
to
contemplate
potentially
settling
for
w3q
as
the
text
record
or
something
along
those
lines
right
or
whatever
the
schema
ends
up
being
because
we
wouldn't
want
an
acc.
E
I
mean
you're
already
following
the
original
uri
url
spec,
so
closely
that
in
the
hypothetical
event
somebody
does
not
set
this
currently
named
web3
key
value
pair
right
on
their
ens
record
that
it
could
be
a
url
that
looks
like
web3.
But
do
you
know
how,
with
most
browsers,
if
I
type
in
google.com
it
automatically
goes
to
https
colon,
slash,
google.com
right?
E
We
wouldn't
want
somebody
only
copying
everything
after
the
schema
pasting
it
in
there
and
instead
of
it
automatically
going
to
web3
colon
slash
automatically
going
to
https,
and
somebody
has
already
claimed
the
contract
name
or
somebody
has
already
overtaken
it
in
another
way.
Right
because
what
will
end
up
happening,
then,
is
you
can
make
4804
urls
right
that
are
4804
compatible
your
eip,
but
that
if
misentered
ever
so
slightly
goes
straight
to
an
https
site,
which
is
a
high
risk
of
you
know
it's
essentially
introducing
another
vector
for
attackers
to
come
in.
D
So
if
there's
a
short
name,
so,
for
example,
if
there's
just
something
dot
adhd,
then
definitely
it
may
translate
to
https.
But
if
we,
the
user
provider
for
schema,
no
matter
is
vms
web
3
or
evm,
then
I
think
that
the
browser
yeah,
we
will
automatically
say-
oh
sorry,
either.
I
cannot
handle
this.
Oh,
oh,
this
is
something
actually
the
the
we
have
basically.
D
E
D
E
D
D
D
D
F
A
Thank
you.
Thank
you
ki,
and
look
for
this
discussion.
It
is
important
that
we
learn
about
the
proposal
and
their
statuses.
I
would
be
happy
to
organize
a
peep
in
each
session
for
this
particular
proposal
to
maybe
explain
it
in
a
detailed
way,
so
it
can
be
followed
by
other
implementers
and
yeah.
I
will
be
happy
to
connect
with
you
offline
to
get
this
thing
arranged
whenever
you're
ready
for
that.
A
A
G
So
yeah,
thank
you
so
this
proposal
I've
written
some
years
ago
and
I
tried
to
extend
an
ex
existing
eip
about
the
transaction
requests
and
we
were
using
the
transaction
requests
standard
in
status
to
when
you,
when
you
are
in
a
chat,
you
can
ask
someone
to
send
you
a
transaction.
So
this
is
one
user
who
sends
the
request,
and
then
you
need
a
way
to
answer
back
in
a
standard
that
the
software
can
understand
automatically.
G
So
then
me
and
my
colleague
my
work
colleague
eric
we
written
the
cip
just
to
specify
the
transaction
receipt
and
if
there
was
some
contract
call
to
to
translate
because
the
you
know
the
four
bytes
and
you
you
want
to
be
able
to
know
exactly
everything
about
the
transaction
both
but
for
status.
We
are
basically
using
just
a
transaction
receipt
because
for
one
user
to
another
there
is
no
contract
calls
or
usually
is
just
a
normal
transfer.
G
But
of
course,
if
this
is
a
your
c20
token
and
then
you
have
a
transfer,
you
have
the
match
of
that.
There
are
two:
it's
a
little
bit
more
complex,
something
I
don't
like
about
the
eip.
Everything
is,
is
that
it's
it's
not
very
elegant.
I
mean
it's
a
little
bit
ugly,
like
the
full
name,
ethereum
dash
transaction
and
I
feel
like
it
could
be
better,
but
it
works
it's
simple
and
straightforward.
E
G
A
G
And
maybe
we
can
make
something
better
than
that,
but
for
now
I
think
it
like.
I
don't
know
audi
of
the
use
case,
because
a
lot
of
things
are
changing
in
the
ethereum
world,
with
all
these
l
choose
and-
and
it's
supposedly
at
the
time
that,
when
I've
written
it,
I've
written
it
to
be
compatible
with
everything.
I
knew
that
that
is
on
the
interior
ecosystem,
but
maybe
something
now
changes.
A
A
You
can
probably
withdraw
it
or
if
you
think
that
you
can
make
some
improvement
to
the
present
proposal
and
would
like
to
continue
doing
it.
So
you
can
let
it
live
in
statement
for
some
more
time
and
whenever
you
make
those
changes,
you
can
bring
it
back
to
draft
or
to
review.
So
we
can
start
discussing
it.
G
E
So
there
is
currently
a
javascript
package
available
that
allows
you
to
take
in
one
of
these
urls
and
then
turn
it
into
an
object.
That
simply
says
this
is
the
prefix
it's
tx.
The
address
is
this:
the
variables
are
this
etc,
etc,
etc.
So
there
is
already
tooling
written
for
it.
So
when
it
comes
to
that,
even
though
it
was
created
in
2019
or
end
of
2019,
I
also
think
it
is
worth
moving
to
final.
G
G
G
You
receive
a
transaction
you
you
know
immediately,
even
when
the
transaction
is
painting,
so
that's
a
way
to
improve
the
the
ecosystem
as
a
whole,
because
right
now
painting
transactions
don't
appear
in
states
because
of
this.
So
it's
first
needs
to
be
included
in
a
block
yeah.
There
is
a
lot
of
use
cases
we
can
find
on
top
of
I
already
thinking
about
that,
but
yeah
and
we
needed
other
wallets
to
implement
this.
Using
this.
A
Just
again
a
piece
of
information
here,
this
new
proposal
is
currently
in
draft
status
and
it
cannot
be
moved
to
sign
final
as
yet.
This
has
to
go
through
different
statuses
and
the
best
one,
if
you
are
willing
to
move
ahead,
would
be
to
move
it
into
the
review
status.
By
doing
so,
you
would
be
attracting
eip
editors
and
community
review,
I'm
assuming
okay.
Let
me
quickly
check.
F
A
From
review
to
last
call,
there
is
no
fixed
duration.
Whenever
you
are
ready,
you
can
move
the
proposal
from
review
to
last
call,
but
once
the
proposal
moves
into
the
last
call,
it
has
to
stay
there
for
14
days
and
that
14
days
is
for
aggressively
getting
feedback
on
the
proposal,
and
then
we
can
probably
move
it
to
the
final
starter.
A
Yeah
yeah
the
moment
you
create
a
pull
request
and
it
is
merged,
so
I'm
I'm
sure
that
it
will
get
attention
from
eip
editors
and
obviously
from
the
community
when
any.
Whenever
any
proposal
comes
into
active
discussion,
people
come
forward
and
share
their
feedback
and,
moreover,
the
cata
has
also
organized
a
video
series
on
eip
special,
in
which
you
will
get
an
opportunity
to
explain
all
about
the
proposal
and
maybe
take
some
questions
from
community
and
yeah.
A
Well,
thank
you.
So
the
idea
of
this
call
is
to
get
moving
the
proposals
which
are
already
into
stagnant
status
and
help
out
getting
consensus
on
like
if
there
are
more
than
one
proposal
of
the
same
category
serving
the
same
use
case
as
of
now
from
the
list.
It
doesn't
look
like
that
there
is
any
other
eip
which
is
in
competition
to
that.
Please,
someone
correct
me
if
there
is
any
and
I'm
missing
on
that,
if
not,
then
it's
a
good
idea
to
move
the
proposal.
A
A
So
thanks
for
that,
how
do
people
think
about
getting
back
on
a
call
in
next
two
week
and
see
where
we
are
on
the
progress?
I
know
in
the
last
meeting
we
discussed
about
reaching
out
to
different
wallets.
We
we
were
not
able
to
connect
that,
but
samantha
earlier
mentioned
that
he
will
try
to
reach
out
to
them
and
even
from
our
end,
we'll
try
to
do
so.