Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    kambit
    @kambit
    @Shirikatsu If you have time, please help check my steps. Thank you very much!
    kambit
    @kambit
    I check the error is from require( checkSignature(_chainId, signedHeader[12].toBytes(), _rlpUnsignedBlockHeader, parentBlockHash), "Signer is not validator" ); in SubmitBlock method. In the checkSignature method, extraDataSig is 0x0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000. I donot know why extraDataSig is abnormal.
    Shirikatsu
    @Shirikatsu
    @kambit Hi kambit. Thanks for pasting this.

    So your steps are slightly jumbled here. Registering a chain requires you to provide a genesis block. What this does is then gives you a base from which you will start submitting consequent blocks by referencing the previous one. This is how the submission of blocks works to ensure that you are submitting something correct (by checking against the previous known block for validator sets and the valid signature(s) against the block being submitted).

    In this case you've registered the chain by using block 513 as the genesis but also attempting to submit the same block 513. If you submit block 513 as your genesis, you will need to submit block 514 onwards. Thus in your case, if you want to use block 513 (which contains your transaction with the transaction you want to prove and use for interoperation) you must register block 512 as your genesis with RegisterChain, then submit block 513 with SubmitBlock.

    kambit
    @kambit
    @Shirikatsu Thank you for your explanation! I will try again. Thank you very much!!!
    Coenie Beyers
    @coeniebeyers
    Hi, are you using the tendermint implementation from https://docs.tendermint.com/master/introduction/what-is-tendermint.html ?
    Shirikatsu
    @Shirikatsu
    @coeniebeyers Hi Coenie, we'll be using a slightly different version of Tendermint implemented in the Autonity client.
    The block validation mechanisms remain the same, but some of the validator rotating and economic mechanisms have not yet been completed.
    Coenie Beyers
    @coeniebeyers
    hi @Shirikatsu! Thanks :)
    Do you have some documentation specific to your implementation that you could share with me?
    Shirikatsu
    @Shirikatsu
    Hey @coeniebeyers
    So implementation docs don't yet exist as we're still in the midst of completing and hardening the implementation. We are trying to follow the Tendermint specification written by the Tendermint guys though. By the time we finish the implementation we should have documents out detailing it and outlining any deltas between our implementation vs Cosmos Tendermint.
    Although the source code at the moment is probably your best source of documentation https://github.com/clearmatics/autonity/tree/master/consensus/tendermint :D
    Out of curiosity, what interests you? :D
    Coenie Beyers
    @coeniebeyers
    okay awesome, thanks!
    I'm trying to do a deeper dive into the differences between IBFT2 and Tendermint used by you guys, but needed to first make sure which implementation you are using :)
    Coenie Beyers
    @coeniebeyers
    @Shirikatsu have you done tests with more than ~20 validators in a single network?
    Guillaume
    @glesaint
    Thanks for the presentation on the EEA WG
    Shirikatsu
    @Shirikatsu
    @coeniebeyers I'm sorry for missing your message! I'm not entirely sure. We have a different team working on our client and the implementation of the consensus. Try https://github.com/clearmatics/autonity/ . Sorry I haven't got any answers on that front.
    @glesaint You're welcome! Let us know if you have any issues or questions. Happy to help.
    Sara Feenan
    @saronimo
    @glesaint Would be good to hear a bit more about the use case so we can weave in practical examples to the taskforce. Would you be able to shoot me an email -> sf at clearmatics.com thanks!
    Fabian Vogelsteller
    @frozeman
    @Shirikatsu i would like to talk to you guys about some ideas for side chains using part of the work you guys did with ion.
    Lets connect here, or in telegram (same user channel)
    Zoe Nolan
    @zoenolan
    @frozeman @Shirikatsu is currently off but I'm happy to chat here or elsewhere
    Fabian Vogelsteller
    @frozeman
    Hi super
    I guess a call would be super, as its easiest to explain that writting
    Fabian Vogelsteller
    @frozeman
    its some technical questions
    Friedrich
    @maxrobot
    Hi Fabian, if you send an email to opensource@clearmatics.com then we can organise a call :)
    Fabian Vogelsteller
    @frozeman
    thx
    done