Chaos Unicorn Day LIVE Discussion


#42

Ah, that is true, mine is lazy thing based on the eth.beta that doesn’t work.
Do you have some success with your config?
Also, make sure that you are running the very latest commit of status-go, there was one bug fixed there that might not allow running a mailserver: https://github.com/status-im/status-go/commit/96aba9f3afa27110399db3748755011d94916aa1


#43

So I managed to setup my own mailserver about a week ago and have been using that ever since, figured I’d be good to go for chaos day.

Turns out I am not, tried adding one of the bootnodes listed here but no luck :confused:


#44

My BootNode: "enode://43c1357211478acad2290f4206405eeda426fac5df4e5b6a2c8bb2fb3d4245a55[email protected]191.6.92.157:30403"

My Mailserver: "enode://8a7839270b6f96e3163596f6c957abcc6cb1cd9872e3ecf09610c1b5d511c721365c6fdddafd3e2e9bbe2d3acc719bf779a970a97033fca10a4c22bd0725bdb1:[email protected]:30303"

My mailserver is now serving me messages, it connected with the other 4 mailservers listed here, so if you use mine you will get messages from those aswell.

A config file for whoever want to startup their own mailserver:

Replace the contents of config/cli/fleet-eth.beta.json

{
  "Rendezvous": false,
  "NoDiscovery": false,
  "ClusterConfig": {
    "Enabled": true,
    "Fleet": "eth.beta",
    "BootNodes": [
      "enode://bbdcc75aedfd86bdd8812e412e8e1d99da6bb6faeb93cf9cf9ce79009e9bba416[email protected]34.251.227.15:30403",
      "enode://43c1357211478acad2290f4206405eeda426fac5df4e5b6a2c8bb2fb3d4245a55[email protected]191.6.92.157:30403",
    ],
    "TrustedMailServers": [
      "enode://8a7839270b6f96e3163596f6c957abcc6cb1cd9872e3ecf09610c1b5d511c7213[email protected]191.6.92.157:30303",
      "enode://6fa400daf954a9766aa0bb9a29ac461214fb407a6bc0d805bc6c3f2f9424a047e[email protected]34.251.227.15:30303",
      "enode://b7a2fe6c8b53650076cb71b5acfad89a74adb2f123ad21d21e9a6dec733299f03[email protected]77.216.106.68:30304",
      "enode://1dabf696e734115ecb023eaaf8d9263ba53d24d67aa40750383d75ab4df82669d[email protected]165.227.79.62:30303",
      "enode://f05f9b7460ebc6c0f812981e7ebd837a6b9c29dc952dc922ba32c5ad1b6220ab5[email protected]100.16.172.52:30303"
    ],
    "StaticNodes": [
      "enode://8a7839270b6f96e3163596f6c957abcc6cb1cd9872e3ecf09610c1b5d511c7213[email protected]191.6.92.157:30303",
      "enode://6fa400daf954a9766aa0bb9a29ac461214fb407a6bc0d805bc6c3f2f9424a047e[email protected]34.251.227.15:30303",
      "enode://b7a2fe6c8b53650076cb71b5acfad89a74adb2f123ad21d21e9a6dec733299f03[email protected]77.216.106.68:30304",
      "enode://1dabf696e734115ecb023eaaf8d9263ba53d24d67aa40750383d75ab4df82669d[email protected]165.227.79.62:30303",
      "enode://f05f9b7460ebc6c0f812981e7ebd837a6b9c29dc952dc922ba32c5ad1b6220ab5[email protected]100.16.172.52:30303"
    ],
    "RendezvousNodes": [
     
    ]
  }
}

#45

By default some things didnt worked aswell on CUD:

  • ENS Usernames Lookup
  • Dapps (including ENS Usernames Registration).
  • Wallet balances
  • Crypto-Fiat value

after running geth light client and specifying a “Custom Network Settings” pointing to the RPC I opened, now
I am able to sucessfuly query the balances of my tokens in CUD, also I registered a ens name using status in unicorn day https://etherscan.io/tx/0xbd7ce297e33989a223e73cb55b1a500d9cccfa6d68604741a22245e5d60635dd, now I am the proudly owner of “unicorn.stateofus.eth”.

I needed to wait until light sync catches up with recent block to be able to use it.

If you are running also a mailserver, you need to set a different RPC port to geth light client (for ethereum) and another to status-go mailserver.

Using my own mailserver, my own ipfs (even it infura ipfs was not blocked in CUD), and my own light client is getting me almost totally around CUD, and able to use Status Network with no problems without the status official cluster.


#46

I added Jakub’s mailserver and bootnode on Status Desktop/Linux but no peers were found. When I manually selected his mailserver, 1 peer was found and I started receiving messages. However when I re-enabled automatic mailserver selection, the selection moved away from Jakub’s mailserver and started testing the cluster servers.


#47

Yeah, it is probably worth adding to the feedback document.


#48

By request we’ll have a dedicated retrospective first. Retrospective on Thursday 11am UTC, in Status Calendar. Optional. Please add people I missed, added a random selection of people involved. Agenda: https://notes.status.im/DeeWO2TGSVy7PeJiNIfmpQ#