New sealer request: 0x1E3db8B04144832dE4D41B7c51fd8471cA26c7ed

[slyfox90]

Fill this form to identify yourself

Required information

• Your identity (Full name, company): Félix Mouhat, Saint Gobain Research Paris
• A contact email (corporate email only): [email protected]
• Company web site that display your sealer address to prove that you are you you pretend: ? (I am not sure to understand)
• Your sealer address (ie the address that should sign the blocks): 0x1E3db8B04144832dE4D41B7c51fd8471cA26c7ed

Motivations

Test Kerleano POC within IMA context

[guenoledc]

Company web site that display your sealer address to prove that you are you you pretend: ? (I am not sure to understand)

In theory, we should make sure that the sealer address and the requesting user is really operating for the institution. One way of doing it is to have an admin controlling an https website to display the sealer address so we can be sure that it comes from the company.

In your case we will do an exception

[guenoledc]

@wiktorhejchman @johanhormark @johnny78500 could you review and make up your mind in accepting St Gobain as a sealer for Kerleano.

These tests will allow us to reherse the actual onboarding in PoCRNet.

Thanks

[guenoledc]

@slyfox90 Could you confirm that you can maintain the sealer node as a test net node in the long run?

The testnet needs to stay stable and nodes that are dropping causes other nodes to take over. But if more that half of the nodes are down the network stale to protect against forks and brain split attacks

Also, as sealer you will start receiving CRC (testnet ones), after the audit, please confirm that you will manage them carefully to not largely distribute them to actors with potential intention to conduct attacks on the network (a small size network is not as reliable than a large one)

[guenoledc]

I confirm @slyfox90 email @saint-gobain

[slyfox90]

@guenoledc: what does it actually implies to maintain the sealer node? In principle, I should be able to do so if the daily/weekly actions are not too time-consuming.

For the CRCs, yes, I confirm that I will manage them carefully and keep them. What are the actions to do to audit my node?

[guenoledc]

@slyfox90

Running a sealer implies (in Kerleano) little workload, but the node should be running 24/7. Our nodes run without actions since several months now.
In test net, to get your node assessed for the environmental footprint, I can do it in a fake model as soon as your node is in the consensus.

Thanks for the acknowledgement of the CRC production

[guenoledc]

@slyfox90
with @wiktorhejchman (SEB) we are ok with granting you a sealer capacity. So I will proceed

[guenoledc]

One approval done from my node

> clique.getSnapshot()
{
  hash: "0x12f2e920a9f8df662b711cc1ce53e1ff64d61ae532dc46f242ad2af9ee4ebc57",
  number: 3295513,
  recents: {
    3295511: "0x20c8f6d7e11c42c83c9af2f6144c963315106fc9",
    3295512: "0x1311aef86d1db33db945fc488eeff1c6105b9593",
    3295513: "0xcca833ec5bb4fceb5145fa2fd65c94c446028ff6"
  },
  signers: {
    0x1311aef86d1db33db945fc488eeff1c6105b9593: {},
    0x20c8f6d7e11c42c83c9af2f6144c963315106fc9: {},
    0xc16c63da5f6e464148ffc0bcef9e761a16af6004: {},
    0xcca833ec5bb4fceb5145fa2fd65c94c446028ff6: {},
    0xec3f218d9876bfc01e9a4601575fe60f1b2c8f76: {}
  },
  tally: {
    0x1e3db8b04144832de4d41b7c51fd8471ca26c7ed: {
      authorize: true,
      votes: 1
    }
  },
  votes: [{
      address: "0x1e3db8b04144832de4d41b7c51fd8471ca26c7ed",
      authorize: true,
      block: 3295512,
      signer: "0x1311aef86d1db33db945fc488eeff1c6105b9593"
  }]
}

[guenoledc]

@slyfox90 Hope you are doing well

We haven't been able to progress on your request. But I will try to get it promoted.
Do you still want your node to participate to the consensus ?

[slyfox90]

Hello Guénolé, No problem, for the moment I am very busy on other topics not related to blockchain so you can pause my request. Thank you for taking the time to keep me posted on this very nice project. Kind regards, Félix Le mer. 12 juil. 2023 à 19:23, Guénolé de Cadoudal ***@***.***> a écrit :

…

@slyfox90 <https://github.com/slyfox90> Hope you are doing well We haven't been able to progress on your request. But I will try to get it promoted. Do you still want your node to participate to the consensus ? — Reply to this email directly, view it on GitHub <#40 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEZ4EW7U6AACDOI2J7SQR3DXP3MPNANCNFSM6AAAAAAX5UES7M> . You are receiving this because you were mentioned.Message ID: ***@***.***>