You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/private-networks/concepts/permissioning/plugin.md
+6-2Lines changed: 6 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,12 +10,16 @@ tags:
10
10
11
11
You can define complex [permissioning](index.md) solutions by building a plugin that extends Besu functionality.
12
12
13
-
The plugin API provides a `PermissioningService` interface that currently supports connection permissioning and message permissioning.
13
+
The plugin API provides a `PermissioningService` interface that currently supports connection (node) permissioning, transaction permissioning and message permissioning.
14
14
15
-
## Connection permissioning
15
+
## Connection (node) permissioning
16
16
17
17
Use connection permissioning when deciding whether to restrict node access to known participants only.
18
18
19
+
## Transaction permissioning
20
+
21
+
Use transaction permissioning when deciding whether to restrict transaction processing based on transaction properties.
22
+
19
23
## Message permissioning
20
24
21
25
Use message permissioning to propagate different types of devP2P messages to particular nodes. For example, this can be used to prevent pending transactions from being forwarded to other nodes.
0 commit comments