PegaSysEng/pantheon

Joshua Fernandes

@joshuafernandes

@matias8_gitlab are you having any specific issues at the moment? We use it docker in much the same manner as we do when running them natively with the addition that we mount a volume for data and config (genesis file & keys for validators)

Felipe Faraggi

@faraggi

Hyperledger Besu 1.2.4 has been released!
Download here:
https://github.com/hyperledger/besu/releases/tag/1.2.4

Christian Felde

@cfelde

@faraggi would be good to get progress on hyperledger/besu#24

MadelineMurray

@MadelineMurray

@cfelde - have followed up on that one.

Christian Felde

@cfelde

Thanks @MadelineMurray , could you give me a pointer/url to your follow up? I can't seem to spot it..

Genysys

@Genysys

I know there was talk about this a while back, but does pantheon support a gethlike interactive console yet?

i.e. can i run something like this:

sudo docker run --rm -it quorumengineering/quorum:2.2.5 attach http://18.222.154.235:8545

MadelineMurray

@MadelineMurray

@Genysys you can connect the geth console - https://besu.hyperledger.org/en/stable/HowTo/Interact/APIs/Using-JSON-RPC-API/#geth-console

Genysys

@Genysys

does this mean geth has to be installed , or can we use an image like i have done above?

Felipe Faraggi

@faraggi

As long as you have access to the geth console, and it can communicate with your local besu env, it'll be fine.
(correct endpoints and flags)

Genysys

@Genysys

[ec2-user@ip-10-0-0-201 ~]$ sudo docker run --rm -it quorumengineering/quorum:2.2.5 attach http://13.58.206.181:8545 
WARNING: call to admin.getNodeInfo() failed, unable to determine consensus mechanism
Welcome to the Geth JavaScript console!

instance: pantheon/v1.2.0/linux-x86_64/oracle_openjdk-java-11
coinbase: 0xa65cefc421d574089d3aa1c5a48104042962ed4b
at block: 0 (Thu, 01 Jan 1970 00:00:30 UTC)
 modules: eth:1.0 ibft:1.0 net:1.0 web3:1.0

> eth.accounts
[]
> eth.account[0]
TypeError: Cannot access member '0' of undefined
    at <anonymous>:1:1

> eth.accounts[0]
undefined
>  admin.datadir
ReferenceError: 'admin' is not defined
    at <anonymous>:1:2

> eth.syncing
false
>

Nicolas MASSART

@NicolasMassart

Yes that's ok, you are using it correctly as indicated in http://besu.hyperledger.org/en/latest/HowTo/Interact/APIs/Using-JSON-RPC-API/#geth-console
The only errors here are because you try to access non existing functions on the console: Besu does not provide account management, hence the error for eth.account[0] and does not provide admin.datadir either.

For the sync returning false, it either means that it's not connected to peers ant then can't sync or already in sync with the peers.

Can you give us logs of this node to check the sync status?

Genysys

@Genysys

that will be tricky as i have destroyed the instance but will post it the errors come back

Nicolas MASSART

@NicolasMassart

Ok, let us know. Also, FYI, we moved to https://chat.hyperledger.org/channel/besu for Besu support.

Genysys

@Genysys

will dop

last question

does the format of this enode look right?

{
  "jsonrpc": "2.0",
  "id": 1,
  "result": "enode://3f0fa5a82a6e77a773f7ad62b02cb4519a71ac9894b52addaeae79e76fefe55fb580bcd9b72c882fbc4006dedd16d4fac42b288eb7d9d9df3d9944dd71a291e6@127.0.0.1:30303?discport=0"
}

Felipe Faraggi

@faraggi

I'm not too familiar with discport, the enode format is:
enode://<id>@<host:port>

Genysys

@Genysys

hmmm

Danno Ferrin

@shemnon

discport seems fine. That will open discovery on a different udp port each time however

the use of 127.0.0.1 however will limit visibility to the local machine. i.e. you cannot connect from an external source.

Mauhcs

@mauhcs

@NicolasMassart the link does not load. Is the chat up?

Edward

@EdJoJob

@mauhcs unfortunately you will need to go to https://chat.hyperledger.org first to log in, and then you can reach the besu channel. We are working with Hyperledger to get this transition and onboarding more seamless.

ashliechin

@ashliechin_twitter

Hey!
We just published our findings on a study of the distribution of ethereum nodes. Here’s how we found that 62% of all ethereum nodes are run in cloud and more stats. Please check it out!
https://chainstack.com/the-ethereum-cloud-vs-on-premises-nodes-conundrum/

Mauhcs

@mauhcs

@EdJoJob Thanks, I followed your instructions and I am in the chat already. Cheers

Erick Pacheco Pedraza

@eum602

Hi everyone, I would like to know what are cons of having opened p2p ports; is there any potential issue for that?; if so, how can we make more secure p2p communication in a production environment?. Any answer is well received. Thanks in advance.

Lucas Saldanha

@lucassaldanha

@eum602 are you planning to run your nodes on Mainnet or a private network?

Erick Pacheco Pedraza

@eum602

on a private-permisioned network @lucassaldanha

Lucas Saldanha

@lucassaldanha

@eum602 in a private permissioned network, if the set of nodes that will join the network is known, you could have firewall rules to expose the p2p ports only to/from the addresses of the servers where the nodes are running. The downside of this approach is that for each new node, you'd need to update the firewall rules.

@eum602 if you'll run all nodes in a cloud service like AWS, you also have the option to create the instances within a VPC, isolating the nodes from any access outside the VPC. Other cloud services offer a similar thing.

Erick Pacheco Pedraza

@eum602

I imagine, that could be for validator nodes, but what about regular nodes that are running outisde the VPC and are part of the network. For those regulars how can we deal with P2P ports?; thanks in advance.

Yunho Chung

@yunhochung

Hi!. I did deploy/invoke some smart contract and I got error in node log as below. " ERROR | PrivacyPrecompiledContract | Failed to process the private transaction: private transaction nonce 0 does not match sender account nonce 1." It seems that transaction is ok. Is it correct??

Felipe Faraggi

@faraggi

PSA:
Our next contributor call is tomorrow at 1500UTC.
For more details, and your timezone, check out the wiki's agenda:
https://wiki.hyperledger.org/display/BESU/2019-10-01+Besu+Contributor+Call

MadelineMurray

@MadelineMurray

@yunhochung - what Besu version are you using?

Our Besu chat is https://chat.hyperledger.org/channel/besu - you'll find more Besu developers there to answer questions

Unfortunately you will need to go to https://chat.hyperledger.org first to log in, and then you can reach the besu channel. We are working with Hyperledger to get this transition and onboarding more seamless.

Adam Schmideg

@adamschmideg

@MadelineMurray is there a desktop client for the chat app you’re using? I can’t recognize what it is. (I already logged in but don’t want to keep a browser tab open for it)

Danno Ferrin

@shemnon

https://rocket.chat/install

Adam Schmideg

@adamschmideg

thank you

Felipe Faraggi

@faraggi

Besu contributor call starting now: https://consensys.zoom.us/j/725448960

Felipe Faraggi

@faraggi

Yesterday's contributor call notes have been added to the wiki:
https://wiki.hyperledger.org/display/BESU/2019-10-01+Contributor+call

Felipe Faraggi

@faraggi

We're looking for contributors for this Truffle-Besu (pantheon) integration.
https://www.trufflesuite.com/blog/open-call-for-contributions-truffle-pegasys-eea-private-transactions
https://twitter.com/felipefaraggi/status/1179331828739710977
Any takers?

Enrique Arizón Benito

@earizon

Hi (Sorry to disturb, but I don't have the time to clone, fix and send back a pull request, so I broadcast it here for anyone interested). In besu-quickstart, consider changing "#!/bin/sh" by "#!/bin/bash". This will fix many weird errors in Debian 9 (and possible Alpine and other light-systems). They all default to simplest shells that will fail with any script containing "[[" conditionals.

Felipe Faraggi

@faraggi

Thanks for the tip @earizon, as a Linux user myself, I appreciate it.

Felipe Faraggi

@faraggi

@earizon https://pegasys1.atlassian.net/projects/PAN/issues/PAN-3215?filter=allopenissues&orderby=priority%20DESC

Nicolas MASSART

@NicolasMassart

@earizon updated version of the quickstart is now available https://github.com/PegaSysEng/besu-quickstart/releases/tag/1.3.0-RC1

Felipe Faraggi

@faraggi

Hyperledger Besu 1.3 has been released!!
Get your copy here: https://bintray.com/hyperledger-org/besu-repo/besu/1.3.0#
Change log available at: https://github.com/hyperledger/besu/releases/tag/1.3.0

Orion 1.4.0 has been released!
https://github.com/PegaSysEng/orion/releases/tag/v1.4.0
Questions and more information here: https://gitter.im/PegaSysEng/orion

Where communities thrive

People

Repo info

Activity