Welcome to the multiverse: bridging the Zenon ecosystem

Development ╰ Funding | Submissions
,
128

UPDATE: All 14 guardians have provided NoM and EVM addresses.
UPDATE 2: They have been NoMinated: Zenon Transaction Details | Zenon Hub

7 Likes
129

what is the minimum number of Orchestrators required to run the bridge? Also, can I fire up an Orchestrator? I see it was updated 2 days ago.

3 Likes
130

We’ll start with 40 and see how it goes. If a TSS key is not generated in the first 24 hours, we’ll lower it to 30 and wait until there are enough participants.

Yes, you can already run the orchestrator. It might still be updated, but we’ll make announcements once a final version is out.

By itself, it won’t do much until the “official” orchestrator bootstrap peer is announced and added to the orchestrator’s config.json

2 Likes
131

So all Pillars aren’t orchestrators ?

132

you can elect to become one, if you run the required binary.

133

So how does this works ? I run the binary and wait but the orchestrator needs to be tied to a pillar or those are two separate things ?

134

The orchestrator binary requires a pillar producer address and password. You can get that by running the status command with the znn-controller

You will provide that information to the orchestrator binary along with the address of a znnd and geth node. I plan to run a small orchestrator node with 2 vCPUs and 4G RAM.

I’ll write up instructions soon.

1 Like
135

I’ll be ready to fire up one on my Nintendo Switch Ubuntu version. I then will proceed to shill telling people we run interop’ solutions for Zenon on Nintendo Switchs while theirs is crap and not even that decentralized.

136

@samamu if the guardians are nominated shouldn’t they be returned by the security rpc methods?

sonRpc Information: 8 : {"id":3,"method":"embedded.liquidity.getSecurityInfo"}
JsonRpc Verbose: 8 : Sent: {
  "jsonrpc": "2.0",
  "id": 3,
  "method": "embedded.liquidity.getSecurityInfo",
  "params": []
}
JsonRpc Information: 7 : {"id":3}
JsonRpc Verbose: 7 : Received: {
  "jsonrpc": "2.0",
  "id": 3,
  "result": {
    "guardians": [],
    "guardiansVotes": [],
    "administratorDelay": 17280,
    "softDelay": 8640
  }
}

JsonRpc Information: 8 : {"id":3,"method":"embedded.bridge.getSecurityInfo"}
JsonRpc Verbose: 8 : Sent: {
  "jsonrpc": "2.0",
  "id": 3,
  "method": "embedded.bridge.getSecurityInfo",
  "params": []
}
JsonRpc Information: 7 : {"id":3}
JsonRpc Verbose: 7 : Received: {
  "jsonrpc": "2.0",
  "id": 3,
  "result": {
    "guardians": [],
    "guardiansVotes": [],
    "administratorDelay": 17280,
    "softDelay": 8640
  }
}
137

They were only nominated, they need to be commited and they will be commited tomorrow. There is a timechallenge of 2 days between nomination and commitment.

2 Likes
138

@sumamu what all steps do we have left? Any approximate date of when bridge would be live?

139

NoM guardians are set. We’re working on deploying the solidity bridge contract and waiting for some funds to cover the gas costs.

3 Likes
140

Can the community help with the gas funds?

1 Like
141

Can confirm, security info is now returning the guardians.

{
  "jsonrpc": "2.0",
  "id": 3,
  "result": {
    "guardians": [
      "z1qphnq6jfaf82kmpyuuc88983ar66dmh7e59f67",
      "z1qppk2p26xwwzu5w4zyzwknrx28whvjgy9ukc6h",
      "z1qprccs7kjvx9q78m5v5ghwwfvxr6py8rtwcfrd",
      "z1qpxswrfnlll355wrx868xh58j7e2gu2n2u5czv",
      "z1qqcz0rmkz7f5442hjjr0thh2v6txu4875eyrkd",
      "z1qqeyp02thdets4k245fnnjpk764ls65gwsy0cg",
      "z1qr6k9c0z73c2zx22grhcw702slyz0gelt2uwvd",
      "z1qr7urykpjth3w9lcl66atgvu5fc0ywawzha220",
      "z1qrawthjzd95hcz73r3e5wd0xxzjmrt4vfqla0z",
      "z1qrgh8w9q3xj5a2t2atnt3reqhh0akm4qae8ezk",
      "z1qrztagl9rukq3ltdflnvg4zrvpfp84mydfejk9",
      "z1qzjnnpmnqp6uqz2m9uet8l5e42ewwaty2mqcpy",
      "z1qzup2zm6c9g68t085zjn5ycvdnr0u4pt0k4c80",
      "z1qzymmtmfr3gxz3fr80cq94rgaefzkvst4e90lz"
    ],
    "guardiansVotes": [
      "z1qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqsggv2f",
      "z1qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqsggv2f",
      "z1qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqsggv2f",
      "z1qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqsggv2f",
      "z1qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqsggv2f",
      "z1qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqsggv2f",
      "z1qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqsggv2f",
      "z1qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqsggv2f",
      "z1qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqsggv2f",
      "z1qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqsggv2f",
      "z1qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqsggv2f",
      "z1qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqsggv2f",
      "z1qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqsggv2f",
      "z1qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqsggv2f"
    ],
    "administratorDelay": 17280,
    "softDelay": 8640
  }
}
142

done

1 Like
143

The contracts have been deployed and we’re now in the process of configuring them. It takes a few days to do that because of the security we’ve implemented, which requires us to propose changes first and then accept them a few days later, after the timechallenge is complete.

2 Likes
144

I would like to bring to your attention that it would be wise to at least update the chain id identifier (currently 3) in the syrius chrome extension, as even if you add a valid live public node the transactions never get received.

There is no way to do it in the UI.

1 Like
145

Did you check both releases? There’s one for mainnet and one for testnet.

1 Like
146

I think the plan is to release walletconnect asap so people can use syrius instead of the extension with the bridge webapp.

1 Like
147

Working on it. WalletConnect v2 is still work in progress and there is a lot of undocumented behavior. Next week hopefully we have a fully functional implementation.

8 Likes