Sabitlenmiş Tweet
as part of @RBAInfo @DigiFinanceCRC Project Acacia, here's a primer on pubilc versus permissioned DLTs (distributed ledger technology), and on the back of the @RedbellyNetwork Insights podcast on right now (see x.com/RedbellyNetwor…), here's some explainers
First up Public vs Private DLT
Private Permissioned DLT:
- Only selected, known participants (such as specific banks or financial institutions) are allowed to join and validate transactions.
- Access is tightly controlled and not open to the general public; every participant is vetted and given explicit permission to participate.
- Used when confidentiality and control are top priorities, often for sensitive financial transactions.
Public Permissioned DLT (think more eligibility criteria which depends on market as @RedbellyAlan mentions in the show):
- The underlying platform is open and potentially accessible to anyone for certain functions (like reading the blockchain or using apps), but only approved participants can validate transactions or issue assets.
- A wider group can interact with the platform, but core functions (like settling tokenised assets or issuing CBDC) are restricted to those given explicit permission.
- Balances transparency and openness with the need for regulatory control and permissioned access.
In summary:
So in summary
- Private permissioned = access and participation are tightly restricted to a closed group.
- Public permissioned = the network is broadly accessible, but only whitelisted participants can perform critical functions.
Redbelly Network@RedbellyNetwork
Redbelly Insights - Episode 11 x.com/i/broadcasts/1…
English
