@jlpell Guess I’m most curious what it’s purpose is.
Seeing it separated out and such.
As it is in the code we have that kind of verbiage in the code with things like section chains which are what evolved from data chains I believe but this one is new and I know there are some things coming along and wasn’t sure if perhaps it was related…
Yes that’s it @Nigel it’s all lingo from data chains and now the Section Chain. So SectionChain is a linked list where a key is signed by the previous key. We don’t identify who made up that key except in the current block and that is where we link the SAP (Section Authority Provider).
The SAP tells us the members of the group (Elders) plus their key and this section key part as well as identifying the prefix (as the section keys are not related to prefix and require a mapping). This SAP is signed by the previous key.
Would be interested to know beyond SafeId for the individual, what might become possible for groups shared access to data. I don’t know, if that’s a matter of iterating a shared password on each change and whether there are simple options for this. I don’t know then if necessarily a member retains access to what they had access to, in the event they fall outside that group later, or whether this is less fundamental and more a layer on top managing this.
I’m just speculating without getting traction to be sure of atm… so, I don’t know if one option is some mutable list of members and individual knocks the door that is the list and is granted access or not.
Getting that Thursday feeling again who knows what we are going to find out tomorrow.
I used to measure time passing by Saturday Nights now it’s Thursday afternoons that are my peak of the week.
haha, yous are fast. @chriso is diving about testing and dekinking the new release process the now. So you may see some versions come and go. Don’t panic!
Panic? When have you ever seen the good folk of this forum panicking?! Nothing but cool heads, unhurried hands and reasoned discussion around here these days
