►
From YouTube: "Baselining". The Baseline Protocoll as a design pattern - within the Unibright Framework.
Description
In this video, Unibright's CTO and Baseline TSC member Stefan Schmidt explains:
- Why it is meaningful to define business processes on an abstract level, like with our Unibright Workflow Designer, and to be not only "blockchain agnostic" but also "design pattern agnostic".
- That enterprises may be cautious to use a public blockchain, because they do not want to give others any insights (even if they are pseudonymized) into their processes.
That a "private" chain does not solve all the concerns enterprises may have towards privacy, as a private chain still can give others insights that should not be made public.
- How integration changes (or doesn't change) in regards to Baseline as long as you have a low-coding integration component like the Unibright Connector which can connect to blockchains, off-chain-systems and APIs (like that one of Baseline).
- How important code generation (like with our Unibright Lifecycle Manager) becomes in the world of Baseline, because generated code becomes the "shared" and trusted codebook of all participants of a business process.
- How tokenization processes (like with out Freequity components) come into play, when blockchain is not "only" used as a middleware, but also as a token environment for tokens representing digital identities or even securities.
Check out the corresponding blog: https://medium.com/@UnibrightIO/baseline-repo-public-unibright-on-the-tsc-baselining-explained-84a3bc4c2e58
The Baseline Repo on GitHub:
https://github.com/ethereum-oasis/baseline
Documentation on Baseline Governance and the TSC:
https://docs.baseline-protocol.org/community/community-members
Check out a great baseline explainer FAQ by EY's Paul Brody: https://www.reddit.com/r/ethfinance/comments/fds4sy/a_sort_of_baseline_explainer_faq/
A
Hello
and
welcome
to
the
short
explanatory
baseline
video,
my
name
is
Stefan
twigs,
I'm
CTO
of
the
new
bride
and
part
of
the
technical
steering
committee
of
the
baseline
protocol.
The
code
repo
on
github
for
the
baseline
protocol
we'll
go
live
today,
open
source
publicly
available
for
everybody,
and
this
video
is
the
opportunity
to
explain
why
we
should
think
of
baseline
more
like
a
protocol
or
a
design
pattern,
but
not
so
much
of
a
product.
A
Yeah
thinking
of
baseline
as
a
design
pattern
helps
us
to
understand
what
what
it's
all
about.
It's
about
bringing
processes
into
blockchain
and
using
the
baseline
protocol
as
a
pattern,
how
it
can
be
successfully
achieved,
and
we
want
to
give
a
short
example
out
of
the
unified
context,
because
what
we
offer
is
templates
for
different
use
cases
and
you
can
use
our
tools
to
define
your
specific
use
case.
Without
writing
any
code
and
use
case
that
we
also
enabled
in
our
public
available
demo,
is
a
multi-party
approval
process.
A
So
basically,
a
checklist
of
things
to
be
done
or
to
be
agreed
on
and
different
parties
give
their
okay
in
a
predefined
workflow
and
once
all
they
gave
their
ok.
The
whole
process
is
finished
with
a
dedicated
status
and
our
tools
to
do
so
are,
for
example,
the
uniprot
workflow
designer,
where
you
can
do
you
find
that
use
case
visually,
and
then
you
get
the
code
generated
for
any
smart
contract
language
or
any
blockchain
available.
A
So
the
idea
behind
it
is
to
have
a
little
less
complexity,
so
not
have
too
much
knowledge
needed
by
a
specific
coder,
but
rather
use
the
knowledge
of
the
domain
specialists.
Who
knows
how
the
approval
process
should
like
like,
rather
than
knowing
how
to
code
it
so
yeah?
You
see
a
short
example
that
all
this
is
visually
and
graphical
and
in
the
end
you
have
the
option
to
generate
code
and
the
understanding
of
the
unified
framework
is
to
be
blockchain
agnostic.
So
you
can
generate
code
for
whatever
blockchain,
for
example,
solidity
code
for
aetherium.
A
So,
let's
just
have
a
look
at
how
the
multi-party
approval
works
on
a
public
chain,
so
you
would
use
the
unified
framework.
You
choose
a
template
model
in
this
case,
a
multi-party
approval,
template,
and
then
you
create
your
very
specific
instance
with
exactly
the
workflow
steps
that
you
need
for
your
specific
approval
process,
for
example
between
you
and
your
supplier,
and
then
you
generate
code
out
of
it.
It's
a
smart
contract
and
this
smart
contract
can
be
published
to
public
blockchain.
A
A
So
from
a
perspective
of
of
an
enterprise,
there
may
be
some
issues
they
have
with
the
privacy
of
the
processes,
because
once
it's
on
a
public
blockchain,
even
though
it's
all
about
addresses
who
run
transactions-
and
there
are
some
help-
so
don't
know
randomized,
it's
still
that
third
party
could
get
some
information
out
of
it.
Just
because
the
smart
contract
is
there,
for
example,
you
could
so
to
say
screen
the
the
blockchain
for
other
smart
contracts
of
that
type,
and
then
you
would
have
an
idea
like
okay,
this
party,
who
did
the
smart
contracts.
A
They
do
like
hundreds
approval
processes
each
day,
might
give
you
some
idea
or
inside
this
enterprises,
or
you
can
check
the
timestamps
when
the
participants
gave
their
okay
and
then
telling
from
different
time
zones.
It
might
be
that
you
tell
that
they
are
on
from
Europe
or
Asia
or
the
USA
whatever.
A
What
I
want
to
say
is
that
the
blockchain
features
that
are
promising,
because
it's
immutable
and
you
can
use
it
like
a
like
a
registrar
to
or
a
notary
service,
to
see
who
gave
their
okay.
It's
still
a
problem
for
some
of
the
enterprises
to
make
this
public.
So
our
approach
from
YouTube
right,
of
course,
from
the
very
beginning,
was
to
support
many
different
block
chains
being
blockchain
agnostic.
And
then
the
answer
might
have
been:
okay,
don't
take
a
public
chain,
but
rather
take
a
private
chain
which
basically
looks
just
the
same.
A
So
the
idea,
the
one
of
the
main
goals
of
the
the
baseline
protocol,
is
to
provide
privacy
in
business
processes,
but
still
using
the
public
available
blockchain
with
all
the
countless
nodes
that
contribute
to
the
overall
security
of
the
system
to
use
their
public
blockchain,
some
kind
of
middleware
or
messaging
bus.
So
in
baseline,
the
complete
process
would
look
like
this.
You
still
have
a
template
model.
A
You
still
have
your
template
instance
and
in
the
end,
you
do
not
create
a
smart
contract,
but
something
that
is
called
a
shared
code
book
within
the
baseline
wording,
and
this
shared
code
book
holds
the
workflow
of
that
approval
process,
for
example
in
whatever,
for
example,
solidity.
But
it
could
also
be
like
c-sharp
Lynette
or
it
could
be,
could
be
s
ap
code,
whatever
the
parties
who
are
participating
on
this
approval
process
are
agreeing
on,
and
then
this
shared
codebook
is
used
by
all
the
participants.
A
So
the
baseline
architecture
ensures
that
the
participants
can
all
be
sure
that
the
other
party
is
using
the
same
code
that
they
not
altered
it
in
any
of
their
favor,
but
all
are
relying
on
the
same
code
and
they
do
the
messaging
so,
for
example,
giving
an
approval
in
a
private
manner
like
in
a
broadcasting
network.
The
first
version
is
using
the
whisper
protocol,
but
this
may
change
to
to
a
more
feasible
protocol
during
the
lifetime
of
the
baseline
development.
A
So
there
is
no
option
for
a
third
party
to
tell
from
from
timestamps
or
from
the
content
what
is
actually
hashed
or
which
business
process
is
used
here
or
who
are
the
participants.
So
this
is
the
the
main
idea
you
have
the
main
net,
with
all
its
it's
always
on
as
a
public
available
blockchain,
and
you
have
your
own
baseline
architecture
between
all
participants
of
a
business
process
and
from
the
unified
perspective
is
just
the
same
as
before.
A
It's
still
very
valuable
and
meaningful
to
have
all
the
cogeneration
stuff
beforehand,
because
now
it's
even
more
important.
If
you
talk
about
shared
code
books
so
code,
that
is
not
only
published
once
in
one
smart
contract
in
one
block
chain,
but
it's
shared
between
the
participants.
Then
it's
even
more
important
that
they
all
rely
on
the
same
understanding
and
the
same
model
and
not
have
like
individual
coding
for
these
code
books
for
every
single
use
case
they
want
to.
They
want
to
apply
on
the
logic.
A
So
this
is
the
the
basic
idea
and,
from
from
unep,
write
all
that
we
build
with
that
workflow
designing
the
automatic
code
generation,
the
automatic
integration
of
off
chain
systems,
using
that
these
code
books
and
also
the
contracts
and
the
Manor
makes
perfectly
sense.
And
that's
that's
a
good
thing
for
us
of
course,
and
there
are
even
steps
that
you
don't
don't
only
use
the
main
head
as
a
messaging
bus,
but
as
soon
as
it
comes
into
tokenization.
A
So
everything
that
comes
around
when,
when
it's
really
about
tokens,
then
of
course
the
main
net
or,
for
example,
in
theorem,
makes
even
more
sense,
because
it's
not
only
used
as
a
message
bus,
but
also
as
a
place
where
token
contracts
can
live
and
do
what
they
are
supposed
to
do
and
just
to
have
a
short
outlook.
If
tokenization
even
goes
further
further.
A
Like
that,
what
we
understand-
or
we
barter
with
in
uniprot
frequentiy
so
representing
world
assets
or
securities,
then
it
even
makes
more
sense
by
mentioning
all
that,
because
of
course
we
are
blockchain
agnostic
and
baseline
protocol
emphasizes
on
using
the
the
main
net.
So
the
public
ethereum
blockchain
as
a
messaging
bus.
Theoretically,
of
course,
you
could
use
other
block
chains
as
well
and
as
it's
a
open
source
pattern,
it's
perhaps
likely
to
be
adopted
by
other
block
chains
as
well,
but
as
soon
as
tokenization
comes
in.
A
Of
course,
it's
always
valuable
to
keep
in
mind
where
do
99%
of
the
tokens.
Nowaday
live
as
ERC
20
tokens
or
security
tokens,
or
whatever
it's
a
theorem,
and
that's
why
it's
a
very
good
choice
and,
in
our
opinion,
to
start
and
everything
that
is
built
around
baseline,
coming
from
integration,
for
example,
bringing
an
S
AP
system
to
use
the
baseline
protocol
could
also,
at
the
time
given
be
adopted
to
other
block
chains
if
needed
and
but
I
think
in
the
and
the
bootstrapping
phase,
where
we
are
currently
at
the
etherium.
A
A
Also
more
deep-diving
stuff
really
into
the
tech
stuff
and
showing
some
coding
of
development
progress,
also
from
Unipart.
If
you
are
interested
in
some
of
the
links
or
resources
I
mentioned
during
the
video,
please
check
out
the
description
section
of
this
YouTube
video
and
also
the
corresponding
block
on
uniprot
I/o.
Thank
you
very
much.