Preskoči na sadržaj
Korištenjem servisa na Twitteru pristajete na korištenje kolačića. Twitter i partneri rade globalno te koriste kolačiće za analize, personalizaciju i oglase.

Za najbolje sučelje na Twitteru koristite Microsoft Edge ili instalirajte aplikaciju Twitter iz trgovine Microsoft Store.

  • Naslovnica Naslovnica Naslovnica, trenutna stranica.
  • O Twitteru

Spremljena pretraživanja

  • obriši
  • U ovom razgovoru
    Ovjeren akauntZaštićeni tweetovi @
Predloženi korisnici
  • Ovjeren akauntZaštićeni tweetovi @
  • Ovjeren akauntZaštićeni tweetovi @
  • Jezik: Hrvatski
    • Bahasa Indonesia
    • Bahasa Melayu
    • Català
    • Čeština
    • Dansk
    • Deutsch
    • English
    • English UK
    • Español
    • Filipino
    • Français
    • Italiano
    • Magyar
    • Nederlands
    • Norsk
    • Polski
    • Português
    • Română
    • Slovenčina
    • Suomi
    • Svenska
    • Tiếng Việt
    • Türkçe
    • Български език
    • Русский
    • Српски
    • Українська мова
    • Ελληνικά
    • עִבְרִית
    • العربية
    • فارسی
    • मराठी
    • हिन्दी
    • বাংলা
    • ગુજરાતી
    • தமிழ்
    • ಕನ್ನಡ
    • ภาษาไทย
    • 한국어
    • 日本語
    • 简体中文
    • 繁體中文
  • Imate račun? Prijava
    Imate račun?
    · Zaboravili ste lozinku?

    Novi ste na Twitteru?
    Registrirajte se
Profil korisnika/ce ekuzyakov
Evgeny Kuzyakov
Evgeny Kuzyakov
Evgeny Kuzyakov
@ekuzyakov

Tweets

Evgeny Kuzyakov

@ekuzyakov

Runtime, usability and composability at @NearProtocol #wasm #rustlang Ex-@google, ex-@facebook

kuzyakov.com
Vrijeme pridruživanja: kolovoz 2013.

Tweets

  • © 2020 Twitter
  • O Twitteru
  • Centar za pomoć
  • Uvjeti
  • Pravila o privatnosti
  • Imprint
  • Kolačići
  • Informacije o oglasima
Odbaci
Prethodni
Sljedeće

Idite na profil osobe

Spremljena pretraživanja

  • obriši
  • U ovom razgovoru
    Ovjeren akauntZaštićeni tweetovi @
Predloženi korisnici
  • Ovjeren akauntZaštićeni tweetovi @
  • Ovjeren akauntZaštićeni tweetovi @

Odjava

Blokiraj

  • Objavi Tweet s lokacijom

    U tweetove putem weba ili aplikacija drugih proizvođača možete dodati podatke o lokaciji, kao što su grad ili točna lokacija. Povijest lokacija tweetova uvijek možete izbrisati. Saznajte više

    Vaši popisi

    Izradi novi popis


    Manje od 100 znakova, neobavezno

    Privatnost

    Kopiraj vezu u tweet

    Ugradi ovaj Tweet

    Embed this Video

    Dodajte ovaj Tweet na svoje web-mjesto kopiranjem koda u nastavku. Saznajte više

    Dodajte ovaj videozapis na svoje web-mjesto kopiranjem koda u nastavku. Saznajte više

    Hm, došlo je do problema prilikom povezivanja s poslužiteljem.

    Integracijom Twitterova sadržaja u svoje web-mjesto ili aplikaciju prihvaćate Twitterov Ugovor za programere i Pravila za programere.

    Pregled

    Razlog prikaza oglasa

    Prijavi se na Twitter

    · Zaboravili ste lozinku?
    Nemate račun? Registrirajte se »

    Prijavite se na Twitter

    Niste na Twitteru? Registrirajte se, uključite se u stvari koje vas zanimaju, i dobivajte promjene čim se dogode.

    Registrirajte se
    Imate račun? Prijava »

    Dvosmjerni (slanje i primanje) kratki kodovi:

    Država Kod Samo za korisnike
    Sjedinjene Američke Države 40404 (bilo koje)
    Kanada 21212 (bilo koje)
    Ujedinjeno Kraljevstvo 86444 Vodafone, Orange, 3, O2
    Brazil 40404 Nextel, TIM
    Haiti 40404 Digicel, Voila
    Irska 51210 Vodafone, O2
    Indija 53000 Bharti Airtel, Videocon, Reliance
    Indonezija 89887 AXIS, 3, Telkomsel, Indosat, XL Axiata
    Italija 4880804 Wind
    3424486444 Vodafone
    » Pogledajte SMS kratke šifre za druge zemlje

    Potvrda

     

    Dobro došli kući!

    Vremenska crta mjesto je na kojem ćete provesti najviše vremena i bez odgode dobivati novosti o svemu što vam je važno.

    Tweetovi vam ne valjaju?

    Prijeđite pokazivačem preko slike profila pa kliknite gumb Pratim da biste prestali pratiti neki račun.

    Kažite mnogo uz malo riječi

    Kada vidite Tweet koji volite, dodirnite srce – to osobi koja ga je napisala daje do znanja da vam se sviđa.

    Proširite glas

    Najbolji je način da podijelite nečiji Tweet s osobama koje vas prate prosljeđivanje. Dodirnite ikonu da biste smjesta poslali.

    Pridruži se razgovoru

    Pomoću odgovora dodajte sve što mislite o nekom tweetu. Pronađite temu koja vam je važna i uključite se.

    Saznajte najnovije vijesti

    Bez odgode pogledajte o čemu ljudi razgovaraju.

    Pratite više onoga što vam se sviđa

    Pratite više računa da biste dobivali novosti o temama do kojih vam je stalo.

    Saznajte što se događa

    Bez odgode pogledajte najnovije razgovore o bilo kojoj temi.

    Ne propustite nijedan aktualni događaj

    Bez odgode pratite kako se razvijaju događaji koje pratite.

    Evgeny Kuzyakov‏ @ekuzyakov 9. sij
    • Prijavi Tweet

    Sharded cross-contract composability at NEAR protocol. Before I can explain it, I need to give a lot of background on sharding design at NEAR. Thread 👇pic.twitter.com/13ZuzriSH5

    14:00 - 9. sij 2020.
    • 27 proslijeđenih tweetova
    • 72 oznake „sviđa mi se”
    • xrp_manifesto7247 GOPALगोपल जी सिंह JI SINGH Mayato 🇮🇩インドネシアのテック&スタートアップ情報発信 Bari Abbassi Thilagavathy S Kentucky Bitcoin 小林さん Maddie Ohio Bitcoin
    27 proslijeđenih tweetova 72 korisnika označavaju da im se sviđa
      1. Novi razgovor
      2. Evgeny Kuzyakov‏ @ekuzyakov 9. sij
        • Prijavi Tweet

        NEAR is a sharded blockchain. Both state and compute are sharded. It allows to achieve almost linear TPS scaling with the increase in the number of shards. The state can be rebalanced to a new number of shards on demand.

        1 reply 0 proslijeđenih tweetova 6 korisnika označava da im se sviđa
        Prikaži ovu nit
      3. Evgeny Kuzyakov‏ @ekuzyakov 9. sij
        • Prijavi Tweet

        A single shard TPS is bounded by sequential operations to access the same data in the state. That's why Ethereum 1.0 TPS is low, it has to execute every transaction consequently to be able to reuse previous modifications of the state.

        1 reply 0 proslijeđenih tweetova 7 korisnika označava da im se sviđa
        Prikaži ovu nit
      4. Evgeny Kuzyakov‏ @ekuzyakov 9. sij
        • Prijavi Tweet

        It’s also why Ethereum has such a great cross-contract composability. Any contract can call any other contract and then commit or revert all state changes made during this transaction. Every transaction is either entirely succeeds or fails.

        1 reply 0 proslijeđenih tweetova 8 korisnika označava da im se sviđa
        Prikaži ovu nit
      5. Evgeny Kuzyakov‏ @ekuzyakov 9. sij
        • Prijavi Tweet

        It has benefits and limitations. The benefits are the magical DeFi composability where a contract can borrow tokens, exchange on Uniswap, lend it back all in one transaction. Your only risk are the transaction fees that you may lose if the TX fails and changes are reverted.

        1 reply 0 proslijeđenih tweetova 7 korisnika označava da im se sviđa
        Prikaži ovu nit
      6. Evgeny Kuzyakov‏ @ekuzyakov 9. sij
        • Prijavi Tweet

        This is is guaranteed by having single-threaded atomic access to the entire state. Essentially, a VM locks the state at the beginning of a transaction, executes everything and unlocks the state only at the end.

        1 reply 0 proslijeđenih tweetova 6 korisnika označava da im se sviđa
        Prikaži ovu nit
      7. Evgeny Kuzyakov‏ @ekuzyakov 9. sij
        • Prijavi Tweet

        In a sharded system like NEAR (or Eth 2.0), the full state is not available at any given moment, because the compute is running in parallel asynchronously. The state in one shard can be modified at the same time as the state in another shard. Shard states are independent.

        1 reply 0 proslijeđenih tweetova 6 korisnika označava da im se sviđa
        Prikaži ovu nit
      8. Evgeny Kuzyakov‏ @ekuzyakov 9. sij
        • Prijavi Tweet

        To better understand state sharding, think about an example with 2 shards. If the hash of an account ID ends with 0, it goes to shard #0, if the hash ends with 1, it goes to shard #1. Now every transaction that has to be processed by the corresponding shard based on account ID.

        1 reply 0 proslijeđenih tweetova 3 korisnika označavaju da im se sviđa
        Prikaži ovu nit
      9. Evgeny Kuzyakov‏ @ekuzyakov 9. sij
        • Prijavi Tweet

        At NEAR once a transaction is verified and the signer’s account is charged with the full prepaid cost of the transaction, the transaction is transformed to a `Receipt`. To simplify, NEAR Runtime executes a list of receipts, modifies the state and produces a list of new receipts.

        1 reply 0 proslijeđenih tweetova 4 korisnika označavaju da im se sviđa
        Prikaži ovu nit
      10. Evgeny Kuzyakov‏ @ekuzyakov 9. sij
        • Prijavi Tweet

        Each receipt has a predecessor account ID and the receiver account ID. The predecessor is the account which created this receipt. The receiver is the account on which the receipt is executed upon. NEAR Blockchain layer uses receiver IDs to route the new receipts across shards.

        0 proslijeđenih tweetova 4 korisnika označavaju da im se sviđa
        Prikaži ovu nit
      11. Evgeny Kuzyakov‏ @ekuzyakov 9. sij
        • Prijavi Tweet

        While NEAR Runtime is completely unaware of sharding, it operates on accounts. Runtime treats each account independently. Even if 2 accounts are collocated on the same shard, they are treated as accounts on different shards. So account collocation doesn’t give any benefits.

        0 proslijeđenih tweetova 5 korisnika označava da im se sviđa
        Prikaži ovu nit
      12. Evgeny Kuzyakov‏ @ekuzyakov 9. sij
        • Prijavi Tweet

        Now as we covered the basics of NEAR sharding, let’s jump to the composability!pic.twitter.com/aVcTDqv3r3

        1 reply 0 proslijeđenih tweetova 6 korisnika označava da im se sviđa
        Prikaži ovu nit
      13. Evgeny Kuzyakov‏ @ekuzyakov 9. sij
        • Prijavi Tweet

        If a contract A wants to call another contract B, it creates an async promise P1. Then if contract A wants to act on top of the result of P1, contract A can attach a callback to P1 to call a method on A. It will create a promise P2. Internally in Runtime P1 and P2 are receipts.pic.twitter.com/nvneCP2q2t

        1 reply 0 proslijeđenih tweetova 5 korisnika označava da im se sviđa
        Prikaži ovu nit
      14. Evgeny Kuzyakov‏ @ekuzyakov 9. sij
        • Prijavi Tweet

        Each contract can also call other contracts and instead of returning the result immediately, it can depend on some other callbacks. E.g. if in the above example B was depending on the call to C, the callback to A will only be called after callback back to B is completed.pic.twitter.com/j7h6FhglDc

        1 reply 0 proslijeđenih tweetova 3 korisnika označavaju da im se sviđa
        Prikaži ovu nit
      15. Evgeny Kuzyakov‏ @ekuzyakov 9. sij
        • Prijavi Tweet

        If you are familiar with JS promise API, then NEAR promise API is going to be similar. API allows contracts to create multiple async promises, join them together and to create callbacks to other contracts. E.g. A calls B and C, then calls D on the joint result of B, C execution.pic.twitter.com/04EaSCuVZL

        1 reply 0 proslijeđenih tweetova 5 korisnika označava da im se sviđa
        Prikaži ovu nit
      16. Evgeny Kuzyakov‏ @ekuzyakov 9. sij
        • Prijavi Tweet

        When B executes some call, it knows the predecessor A (the immediate caller), so it knows the context. The contract can use it to check access permission for a certain action. E.g. check that a Dex contract has an allowance for a token transfer from Alice.

        1 reply 0 proslijeđenih tweetova 3 korisnika označavaju da im se sviđa
        Prikaži ovu nit
      17. Evgeny Kuzyakov‏ @ekuzyakov 9. sij
        • Prijavi Tweet

        Let’s look at the concrete example where a Dex contract wants to swap X wDAI tokens from Alice to Y wETH tokens from Bob. Dex doesn’t want to own the tokens even temporarily, but instead it has an allowance to spend them from Alice and Bob.pic.twitter.com/1GMbMEs3Xs

        1 reply 0 proslijeđenih tweetova 4 korisnika označavaju da im se sviđa
        Prikaži ovu nit
      18. Evgeny Kuzyakov‏ @ekuzyakov 9. sij
        • Prijavi Tweet

        If a Dex doesn’t own tokens (but just has an allowance) it has to lock the tokens first to make sure they are still available on corresponding accounts, because the token states are located on different shards.

        1 reply 0 proslijeđenih tweetova 4 korisnika označavaju da im se sviđa
        Prikaži ovu nit
      19. Evgeny Kuzyakov‏ @ekuzyakov 9. sij
        • Prijavi Tweet

        Dex calls wDAI to lock X tokens from Alice, and in parallel calls wETH to lock Y tokens from Bob. The results of the calls are acquired locks.

        1 reply 0 proslijeđenih tweetova 3 korisnika označavaju da im se sviđa
        Prikaži ovu nit
      20. Evgeny Kuzyakov‏ @ekuzyakov 9. sij
        • Prijavi Tweet

        Once Dex has successfully acquired both locks, Dex calls wDAI and wETH to transfer tokens between Alice and Bob. If one of the locks failed, then Dex needs to unlock the other successfully acquired lock.pic.twitter.com/68AYGxx8kI

        1 reply 0 proslijeđenih tweetova 6 korisnika označava da im se sviđa
        Prikaži ovu nit
      21. Evgeny Kuzyakov‏ @ekuzyakov 9. sij
        • Prijavi Tweet

        If for some reason the Dex contract after acquiring locks, the tokens might be stuck in a locked state. To avoid this issue we propose a WIP concept of a `Safe`. It has a secure auto-unlocking mechanism to avoid situations with lost locks. More details:https://github.com/nearprotocol/NEPs/pull/26/files?short_path=0ccd6ae#diff-0ccd6ae29ca4dfdda66ca7c7f58cd75d …

        1 reply 0 proslijeđenih tweetova 5 korisnika označava da im se sviđa
        Prikaži ovu nit
      22. Evgeny Kuzyakov‏ @ekuzyakov 9. sij
        • Prijavi Tweet

        It may all sound complicated right now, but hopefully a lot of this is going to be addressed through examples and high-level APIs. Right now, NEAR provides Rust API and AssemblyScript API to write smart contracts which are complied to WebAssembly that can be deployed.

        0 proslijeđenih tweetova 6 korisnika označava da im se sviđa
        Prikaži ovu nit
      23. Evgeny Kuzyakov‏ @ekuzyakov 9. sij
        • Prijavi Tweet

        Please ask any questions here and I’ll try to answer them. Join discord https://near.chat  for DEV discussions or telegramhttps://t.me/cryptonear 

        2 proslijeđena tweeta 11 korisnika označava da im se sviđa
        Prikaži ovu nit
      24. Kraj razgovora
    1. Prikaži još odgovora, uključujući one koji mogu sadržavati uvredljiv sadržaj

    Č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.

      Sponzorirani tweet

      false

      • © 2020 Twitter
      • O Twitteru
      • Centar za pomoć
      • Uvjeti
      • Pravila o privatnosti
      • Imprint
      • Kolačići
      • Informacije o oglasima