Skip to content

Commit cfec3e2

Browse files
authored
multi-tenancy now works with onchain groups (#527)
* multi-tenancy now works with onchain groups Signed-off-by: Sally MacFarlane <[email protected]> * capitalization Signed-off-by: Sally MacFarlane <[email protected]>
1 parent b72f8ad commit cfec3e2

File tree

2 files changed

+5
-9
lines changed

2 files changed

+5
-9
lines changed

docs/Concepts/Privacy/Flexible-PrivacyGroups.md

Lines changed: 4 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
11
---
2-
description: Flexible Privacy Groups
2+
description: Flexible privacy groups
33
---
44

5-
# Flexible Privacy Groups
5+
# Flexible privacy groups
66

77
Flexible privacy groups use smart contracts to store and maintain the group membership. You can add
88
and remove members to and from flexible privacy groups.
@@ -16,16 +16,14 @@ and remove members to and from flexible privacy groups.
1616

1717
Flexible privacy groups are an early access feature. Do not use in production networks.
1818

19-
Flexible privacy groups are not supported with [multi-tenancy](Multi-Tenancy.md).
20-
2119
The flexible privacy group interfaces might change between releases. There might not be an
2220
upgrade path from flexible privacy groups created using v1.5 or earlier to enable use of flexible privacy
2321
group functionality in future versions.
2422

2523
It's not recommended to create flexible privacy groups in a chain with existing
2624
[offchain privacy groups](Privacy-Groups.md).
2725

28-
## Group Management Contracts
26+
## Group management contracts
2927

3028
The privacy group management contract bytecode is hard-coded into Hyperledger Besu and when you
3129
create a privacy group, the contract bytecode is part of the genesis state of the privacy group.
@@ -42,7 +40,7 @@ and upgrade the management contract.
4240
The owner is identified by the signing key. Transactions to add and remove participants, or upgrade
4341
the management contract, must be signed by the same key that signed the group creation transaction.
4442

45-
## Flexible Privacy Group IDs
43+
## Flexible privacy group IDs
4644

4745
When creating a flexible privacy group, generate the privacy group ID for the group outside of Besu
4846
and pass the ID as a parameter.

docs/HowTo/Use-Privacy/Use-FlexiblePrivacy.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -16,8 +16,6 @@ membership of [flexible privacy groups](../../Concepts/Privacy/Flexible-PrivacyG
1616
[Flexible privacy groups](../../Concepts/Privacy/Flexible-PrivacyGroups.md) are an early access
1717
feature. Do not use in production networks.
1818

19-
Flexible privacy groups are not supported with [multi-tenancy](../../Tutorials/Privacy/Configuring-Multi-Tenancy.md).
20-
2119
The flexible privacy group interfaces may change between releases. There may not be an
2220
upgrade path from flexible privacy groups created using v1.5 or earlier to enable use of flexible privacy
2321
group functionality in future versions.
@@ -52,7 +50,7 @@ the [web3.js-eea library](https://github.com/PegaSysEng/web3js-eea):
5250

5351
!!! tip
5452

55-
The Orion logs for Orion 1 and Orion 2 displays `PrivacyGroupNotFound` errors. This is expected
53+
The Orion logs for Orion 1 and Orion 2 display `PrivacyGroupNotFound` errors. This is expected
5654
behavior because private transactions check offchain and onchain to find the privacy group for
5755
a private transaction.
5856

0 commit comments

Comments
 (0)