Agree

I was thinking about a same approach. Just want to know another opinions.

just note. The topic is about deffinition of Public Permissioned

Thx for your anwer, if i understand well u count is as a public  if it fits atleast into the first criterion

1) Read - blockchain explorer
2) Submit TX - send money
3) be part of consensus mechanism - validate TXs, create blocks

The question was theoretical, and decentralization is not important within this question.
(I wondered where is the line to tell that its public and not private)

Hi,

I was just wondering, how to understand differences in these kind of blockchains and its combinations.

Public - open for public
Private - closed for public
Permissionless - no further permission to read, propose TXs or take part on consensus
Permissioned - some restriction on different levels (read, propose TXs or take part on consensus)

Now combinations:

Public permissionless - just bitcoin and other staff (free and open)
Private Permissioned - Maybe just internal blockchain in some organization
Private Permissionless - doesnt exist

Public permissioned - Now the intersting part begins (at least for me)

How to define this kind? I can imagine some blockchain which is open source and doesnt restrict at least Read or Proposing TXs permissions for public, but the consensus part is restricted to certain entities.

In real world (dont hate me, Im not fan of it) it could be something like Ripple, or is there any other project which suits better?
Do you have better explanation for these terminology nuances? or Public permissioned blockchain is just same as Private permissioned blockchain at all

(thx. for your time, looking forward for constructive answers and suggestions )