[ANN] Expanse (EXP) - 1st Stable fork of Ethereum (New Algo + PirlGuard)

[defaced]

Something i'm noticing is that my mainnode, the one all yall are connecting too, is getting tons of connections. My other nodes however are only connecting to my main node and nothing else. I didnt change anything about how nodes gossip with each other, or peer discovery, which then makes me wonder why this is happening.

I'm connected to both linux and windows nodes.

Please delay the launch by 48 hours until the issue is resolved.

I'll talk with the others about it.

[1714029435]

1714029435

[1714029435]

1714029435

[1714029435]

1714029435

[1714029435]

1714029435

[1714029435]

1714029435

[1714029435]

1714029435

[Dave5]

Something i'm noticing is that my mainnode, the one all yall are connecting too, is getting tons of connections. My other nodes however are only connecting to my main node and nothing else. I didnt change anything about how nodes gossip with each other, or peer discovery, which then makes me wonder why this is happening.

I'm connected to both linux and windows nodes.

Please delay the launch by 48 hours until the issue is resolved.

I'll talk with the others about it.

Thanks!

We want the launch to be FAIR. Doesn't look like much testing was done.

[defaced]

Something i'm noticing is that my mainnode, the one all yall are connecting too, is getting tons of connections. My other nodes however are only connecting to my main node and nothing else. I didnt change anything about how nodes gossip with each other, or peer discovery, which then makes me wonder why this is happening.

I'm connected to both linux and windows nodes.

Please delay the launch by 48 hours until the issue is resolved.

I'll talk with the others about it.

Thanks!

We want the launch to be FAIR. Doesn't look like much testing was done.

Wait.. what? Lol.. thats what we are doing right now man.

[techbytes]

Something i'm noticing is that my mainnode, the one all yall are connecting too, is getting tons of connections. My other nodes however are only connecting to my main node and nothing else. I didnt change anything about how nodes gossip with each other, or peer discovery, which then makes me wonder why this is happening.

I'm connected to both linux and windows nodes.

Please delay the launch by 48 hours until the issue is resolved.

I'll talk with the others about it.

Thanks!

We want the launch to be FAIR. Doesn't look like much testing was done.

Wait.. what? Lol.. thats what we are doing right now man.

I'm mining on testnet right now...  I'm ready.   

-tb-

[defaced]

Something i'm noticing is that my mainnode, the one all yall are connecting too, is getting tons of connections. My other nodes however are only connecting to my main node and nothing else. I didnt change anything about how nodes gossip with each other, or peer discovery, which then makes me wonder why this is happening.

I'm connected to both linux and windows nodes.

Please delay the launch by 48 hours until the issue is resolved.

I'll talk with the others about it.

Thanks!

We want the launch to be FAIR. Doesn't look like much testing was done.

Wait.. what? Lol.. thats what we are doing right now man.

I'm mining on testnet right now...  I'm ready.   

-tb-

how many nodes are you connected too?

[yudhistira]

what is nodes?
how to mining with nodes?
whether the miners I've been running correctly?
if my coin will be lost at launch?

[herbitcoins]

Something i'm noticing is that my mainnode, the one all yall are connecting too, is getting tons of connections. My other nodes however are only connecting to my main node and nothing else. I didnt change anything about how nodes gossip with each other, or peer discovery, which then makes me wonder why this is happening.

I'm connected to both linux and windows nodes.

First launch clean node (without peers connected or admin.addPeer("enode:// ... or bootnodes)
launch this node with --vmodule=udp=6,server=6,downloader=6 console


 >>> then try to add 'problematic node' for ex admin.addPeer("enode://4055ec69e53df4bfecb95e3b65c28e4f2a1145a3bdc4d85d077b552248cf159951afd649f044783bebf48b902fbc0e96978c76236fd4ab3d5ef7d95d72b84ee5@[::]:42786")


I0912 10:27:40.704880    2840 server.go:624] dyn dial conn 0055fd5099543df0 [::1
]:42786 failed checkpoint posthandshake: Connected to self

>>> Now try with the working node : this one admin.addPeer("enode://f944c6702a78a0cbcd6505b76daff069dad2e45ff88896c475da2bef47091c88e5b4042211233e397ad958be998003a2674151e60719c5fdeeff5f8cc2c231a1@74.196.59.103:42786")


> I0912 10:29:05.517708    2840 server.go:475] <-posthandshake: static dial conn
 f944c6702a78a0cb 74.196.59.103:42786
I0912 10:29:05.519694    2840 server.go:481] <-addpeer: static dial conn f944c67
02a78a0cb 74.196.59.103:42786
I0912 10:29:05.520124    2840 server.go:670] Added Peer f944c6702a78a0cb 74.196.
59.103:42786
I0912 10:29:05.520515    2840 server.go:465] <-taskdone: static dial f944c6702a7
8a0cb 74.196.59.103:42786
I0912 10:29:05.624936    2840 downloader.go:215] Registering peer f944c6702a78a0
cb
I0912 10:29:08.564406    2840 server.go:465] <-taskdone: discovery lookup (1 res
ults)
I0912 10:29:08.564950    2840 server.go:431] new task: discovery lookup
I0912 10:29:11.954980    2840 downloader.go:237] Attempting synchronisation: f94
4c6702a78a0cb, head 0x6b5c6511, TD 70648672834
I0912 10:29:11.955575    2840 downloader.go:278] Block synchronisation started
I0912 10:29:11.956055    2840 downloader.go:322] Synchronizing with the network
using: f944c6702a78a0cb, exp/61


No error for this one.

So conclusion : Encryption handshake problem.

What it coulb be? lot of reasons ...

[GoldenEye]

how many nodes are you connected too?

I'm connected to only one node, but tried all the other nodes mentioned in this thread.

> admin.peers
[{
    Caps: "exp/60, exp/61",
    ID: "f944c6702a78a0cbcd6505b76daff069dad2e45ff88896c475da2bef47091c88e5b4042211233e3 97ad958be998003a2674151e60719c5fdeeff5f8cc2c231a1",
    LocalAddress: "192.168.0.101:33095",
    Name: "Gexp/v1.1.2-74cee8c3/linux/go1.4",
    RemoteAddress: "74.196.59.103:42786"
}]

[GoldenEye]

2 minutes later (with the same running server instance):

> admin.peers
null
> admin.peers
null
> admin.peers
null
> I0912 16:48:19.542541   29792 chain_manager.go:661] imported 0 block(s) (0 queued 1 ignored) including 0 txs in 9.543578ms. #888 [1dd75bcd / 1dd75bcd]
> admin.peers
null
>

[GoldenEye]

Now again:
> admin.peers
[{
    Caps: "exp/60, exp/61",
    ID: "f944c6702a78a0cbcd6505b76daff069dad2e45ff88896c475da2bef47091c88e5b4042211233e3 97ad958be998003a2674151e60719c5fdeeff5f8cc2c231a1",
    LocalAddress: "192.168.0.101:34810",
    Name: "Gexp/v1.1.2-74cee8c3/linux/go1.4",
    RemoteAddress: "74.196.59.103:42786"
}]


Could it be that the nodes given in the OP have not network port (42786) opened in the firewall

[techbytes]

Something i'm noticing is that my mainnode, the one all yall are connecting too, is getting tons of connections. My other nodes however are only connecting to my main node and nothing else. I didnt change anything about how nodes gossip with each other, or peer discovery, which then makes me wonder why this is happening.

I'm connected to both linux and windows nodes.

Please delay the launch by 48 hours until the issue is resolved.

I'll talk with the others about it.

Thanks!

We want the launch to be FAIR. Doesn't look like much testing was done.

Wait.. what? Lol.. thats what we are doing right now man.

I'm mining on testnet right now...  I'm ready.   

-tb-

how many nodes are you connected too?

Just the one I added manually.

[GoldenEye]

The running peer (ID: "f944c6702a78a...") has an IP (74.196.59.103) in the ID peer address, all other only [::] (IPv6 broadcast?)

How should my client connect the peer in a decentralized network?

[herbitcoins]

admin.addPeer("enode://0055fd5099543df005a13ea5bec103def47340de81a6c1b0ba20f8ef756a7fe575b362976b1a52c9f561dda95321700a1c9e769004d25278ce53d2d6aa0b65b7@80.240.138.173:42786")

[defaced]

Everyone admin.peers and see if you are connected to others now.. Also remember to portforward all UDP traffic for port 42786 for the machine hosting the node.

Also, everyone on linux

Code:

git pull origin
make gexp

then restart your node and see if you find some more peers

I'll remake the windows binaries soon.

[herbitcoins]

admin.addPeer("enode://0055fd5099543df005a13ea5bec103def47340de81a6c1b0ba20f8ef756a7fe575b362976b1a52c9f561dda95321700a1c9e769004d25278ce53d2d6aa0b65b7@80.240.138.173:42786")

this one will work 100% sure

just type admin.peers to confirm

[defaced]

admin.addPeer("enode://0055fd5099543df005a13ea5bec103def47340de81a6c1b0ba20f8ef756a7fe575b362976b1a52c9f561dda95321700a1c9e769004d25278ce53d2d6aa0b65b7@80.240.138.173:42786")

this one will work 100% sure

just type admin.peers to confirm

Yes that works fine.
It is odd. I have three nodes.
Two nodes recognize each other and the third node as peers.
The third node does not recognize the other two nodes as peers.

I was noticing the same sort of behavior also. It is strange. Whats strange about it is, the behavior is inherited from ETH since I didnt change that stuff at all. I found though that once I forwarded all UDP traffic on my nodes, everything started working alot smoother.

[Dave5]

Everyone admin.peers and see if you are connected to others now.. Also remember to portforward all UDP traffic for port 42786 for the machine hosting the node.

Also, everyone on linux

Code:

git pull origin
make gexp

then restart your node and see if you find some more peers

I'll remake the windows binaries soon.

Done that admin.peers   is null.

Did you hardcode nodes or we have to enter them maunaly?

[defaced]

Everyone admin.peers and see if you are connected to others now.. Also remember to portforward all UDP traffic for port 42786 for the machine hosting the node.

Also, everyone on linux

Code:

git pull origin
make gexp

then restart your node and see if you find some more peers

I'll remake the windows binaries soon.

Done that admin.peers   is null.

Did you hardcode nodes or we have to enter them maunaly?

hardcoded like 6 of them. Did you set up your router to port forward?

Also you are on the develop branch right?

[skunk]

everything works fine here on lan without port forwarding:

Code:

instance: Gexp/v1.1.3-df8d5237/linux/go1.4.2
 datadir: /home/skunk/.expanse
coinbase: 0xe3d38133565af3acf698bb6f193a7c9d9269a8b3
at block: 905 (Sat, 12 Sep 2015 17:47:00 CEST)
modules: admin:1.0 db:1.0 debug:1.0 exp:1.0 miner:1.0 net:1.0 personal:1.0 shh:1.0 txpool:1.0 web3:1.0
> net.peerCount
4
> admin.peers
[{
    Caps: "exp/60, exp/61",
    ID: "f944c6702a78a0cbcd6505b76daff069dad2e45ff88896c475da2bef47091c88e5b4042211233e397ad958be998003a2674151e60719c5fdeeff5f8cc2c231a1",
    LocalAddress: "192.168.100.246:50910",
    Name: "Gexp/v1.1.2-74cee8c3/linux/go1.4",
    RemoteAddress: "74.196.59.103:42786"
}, {
    Caps: "exp/60, exp/61",
    ID: "4055ec69e53df4bfecb95e3b65c28e4f2a1145a3bdc4d85d077b552248cf159951afd649f044783bebf48b902fbc0e96978c76236fd4ab3d5ef7d95d72b84ee5",
    LocalAddress: "192.168.100.246:45994",
    Name: "Gexp/v1.1.3-df8d5237/linux/go1.4",
    RemoteAddress: "45.55.217.136:42786"
}, {
    Caps: "exp/60, exp/61",
    ID: "5da15ed702057b08c841857226a532b4169c3e248189a26585d4c7812887c8a2588d4e30092ebacdbaf2893acdae0910db92fd91b8c7df10ef7fd4a8b05b543f",
    LocalAddress: "192.168.100.246:55798",
    Name: "Gexp/v1.1.3-ec3fb93c/linux/go1.4",
    RemoteAddress: "138.128.169.51:42786"
}, {
    Caps: "exp/60, exp/61",
    ID: "6806712796f1e84b868d895c2f63b59ef90a7ae28ac3ce8a5dd4bf534778468652473882c9a0e0259ba0e7fb80257992031b5b5ed4f902f8dadc3bd0fe576732",
    LocalAddress: "192.168.100.246:53369",
    Name: "Gexp/v1.1.3-ec3fb93c/linux/go1.4",
    RemoteAddress: "212.18.233.114:42786"
}]
> web3.fromWei(exp.getBalance(exp.coinbase))
240

will:

Code:

git pull
make
./build/bin/gexp account new
./build/bin/gexp --rpc

suffice on launch? or should i do something else?
thank you

[defaced]

Updated the windows builds.

https://github.com/expanse-project/go-expanse/tree/develop/BUILDS-GEXP/gexp1.1.3-go1.5.1