Tweetovi

Blokirali ste korisnika/cu @TimBeiko

Jeste li sigurni da želite vidjeti te tweetove? Time nećete deblokirati korisnika/cu @TimBeiko

  1. Prikvačeni tweet
    5. pro 2019.

    If you're using Hyperledger Besu, you can upgrade to v1.3.6 to support both Istanbul & Muir Glacier 🏔

    Poništi
  2. proslijedio/la je Tweet
    prije 1 sat

    Any reports of ETH's, ConsenSys's, or 's demise would be greatly exaggerated. Why the layoffs are short-term bad, long-term good for the company and ETH ecosystem in this morning's newsletter.

    Poništi
  3. proslijedio/la je Tweet
    prije 21 sat

    I know a few great people looking for work at the moment. If you’re looking for people to get the best out of dev teams either from an engineering manager/agile coach perspective or product owner/business analyst, DM me and I’ll put you in touch.

    Poništi
  4. 4. velj
    Poništi
  5. 4. velj

    Quick funding update by 📝 TL;DR: due to the CLR match and generosity from , the foundation & Atlantic Crypto, we were able to fully refund contributions from individuals to the audit 😁

    Poništi
  6. proslijedio/la je Tweet
    3. velj

    Happening tomorrow - Join and for our Plugin APIs Webinar! There's still time to register for the technical session which will include a demo, best practices + a Q&A ✍️ Sign up below!

    Poništi
  7. 1. velj

    I think this is the clearest articulation of ETH’s path for success I’ve read so far 👏🏻👏🏻👏🏻 To make it more concrete, « multiple times » doesn’t refer just to dapps, IMO. It refers to stuff like too. Need to support that breadth, but stay minimal. Easy 🙃

    Poništi
  8. proslijedio/la je Tweet
    31. sij

    ’s 1.4 Beta 3 is out now: 🎊 3 big changes are in: our Plugin API is now stable, we’ve added TLS support for JSON RPC and we have some new (experimental!) tracing APIs ⚡️ More details below ⬇️

    Prikaži ovu nit
    Poništi
  9. proslijedio/la je Tweet
    30. sij

    Ethereum core dev & Product Manager , talks ETH 2.0, enterprise blockchains, hard forks, & more. Watch it all here:

    Poništi
  10. 28. sij
    Prikaži ovu nit
    Poništi
  11. 24. sij

    And that was it! See you all for another one of these in two weeks 👋🏻

    Prikaži ovu nit
    Poništi
  12. 24. sij

    We agreed to bring this up on the next call. Until then, we'll try and follow up with EIPs champions to get a feel for when they think their work could be ready, which will hopefully inform what EIPs could be bundled together in upgrades.

    Prikaži ovu nit
    Poništi
  13. 24. sij

    The final thing I brought up before we ended the call is that we now have a good amount of proposal for EIPs and upgrades, some of which have dependencies, and a lot of which are substantial, so we should probably start thinking about timelines & coordination for those.

    Prikaži ovu nit
    Poništi
  14. 24. sij

    - If the client developers have the best user feedback, shouldn't they just fix it? Are we just adding process for process' sake? No concrete decision or next steps on this, though.

    Prikaži ovu nit
    Poništi
  15. 24. sij

    2. Should OASIS/OpenRPC be doing this? People didn't seem to be fans of those initiative for a few reasons: - Swagger seems to be a standard already - If OpenRPC is ETH-only, does it make sense to call it a standard? ...

    Prikaži ovu nit
    Poništi
  16. 24. sij

    A few related issues came up: 1. Should we have conformance tests for JSON RPC? The consensus was "yes, but it's complicated to do" and there have been several attempts in the past, none of which are still commonly used today.

    Prikaži ovu nit
    Poništi
  17. 24. sij

    Pending blocks have a parent linked to them (which has a number, so can have number+1), and transactions can actually access their block's number during execution, so the block number is "there" but isn't exposed via the JSON RPC API. People seemed to agree we should expose it.

    Prikaži ovu nit
    Poništi
  18. 24. sij

    The final thing we discussed was an issue with the JSON RPC spec that brought up. When you retrieve a pending block via JSON RPC, it's hash, number and miner are currently NULL. While that's fine for hash and miner, Peter argued those blocks should have a number

    Prikaži ovu nit
    Poništi
  19. 24. sij

    3. There is a telegram group set up to discuss this. If you'd like to join, you can either ping on gitter () or email at hudson@ethereum.org

    Prikaži ovu nit
    Poništi
  20. 24. sij

    2. There was a first meeting held. Over 1/2 of attendees had previously tried to get an EIP implemented. They went over concerns about the process and potential improvements. ...

    Prikaži ovu nit
    Poništi
  21. 24. sij

    That was it for EIPs. Quite the list 😅! Next up was the EIPIP: EIP Improvement Process. shared a couple updates: 1. There is now a dedicated repo for the initiative, listing the next call (Jan 29th, 15:00UTC): ...

    Prikaži ovu nit
    Poništi

Čini se da učitavanje traje već neko vrijeme.

Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.

    Možda bi vam se svidjelo i ovo:

    ·