Skip to content

Moved license note #129

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
MadelineMurray merged 4 commits into from
Jan 31, 2020
Merged

Moved license note #129

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
bb1e8f9
Added default data location
MadelineAu Jan 20, 2020
9479a8c
Merge branch 'master' of https://github.com/hyperledger/besu-docs
MadelineAu Jan 29, 2020
aa204b0
Moved licence note
MadelineAu Jan 29, 2020
b1f84a5
Merge branch 'master' into dappUpdate
MadelineMurray Jan 31, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 7 additions & 4 deletions docs/Concepts/Permissioning/Onchain-Permissioning.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,13 +6,16 @@ description: Onchain Permissioning
Onchain permissioning uses smart contracts to store and maintain the node, account, and admin whitelists.
Using onchain permissioning enables all nodes to read the whitelists from a single source, the blockchain.

!!! important
The dependency chain for our implementation of onchain permissioning includes [web3js](https://github.com/ethereum/web3.js/) which is
LGPL licensed.
!!! note
The permissioning smart contracts and Permissioning Management Dapp are a separate product to Hyperledger Besu
and are provided in the [PegaSysEng/permissioning-smart-contracts](https://github.com/PegaSysEng/permissioning-smart-contracts) repository.

Custom smart contracts and dapps can be implemented to work with onchain permissioning.

## Permissioning Contracts

The permissioning smart contracts are provided in the [PegaSysEng/permissioning-smart-contracts](https://github.com/PegaSysEng/permissioning-smart-contracts) repository:
The permissioning smart contracts provided in the [PegaSysEng/permissioning-smart-contracts](https://github.com/PegaSysEng/permissioning-smart-contracts)
repository are:

* Ingress contracts for nodes and accounts - proxy contracts defined in the genesis file that defer the permissioning logic to the
Node Rules and Account Rules contracts. The Ingress contracts are deployed to static addresses.
Expand Down
3 changes: 3 additions & 0 deletions docs/HowTo/Backup/Backup.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,6 +18,9 @@ If installed locally, the default data location is the directory in which Besu i
We recommend mounting a [separate volume to store data](../Get-Started/Run-Docker-Image.md#starting-besu).
Use the [`--data-path`](../../Reference/CLI/CLI-Syntax.md#data-path) command line option to pass the path to Besu.

The default data location is the directory in which Besu is installed
or `/opt/besu/database` if using the [Besu Docker image](../../HowTo/Get-Started/Run-Docker-Image.md).

Having some data reduces the time to synchronise a new node. Periodic backups can be performed of
the data directory and the data sent to your preferred backup mechanism. For example, cron job and
rsync, archives to cloud such as s3, or `tar.gz` archives.
Expand Down