In this quick tutorial, we will cover Understanding How Permissions Work for Decentralized Systems. This tutorial will introduce you to the Catenis permission system, which will be the subject of the remaining tutorials in the Catenis Flow tutorial series. This system was envisioned and built to protect decentralized applications and devices.
In this video we will cover:
Prerequisite
After watching Understanding How Permissions Work for Decentralized Systems, feel free to watch the next video, Evaluating Catenis Permission Levels, to further expand your knowledge.
Subscribe to our channel for more Bitcoin Blockchain building videos! https://www.youtube.com/c/BlockchainofThings
Links from this video for easy access:
To sign up for your free account, head to our website www.blockchainofthings.com.
Join our community forum for the quickest response time to all your questions and concerns. This forum is our customer support. https://forum.blockchainofthings.com/
[Music]
Hi, this is Claire for Blockchain of Things.
This tutorial will introduce you to the Catenis Permission System.
The Catenis Permission System was envisioned
and built to protect decentralized applications and devices.
Let’s get a better understanding of how permissions work for decentralized systems.
To handle permissions on the decentralized open public Bitcoin Blockchain,
Catenis creates the virtual equivalent of a shield or
force field that can be set on the devices you control.
This is because Catenis does not control the Global Bitcoin Blockchain,
and is unable to keep a random transaction from being sent to any address across the Blockchain.
Therefore, Catenis shields any unauthorized transactions from
ever reaching any device across our network,
and manages permissions for devices which are under your control.
This is why permissioned events are set on the subject or controlling device.
The subject device is the device you control and when setting permission for a given event
you are allowing or denying your subject device to receive events.
Catenis blocks any unwanted events from ever reaching your device.
As an example, if you control virtual device “A”
and set the permission event
“Receive Message” to allow for device “C”,
and deny, for all other devices
it means that random devices can still attempt to send a message to device “A”.
Costing them a network fee and a Bitcoin amount above the bare minimum value that can be sent.
Also known as the dust.
But device “A” will never receive it.
Unless it came from device “C”.
Catenis effectively creates a force field around each device from within its own network and completely shields from systems connected to the Bitcoin Blockchain outside its network.
Great job!
After watching this tutorial, you should have a better idea of how permissions work for decentralized systems,
and you’re ready to go deeper into the Catenis Permissioning System.
In our next tutorial, you’ll learn about the different levels of permission rights used by Catenis.
[Music]