Package Details: bee-git 0.1.2.r0.gb7d9824f-1

Git Clone URL: (read-only, click to copy)
Package Base: bee-git
Description: A framework for IOTA nodes, clients and applications in Rust
Upstream URL:
Keywords: DLT IOTA
Licenses: Apache
Submitter: setBoolean
Maintainer: setBoolean
Last Packager: setBoolean
Votes: 1
Popularity: 0.147469
First Submitted: 2021-04-02 15:57
Last Updated: 2021-05-17 10:44

Latest Comments

setBoolean commented on 2021-05-03 21:27

Mostly on Discord. The public key and peer id are derived from the private key so giving the node only the private key is enough, thats's also the reason I restrict all access to these files to the bee user with 600.

tsangares commented on 2021-05-03 21:16

Why is the private key my identity and what do I do with the public key and peer id? Also where did you learn these steps?

setBoolean commented on 2021-05-03 20:50

My package runs the id generation at first installation and puts it in /etc/bee/id there you will find Your p2p private key: XXXXXXX and this is the identity you put in config.toml. There should also be an info message about this when installing this package for the first time.

Edit: Yeah I think this justifies a PR, at least for as the step regarding bee p2p-identity and how to use it isn't mentioned anywhere. And just to be clear I have no affiliation with the IOTA Foundation whatsoever.

tsangares commented on 2021-05-03 20:08

I don't have an identity yet. I can generate one from bee p2p-identity but I don't see what to do with that data. The config file does not have a section for private keys and when I put the p2p PeerID in the identity field of config.toml running bee then spits out, invalid identity string length.

EDIT So I read the code in /home/myname/.cache/yay/bee-git/src/bee/bee-node/src/ and saw that the identity required a 128 character hex string. I generated a random hex string and put it in as my identity and it seems to work now. Although, that wasn't really well documented. Should I make a PR on this documentation or just wait for them to further develop things?

setBoolean commented on 2021-05-03 19:49

Did you copy over your identity to the new config file. And please clear the content of /var/lib/bee but not the directory itself.

tsangares commented on 2021-05-03 19:28

Hey setBoolean, I am still getting the same issue. I just ran yay -S bee-git and waited for the rust to compile. Then I did sudo cp /etc/bee/config.toml.pacnew /etc/bee/config.toml and it still gives me the same error Failed to build node builder. Do I need to edit the config file?

setBoolean commented on 2021-05-01 10:51

Issues should be fixed now and the config files provided by upstream should now be correctly integrated. There is now also an info message after upgrading to diff ones config files to check for changes made upstream as the package doesn't touch your original configs. Be careful to copy your existing identity to the new config files or it will be gone. You may have to delete the contents of your /var/lib/bee directory, when deleting the whole directory don't forget to change ownership back to bee:bee

setBoolean commented on 2021-05-01 08:19

This is NOT an upstream issue. A fix will be deployed in the next few hours.

tsangares commented on 2021-05-01 04:15

Issue with installing:

██████╗ ███████╗███████╗
██████╦╝█████╗  █████╗
██╔══██╗██╔══╝  ██╔══╝
╚═════╝ ╚══════╝╚══════╝

2021-04-30 21:08:46 bee ERROR Failed to build node builder: Storage backend operation failed: Unhealthy storage: Idle, remove storage folder and restart.

Made an issue on their github: