masa-finance / masa-node-v1.0 Goto Github PK
View Code? Open in Web Editor NEWMasa Blockchain Node
Home Page: https://masa.finance
License: MIT License
Masa Blockchain Node
Home Page: https://masa.finance
License: MIT License
enode://53814c71d6fc43a792cd886b66855af7583703f57dd537c08e2433b8d0947b7e4dfc4623e972821bce8c44fb64bf5e3d0660f57731d1a14d14d940b33c87e6e4@178.250.247.42:30300
I am ready to deploy the bootnode as I have personal hardware server cluster based in data center in Saint-Petersburg (Russia)
When I tried running the node with docker compose v1.25 I got the following error:
Unsupported config option for services.ui: 'extends'
I'm no docker expert but after a bit of research it looks like for v3 extends
is only supported since v1.27. The issue is discussed here
docker/compose#7588
PR added #71
I've installed and run a node more than 20h ago, but new day at morning I've discovered the VPN server dropped me and I can't access to network anymore. Maybe I could have access when somebody leaves. Looks like OpenVPN server has no more IPs for connections. Some guy wrote about it in the discord:
mercury — Today, в 7:33
I have some problems with openvpn connection, tun0 interface just do not receive any IP
I think there just no more IPs left on the server side @teslashibe
You are using net30 topology, so there is only 64 in /24 net
I think we better use subnet topology on server https://community.openvpn.net/openvpn/wiki/Topology
Correct me if I'm wrong, please
Here is some logs:
root@localhost:~/masanode/masa-node-v1.0# docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
7d3f7a4bdd9a quorumengineering/quorum:21.7.1 "/bin/sh -c 'DDIR=/q…" 17 hours ago Up 16 hours (healthy) 8546/tcp, 21000/tcp, 30303/tcp, 50400/tcp, 30303/udp, 0.0.0.0:22001->8545/tcp, :::22001->8545/tcp masa-node-v10_masa-node_1
root@localhost:~# netstat -rn
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
0.0.0.0 10.255.255.1 0.0.0.0 UG 0 0 0 ens192
10.255.255.1 0.0.0.0 255.255.255.255 UH 0 0 0 ens192
172.16.240.0 0.0.0.0 255.255.255.0 U 0 0 0 br-c97d3f3c1d40
172.17.0.0 0.0.0.0 255.255.0.0 U 0 0 0 docker0
root@localhost:~# openvpn3 sessions-list
No sessions available
root@localhost:~# openvpn3 session-start --config ${OPENVPN_CONFIG}
Using pre-loaded configuration profile '/root/openvpnconfig/masausrbad.ovpn'
Session path: /net/openvpn/v3/sessions/50c0a47esc077s4d16sbc6cs7f4a20f490da
session-start: ** ERROR ** Failed to start session
root@localhost:~# openvpn3 session-start --config ${OPENVPN_CONFIG}
Using pre-loaded configuration profile '/root/openvpnconfig/masausrbad.ovpn'
Session path: /net/openvpn/v3/sessions/e6d2bd45s02cfs42fas93c9s7b7a26c92800
session-start: ** ERROR ** Failed to start session
root@localhost:~# openvpn3 session-start --config ${OPENVPN_CONFIG}
Using pre-loaded configuration profile '/root/openvpnconfig/masausrbad.ovpn'
Session path: /net/openvpn/v3/sessions/8fcb31cas190es4dd2sb4dbs9b4eaff655c8
session-start: ** ERROR ** Failed to start session
root@localhost:~# openvpn3 session-start --config ${OPENVPN_CONFIG}
Using pre-loaded configuration profile '/root/openvpnconfig/masausrbad.ovpn'
Session path: /net/openvpn/v3/sessions/5ae9a48ds90a6s4555s9adfs6335f9cf959a
session-start: ** ERROR ** Failed to start session
root@localhost:~# openvpn3 session-start --config ${OPENVPN_CONFIG}
Using pre-loaded configuration profile '/root/openvpnconfig/masausrbad.ovpn'
Session path: /net/openvpn/v3/sessions/70d071f1s0d19s41ccs87a4sa0acd745cf22
session-start: ** ERROR ** Failed to start session
root@localhost:~# openvpn3 session-start --config ${OPENVPN_CONFIG}
Using pre-loaded configuration profile '/root/openvpnconfig/masausrbad.ovpn'
Session path: /net/openvpn/v3/sessions/9e92bf18sbbafs4fdds87f5s6be3b69e2f96
session-start: ** ERROR ** Failed to start session
root@localhost:~# openvpn3 session-start --config ${OPENVPN_CONFIG}
Using pre-loaded configuration profile '/root/openvpnconfig/masausrbad.ovpn'
Session path: /net/openvpn/v3/sessions/dbcfb42ds1343s44b0s813as974d80e76806
session-start: ** ERROR ** Failed to start session
p.s. just got connected when made more tries. But docker container didn't start to work itself. Just restarted docker container and it works fine, but problem with max connections still alive.
enode://50a714f915d94e6d1f07c8b9ace37df410e69e7bf313198f7124fc1315d20db5d3dc54a3e7cc74a2fa1ec7af19d488e047270f074ec0fde603d23654cec44bc1@193.17.92.44:30300
The Node-UI folder is missing from the repository
bad idea to recreate data dirs on every restart container.
i think base structure and genesis need to creane first run only ...
But i am not yet ready to offer a beautiful method for implementing this.
setar@masa-node:~/masa-node-v1.0$ git diff
diff --git a/docker-compose.yml b/docker-compose.yml
index 18934f8c..9dd8f944 100644
--- a/docker-compose.yml
+++ b/docker-compose.yml
@@ -21,14 +21,10 @@ x-masa-testnet-node-v10-def:
- -c
- |
DDIR=/qdata/dd
- rm -rf $${DDIR}
- mkdir -p $${DDIR}/keystore
- mkdir -p $${DDIR}/geth
GENESIS_FILE="/network/genesis.json"
CONSENSUS_RPC_API="istanbul"
NETWORK_ID=$$(cat $${GENESIS_FILE} | grep chainId | awk -F " " '{print $$2}' | awk -F "," '{print $$1}')
GETH_ARGS_istanbul="--emitcheckpoints --istanbul.blockperiod 1 --mine --miner.threads 1 --syncmode full"
- geth --datadir $${DDIR} init $${GENESIS_FILE}
geth \
--identity node$${NODE_ID}-${MASA_CONSENSUS:-istanbul} \
--datadir $${DDIR} \
@@ -54,6 +50,7 @@ services:
hostname: masa-node
ports:
- "22001:8545"
+ - "21000:21000"
volumes:
- vol1:/qdata
- ./network/testnet:/network:ro
enode://85d15b93169559f59a0630a5246c53adaf36ec00f99e715de465f107bfe75cdbe065d73047288d82d67f6984f7de4820bf61c20d61f7c6add3c1b546bf48ee52@91.189.133.78:30300
Initialize the node
In the node directory, initialize the first node:
geth --datadir data init ../network/genesis.json
must be
../network/testnet/genesis.json
after
PRIVATE_CONFIG=ignore geth --identity LuckyNodeTech --datadir data --bootnodes enode://91a3c3d5e76b0acf05d9abddee959f1bcbc7c91537d2629288a9edd7a3df90acaa46ffba0e0e5d49a20598e0960ac458d76eb8fa92a1d64938c0a3a3d60f8be4@54.158.188.182:21000 --emitcheckpoints --istanbul.blockperiod 1 --mine --miner.threads 1 --syncmode full --verbosity 5 --networkid 190250 --rpc --rpccorsdomain "*" --rpcvhosts "*" --rpcaddr 127.0.0.1 --rpcport 8545 --rpcapi admin,db,eth,debug,miner,net,shh,txpool,personal,web3,quorum,istanbul --port 30300
I get flag provided but not defined: -emitcheckpoints
Any idea?
Hi,
it's not the first time setting up a node, but a Masa node with go-ethereum and within Docker.
After fixing the two issues already reported here I'm now at the following points:
running "make test" I get
ok github.com/ethereum/go-ethereum/trie
FAIL
util.go:47: exit status 1
exit status 1
make: *** [Makefile:41: test] Error 1
when I run geth he does not abort due to an error, but is looking for peer nodes, wrting something to disk/cache etc.
executing PRIVATE_CONFIG=ignore geth --identity MasaMoonNode --datadir data --bootnodes enode://91a3c3d5e76b0acf05d9abddee959f1bcbc7c91537d2629288a9edd7a3df90acaa46ffba0e0e5d49a20598e0960ac458d76eb8fa92a1d64938c0a3a3d60f8be4@54.158.188.182:21000 --emitcheckpoints --istanbul.blockperiod 1 --mine --miner.threads 1 --syncmode full --verbosity 5 --networkid 190250 --rpc --rpccorsdomain "" --rpcvhosts "" --rpcaddr 127.0.0.1 --rpcport 8545 --rpcapi admin,db,eth,debug,miner,net,shh,txpool,personal,web3,quorum,istanbul --port 30300
I get the error "flag provided but not defined: -emitcheckpoints". While looking up this error I got references like "the flag provided but not defined message means that you are running a standard Ethereum geth executable, not Quorum. You need to make sure the Quorum geth is the first one found in your path."
Since I have not read anything about Quorum in the Masa guide I'm uncertain to install Quorum and configure it.
Any idea?
And the last thing is: Executing docker-compose up ui
gives me:
[+] Running 2/2
⠿ Network ui_default Created 0.1s
⠿ Container ui-ui-1 Created 0.1s
Attaching to ui-ui-1
ui-ui-1 | standard_init_linux.go:228: exec user process caused: exec format error
ui-ui-1 exited with code 1
So, that are the current issues. Now the question:
I have setup ufw on my VPS. Which port do I need to open for incoming requests? Are there any incoming requests? I saw port 8545, 21000, 30300 and 3000 for the UI.
Ah, there is another question: I saw the issue someone trying to connect MetaMask to Masa. I did not find anything about that in the guide. Where to look for and why should it be done?
many thanks for any help
Hi, I tried to pull Docker containers on Ubuntu 20.04 and node container is constantly crashing with the following error
uname -a gives '...5.4.0-105-generic #119-Ubuntu SMP Mon Mar 7 18:49:24 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux'
Latest docker
Docker-compose is v2.6.1
Any ideas how to fix it?
admin.addPeer("enode://27da4d3139c0b8f2327c7a9fa434f4d4a8ab9b65b0d3c8e11ba749ae51eb9f53efd38fa2560ddd116781cf3235b90ab800aad906ee32f4f99c6466bdbc7b8455@127.0.0.1:21000"")
admin.addPeer("enode://0eb7a3ec302fbc5945e78ba4f4b8a9df9f9788ca4c8970fa25f8bdd79ad73064caff5ac4dbba6550ce83fc8b4958d6152f4719475ed9adac2084a98e249119dd@83.171.249.107:21000")
admin.addPeer(“enode://779bd5a65647920d35cba0b006ba1408cc1ccb035d583831425e8a5ad7a74f53b93da9041d5be0384ce67284c7500a74d832ab0d6ddf3bf690942b6c679f006d@85.21.64.200:21000”)
admin.addPeer("enode://3dc1e7aa7e4fa832973480d4ce8ed9281f04e37504b259ff41d950aeec10b316a47eaffc25a5b332be80d83089f5a78240675ae04907af03f9f3b569d41304ac@139.162.189.112:21000")
admin.addPeer("enode://4ee69fc77b408199aea397afce75cc30a1720c6b2a28dcf90e3bc10b2b7e9eb52b6db0d48f2911933fa73b14d9b5accbb4a66ae556b20a1b1aa61b3c1859d2c0@172.105.72.127:21000")
admin.addPeer("enode://fbd40ee442c149df68e5d81341063329c52e40a222433ca5fce84af5147f87cf718bfff7b713c78156d20d0abe7da96ad3c6f8a6e8d1a41519d3b6d0f14535bd@139.162.169.232:21000")
admin.addPeer("enode://c8150fac4c1040811733b3637333db469fa62cc605b69c7678dc2582e371c829f049ef196fc0d563dbba10cce30edb3735b63e6cfa261e91eba426656871b16a@172.105.73.69:21000")
admin.addPeer("enode://e4cdf51e0f8e77ccb6d88160ea0e98f83af7f81bfd37c5f498d3c351952f7a769ccf9728b7e50405df6a9d2f63f1596d570e32c5ea17e65f9a461cf2b0512a2e@139.162.152.34:21000")
admin.addPeer("enode://7580741b59c89e4a1c14dea9f597a6dac4b0e79e54fbdc61eda4e85f1a18762f3810557aaa2ebd9df7fb74921221768cf6e5286037c702d4a86c6f8e393a04ff@172.104.246.232:21000")
admin.addPeer("enode://2dd2982bd60bf91ec7c0b5d9dd46083021a23d53a6854b4ed2b0d723e01bb3943b09a93ca25eed87dece3ae26912ab577ec55024c926dceea050468e3602a06d@139.177.176.107:21000")
enode://241e078355ec1ec5736ae0149d57799259e22c579a1dd68029ad40532e3c023653f73a667861b84bb254af7128cda19e07065b5b0c15c87a3af30c50a0066cbf@178.250.247.52:30300
Clean install ubuntu 20.4 LTS & full update
GO v1.17.5
bb1d842
~/masa-node-v1.0/src$ make all
break build with error:
signer/core/api.go:29:2: no required module provides package github.com/ethereum/go-ethereum/accounts/keystore; to add it:
go get github.com/ethereum/go-ethereum/accounts/keystore
util.go:47: exit status 1
exit status 1
make: *** [Makefile:26: all] Error 1
go get github.com/ethereum/go-ethereum/accounts/keystore - not work,
go get github.com/ethereum/go-ethereum - also not fix the error
P.S.
GO v1.17.1 - give same error
current source (56eaa13) not build:
go version
$ go version
go version go1.17.5 linux/amd64
build error
~/masa-node-v1.0/src$ make all
env GO111MODULE=on go run build/ci.go install
>>> /usr/local/go/bin/go build -trimpath -v -o /home/setar/masa-node-v1.0/src/build/bin/abidump ./cmd/abidump
signer/core/api.go:29:2: no required module provides package github.com/ethereum/go-ethereum/accounts/keystore; to add it:
go get github.com/ethereum/go-ethereum/accounts/keystore
error on get go module
~/masa-node-v1.0/src$ go get github.com/ethereum/go-ethereum/accounts/keystore
go get github.com/ethereum/go-ethereum/accounts/keystore: no matching versions for query "upgrade"
Command PRIVATE_CONFIG=ignore docker-compose up -d
Throw an error:
ERROR: The Compose file './docker-compose.yml' is invalid because:
Unsupported config option for services.ui: 'extends'
masa-node-v1.0/docker-compose.yml
Line 51 in 768dfdc
Docker version 20.10.16
docker-compose version 1.25.0
My node cant sync for 48 hrs already it just stuck at block 77884
eth.syncing { currentBlock: 77884, highestBlock: 3938700, knownStates: 0, pulledStates: 0, startingBlock: 2
In logs i constantly getting this kind of error
Apr 01 14:11:45 vmi837665.contaboserver.net geth[24553]: DEBUG[04-01|14:11:45.532] Ethereum handshake failed id=be359158062b10b4 conn=inbound err="network ID mismatch: 246 (!= 190260)" Apr 01 14:11:45 vmi837665.contaboserver.net geth[24553]: DEBUG[04-01|14:11:45.533] Removing p2p peer peercount=16 id=be359158062b10b4 duration=97.506ms req=false err="network ID mismatch: 246 (!= 190260)" Apr 01 14:11:45 vmi837665.contaboserver.net geth[24553]: DEBUG[04-01|14:11:45.659] Adding p2p peer peercount=17 id=374afccc4e5c317c conn=inbound addr=178.63.52.9:35106 name=Geth/v1.10.8-stable-... Apr 01 14:11:45 vmi837665.contaboserver.net geth[24553]: DEBUG[04-01|14:11:45.665] Ethereum handshake failed id=374afccc4e5c317c conn=inbound err="network ID mismatch: 23 (!= 190260)" Apr 01 14:11:45 vmi837665.contaboserver.net geth[24553]: DEBUG[04-01|14:11:45.665] Message handling failed in
snap peer=374afccc err=EOF Apr 01 14:11:45 vmi837665.contaboserver.net geth[24553]: DEBUG[04-01|14:11:45.665] Removing p2p peer peercount=16 id=374afccc4e5c317c duration=6.283ms req=false err="network ID mismatch: 23 (!= 190260)" Apr 01 14:11:46 vmi837665.contaboserver.net geth[24553]: DEBUG[04-01|14:11:46.819] Adding p2p peer peercount=17 id=eb80c0a92a5a3bb2 conn=inbound addr=54.164.251.194:51698 name=Geth/v1.9.7.0-v0.1.4... Apr 01 14:11:46 vmi837665.contaboserver.net geth[24553]: DEBUG[04-01|14:11:46.821] Ethereum handshake failed id=eb80c0a92a5a3bb2 conn=inbound err="network ID mismatch: 21 (!= 190260)" Apr 01 14:11:46 vmi837665.contaboserver.net geth[24553]: DEBUG[04-01|14:11:46.823] Removing p2p peer peercount=16 id=eb80c0a92a5a3bb2 duration=3.260ms req=false err="network ID mismatch: 21 (!= 190260)" Apr 01 14:11:46 vmi837665.contaboserver.net geth[24553]: DEBUG[04-01|14:11:46.863] Adding p2p peer peercount=17 id=c93f982c9c571f03 conn=inbound addr=150.230.40.84:29068 name=bor/v0.2.14-stable-1... Apr 01 14:11:46 vmi837665.contaboserver.net geth[24553]: DEBUG[04-01|14:11:46.864] Ethereum handshake failed id=c93f982c9c571f03 conn=inbound err="network ID mismatch: 137 (!= 190260)" Apr 01 14:11:46 vmi837665.contaboserver.net geth[24553]: DEBUG[04-01|14:11:46.864] Message handling failed in
snap peer=c93f982c err=EOF Apr 01 14:11:46 vmi837665.contaboserver.net geth[24553]: DEBUG[04-01|14:11:46.865] Removing p2p peer peercount=16 id=c93f982c9c571f03 duration=1.204ms req=false err="network ID mismatch: 137 (!= 190260)" Apr 01 14:11:47 vmi837665.contaboserver.net geth[24553]: DEBUG[04-01|14:11:47.571] Rejected inbound connnection addr=3.239.221.170:49126 err="too many attempts" Apr 01 14:11:47 vmi837665.contaboserver.net geth[24553]: DEBUG[04-01|14:11:47.840] Adding p2p peer peercount=17 id=f4beb83b5211d973 conn=inbound addr=164.68.112.215:49870 name=Geth/v4.3.0-stable-1... Apr 01 14:11:47 vmi837665.contaboserver.net geth[24553]: DEBUG[04-01|14:11:47.856] Ethereum handshake failed id=f4beb83b5211d973 conn=inbound err="network ID mismatch: 57 (!= 190260)" Apr 01 14:11:47 vmi837665.contaboserver.net geth[24553]: DEBUG[04-01|14:11:47.858] Message handling failed in
snap peer=f4beb83b err=EOF Apr 01 14:11:47 vmi837665.contaboserver.net geth[24553]: DEBUG[04-01|14:11:47.858] Removing p2p peer peercount=16 id=f4beb83b5211d973 duration=17.359ms req=false err="network ID mismatch: 57 (!= 190260)" Apr 01 14:11:48 vmi837665.contaboserver.net geth[24553]: DEBUG[04-01|14:11:48.081] Queued delivered header or block peer=b521e0a36904d609a5715cd75c2a8af6d5077d69891b831f8da63ecf74e911bf number=77897 hash="57eb00…75f834" queued=1
What are the requirements for bootnodes?
Hello!
standard_init_linux.go:228: exec user process caused: exec format error
uname -a
Linux Ubuntu-2110-impish-amd64-base 5.13.0-21-generic #21-Ubuntu SMP Tue Oct 19 08:59:28 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
docker version
Client: Docker Engine - Community
Version: 20.10.12
API version: 1.41
Go version: go1.16.12
Git commit: e91ed57
Built: Mon Dec 13 11:45:33 2021
OS/Arch: linux/amd64
Context: default
Experimental: true
Server: Docker Engine - Community
Engine:
Version: 20.10.12
API version: 1.41 (minimum version 1.12)
Go version: go1.16.12
Git commit: 459d0df
Built: Mon Dec 13 11:43:41 2021
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.4.12
GitCommit: 7b11cfaabd73bb80907dd23182b9347b4245eb5d
runc:
Version: 1.0.2
GitCommit: v1.0.2-0-g52b36a2
docker-init:
Version: 0.19.0
GitCommit: de40ad0
cat /etc/os-release
PRETTY_NAME="Ubuntu 21.10"
NAME="Ubuntu"
VERSION_ID="21.10"
VERSION="21.10 (Impish Indri)"
docker-compose version
docker-compose version 1.27.4, build unknown
docker-py version: 4.4.4
CPython version: 3.9.7
OpenSSL version: OpenSSL 1.1.1l 24 Aug 2021
docker image ls
REPOSITORY TAG IMAGE ID CREATED SIZE
hideonbushx/node-ui latest 9429770f1aa3 2 weeks ago 1.47GB
Hello!
Service UI in https://github.com/masa-finance/masa-node-v1.0/blob/main/docker-compose.yml#L52 dosent have docker-compose file in ./src/ui/docker-compose.yml
Hello! I have installed node Taraxa and Taraxa has already use port http://localhost:3000/.
In this way when i have installed Masa-finance, i have an error "Bind for 0.0.0.0:3000 failed: port is already allocated
ERROR: for ui Cannot start service ui: driver failed programming external connectivity on endpoint masa-node-v10_ui_1 (dcbc12fcdca8679aa4d7ac6d288a81691aabf281cc5b0f5d1d7cfe45f1acd8bc): Bind for 0.0.0.0:3000 failed: port is already allocated"
What i gone do?
gave my node identity with this geth --identity JohnpaulifediNODE and its syncing
now i started the node with this PRIVATE_CONFIG=ignore geth --identity JohnpaulifediNODE --datadir data --bootnodes enode://91a3c3d5e76b0acf05d9abddee959f1bcbc7c91537d2629288a9edd7a3df90acaa46ffba0e0e5d49a20598e0960ac458d76eb8fa92a1d64938c0a3a3d60f8be4@54.158.188.182:21000 --emitcheckpoints --istanbul.blockperiod 10 --mine --miner.threads 1 --syncmode full --verbosity 5 --networkid 190260 --rpc --rpccorsdomain "" --rpcvhosts "" --rpcaddr 127.0.0.1 --rpcport 8545 --rpcapi admin,db,eth,debug,miner,net,shh,txpool,personal,web3,quorum,istanbul --port 30300
but syncing when from 4% to 17%
what could be the issue here?
Hi, what about to add --maxpeers
flag to command line option when run geth?
Lot's of people has issue with no peers when install with your bootnodes provided.
Default maxpeers is 50 so when a bootnode reach 50 connections, nobody can connect anymore.
Also may add --maxpeers
flag to run user's node to increase incoming connections (need to update Readme)
After update to 1.03 and delete "data" folder yesterday, it worked fine and eth.syncing was "false".
Now, when we've got latest block the network says:
geth attach ipc:$HOME/masa-node-v1.0/data/geth.ipc --exec web3.eth.syncing
currentBlock: 4931,
highestBlock: 3938700,
knownStates: 0,
pulledStates: 0,
startingBlock: 2
}
Now highestBlock = 3938700 which seems to be an error.
Lots of ppl have this issue.
admin.addPeer("enode://401d37ceadb99f81cfd8e8d1c473f3ed7e065ad94268cb6f2a6fb3fb2ac4733d0ae6d7fb05fc0a00b626e110fb2b5c854a2d47bf860a1dc43cb49554f3dd171d@172.105.110.119:21000")
admin.addPeer("enode://54d51151b8be47df708df2f4ba70ac8f30954b5bff6ac11dd4b3d3c1202f4511ef86f8d6d87074e42a24f24a3c42cd059e49f76a25b870237ea4320b4e9272a0@172.105.111.221:21000")
admin.addPeer("enode://1e70ab2fd271f5d1368dd4b4e55feb57ea70dd82d6f4213714a5dbba3bf8711771e23fc3066e032ba9b4cf93989859210159650efad42e446607c78c988f6173@172.105.110.133:21000")
admin.addPeer("enode://e2ffea178542e70e05115f32d771bf5d793da7508ec3ddedcc9e4d9fffc0a002334ea6b0664b49b5ec4a7b14e850336d291f4677133923505c077dccdbc57ea7@139.162.224.140:21000")
admin.addPeer("enode://74effb61c8c5578819772d7bb6fa17ee20ebe23982af9ef0ff36cc1ba18eb05e6ee6ef6e44cdcf3548b3ed905f566a4660f733dcaf2c52cd3577570ecf05eea3@192.46.233.116:21000")
admin.addPeer("enode://ef96950807d90cf210113062e9a8c85b865877c83d1ef8480fa53ae3099e64a910c0b17ffa5eee1eb25046fa6d31b527a38bd709ffdf6e76a0572a661a6f454d@172.104.149.193:21000")
admin.addPeer("enode://75632f64ea8e00374fe6ef43d9ab5ea51ac3fce92e786caea231d9ca084e9b78c2d9b500a98f317802015a81551e5f55020cb0f24e20ab9027df22f6ecb6b5fb@172.104.247.197:21000")
admin.addPeer("enode://77201d47bc33d682c0fc39959786317e99710c236245ab6ad54409d6deda39b3aaa4cef5bddac1b9a2fd9d49e0d4e9575c84a0a32b724f96ba9a79a2a1de1caa@164.92.202.192:21000")
admin.addPeer("enode://8f9e4d894bed72ab811d3f15d34eb6b9e527f7b9071ac71e2d260770359b1ae3ee0662100cf23943eb3348f769c672f4184c637c2c7eb33fa893927996e9e6b5@139.162.153.145:21000")
admin.addPeer("enode://29c77a37c375f09b1c14e3f11a6e8143f60a809a145e0492ba03a01c1882d2acc04e2abeb642c336d60af879a4996b5c4aa8a39c99be307e6736ea60239f77d4@139.162.181.157:21000")
admin.addPeer("enode://373c58f32293d7d876d2b481e4ef1268557715858cfc72413be6e5ad47efd4f4d15713564dc32ca3fe56787202c406cc681b88122ae4fe496f1d48e02c3f3bc0@139.59.128.228:21000")
admin.addPeer("enode://59a320782dca51df0e06ec919e184ddaba10d445008d362d3833afb8f80bdfef3093b5d929fbbd2578d9470e1cab0f94de979397fe0b2dd5c85ccd2ead60add0@192.46.233.225:21000")
admin.addPeer("enode://9dbd1f8478c1f03d5c325144cc2dbefbfa926397e86ce11dcaab0e52edb9cc1688db992d493a3ea7f592690ec33a1338f1da0282f1dbe1f6683e1be0012344aa@170.187.185.45:21000")
admin.addPeer("enode://00e23b08adaf22da92475e8334bad7d605a2a5d02911715a04816d07a592e12d51a6ec285a328453d7da00f91119aae0fe830511af0f34244ab0ce2fd9dbc3a7@139.59.214.45:21000")
enode://54c77e53afd2f10680db1e55c66a0ac8e16fc8577ff35bf85b9620e307ca815fc472fe4fe5fa808ea6c97fe51b5246fbd850cb64c20e7f468ea77467e7a2f412@5.182.227.99:30300
A lot of newcomers (2) saying the only working bootnode is the port 30300 one
From README.md
Install The Masa Testnet Node v1.0
git clone https://github.com/masa-finance/masa-node-v1
cd masa-node-v1
Please fix:
git clone https://github.com/masa-finance/masa-node-v1.0.git
cd masa-node-v1.0
enode://355ad8acfa6c104bb65ffce14a97356f444347dfe9a59c13a813843c82fa811b60bc465b634b55de2b6b93bc10ecdc2a1a5d1b8598688b1798c4f01b8a8c6372@65.21.106.191:21000
Docker section:
docker exec -it masa-node-v10_masa-node_1
should be
docker exec -it masa-node-v10_masa-node_1 /bin/sh
enode://5ad3c6cdec198a519f62d02b784cc7f1270c3c86c46abe6ba6cdd174b47b7383a7c5e1363e7ca305c19ecd3180bdbd31a0e50e5ad265a47279a202823cd7c441@193.17.92.45:30300
ERROR[04-04|06:34:14.253] Failed to decode message from payload address=0xb8E1CBD079996642494fE7C62153f1B328961d16 err="unauthorized address"
INFO [04-04|06:34:15.007] Imported new chain segment blocks=1 txs=0 mgas=0.000 elapsed=1.084ms mgasps=0.000 number=101553 hash="d40fb5…62d935" dirty=0.00B
INFO [04-04|06:34:15.008] Commit new mining work number=101554 sealhash="6aefe1…6e2f16" uncles=0 txs=0 gas=0 fees=0 elapsed="486.523µs"
WARN [04-04|06:34:15.008] Block sealing failed err=unauthorized
INFO [04-04|06:34:24.209] Imported new chain segment blocks=1 txs=0 mgas=0.000 elapsed=1.169ms mgasps=0.000 number=101554 hash="d059c1…bc847d" dirty=0.00B
INFO [04-04|06:34:24.209] Commit new mining work number=101555 sealhash="577d8d…1c9306" uncles=0 txs=0 gas=0 fees=0 elapsed="467.667µs"
WARN [04-04|06:34:24.209] Block sealing failed err=unauthorized
Hi guys,
many thanks for the nice update. Everything went smoothly until coming to the point starting the node. I got the following errors:
ERROR[02-28|13:10:11.246] Unavailable modules in HTTP API list unavailable="[db shh quorum istanbul]" available="[admin debug web3 eth txpool personal ethash miner net]"
INFO [02-28|13:10:11.246] Security: TLS not enabled endpoint=127.0.0.1:8545 reason="no TLSConfigurationSource found"
INFO [02-28|13:10:11.246] HTTP server started endpoint=127.0.0.1:8545 prefix= cors=* vhosts=* isTls=false
INFO [02-28|13:10:11.246] Transaction pool price threshold updated price=1000000000
INFO [02-28|13:10:11.246] Updated mining threads threads=1
INFO [02-28|13:10:11.246] Transaction pool price threshold updated price=1000000000
ERROR[02-28|13:10:11.246] Cannot start mining without etherbase err="etherbase must be explicitly specified"
Any tipps for me?
Many thanks !!!
enode://af37a31dd90dde7472209308a72bdf2db425f4d78cb14aebdf94958c882d417a835d1ccfee02dde02ba65ef3171921b034138cba6e952fa53a8b3db19f57e4ba@85.15.176.35:30300
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.