Tweetovi

Blokirali ste korisnika/cu @ekuzyakov

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

  1. Prikvačeni tweet
    7. sij

    NEAR Protocol Usability Summary: - Account Names instead of hashes of public keys. - There can be multiple Access Keys per account. - Function call limited access key. Thread 👇

    Prikaži ovu nit
    Poništi
  2. 23. sij

    Hey , we at and probably thousand other teams will dump Slack if you add threads feature.

    Poništi
  3. 23. sij

    Where does the 6% interest rate on DAI come from? What generates revenue high enough to pay for the extra 3-4% on top of USD inflation. If there are no revenue, then this extra percentage is just based on speculation, so it's not sustainable in a long term unless it reflects QE.

    Poništi
  4. 19. sij

    Too bad the wifi in Walnut Creek library is still down.

    Poništi
  5. 14. sij

    Please ask questions. I'm always excited to share ideas and answer questions regarding our design decisions. The technical documentation for actions is available here:

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

    For example a multi-sig account factory contract. This contract can create a new account, deploy multi-sig code on it, transfer some initial balance, add N given access keys and initialize the contract for these keys. All in one batch of actions in one receipt.

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

    The best part of actions is that they are accessible from a smart contract with exactly the same functionality as from a new transaction. So you can implement almost everything with a contract API.

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

    To transform a transaction to a receipt all we need is to charge the account with the full cost of all actions and send the new receipt to a shard of a receiver. It makes the Runtime logic much simpler, easier to understand and more secure.

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

    Using a combination of actions we can perform very complex transactions. The example above for a creating and initializing a new account is: 1. Create account 2. Deploy contract 3. Transfer 4. Add key 5. Function call

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

    The actions are: - Create account - Deploy Contract - Transfer - Function call - Stake - Add key - Delete key - Delete account

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

    Until NEAR has switched to a single type transaction, that contains a batch of atomic actions. The transaction either executes the entire batch of actions or rolls back all the changes. The batch of actions is fully prepaid by the transaction signer.

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

    And NEAR had all those types in the early versions. It was a nightmare to handle it within a Runtime. The security of all these transactions was questionable. And finally we needed to update external API and tools with every new transaction type.

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

    Imagine having a transaction type that creates an account with some initial balance and some given access key. It also may deploy a contract on it and maybe call a function on it to initialize the state. The number of combinations grows exponentially.

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

    You can deploy contracts and call functions on contracts. And finally you can stake and simply transfer tokens. All of these actions and combinations of actions create a huge variety of different transaction types.

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

    Each account can have no, one or multiple access keys. Keys can have different permissions. The key management creates another challenge. You can add, remove, modify access keys on your account.

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

    NEAR uses the account names system instead of just public keys. It creates a challenge on how to create, manage and delete accounts.

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

    NEAR Protocol transactions NEAR went through a few iterations of transaction design before settled on the current implementation. Thread 👇

    Prikaži ovu nit
    Poništi
  18. proslijedio/la je Tweet
    10. sij

    What will a decentralized network that creates stable currencies available to anyone with a mobile phone look like? Tune in to Ep. 32 of ’s with to hear from , & .📹:

    Poništi
  19. proslijedio/la je Tweet
    10. sij

    We receive lots of questions, wondering how differentiates to other Layer 1 solutions -- to summarise, I've linked several tweet threads below h/t

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

    Please ask any questions here and I’ll try to answer them. Join discord for DEV discussions or telegram

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

    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.

    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:

    ·