Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Yucong Sun
    @thefallentree
    Not yet, we are actually in process of implementing it
    if you have raw block data is relatively easy to manually extract it though
    Matt
    @22tanmat_twitter
    can you drop some pointers? Are you referring to the output from eth_getBlockByNumber ?
    Yucong Sun
    @thefallentree
    the way to get signer is to (from raw block) :
    1. get header.extra_data , seperate it into A: original extra_data and B : last 65 bytes of signatue
    2. get pubkey using keccka256 recover using (header with orignal extra_data).hash and B
    3. get signer address from pubkey
    get raw block data using exisitng api and implement above mentioned logic... or wait maybe next week for an parity json api
    Matt
    @22tanmat_twitter
    Thank you!
    Nikola Jokic
    @JohnnySheffield

    I'm trying to get a better understanding of the nonce value, reading through the spec:

    1.) Nonce value must be NONCE_DROP (0x0000000000000000) when voting to remove a signer,
    2.) Nonce value must be NONCE_AUTH (0xffffffffffffffff) when voting to add a signer
    3.) Nonce value must be NONCE_DROP on checkpoint block.
    4.) All other times must not take up any other value except NONCE_DROP or NONCE_AUTH.

    So the question is - what should be the default nonce value if the block is not casting a vote, and the block is not a checkpoint block?
    Nikola Jokic
    @JohnnySheffield
    It seems default nonce value should be NONCE_DROP, having NONCE_AUTH would mean constantly casting votes for 0x000.... as a signer. More details here: PegaSysEng/pantheon#762
    Yucong Sun
    @thefallentree
    nonce-drop
    just check author field =000...00 for voting
    5chdn
    @5chdn
    I think I will write a Clique v2 spec soon
    We learned a lot from Görli
    ChainSafe Systems
    @ChainSafeSystems
    amazing to hear :)
    Yucong Sun
    @thefallentree
    Yeah it might also be useful to define an official extension field in the eth block structure.
    So we don’t have to abuse extra data or something. I kind of thought seal fields are suppose for that purpose
    Nikola Jokic
    @JohnnySheffield
    @thefallentree Can you please point me to the latest stable parity-clique branch suitable for building or should i go with clique-v5 release?
    Yucong Sun
    @thefallentree
    use the last commit on master branch
    I'm going to release an new one after addressing the PR comments
    roninkaizen
    @roninkaizen
    @JohnnySheffield
    did you had problems with the version5 of fallentrees parity version?
    Nikola Jokic
    @JohnnySheffield
    none that i noticed while working on explorer, but did not get the chance running an authority on it
    James Ray
    @jamesray1

    Hi all, I got a notification that I was approved for https://gitcoin.co/issue/goerli/testnet/9/2178, but then Afri cancelled it. Now I see this Twitter convo: https://twitter.com/MPtherealMVP/status/1100808223844651008.

    I think I will write a Clique v2 spec soon

    It will be good to see that.

    Jared Wasinger
    @jwasinger
    I'm curious what additions would be made to the clique v2 spec
    James Ray
    @jamesray1
    :+1:
    Juan Leni
    @jleni
    Hi guys. I am starting to play with clique. With respect to V2 specs, when are you planning to have that available?
    By the way, are there any integration tests in geth, parity or any of the existing implementations?
    Talha Cross
    @soc1c
    Talha Cross
    @soc1c
    also check this ethereum/go-ethereum#19239
    Jared Wasinger
    @jwasinger
    for clique V2, what if we modified the protocol to have INTURN block difficulty modified based on the number of signers? I.e. set the block difficulty to floor(len(signers) / 2) + 1 so that even if all NOTINTURN signers broadcast blocks immediately, there won't be reorg that removes the INTURN block.
    eh nvm... actually this might affect safety. cuz in turn signers can delay and cause massive reorgs
    Jared Wasinger
    @jwasinger
    problem with the approach is actually that out-of-turn blocks will all get reorged away
    Talha Cross
    @soc1c
    2019-03-26 00:27:16  Imported #304300 0x696d…a88c (1 txs, 0.02 Mgas, 2 ms, 0.71 KiB)
    2019-03-26 00:27:21  Imported #304300 0xb9d0…ff76 (0 txs, 0.00 Mgas, 1 ms, 0.59 KiB)
    2019-03-26 00:27:31  Imported #304301 0x467174a4 (1 txs, 0.04 Mgas, 5 ms, 0.77 KiB)
    2019-03-26 00:27:34  Imported #304301 0x03055f50 (1 txs, 0.04 Mgas, 1 ms, 0.77 KiB)
    2019-03-26 00:27:38  Imported #304301 0x0e548ecd (0 txs, 0.00 Mgas, 0 ms, 0.59 KiB)
    2019-03-26 00:27:46  Imported #304302 0x6c6e3966 (0 txs, 0.00 Mgas, 2 ms, 0.59 KiB)
    2019-03-26 00:27:50  Imported #304302 0xd19d1695 (0 txs, 0.00 Mgas, 2 ms, 0.59 KiB)
    2019-03-26 00:28:01  Imported #304303 0x363f8547 (0 txs, 0.00 Mgas, 1 ms, 0.59 KiB)
    2019-03-26 00:28:02  Imported #304303 0x11a92871 (0 txs, 0.00 Mgas, 1 ms, 0.59 KiB)
    2019-03-26 00:28:05  Imported #304303 0xa3e73435 (0 txs, 0.00 Mgas, 0 ms, 0.59 KiB)
    that's so weird, check the block numbers
    seen on kotti testnet
    2019-03-26 00:28:46  Imported #304306 0xa5df938b (0 txs, 0.00 Mgas, 0 ms, 0.59 KiB)
    2019-03-26 00:28:48  Imported #304306 0x72856241 (0 txs, 0.00 Mgas, 0 ms, 0.59 KiB) + another 1 block(s) containing 0 tx(s)
    2019-03-26 00:29:02  Reorg to #304307 0x34c1…af4f (0xa5df938b #304305 0x512f2932 0x72856241)
    2019-03-26 00:29:02  Imported #304307 0x34c1…af4f (0 txs, 0.00 Mgas, 1 ms, 0.59 KiB)
    2019-03-26 00:29:04  Reorg to #304307 0xce788e13 (0x34c1…af4f 0x72856241 #304305 0x512f2932 0xa5df938b)
    2019-03-26 00:29:04  Imported #304307 0xce788e13 (0 txs, 0.00 Mgas, 1 ms, 0.59 KiB)
    and check the long reorgs
    SiddharthMalhotra
    @SiddharthMalhotra
    Hello Gorli Clique
    Talha Cross
    @soc1c
    Hey :)
    Talha Cross
    @soc1c
    we are starting to work on clique v2 this weekend
    will share results as soon as they are available
    Talha Cross
    @soc1c
    see also ongoing discusisons at https://github.com/goerli/eips-poa/issues
    Talha Cross
    @soc1c
    @jwasinger @JohnnySheffield do you have any thoughts on EIP-1955? ethereum/EIPs#1955
    Yann Carlier
    @yanncarlier

    INFO blockchain: Finished processing beacon block slot=7276
    [2019-05-18 11:43:40] INFO blockchain: Applying LMD-GHOST Fork Choice Rule
    [2019-05-18 11:43:41] INFO blockchain: Chain head block and state updated headRoot=0x45960c7b2be7f69238f9dbbe headSlot=7276 stateSlot=7276

    [2019-05-19 04:30:16] ERROR p2p: Failed to reconnect to peer failed to dial : all dials failed

    • [/ip4/127.0.0.1/tcp/4000] failed to negotiate security protocol: message did not have trailing newline
    • [/ip4/35.224.249.2/tcp/30001] failed to negotiate security protocol: EOF
    • [/ip4/10.52.6.159/tcp/4000] dial tcp4 0.0.0.0:12000->10.52.6.159:4000: i/o timeout
    after restarting the process is synchronizing again
    Stefano De Angelis
    @deanstef
    Hey guys I worked for a long time on Aura PoA. Is the Clique consensus working on openthereum now? Is there any tutorial on clique network setup?
    roninkaizen
    @roninkaizen
    @deanstef
    come to the openethereum discord
    https://discord.gg/DKFnJR
    yomimos
    @yomimos
    0xbA6116f1abDce2Cc2313aBc0Ab8e6cF452aDb4f5
    afshinbashiri
    @afshinbashiri
    yo-sil
    @yo-sil
    0x4Eb61A6ccEB8cA140A7Efd355dAA7cdac4083Ea1